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