<div dir="ltr">I oppose as written.<div><br></div><div>There should not be a different standard of requirement for:</div><div>- re-allocation</div><div>- reassignment containing a /47 or more addresses</div><div>- subdelegation of any size that will be individually announced</div><div><br></div><div>which is "shall"</div><div><br></div><div>and Registration Requested by Recipient</div><div><br></div><div>which is "should"</div><div><br></div><div><br></div><div>I would support if they are both "shall".</div><div><br></div><div><br></div><div>Can ARIN staff discuss what actions it will take if an ISP's</div><div>down stream customer contacts them and explains that their</div><div>ISP refuses to SWIP their reassignment to them?</div><div><br></div><div>Will they do anything more than reach out to the ISP and tell</div><div>them they "should" SWIP it?</div><div><br></div><div>How does this course of action differ if the customer intends to</div><div>route the space individually?</div><div><br></div><div>How does this course of action differ if the customer holds other</div><div>direct allocations, and or re-allocates for another provider?</div><div><br></div><div>How does this course of action differ if the customer has down<br></div><div>stream customers?</div><div><br></div><div>___Jason</div><div><br></div><div><br></div><div> </div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 26, 2017 at 3:03 PM, Jason Schiller <span dir="ltr"><<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>current policy:</div><div><br></div><div>6.5.5.1. Reassignment information</div><div>Each static IPv6 assignment containing a /64 or more addresses shall be registered in </div><div>the WHOIS directory via SWIP or a distributed service which meets the standards set forth in </div><div>section 3.2. Reassignment registrations shall include each client's organizational information, </div><div>except where specifically exempted by this policy.</div><div><br></div><div><div><span class=""><div>6.5.5.2. Assignments visible within 7 days</div></span><div>All assignments shall be made visible as required in section 4.2.3.7.1 within seven calendar </div><div>days of assignment.</div></div></div><div><br></div><div><div>6.5.5.3. Residential Subscribers</div><div> 6.5.5.3.1. Residential Customer Privacy</div><div> To maintain the privacy of their residential customers, an organization with downstream </div><div> residential customers holding /64 and larger blocks may substitute that organization's </div><div> name for the customer's name, e.g. 'Private Customer - XYZ Network', and the customer's </div><div> street address may read 'Private Residence'. Each private downstream residential </div><div> reassignment must have accurate upstream Abuse and Technical POCs visible on the </div><div> WHOIS record for that block.</div><div><br></div></div><div><br></div><div>New proposed policy:</div><div><br></div><div><div>6.5.5.1. Reassignment information</div><div>Each static IPv6 </div><div>+ re-allocation, reassignment containing a /47 or more addresses, or subdelegation of any <br></div><div>+ size that will be individually announced,</div><div><br></div><div>shall be registered in </div><div>the WHOIS directory via SWIP or a distributed service which meets the standards set forth in </div><div>section 3.2. Reassignment registrations shall include each client's organizational information, </div><div>except where specifically exempted by this policy.</div><span class=""><div><br></div><div>6.5.5.2. Assignments visible within 7 days</div></span><div>All assignments shall be made visible as required in section </div><div>+ 6.5.5.1 </div><div>within seven calendar </div><div>days of assignment.</div><div><br></div><div>6.5.5.3. Residential Subscribers</div><div> 6.5.5.3.1. Residential Customer Privacy</div><div> To maintain the privacy of their residential customers, an organization with downstream </div><div> residential customers </div><div> may substitute that organization's </div><div> name for the customer's name, e.g. 'Private Customer - XYZ Network', and the customer's </div><div> street address may read 'Private Residence'. Each private downstream residential </div><div> reassignment must have accurate upstream Abuse and Technical POCs visible on the </div><div> WHOIS record for that block.</div><div><br></div></div><span class=""><div>6.5.5.4 Registration Requested by Recipient</div></span><span class=""><div>If the downstream recipient of a static assignment of /64 or more addresses requests </div><div>publishing of that assignment in ARIN's registration database, the ISP should register </div><div>that assignment as described in section 6.5.5.1.<br></div></span></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Tue, Sep 26, 2017 at 1:31 PM, ARIN <span dir="ltr"><<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 21 September 2017, the ARIN Advisory Council (AC) advanced the following Draft Policy to Recommended Draft Policy status:<br>
<br>
ARIN-2017-5: Improved IPv6 Registration Requirements<br>
<br>
The text of the Recommended Draft Policy is below, and may also be found at:<br>
<br>
<a href="https://www.arin.net/policy/proposals/2017_5.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/pr<wbr>oposals/2017_5.html</a><br>
<br>
You are encouraged to discuss all Recommended Draft Policies on PPML<br>
prior to their presentation at the next ARIN Public Policy and Members Meeting. PPML and PPC discussions are invaluable to the AC when<br>
determining community consensus.<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/pd<wbr>p.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/pr<wbr>oposals/index.html</a><br>
<br>
Regards,<br>
<br>
Sean Hopkins<br>
Policy Analyst<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
AC's Statement of Conformance with ARIN's Principles of Internet Number Resource Policy:<br>
<br>
This proposal is technically sound and enables fair and impartial number policy for easier IPv6 Registrations. The staff and legal review noted a single clarification issue which has been addressed. There is ample support for the proposal on PPML and no concerns have been raised by the community regarding the proposal.<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 "assignment containing a /64 or more addresses" and change to "re-allocation, reassignment containing a /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.2. "Assignments visible within 7 days" of the NRPM to strike the text "4.2.3.7.1" and change to "6.5.5.1"<br>
<br>
and<br>
<br>
3) 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>
4) Add new section 6.5.5.4 "Registration Requested by Recipient" of the NRPM, to read: "If the downstream recipient of a static assignment of /64 or more addresses requests publishing of that assignment in ARIN's registration database, the ISP should register that assignment as described in section 6.5.5.1."<br>
<br>
Comments:<br>
<br>
a. Timetable for implementation:<br>
<br>
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 administrative 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" target="_blank">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" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_4244031056087368024gmail_signature" data-smartmail="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">______________________________<wbr>_________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@<wbr>google.com</a>|<a href="tel:(571)%20266-0006" value="+15712660006" target="_blank">571-266-0006</a></font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</div>