I don't believe a /64 is recommended for a p2p anymore. Rfc 6164<br><br>On Thursday, May 25, 2017, Jason Schiller <<a href="mailto:jschiller@google.com">jschiller@google.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I don't support a relaxation of SWIP requirements for IPv4.<div><br></div><div>I do support updating the language for IPv4 for clarity (if that is useful).</div><div>current IPv4 language: /29 or more</div><div><br></div><div>possibly re-write for clarity: more than a /30.</div><div><br></div><div><br></div><div>As far as IPv6 goes, there are some who recommend a /64 for point-to-point.</div><div>One might argue that in the context of p-t-p an IPv4 /30 maps to a /64.</div><div><br></div><div>I could certainly get behind SWIP requirements for "more than a /64" on these grounds.</div><div><br></div><div>Please make the requirement to SWIP be on a nibble boundary.</div><div> </div><div><br></div><div>Nibbles being nice things, one could argue that end users are likely to get a /64</div><div>or the next size up which is a /60. If you want to catch all customers in the </div><div>smallest size, you might make the boundary at "more than a /61"</div><div><br></div><div>The next size up on the nibble boundary is a /56 putting the boundary at</div><div>"more than a /57" </div><div><br></div><div><br></div><div>Generally speaking any network that is sufficiently large to require subnetting, </div><div>should have sufficient clue to support SWIP. Based on this reasoning "more than</div><div>a /64" seems like an equable place to draw the line. Even "more than a /61" </div><div>seems reasonable, as blocks are likely going to be assigned on nibbles. </div><div>My next preferred choice would be "more than a /57"</div><div><br></div><div>Also don't forget that residential users can opt out of publicly providing information.</div><div><br></div><div>___Jason</div><div><br></div><div> </div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 23, 2017 at 10:04 PM, <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','hostmaster@uneedus.com');" target="_blank">hostmaster@uneedus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
The line has to be drawn somewhere, and the idea when I drafted this proposal was that it was wrong to treat IPv6 less favored than IPv6 as is the current case. It also bothered me that the average residential and small business account would have to go thru the SWIP process, just because they want to have a minimum or so assignment of IPv6 space for their network, when this was never a requirement for IPv4. As discussed, a /60 of v6 is much the same as a /32 of v4.<br>
<br>
I chose 16 addresses/networks as the only reasonable number to make the two protocols equal. As already discussed, 1 network is too small. If the community thinks it is wrong to relax the current IPv4 requirements, I am not opposed to removing 4.2.3.7.1 from the proposal, as long as the community is willing to do something about the "Register every network" problem that is the current policy in v6, and the changes to 6.5.5.1 that I propose.<br>
<br>
While I suggest that a /60 should not trigger registration, if the community would rather kick that up to a /56, I have no problem with this. This would seem to be the more future proof option. Of course such a change calls for a new title, maybe "New policy for IPv6 Assignment Registration", and cite it as allowing even the small networks with a /32 of IPv4 to obtain a reasonable assignment of IPv6 without registration requirements, as is the current case with IPv4.<br>
<br>
Albert Erdmann<br>
Network Administrator<br>
Paradise On Line Inc.<div><div><br>
<br>
<br>
On Tue, 23 May 2017, William Herrin wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, May 23, 2017 at 2:35 PM, ARIN <<a href="javascript:_e(%7B%7D,'cvml','info@arin.net');" target="_blank">info@arin.net</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Draft Policy ARIN-2017-5: Equalization of Assignment Registration<br>
requirements between IPv4 and IPv6<br>
<br>
Policy statement:<br>
<br>
Amend 4.2.3.7.1 of the policy manual to strike "/29 or more" and change to<br>
"more than a /28".<br>
<br>
</blockquote>
<br>
Hello,<br>
<br>
In my opinion...<br>
<br>
Leave /29 alone or change it to "more than a single IP address." In these<br>
days of IPv4 shortage, substantial networks sit behind small blocks of<br>
public addresses. These networks should be documented with reachable POCs<br>
lest the anti-spam/virus/malware folks slam down /24 filters for lack of<br>
information about how misbehaving networks are partitioned.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Amend 6.5.5.1 of the policy manual to strike "/64 or more" and change to<br>
"more than a /60".<br>
<br>
</blockquote>
<br>
Change this to "more than a /56." Service providers should NOT be assigning<br>
/64's to end users. If you're doing that, you're doing it wrong. An IPv6<br>
customer should be able to have more than one /64 subnet without resorting<br>
to NAT so /60 should be the absolute minimum end-user assignment,<br>
equivalent for all intents and purposes to an IPv4 /32. If we then want<br>
"equivalence" to the /29 policy so that individuals with the minimum and<br>
near-minimum assignment do not need to be SWIPed, it makes sense to move<br>
the next subnetting level up. In IPv6, assignment is strongly recommended<br>
on nibble boundaries, so that means /56.<br>
<br>
Regards,<br>
Bill Herrin<br>
<br>
-- <br>
William Herrin ................ <a href="javascript:_e(%7B%7D,'cvml','herrin@dirtside.com');" target="_blank">herrin@dirtside.com</a> <a href="javascript:_e(%7B%7D,'cvml','bill@herrin.us');" target="_blank">bill@herrin.us</a><br>
Dirtside Systems ......... Web: <<a href="http://www.dirtside.com/" rel="noreferrer" target="_blank">http://www.dirtside.com/</a>><br>
<br>
</blockquote></div></div><div><div>
______________________________<wbr>_________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="javascript:_e(%7B%7D,'cvml','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="javascript:_e(%7B%7D,'cvml','info@arin.net');" target="_blank">info@arin.net</a> if you experience any issues.<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div 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="javascript:_e(%7B%7D,'cvml','jschiller@google.com');" target="_blank">jschiller@<wbr>google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</div>
</blockquote>