In general support of 2017-5 draft as written. rd On Aug 15, 2017 2:10 PM, <[email protected]> wrote:
> Send ARIN-PPML mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.arin.net/mailman/listinfo/arin-ppml > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ARIN-PPML digest..." > > > Today's Topics: > > 1. NRPM 2017.4: New Policies Implemented (ARIN) > 2. Weekly posting summary for [email protected] ([email protected]) > 3. Revised: Draft Policy ARIN-2017-5: Equalization of Assignment > Registration requirements between IPv4 and IPv6 (ARIN) > 4. Re: Revised: Draft Policy ARIN-2017-5: Equalization of > Assignment Registration requirements between IPv4 and IPv6 > (David Huberman) > 5. Re: Revised: Draft Policy ARIN-2017-5: Equalization of > Assignment Registration requirements between IPv4 and IPv6 > (Chris Woodfield) > 6. Re: Revised: Draft Policy ARIN-2017-5: Equalization of > Assignment Registration requirements between IPv4 and IPv6 > (Austin Murkland) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 8 Aug 2017 11:08:52 -0400 > From: ARIN <[email protected]> > To: [email protected] > Subject: [arin-ppml] NRPM 2017.4: New Policies Implemented > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 22 June 2017, the Board of Trustees adopted the following Recommended > Draft Policies: > > Recommended Draft Policy ARIN-2016-3: Alternative simplified criteria > for justifying small IPv4 transfers > > Recommended Draft Policy ARIN-2016-9: Streamline Merger & Acquisition > Transfers > > These policies are now in effect. A new version of the ARIN Number > Resource Policy Manual (NRPM) has been published to the ARIN website. > > NRPM version 2017.4 is effective 8 August 2017 and supersedes the > previous version. > > The NRPM is available at: > > https://www.arin.net/policy/nrpm.html > > Board minutes are available at: > > https://www.arin.net/about_us/bot/index.html > > Draft policies and proposals are available at: > > https://www.arin.net/policy/proposals/ > > The ARIN Policy Development Process (PDP) is available at: > > https://www.arin.net/policy/pdp.html > > Regards, > > Sean Hopkins > Policy Analyst > American Registry for Internet Numbers (ARIN) > > > ------------------------------ > > Message: 2 > Date: Fri, 11 Aug 2017 00:53:23 -0400 > From: [email protected] > To: [email protected] > Subject: [arin-ppml] Weekly posting summary for [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Total of 2 messages in the last 7 days. > > script run at: Fri Aug 11 00:53:18 EDT 2017 > > Messages | Bytes | Who > --------+------+--------+----------+------------------------ > 50.00% | 1 | 57.15% | 8155 | [email protected] > 50.00% | 1 | 42.85% | 6114 | [email protected] > --------+------+--------+----------+------------------------ > 100.00% | 2 |100.00% | 14269 | Total > > > > ------------------------------ > > Message: 3 > Date: Tue, 15 Aug 2017 13:06:58 -0400 > From: ARIN <[email protected]> > To: [email protected] > Subject: [arin-ppml] Revised: Draft Policy ARIN-2017-5: Equalization > of Assignment Registration requirements between IPv4 and IPv6 > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > The following has been revised: > > * Draft Policy ARIN-2017-5: Equalization of Assignment Registration > requirements between IPv4 and IPv6 > > Revised text is below and can be found at: > https://www.arin.net/policy/proposals/2017_5.html > > You are encouraged to discuss all Draft Policies on PPML. The AC will > evaluate the discussion in order to assess the conformance of this draft > policy with ARIN's Principles of Internet number resource policy as > stated in the Policy Development Process (PDP). Specifically, these > principles are: > > * Enabling Fair and Impartial Number Resource Administration > * Technically Sound > * Supported by the Community > > The PDP can be found at: > https://www.arin.net/policy/pdp.html > > Draft Policies and Proposals under discussion can be found at: > https://www.arin.net/policy/proposals/index.html > > Regards, > > Sean Hopkins > Policy Analyst > American Registry for Internet Numbers (ARIN) > > > > > Problem Statement: > > Current ARIN policy has different WHOIS directory registration > requirements for IPv4 vs IPv6 address assignments. IPv4 registration is > triggered for an assignment of any address block equal to or greater > than a /29 (i.e., eight IPv4 addresses). In the case of IPv6, > registration occurs for an assignment of any block equal to or greater > than a /64, which constitutes one entire IPv6 subnet and is the minimum > block size for an allocation. Accordingly, there is a significant > disparity between IPv4 and IPv6 WHOIS registration thresholds in the > case of assignments, resulting in more work in the case of IPv6 than is > the case for IPv4. There is no technical or policy rationale for the > disparity, which could serve as a deterrent to more rapid IPv6 adoption. > The purpose of this proposal is to eliminate the disparity and > corresponding adverse consequences. > > Policy statement: > > 1) Alter section 6.5.5.1 "Reassignment information" of the NRPM to > strike "/64 or more addresses" and change to "/47 or more addresses, or > subdelegation of any size that will be individually announced," > > and > > 2) Alter section 6.5.5.3.1. "Residential Customer Privacy" of the NRPM > by deleting the phrase "holding /64 and larger blocks" > > and > > 3) Add new section 6.5.5.4 "Downstream Registration Requests" to the > NRPM that reads "If the downstream recipient of a netblock ( a /64 or > more addresses) requests publishing in ARIN's registration database, the > ISP must register the netblock, regardless of size." > > Comments: > > a. Timetable for implementation: Policy should be adopted as soon as > possible. > > b. Anything else: > > Author Comments: > > IPv6 should not be more burdensome than the equivalent IPv4 network > size. Currently, assignments of /29 or more of IPv4 space (8 addresses) > require registration. The greatest majority of ISP customers who have > assignments of IPv4 space are of a single IPv4 address which do not > trigger any ARIN registration requirement when using IPv4. This is NOT > true when these same exact customers use IPv6, as assignments of /64 or > more of IPv6 space require registration. Beginning with RFC 3177, it has > been standard practice to assign a minimum assignment of /64 to every > customer end user site, and less is never used. This means that ALL > IPv6 assignments, including those customers that only use a single IPv4 > address must be registered with ARIN if they are given the minimum > assignment of /64 of IPv6 space. This additional effort may prevent > ISP's from giving IPv6 addresses because of the additional expense of > registering those addresses with ARIN, which is not required for IPv4. > The administrative burden of 100% customer registration of IPv6 > customers is unreasonable, when such is not required for those customers > receiving only IPv4 connections. > > > ------------------------------ > > Message: 4 > Date: Tue, 15 Aug 2017 14:03:55 -0400 > From: David Huberman <[email protected]> > To: [email protected] > Subject: Re: [arin-ppml] Revised: Draft Policy ARIN-2017-5: > Equalization of Assignment Registration requirements between IPv4 > and > IPv6 > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Very well done, everyone! Strongly support this draft. > > Kudos to Albert Erdmann and the AC shepherds for their leadership on this > proposal. > > > > On Aug 15, 2017, at 1:06 PM, ARIN <[email protected]> wrote: > > > > The following has been revised: > > > > * Draft Policy ARIN-2017-5: Equalization of Assignment Registration > requirements between IPv4 and IPv6 > > > > Revised text is below and can be found at: > > https://www.arin.net/policy/proposals/2017_5.html > > > > You are encouraged to discuss all Draft Policies on PPML. The AC will > evaluate the discussion in order to assess the conformance of this draft > policy with ARIN's Principles of Internet number resource policy as stated > in the Policy Development Process (PDP). Specifically, these principles are: > > > > * Enabling Fair and Impartial Number Resource Administration > > * Technically Sound > > * Supported by the Community > > > > The PDP can be found at: > > https://www.arin.net/policy/pdp.html > > > > Draft Policies and Proposals under discussion can be found at: > > https://www.arin.net/policy/proposals/index.html > > > > Regards, > > > > Sean Hopkins > > Policy Analyst > > American Registry for Internet Numbers (ARIN) > > > > > > > > > > Problem Statement: > > > > Current ARIN policy has different WHOIS directory registration > requirements for IPv4 vs IPv6 address assignments. IPv4 registration is > triggered for an assignment of any address block equal to or greater than a > /29 (i.e., eight IPv4 addresses). In the case of IPv6, registration occurs > for an assignment of any block equal to or greater than a /64, which > constitutes one entire IPv6 subnet and is the minimum block size for an > allocation. Accordingly, there is a significant disparity between IPv4 and > IPv6 WHOIS registration thresholds in the case of assignments, resulting in > more work in the case of IPv6 than is the case for IPv4. There is no > technical or policy rationale for the disparity, which could serve as a > deterrent to more rapid IPv6 adoption. The purpose of this proposal is to > eliminate the disparity and corresponding adverse consequences. > > > > Policy statement: > > > > 1) Alter section 6.5.5.1 "Reassignment information" of the NRPM to > strike "/64 or more addresses" and change to "/47 or more addresses, or > subdelegation of any size that will be individually announced," > > > > and > > > > 2) Alter section 6.5.5.3.1. "Residential Customer Privacy" of the NRPM > by deleting the phrase "holding /64 and larger blocks" > > > > and > > > > 3) Add new section 6.5.5.4 "Downstream Registration Requests" to the > NRPM that reads "If the downstream recipient of a netblock ( a /64 or more > addresses) requests publishing in ARIN's registration database, the ISP > must register the netblock, regardless of size." > > > > Comments: > > > > a. Timetable for implementation: Policy should be adopted as soon as > possible. > > > > b. Anything else: > > > > Author Comments: > > > > IPv6 should not be more burdensome than the equivalent IPv4 network > size. Currently, assignments of /29 or more of IPv4 space (8 addresses) > require registration. The greatest majority of ISP customers who have > assignments of IPv4 space are of a single IPv4 address which do not trigger > any ARIN registration requirement when using IPv4. This is NOT true when > these same exact customers use IPv6, as assignments of /64 or more of IPv6 > space require registration. Beginning with RFC 3177, it has been standard > practice to assign a minimum assignment of /64 to every customer end user > site, and less is never used. This means that ALL IPv6 assignments, > including those customers that only use a single IPv4 address must be > registered with ARIN if they are given the minimum assignment of /64 of > IPv6 space. This additional effort may prevent ISP's from giving IPv6 > addresses because of the additional expense of registering those addresses > with ARIN, which is not required for IPv4. The adm > inistrative burden of 100% customer registration of IPv6 customers is > unreasonable, when such is not required for those customers receiving only > IPv4 connections. > > _______________________________________________ > > PPML > > You are receiving this message because you are subscribed to > > the ARIN Public Policy Mailing List ([email protected]). > > Unsubscribe or manage your mailing list subscription at: > > http://lists.arin.net/mailman/listinfo/arin-ppml > > Please contact [email protected] if you experience any issues. > > > > > > ------------------------------ > > Message: 5 > Date: Tue, 15 Aug 2017 11:08:10 -0700 > From: Chris Woodfield <[email protected]> > To: David Huberman <[email protected]>, [email protected] > Subject: Re: [arin-ppml] Revised: Draft Policy ARIN-2017-5: > Equalization of Assignment Registration requirements between IPv4 > and > IPv6 > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Agreed. While there are a wide range of opinions on where this line > belongs, The /47 line appears to have the most consensus, and has my > support. > > -Chris > > > On Aug 15, 2017, at 11:03 AM, David Huberman <[email protected]> wrote: > > > > Very well done, everyone! Strongly support this draft. > > > > Kudos to Albert Erdmann and the AC shepherds for their leadership on > this proposal. > > > > > >> On Aug 15, 2017, at 1:06 PM, ARIN <[email protected]> wrote: > >> > >> The following has been revised: > >> > >> * Draft Policy ARIN-2017-5: Equalization of Assignment Registration > requirements between IPv4 and IPv6 > >> > >> Revised text is below and can be found at: > >> https://www.arin.net/policy/proposals/2017_5.html > >> > >> You are encouraged to discuss all Draft Policies on PPML. The AC will > evaluate the discussion in order to assess the conformance of this draft > policy with ARIN's Principles of Internet number resource policy as stated > in the Policy Development Process (PDP). Specifically, these principles are: > >> > >> * Enabling Fair and Impartial Number Resource Administration > >> * Technically Sound > >> * Supported by the Community > >> > >> The PDP can be found at: > >> https://www.arin.net/policy/pdp.html > >> > >> Draft Policies and Proposals under discussion can be found at: > >> https://www.arin.net/policy/proposals/index.html > >> > >> Regards, > >> > >> Sean Hopkins > >> Policy Analyst > >> American Registry for Internet Numbers (ARIN) > >> > >> > >> > >> > >> Problem Statement: > >> > >> Current ARIN policy has different WHOIS directory registration > requirements for IPv4 vs IPv6 address assignments. IPv4 registration is > triggered for an assignment of any address block equal to or greater than a > /29 (i.e., eight IPv4 addresses). In the case of IPv6, registration occurs > for an assignment of any block equal to or greater than a /64, which > constitutes one entire IPv6 subnet and is the minimum block size for an > allocation. Accordingly, there is a significant disparity between IPv4 and > IPv6 WHOIS registration thresholds in the case of assignments, resulting in > more work in the case of IPv6 than is the case for IPv4. There is no > technical or policy rationale for the disparity, which could serve as a > deterrent to more rapid IPv6 adoption. The purpose of this proposal is to > eliminate the disparity and corresponding adverse consequences. > >> > >> Policy statement: > >> > >> 1) Alter section 6.5.5.1 "Reassignment information" of the NRPM to > strike "/64 or more addresses" and change to "/47 or more addresses, or > subdelegation of any size that will be individually announced," > >> > >> and > >> > >> 2) Alter section 6.5.5.3.1. "Residential Customer Privacy" of the NRPM > by deleting the phrase "holding /64 and larger blocks" > >> > >> and > >> > >> 3) Add new section 6.5.5.4 "Downstream Registration Requests" to the > NRPM that reads "If the downstream recipient of a netblock ( a /64 or more > addresses) requests publishing in ARIN's registration database, the ISP > must register the netblock, regardless of size." > >> > >> Comments: > >> > >> a. Timetable for implementation: Policy should be adopted as soon as > possible. > >> > >> b. Anything else: > >> > >> Author Comments: > >> > >> IPv6 should not be more burdensome than the equivalent IPv4 network > size. Currently, assignments of /29 or more of IPv4 space (8 addresses) > require registration. The greatest majority of ISP customers who have > assignments of IPv4 space are of a single IPv4 address which do not trigger > any ARIN registration requirement when using IPv4. This is NOT true when > these same exact customers use IPv6, as assignments of /64 or more of IPv6 > space require registration. Beginning with RFC 3177, it has been standard > practice to assign a minimum assignment of /64 to every customer end user > site, and less is never used. This means that ALL IPv6 assignments, > including those customers that only use a single IPv4 address must be > registered with ARIN if they are given the minimum assignment of /64 of > IPv6 space. This additional effort may prevent ISP's from giving IPv6 > addresses because of the additional expense of registering those addresses > with ARIN, which is not required for IPv4. The ad > m > > inistrative burden of 100% customer registration of IPv6 customers is > unreasonable, when such is not required for those customers receiving only > IPv4 connections. > >> _______________________________________________ > >> PPML > >> You are receiving this message because you are subscribed to > >> the ARIN Public Policy Mailing List ([email protected]). > >> Unsubscribe or manage your mailing list subscription at: > >> http://lists.arin.net/mailman/listinfo/arin-ppml > >> Please contact [email protected] if you experience any issues. > >> > > > > _______________________________________________ > > PPML > > You are receiving this message because you are subscribed to > > the ARIN Public Policy Mailing List ([email protected]). > > Unsubscribe or manage your mailing list subscription at: > > http://lists.arin.net/mailman/listinfo/arin-ppml > > Please contact [email protected] if you experience any issues. > > > > > > ------------------------------ > > Message: 6 > Date: Tue, 15 Aug 2017 14:09:18 -0400 > From: Austin Murkland <[email protected]> > To: Chris Woodfield <[email protected]> > Cc: David Huberman <[email protected]>, [email protected] > Subject: Re: [arin-ppml] Revised: Draft Policy ARIN-2017-5: > Equalization of Assignment Registration requirements between IPv4 > and > IPv6 > Message-ID: > <CAF2zaZUsvvnW0MceEFM9Y2hjLxKx1Mw3X9h9fhHP=DwweyqsiA@mail. > gmail.com> > Content-Type: text/plain; charset="utf-8" > > Concur with the above, Support the draft as written. > > On Tue, Aug 15, 2017 at 2:08 PM, Chris Woodfield <[email protected]> > wrote: > > > Agreed. While there are a wide range of opinions on where this line > > belongs, The /47 line appears to have the most consensus, and has my > > support. > > > > -Chris > > > > > On Aug 15, 2017, at 11:03 AM, David Huberman <[email protected]> wrote: > > > > > > Very well done, everyone! Strongly support this draft. > > > > > > Kudos to Albert Erdmann and the AC shepherds for their leadership on > > this proposal. > > > > > > > > >> On Aug 15, 2017, at 1:06 PM, ARIN <[email protected]> wrote: > > >> > > >> The following has been revised: > > >> > > >> * Draft Policy ARIN-2017-5: Equalization of Assignment Registration > > requirements between IPv4 and IPv6 > > >> > > >> Revised text is below and can be found at: > > >> https://www.arin.net/policy/proposals/2017_5.html > > >> > > >> You are encouraged to discuss all Draft Policies on PPML. The AC will > > evaluate the discussion in order to assess the conformance of this draft > > policy with ARIN's Principles of Internet number resource policy as > stated > > in the Policy Development Process (PDP). Specifically, these principles > are: > > >> > > >> * Enabling Fair and Impartial Number Resource Administration > > >> * Technically Sound > > >> * Supported by the Community > > >> > > >> The PDP can be found at: > > >> https://www.arin.net/policy/pdp.html > > >> > > >> Draft Policies and Proposals under discussion can be found at: > > >> https://www.arin.net/policy/proposals/index.html > > >> > > >> Regards, > > >> > > >> Sean Hopkins > > >> Policy Analyst > > >> American Registry for Internet Numbers (ARIN) > > >> > > >> > > >> > > >> > > >> Problem Statement: > > >> > > >> Current ARIN policy has different WHOIS directory registration > > requirements for IPv4 vs IPv6 address assignments. IPv4 registration is > > triggered for an assignment of any address block equal to or greater > than a > > /29 (i.e., eight IPv4 addresses). In the case of IPv6, registration > occurs > > for an assignment of any block equal to or greater than a /64, which > > constitutes one entire IPv6 subnet and is the minimum block size for an > > allocation. Accordingly, there is a significant disparity between IPv4 > and > > IPv6 WHOIS registration thresholds in the case of assignments, resulting > in > > more work in the case of IPv6 than is the case for IPv4. There is no > > technical or policy rationale for the disparity, which could serve as a > > deterrent to more rapid IPv6 adoption. The purpose of this proposal is to > > eliminate the disparity and corresponding adverse consequences. > > >> > > >> Policy statement: > > >> > > >> 1) Alter section 6.5.5.1 "Reassignment information" of the NRPM to > > strike "/64 or more addresses" and change to "/47 or more addresses, or > > subdelegation of any size that will be individually announced," > > >> > > >> and > > >> > > >> 2) Alter section 6.5.5.3.1. "Residential Customer Privacy" of the NRPM > > by deleting the phrase "holding /64 and larger blocks" > > >> > > >> and > > >> > > >> 3) Add new section 6.5.5.4 "Downstream Registration Requests" to the > > NRPM that reads "If the downstream recipient of a netblock ( a /64 or > more > > addresses) requests publishing in ARIN's registration database, the ISP > > must register the netblock, regardless of size." > > >> > > >> Comments: > > >> > > >> a. Timetable for implementation: Policy should be adopted as soon > as > > possible. > > >> > > >> b. Anything else: > > >> > > >> Author Comments: > > >> > > >> IPv6 should not be more burdensome than the equivalent IPv4 network > > size. Currently, assignments of /29 or more of IPv4 space (8 addresses) > > require registration. The greatest majority of ISP customers who have > > assignments of IPv4 space are of a single IPv4 address which do not > trigger > > any ARIN registration requirement when using IPv4. This is NOT true when > > these same exact customers use IPv6, as assignments of /64 or more of > IPv6 > > space require registration. Beginning with RFC 3177, it has been standard > > practice to assign a minimum assignment of /64 to every customer end user > > site, and less is never used. This means that ALL IPv6 assignments, > > including those customers that only use a single IPv4 address must be > > registered with ARIN if they are given the minimum assignment of /64 of > > IPv6 space. This additional effort may prevent ISP's from giving IPv6 > > addresses because of the additional expense of registering those > addresses > > with ARIN, which is not required for IPv4. The ad > > m > > > inistrative burden of 100% customer registration of IPv6 customers is > > unreasonable, when such is not required for those customers receiving > only > > IPv4 connections. > > >> _______________________________________________ > > >> PPML > > >> You are receiving this message because you are subscribed to > > >> the ARIN Public Policy Mailing List ([email protected]). > > >> Unsubscribe or manage your mailing list subscription at: > > >> http://lists.arin.net/mailman/listinfo/arin-ppml > > >> Please contact [email protected] if you experience any issues. > > >> > > > > > > _______________________________________________ > > > PPML > > > You are receiving this message because you are subscribed to > > > the ARIN Public Policy Mailing List ([email protected]). > > > Unsubscribe or manage your mailing list subscription at: > > > http://lists.arin.net/mailman/listinfo/arin-ppml > > > Please contact [email protected] if you experience any issues. > > > > > > > _______________________________________________ > > PPML > > You are receiving this message because you are subscribed to > > the ARIN Public Policy Mailing List ([email protected]). > > Unsubscribe or manage your mailing list subscription at: > > http://lists.arin.net/mailman/listinfo/arin-ppml > > Please contact [email protected] if you experience any issues. > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.arin.net/pipermail/arin-ppml/ > attachments/20170815/0b5af2a5/attachment.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > ARIN-PPML mailing list > [email protected] > http://lists.arin.net/mailman/listinfo/arin-ppml > > ------------------------------ > > End of ARIN-PPML Digest, Vol 146, Issue 2 > ***************************************** >
_______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
