<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
Some of this discussion is above my pay grade as I am not a technical expert in IXPs.
<div><br>
</div>
<div>However from a neutral point of view, I agree that the exclusion of the word “ethernet” would tend to leave the policy flexible for future evolutions or changes to network hardware, protocols etc. However, I am in two minds as to whether or not this is
urgently necessary. I don’t see any specific technical advancements that would render ethernet defunct in the pipeline when implemented in this specific scenario.</div>
<div><br>
</div>
<div>So, my pov is ok, why not exclude “ethernet”, but it is not urgent.<br id="lineBreakAtBeginningOfMessage">
<div>
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<br>
—<br>
My best/Cordialement,<br>
<br>
Matthew Cowen<br>
dgtlfutures<br>
<br>
</div>
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<br>
</div>
</div>
</div>
</div>
<div>
<blockquote type="cite">
<div>On 26 May 2024, at 15:22, Roman Tatarnikov <roman@intlos.org> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div>I do agree with Bill's proposal as well. Breaking a big cumbersome task into multiple small ones will get the things moving faster. So updating the definitions first should help everyone.<br>
<br>
However, I do believe that the word `Ethernet` should be avoided. While it addresses today's situation, we don't know what's going to happen tomorrow. Ideally what we want is to write a policy that will address not only today's needs, but will be prepared to
withstand challenges of time. I can behind of what Owen and Tyler proposed, however I'm not a wordsmith and can't settle on what's the best replacement for "Ethernet" should be. All I know is that there should be one.<br>
<br>
On Sat, May 25, 2024 at 12:46:06AM -0400, Martin Hannigan wrote:<br>
<blockquote type="cite">On Fri, May 24, 2024 at 4:42 PM Owen DeLong via ARIN-PPML <<br>
arin-ppml@arin.net> wrote:<br>
<br>
<blockquote type="cite">I think the best resolution here would be to move all definitional text<br>
for IX in both proposals into a proposed (and identical) definition in NRPM<br>
section 2 and then it’s harmonious and not in need of future<br>
synchronization regardless of whether either or both proposals are adopted.<br>
<br>
</blockquote>
<br>
I do agree with Bill's suggestion that we finish 2024-4 including a<br>
definition and defined term for 2024-5 and anything else related ("Defined<br>
Term"). So I think we're agreeing.<br>
<br>
I object to the removal of "ethernet" from 2024-5.<br>
</blockquote>
<br>
-- <br>
Roman V Tatarnikov | https://linkedin.com/in/rtatarnikov<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<br>
Unsubscribe or manage your mailing list subscription at:<br>
https://lists.arin.net/mailman/listinfo/arin-ppml<br>
Please contact info@arin.net if you experience any issues.<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>