<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Absolutely.<div><br></div><div>I’d love to see the number be higher, like 3 or 5. If you can’t find more than two, are you really going to get anywhere?</div><div><div><br id="lineBreakAtBeginningOfSignature"><div dir="ltr">-- <div>Richard</div></div><div dir="ltr"><br><blockquote type="cite">On Dec 5, 2023, at 17:51, Martin Hannigan <hannigan@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div><h3 id="gmail-4-4-micro-allocation"><font size="2"><span style="font-weight:normal;font-family:arial,sans-serif">- 4.4. Micro-allocation</span></font></h3><div>Defines the minimum participant count as "three"<br></div></div><div><h4 id="gmail-6-10-1-micro-allocations-for-critical-infrastructure"><font size="2"><span style="font-weight:normal;font-family:arial,sans-serif">- 6.10.1. Micro-allocations for Critical Infrastructure</span></font></h4><div>Defines the minimum participants count justification as "two"</div><div><br></div>How'd that happen? I can't seem to pin down a draft to see.</div><div><br></div><div>As I researched this, however, I again saw widely and was reminded of the below.<br></div><div><br></div><div>Here's what we have justification wise in both:<br></div><div><br></div><div>Exchange point operators must provide justification for the allocation,
including: connection policy, location, other participants (minimum of
two total), ASN, and contact information. </div><div><br></div><div>Here's what we see a lot as a result (which is not in the spirit of the policy):<br><div><div><br></div><div>Spaghetti-IX Justification Peer 1: Spaghetti-IX Route Server ASN 65536<br></div><div><div>Spaghetti-IX Justification Peer 2: Spaghetti-IX Route Server ASN 65537</div><div><div>Spaghetti-IX Justification Peer 1: CedgeoEonnecto (BOS)</div><br></div></div></div></div><div>Here's what I suggest would be meaningful:<br></div><div><br></div><div>Exchange point operators must justify the allocation by providing the location of the switch, the contact information information and public ASN of the initial connecting parties. The initial connecting pirates must be unique and independent from each other.<br></div><div><br></div><div>Which should result in:</div><br><div>Meatball-IX Justification Peer 1: Unique Network ASN 65536<br></div><div><div>Meatball-IX Justification Peer 2: Unique Network ASN 65537</div><div><div>Meatball-IX Justification Peer 1: Unique Network ASN 65538<br></div><div><br></div><div>That would prevent quite a bit of cruft IMHO.</div><div><br></div></div></div><div><div><div><div>FYI,</div><div><br></div><div>-M<</div><div><br></div><div><br></div><div><br></div></div><div><br></div></div></div></div>
<span>_______________________________________________</span><br><span>ARIN-PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span>https://lists.arin.net/mailman/listinfo/arin-ppml</span><br><span>Please contact info@arin.net if you experience any issues.</span><br></div></blockquote></div></div></body></html>