<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: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 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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 style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>I accept the draft policy statement for the most part, with the only change to swap “Ethernet” with “Layer 2”. This I believe will satisfy both camps of the debate, ie those who think that the definition should be in keeping with standards bodies’ technical definition and those who want the policy to remain technology neutral.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Yves Ephraim<span style='color:#1F497D;mso-ligatures:standardcontextual'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='color:#1F497D;mso-ligatures:standardcontextual'><o:p> </o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> ARIN-PPML <arin-ppml-bounces@arin.net> <b>On Behalf Of </b>Chris Woodfield<br><b>Sent:</b> Wednesday, May 29, 2024 12:33 PM<br><b>To:</b> Martin Hannigan <hannigan@gmail.com><br><b>Cc:</b> arin-ppml <arin-ppml@arin.net><br><b>Subject:</b> Re: [arin-ppml] Draft Policy ARIN-2024-5: Rewrite of NRPM Section 4.4 Micro-Allocation<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’d argue that the examples you point out are a bit different, as in they are inherent aspects of the specific technologies and functionality that ARIN is charged with its stewardship of (in this case, IP and AS resources), but does not necessarily call out a specific technology other than those. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>As a counterexample, there are no references to BGP in the NRPM; while it’s highly unlikely that a new protocol will overtake it, there would be no needed changes to the NRPM to accommodate should that happen. More importantly, should there be a technical need and will to standardize on a new protocol to replace BGP, there’s zero concern that ARIN policy will slow the development or adoption of such a technology.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>(True, the chances of BGP being eclipsed by a new protocol are probably lower than the chances of Ethernet being replaced, but I don’t think that dilutes the argument here.)<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This is my main concern around the use “Ethernet” in this proposal - it’s not that we are simply acknowledging what is standard practice today, but I would never want ARIN policy to be a blocker for the adoption of new technologies, and the more specific we get about what technologies are required per policy, the higher that risk becomes.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>-Chris<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On May 29, 2024, at 07:34, Martin Hannigan <<a href="mailto:hannigan@gmail.com">hannigan@gmail.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, May 29, 2024 at 01:22 Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal>Again, I think (and if I were involved in Open-IX would argue there) that their standard is over-specified and over-constrained. While 802.3z and 802.3ae are very common interfaces today, I know, for example, that there are at least a couple of IXPs that are considering (if not implemented) the elimination of 802.3z and moved up to 802.3ae as a minimum IX connection. I think the days of every IX offering 1Gpbs connections are certainly numbered as 10G becomes ever cheaper to implement.<o:p></o:p></p></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I hear you. We disagree (rarely). The benefit is we close a massive hole in policy and not replace one loop hole with another. There are other prescriptive requirements in the NRPM. Multihoming. 6.4.4. Minimum allocation sizes. Policies by shepherd singling out IX allocation sizes eg /26. IETF -> IANA global instructions. Nothing really new here. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>HTH<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>-M<<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div><p class=MsoNormal>_______________________________________________<br>ARIN-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="https://lists.arin.net/mailman/listinfo/arin-ppml">https://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></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>