<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#993366;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">All -<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"> The recent additional discussion on the list has prompted me to reconsider how I'm approaching the<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">rework of this policy.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"> I'll be discussing this internally with other AC members, and provide updates at the conclusion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">There will be plenty of opportunity to provide additional feedback afterword.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">Thank you for your patience.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">Leif<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Leif Sawyer
<br>
<b>Sent:</b> Wednesday, July 05, 2017 8:30 AM<br>
<b>To:</b> arin-ppml@arin.net<br>
<b>Cc:</b> 'hostmaster@uneedus.com'<br>
<b>Subject:</b> RE: [arin-ppml] Draft Policy ARIN-2017-5: Equalization of Assignment Registration requirements between IPv4 and IPv6<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks, Albert.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> We're taking all of this feedback under consideration, and I'll endeavor to have updates after the holiday week is over.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Leif Sawyer<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">ARIN Advisory Council<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> ARIN-PPML [<a href="mailto:arin-ppml-bounces@arin.net">mailto:arin-ppml-bounces@arin.net</a>]
<b>On Behalf Of </b><a href="mailto:hostmaster@uneedus.com">hostmaster@uneedus.com</a><br>
<b>Sent:</b> Wednesday, July 05, 2017 12:48 AM<br>
<b>To:</b> <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<b>Subject:</b> [arin-ppml] Draft Policy ARIN-2017-5: Equalization of Assignment Registration requirements between IPv4 and IPv6<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:red">[External Email]</span>
<br>
<br>
It has now been about 4 weeks since ARIN-2017-5 was last revised.<br>
<br>
Based on the comments received, "more than a /56" is the consensus.<br>
I ask that the AC revise the proposal to this value, so it can be further <br>
considered.<br>
<br>
This is the tally so far:<br>
/56 9 votes<br>
Any of these levels are OK - 2 votes<br>
/60 2 votes<br>
/61 1 vote<br>
/57 1 vote<br>
/53 1 vote<br>
/49 1 vote<br>
<br>
Albert Erdmann<br>
Network Administrator<br>
Paradise On Line Inc.<br>
<br>
<br>
On Wed, 7 Jun 2017, Leif Sawyer wrote:<br>
<br>
> That was not changed yet, as I'm still waiting for more folks to respond.<br>
><br>
> The update was only for the removal of the IPv4 portion, as I mentioned in my previous email.<br>
><br>
> From: ARIN-PPML [<a href="mailto:arin-ppml-bounces@arin.net">mailto:arin-ppml-bounces@arin.net</a>] On Behalf Of Scott Leibrand<br>
> Sent: Wednesday, June 07, 2017 11:13 AM<br>
> To: ARIN<br>
> Cc: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
> Subject: Re: [arin-ppml] Revised: Draft Policy ARIN-2017-5: Equalization of Assignment Registration requirements between IPv4 and IPv6<br>
><br>
> [External Email]<br>
><br>
> It looks like /60 still needs to be changed to /56 to reflect the consensus on PPML. Or was there some reason not to do that (yet)?<br>
><br>
> Scott<br>
><br>
>> On Jun 7, 2017, at 11:58 AM, ARIN <<a href="mailto:info@arin.net%3cmailto:info@arin.net">info@arin.net<mailto: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">https://www.arin.net/policy/proposals/2017_5.html</a><<a href="https://www.arin.net/policy/proposals/2017_5.html">https://www.arin.net/policy/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">https://www.arin.net/policy/pdp.html</a><<a href="https://www.arin.net/policy/pdp.html">https://www.arin.net/policy/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">https://www.arin.net/policy/proposals/index.html</a><<a href="https://www.arin.net/policy/proposals/index.html">https://www.arin.net/policy/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>
>><br>
>> Problem Statement:<br>
>><br>
>> 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 or less (CGnat), which do not trigger any ARIN registration requirement
when using IPv4. This is NOT true when these same exact customers use IPv6.<br>
>><br>
>> Currently, 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.<br>
>><br>
>> IPv6 assignments are therefore treated stricter than IPv4 assignments. Policy should either treat both protocols the same, or provide incentive for the IPv6 future. A typical ISP serving residential and small business customers with both IPv4 and IPv6 would
typically provide the following assignments to each customer site: /32 (one IP) of IPv4 and a /64 (one network) of IPv6. Under the current policy, that small network customer is exempt from registration for their IPv4 assignment, but the ISP would be required
to register ALL IPv6 customers, even those of this smallest network size.<br>
>><br>
>> In actual fact, most ISP's that are providing their customers with a /64 or more of IPv6 space are not in fact registering this fact with ARIN, even though 6.5.5.1 clearly requires this.<br>
>><br>
>> It is my belief that these residential and small business customers should not require registration if they did not require registration for the same size IPv4 network, including routers with Vlan and other security support. and thus I propose to make the
standard for registration only those customers that have more than 16 IPv6 /64 networks. This would treat IPv6 slightly better than IPv4, and provide additional encouragement for adoption.<br>
>><br>
>> Policy statement:<br>
>><br>
>> Amend 6.5.5.1 of the policy manual to strike "/64 or more" and change to "more than a /60".<br>
>><br>
>> Comments:<br>
>><br>
>> a. Timetable for implementation:<br>
>><br>
>> Policy should be adopted as soon as possible, as the new administrative burden of 100% customer registration of IPv6 customers is unreasonable, when such is not required for those customers receiving only IPv4 connections. IPv6 should not be more burdensome
than the equivalent IPv4 network size.<br>
>><br>
>> b. Anything else:<br>
>><br>
>> The specific sizes chosen set the point of registration for each site to more than 16 networks or addresses, so that those with 16 or less IPv6 networks (/60) have no registration requirement. This change will result in both protocols being treated exactly
the same, and removes residential and small business accounts from any registration requirement with ARIN, and the burden that will create for all ISP's.<br>
>><br>
>> There are those that might argue that a residental customer will never have a need for more than a /64 of IPv6. Clearly this is false in an IOT and/or wireless world, as many routers already provide a separate address range for wired vs wireless to prevent
wired hacking via the wireless space, and also may provide a guest wireless SSID apart from the one provided to the regular users of that same network. Such separation in the IPv4 world is currently done in RFC1918 space using NAT. In IPv6, the equivalent
must be done with different /64 blocks. Since good security practices require use at least 2 /64 blocks for wireless and/or IOT isolation, this would require a minimum of a /60 of IPv6 space or up to 16 networks or vlans, an amount that is consistent with
a residential or small business network. This type network does not trigger registration under the current IPv4 policy, and its equal should not trigger registration with ARIN based on the current IPv6 policy as is cu!<br>
rr<br>
> ently the case, and thus, this policy needs to be changed.<br>
>> _______________________________________________<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%3cmailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net<mailto: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">
http://lists.arin.net/mailman/listinfo/arin-ppml</a><<a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a>><br>
>> Please contact <a href="mailto:info@arin.net%3cmailto:info@arin.net">info@arin.net<mailto:info@arin.net</a>> if you experience any issues.<br>
> _______________________________________________<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%3cmailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net<mailto: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">
http://lists.arin.net/mailman/listinfo/arin-ppml</a><<a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a>><br>
> Please contact <a href="mailto:info@arin.net%3cmailto:info@arin.net">info@arin.net<mailto:info@arin.net</a>> if you experience any issues.<br>
><br>
_______________________________________________<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">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<o:p></o:p></p>
</div>
</body>
</html>