<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>How about if each company would have to make their case, based on the greatest number of attachment points to a particular area? They could show they have a plurality of elements linking them to ARIN's region rather than to any other region (such as a majority of their end-users being present in that region and/or it makes sense operationally to submit the request to ARIN because of the presence of a majority of its equipment located in that region, and/or other attachment elements to be defined). Instead of having only 1 criteria for attachment to a particular region, there could be several and if 3 out 5 are verified, than the entity would receive number resources from the RIR. </span></div><div><span>This would allow staff to have a global picture of that entity and the policy could be made as liberal or as
restrictive as desired by the community.</span></div><div><span><br></span></div><div><span style="font-size: 12pt;"> </span><br></div><div>Nathalie Coupet<br>ARIN Member</div> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font size="2" face="Arial"> <b><span style="font-weight:bold;">From:</span></b> nathalie coupet <nathaliecoupet@yahoo.com><br> <b><span style="font-weight: bold;">To:</span></b> "arin-ppml@arin.net" <arin-ppml@arin.net> <br> <b><span style="font-weight: bold;">Sent:</span></b> Saturday, September 14, 2013 1:58 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> "Re: Contents of ARIN-PPML digest, Vol 99, Issue 10..."<br> </font> </div> <div class="y_msg_container"><br><div id="yiv6494731775"><div><div style="color: rgb(0, 0, 0); background-color:
rgb(255, 255, 255); font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"><div><span>How about if each company would have to make their case, based on the greatest number of attachment points to a particular area? They could show they have a plurality of elements linking them to ARIN's region rather than to any other region (such as a majority of their end-users being present in that region and/or it makes sense operationally to submit the request to ARIN because of the presence of a majority of its equipment located in that region, and/or other attachment elements to be defined). </span></div><div></div><div> </div><div>Nathalie Coupet<br>ARIN Member</div><div><br></div> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font size="2" face="Arial"> <b><span
style="font-weight:bold;">From:</span></b> "arin-ppml-request@arin.net" <arin-ppml-request@arin.net><br> <b><span style="font-weight:bold;">To:</span></b> arin-ppml@arin.net <br> <b><span style="font-weight:bold;">Sent:</span></b> Friday, September 13, 2013 5:45 PM<br> <b><span style="font-weight:bold;">Subject:</span></b> ARIN-PPML Digest, Vol 99, Issue 9<br> </font> </div> <div class="yiv6494731775y_msg_container"><br>Send ARIN-PPML mailing list submissions to<br> <a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a rel="nofollow" target="_blank" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>or, via email, send a message with subject or body 'help' to<br> <a rel="nofollow"
ymailto="mailto:arin-ppml-request@arin.net" target="_blank" href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a><br><br>You can reach the person managing the list at<br> <a rel="nofollow" ymailto="mailto:arin-ppml-owner@arin.net" target="_blank" href="mailto:arin-ppml-owner@arin.net">arin-ppml-owner@arin.net</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of ARIN-PPML digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Draft Policy ARIN-2013-6: Allocation of IPv4 and IPv6<br> Address Space to Out-of-region Requestors - Revised Problem<br> Statement and Policy Text (William Herrin)<br> 2. Re: Draft Policy ARIN-2013-6: Allocation of IPv4 and IPv6<br> Address Space to Out-of-region Requestors - Revised Problem<br> Statement and Policy Text (William Herrin)<br> 3. Re:
Draft Policy ARIN-2013-6: Allocation of IPv4 and IPv6<br> Address Space
to Out-of-region Requestors - Revised Problem<br> Statement and Policy Text (William Herrin)<br> 4. Re: Draft Policy ARIN-2013-6: Allocation of IPv4 and IPv6<br> Address Space to Out-of-region Requestors - Revised Problem<br> Statement and Policy Text (John Curran)<br> 5. Re: Draft Policy ARIN-2013-6: Allocation of IPv4 and IPv6<br> Address Space to Out-of-region Requestors - Revised Problem<br> Statement and Policy Text (David Conrad)<br> 6. Re: Draft Policy ARIN-2013-6: Allocation of IPv4 and IPv6<br> Address Space to Out-of-region Requestors - Revised Problem<br> Statement and Policy Text (Kevin Kargel)<br> 7. Re: Draft Policy ARIN-2013-6: Allocation of IPv4 and IPv6<br> Address Space to Out-of-region Requestors
- Revised Problem<br> Statement and Policy Text (David Conrad)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 13 Sep 2013 15:54:37 -0400<br>From: William Herrin <<a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a>><br>To: John Curran <<a rel="nofollow" ymailto="mailto:jcurran@arin.net" target="_blank" href="mailto:jcurran@arin.net">jcurran@arin.net</a>><br>Cc: "<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2013-6: Allocation of IPv4<br> and IPv6 Address Space to Out-of-region Requestors - Revised
Problem<br> Statement and Policy Text<br>Message-ID:<br>
<CAP-guGWHiFfyHSzgRVghqK+cSNwhoD+S_G-H_AgBs+<a rel="nofollow" ymailto="mailto:Nn6he2QQ@mail.gmail.com" target="_blank" href="mailto:Nn6he2QQ@mail.gmail.com">Nn6he2QQ@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>On Fri, Sep 13, 2013 at 3:26 PM, John Curran <<a rel="nofollow" ymailto="mailto:jcurran@arin.net" target="_blank" href="mailto:jcurran@arin.net">jcurran@arin.net</a>> wrote:<br>> It is ARIN's practice to assign number resources to organizations,<br>> not individuals.<br><br>That's me, Mr. Outlier.<br><br><br>>> On Sep 13, 2013, at 11:59 AM, William Herrin <<a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a>> wrote:<br>>>> More importantly: why not?<br>><br>> At a minimum, NRPM 2.6 ("End-user" definition) would need to be<br>> changed to recognize IP address assignments to individuals -<br>><br>> "2.6 An
end-user is an organization receiving assignments of IP<br>>
addresses exclusively for use in its operational networks."<br><br>An organization is some number of people acting on concert towards a<br>common goal. One is an acceptable number. Given Citizens United and<br>the history of similar rulings, I'm pretty sure I can make that claim<br>stick.<br><br>Besides which, I presume ARIN doesn't refuse to do business with sole<br>proprietorships. A sole proprietorship has no legal existence separate<br>from the single individual who owns it. With minor exceptions (Bob's<br>Bait and Tackle can't get married or adopt children) a proprietorship<br>is legally synonymous with its owner.<br><br>What else ya got? :)<br><br>Regards,<br>Bill Herrin<br><br>-- <br>William D. Herrin ................ <a rel="nofollow" ymailto="mailto:herrin@dirtside.com" target="_blank" href="mailto:herrin@dirtside.com">herrin@dirtside.com</a> <a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank"
href="mailto:bill@herrin.us">bill@herrin.us</a><br>3005 Crane Dr. ...................... Web:
<<a rel="nofollow" target="_blank" href="http://bill.herrin.us/">http://bill.herrin.us/</a>><br>Falls Church, VA 22042-3004<br><br><br>------------------------------<br><br>Message: 2<br>Date: Fri, 13 Sep 2013 16:41:42 -0400<br>From: William Herrin <<a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a>><br>To: John Santos <<a rel="nofollow" ymailto="mailto:JOHN@egh.com" target="_blank" href="mailto:JOHN@egh.com">JOHN@egh.com</a>><br>Cc: "<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2013-6: Allocation of IPv4<br> and IPv6 Address Space to Out-of-region Requestors - Revised Problem<br>
Statement and Policy Text<br>Message-ID:<br> <CAP-guGUe5kebTSQNgD_jsNznMv3=<a rel="nofollow" ymailto="mailto:2bjm_gqQAd7BbfxER-uLKQ@mail.gmail.com" target="_blank" href="mailto:2bjm_gqQAd7BbfxER-uLKQ@mail.gmail.com">2bjm_gqQAd7BbfxER-uLKQ@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>On Fri, Sep 13, 2013 at 12:52 PM, John Santos <<a rel="nofollow" ymailto="mailto:JOHN@egh.com" target="_blank" href="mailto:JOHN@egh.com">JOHN@egh.com</a>> wrote:<br>> What if the business is international, with sites all over the world?<br>> Should they be forced to run at least 5 separate networks instead of a<br>> single integrated network?<br><br>Hi John,<br><br>That's a fair question. I hope I don't mischaracterize the ITU's<br>position when I say they think a strictly regionalized registry system<br>is detrimental to business in exactly this manner. They would have<br>themselves designated as a
registry with worldwide scope in order to<br>serve these interests among others.<br><br>I'd offer this answer: if we want to continue as a system of
regional<br>registries then it's generally appropriate for a multinational<br>organization get acquire the number resources it deploys in each<br>region from that region's registry. One network. Five suppliers, whose<br>goods have geographical constraints on their use.<br><br>If a system of regional registries is no longer indicated, that's a<br>much bigger topic of discussion which we shouldn't back-door by having<br>ARIN unilaterally act as registry to the world.<br><br>Regards,<br>Bill Herrin<br><br><br>-- <br>William D. Herrin ................ <a rel="nofollow" ymailto="mailto:herrin@dirtside.com" target="_blank" href="mailto:herrin@dirtside.com">herrin@dirtside.com</a> <a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a><br>3005 Crane Dr. ...................... Web: <<a rel="nofollow" target="_blank" href="http://bill.herrin.us/">http://bill.herrin.us/</a>><br>Falls Church, VA
22042-3004<br><br><br>------------------------------<br><br>Message:
3<br>Date: Fri, 13 Sep 2013 16:30:36 -0400<br>From: William Herrin <<a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a>><br>To: Gary Buhrmaster <<a rel="nofollow" ymailto="mailto:gary.buhrmaster@gmail.com" target="_blank" href="mailto:gary.buhrmaster@gmail.com">gary.buhrmaster@gmail.com</a>><br>Cc: "<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2013-6: Allocation of IPv4<br> and IPv6 Address Space to Out-of-region Requestors - Revised Problem<br> Statement and Policy Text<br>Message-ID:<br> <CAP-guGWPfrSPJbsvc2ZTshWgyQ-KzXF-+Zjhq0aoBq3=3Z=<a rel="nofollow"
ymailto="mailto:m1g@mail.gmail.com" target="_blank" href="mailto:m1g@mail.gmail.com">m1g@mail.gmail.com</a>><br>Content-Type: text/plain;
charset=ISO-8859-1<br><br>On Fri, Sep 13, 2013 at 1:06 PM, Gary Buhrmaster<br><<a rel="nofollow" ymailto="mailto:gary.buhrmaster@gmail.com" target="_blank" href="mailto:gary.buhrmaster@gmail.com">gary.buhrmaster@gmail.com</a>> wrote:<br>> On Fri, Sep 13, 2013 at 3:53 PM, William Herrin <<a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a>> wrote:<br>>> Yuck!<br>><br>> Unless I am misreading this, this proposal deals with the initial<br>> (or additional) allocation/assignments, and not on-going activities.<br>> Once you get the numbers, you could then move the numbers<br>> to other regions.<br><br>Hi Gary,<br><br>Did I miss the text which exempts this draft from the exercise of NRPM<br>section 12.2.c and d?<br><br>Regards,<br>Bill Herrin<br><br><br><br>-- <br>William D. Herrin ................ <a rel="nofollow" ymailto="mailto:herrin@dirtside.com"
target="_blank" href="mailto:herrin@dirtside.com">herrin@dirtside.com</a> <a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a><br>3005 Crane Dr. ...................... Web: <<a rel="nofollow" target="_blank" href="http://bill.herrin.us/">http://bill.herrin.us/</a>><br>Falls Church, VA 22042-3004<br><br><br>------------------------------<br><br>Message: 4<br>Date: Fri, 13 Sep 2013 21:13:39 +0000<br>From: John Curran <<a rel="nofollow" ymailto="mailto:jcurran@arin.net" target="_blank" href="mailto:jcurran@arin.net">jcurran@arin.net</a>><br>To: William Herrin <<a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a>><br>Cc: "<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net"
target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2013-6: Allocation of IPv4<br> and IPv6 Address Space to Out-of-region Requestors - Revised Problem<br>
Statement and Policy Text<br>Message-ID: <<a rel="nofollow" ymailto="mailto:0336F44F-01C1-4724-83D2-DA4AF763D225@arin.net" target="_blank" href="mailto:0336F44F-01C1-4724-83D2-DA4AF763D225@arin.net">0336F44F-01C1-4724-83D2-DA4AF763D225@arin.net</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>On Sep 13, 2013, at 3:54 PM, William Herrin <<a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank" href="mailto:bill@herrin.us">bill@herrin.us</a>> wrote:<br><br>> On Fri, Sep 13, 2013 at 3:26 PM, John Curran <<a rel="nofollow" ymailto="mailto:jcurran@arin.net" target="_blank" href="mailto:jcurran@arin.net">jcurran@arin.net</a>> wrote:<br>>> It is ARIN's practice to assign number resources to organizations,<br>>> not individuals.<br>> <br>> That's me, Mr. Outlier.<br>> <br>>>> On Sep 13, 2013, at 11:59 AM, William Herrin <<a rel="nofollow" ymailto="mailto:bill@herrin.us" target="_blank"
href="mailto:bill@herrin.us">bill@herrin.us</a>> wrote:<br>>>>> More importantly: why not?<br>>>
<br>>> At a minimum, NRPM 2.6 ("End-user" definition) would need to be<br>>> changed to recognize IP address assignments to individuals -<br>>> <br>>> "2.6 An end-user is an organization receiving assignments of IP<br>>> addresses exclusively for use in its operational networks."<br>> <br>> An organization is some number of people acting on concert towards a<br>> common goal. One is an acceptable number. Given Citizens United and<br>> the history of similar rulings, I'm pretty sure I can make that claim<br>> stick.<br>> <br>> Besides which, I presume ARIN doesn't refuse to do business with sole<br>> proprietorships. A sole proprietorship has no legal existence separate<br>> from the single individual who owns it. With minor exceptions (Bob's<br>> Bait and Tackle can't get married or adopt children) a proprietorship<br>> is legally synonymous with its owner.<br>> <br>>
What else ya got? :)<br><br>Bill - <br> <br> We have no problem dealing with sole proprietorships; they are<br> organizations and can receive assignments. Note that the number<br> resources are still assigned in such cases to the organization<br> (i.e. in the name of the sole proprietorship) not the individual.<br><br>FYI,<br>/John<br><br>John Curran<br>President and CEO<br>ARIN<br><br><br><br><br>------------------------------<br><br>Message: 5<br>Date: Fri, 13 Sep 2013 17:12:58 -0400<br>From: David Conrad <<a rel="nofollow" ymailto="mailto:drc@virtualized.org" target="_blank" href="mailto:drc@virtualized.org">drc@virtualized.org</a>><br>To: Kevin Kargel <<a rel="nofollow" ymailto="mailto:kkargel@polartel.com" target="_blank" href="mailto:kkargel@polartel.com">kkargel@polartel.com</a>><br>Cc: "<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a
rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2013-6: Allocation of IPv4<br> and IPv6 Address Space to Out-of-region Requestors - Revised Problem<br> Statement and Policy Text<br>Message-ID: <<a rel="nofollow" ymailto="mailto:B4388CB9-5E8B-4071-B438-C74D35AA780E@virtualized.org" target="_blank" href="mailto:B4388CB9-5E8B-4071-B438-C74D35AA780E@virtualized.org">B4388CB9-5E8B-4071-B438-C74D35AA780E@virtualized.org</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>Kevin,<br><br>On Sep 13, 2013, at 2:42 PM, Kevin Kargel <<a rel="nofollow" ymailto="mailto:kkargel@polartel.com" target="_blank" href="mailto:kkargel@polartel.com">kkargel@polartel.com</a>> wrote:<br>> I still don't see how this is going to be enforceable. To my eye it would
entail getting geo-data for all last mile routers that service IP's under ARIN control and having someone or a sophisticated AI
bot continuously scanning the BGP tables to enumerate and verify the geo-locations of the endpoints.<br><br>Why wouldn't an assertion by the applicant that they run a network in the ARIN region and perhaps a traceroute or two be sufficient to meet the "operating a network located in the ARIN service region" requirement?<br><br>> If the idea is just to ask people if they are in the ARIN governance area and make them promise to never move offshore (knowing it will not be subsequently policed) then I submit that the algorithm is way too easy to game by unscrupulous operators and will end up being a token policy that creates more bureaucracy and trouble for legitimate operators. <br><br>I don't see this being significantly different than gaming the "operational needs" requirement. I think the issue here is establishing a policy basis upon which violations, when detected, can be addressed. If it is discovered that someone is getting addresses to
stockpile them for later sale, ARIN policy exists to allow ARIN to revoke those addresses. This draft policy is saying that if someone is getting addresses for use outside ARIN's region, there would be a policy to allow ARIN to address that issue.<br><br>And, FWIW, I'll note that both AfriNIC and LACNIC (the remaining RIRs that have not gone into "last /8" policy) require companies to demonstrate in-region legal status and network usage. <br><br>> If you can figure out a way to enforce *and* implement it I would support the policy, but until that time I have to vote "nay". I suspect that even if it were implemented enforcement would only be possible if it were written with an anti-grandfather clause.<br><br>Wait, I liked my grandfather... :) (sorry, not sure what an 'anti-grandfather clause is)<br><br>Regards,<br>-drc<br><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: signature.asc<br>Type:
application/pgp-signature<br>Size: 495 bytes<br>Desc: Message signed with OpenPGP using GPGMail<br>URL: <<a rel="nofollow" target="_blank" href="http://lists.arin.net/pipermail/arin-ppml/attachments/20130913/62daaa5d/attachment-0001.bin">http://lists.arin.net/pipermail/arin-ppml/attachments/20130913/62daaa5d/attachment-0001.bin</a>><br><br>------------------------------<br><br>Message: 6<br>Date: Fri, 13 Sep 2013 16:20:22 -0500<br>From: Kevin Kargel <<a rel="nofollow" ymailto="mailto:kkargel@polartel.com" target="_blank" href="mailto:kkargel@polartel.com">kkargel@polartel.com</a>><br>To: "<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2013-6: Allocation of IPv4<br> and
IPv6 Address Space to Out-of-region Requestors - Revised Problem<br> Statement and Policy
Text<br>Message-ID:<br> <<a rel="nofollow" ymailto="mailto:8695009A81378E48879980039EEDAD28012B3D4D77@MAIL1.polartel.local" target="_blank" href="mailto:8695009A81378E48879980039EEDAD28012B3D4D77@MAIL1.polartel.local">8695009A81378E48879980039EEDAD28012B3D4D77@MAIL1.polartel.local</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br><br><br>-----Original Message-----<br>From: David Conrad [mailto:<a rel="nofollow" ymailto="mailto:drc@virtualized.org" target="_blank" href="mailto:drc@virtualized.org">drc@virtualized.org</a>] <br>Sent: Friday, September 13, 2013 4:13 PM<br>To: Kevin Kargel<br>Cc: <a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2013-6: Allocation of IPv4 and IPv6 Address Space to Out-of-region Requestors - Revised Problem Statement and Policy Text<br><br>Kevin,<br><br>On Sep 13, 2013, at
2:42 PM, Kevin Kargel <<a rel="nofollow" ymailto="mailto:kkargel@polartel.com" target="_blank" href="mailto:kkargel@polartel.com">kkargel@polartel.com</a>> wrote:<br>> I still don't see how this is going to be enforceable. To my eye it would entail getting geo-data for all last mile routers that service IP's under ARIN control and having someone or a sophisticated AI bot continuously scanning the BGP tables to enumerate and verify the geo-locations of the endpoints.<br><br>>>Why wouldn't an assertion by the applicant that they run a network in the ARIN region and perhaps a traceroute or two be sufficient to meet the "operating a network located in the ARIN service region" requirement?<br><br>A traceroute would only satisfy an initial test. Trivially easy to set one up, get your allocation, and then move the network to where you really wanted it.<br><br>> If the idea is just to ask people if they are in the ARIN governance area
and make them promise to never move offshore (knowing it will not be subsequently policed) then I
submit that the algorithm is way too easy to game by unscrupulous operators and will end up being a token policy that creates more bureaucracy and trouble for legitimate operators. <br><br>>>I don't see this being significantly different than gaming the "operational needs" requirement. I think the issue here is establishing a policy basis upon which violations, when detected, can be addressed. If it is discovered that someone is getting addresses to stockpile them for later sale, ARIN policy exists to allow ARIN to revoke those addresses. This draft policy is saying that if someone is getting addresses for use outside ARIN's region, there would be a policy to allow ARIN to address that issue.<br><br>Just like ARIN follows up on the utilization requirement? <br><br>>>And, FWIW, I'll note that both AfriNIC and LACNIC (the remaining RIRs that have not gone into "last /8" policy) require companies to demonstrate in-region legal
status and network usage. <br><br>Maybe they have a way to test and enforce their requirement. If so perhaps it is a model we should pattern after.<br><br>> If you can figure out a way to enforce *and* implement it I would support the policy, but until that time I have to vote "nay". I suspect that even if it were implemented enforcement would only be possible if it were written with an anti-grandfather clause.<br><br>>>Wait, I liked my grandfather... :) (sorry, not sure what an 'anti-grandfather clause is)<br><br>Anti-grandfather means that the restrictions should equally apply to existing allocations, and current allocations that are operating outside of the ARIN region should be required to obtain allocations from their region and return the ARIN allocation. Old allocations should not have a 'grandfather' exemption. We would probably need to forgive their latest set of fees.<br>It would be onerously difficult to
separate the pre and post allocations for enforcement.<br><br><br><br>Regards,<br>-drc<br><br><br><br>------------------------------<br><br>Message: 7<br>Date: Fri, 13 Sep 2013 17:45:41 -0400<br>From: David Conrad <<a rel="nofollow" ymailto="mailto:drc@virtualized.org" target="_blank" href="mailto:drc@virtualized.org">drc@virtualized.org</a>><br>To: Kevin Kargel <<a rel="nofollow" ymailto="mailto:kkargel@polartel.com" target="_blank" href="mailto:kkargel@polartel.com">kkargel@polartel.com</a>><br>Cc: "<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a rel="nofollow" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2013-6: Allocation of IPv4<br> and IPv6 Address Space to Out-of-region Requestors -
Revised Problem<br> Statement and Policy Text<br>Message-ID: <<a rel="nofollow" ymailto="mailto:D17E2A39-386B-4804-9E26-AA8CB39B7D10@virtualized.org" target="_blank" href="mailto:D17E2A39-386B-4804-9E26-AA8CB39B7D10@virtualized.org">D17E2A39-386B-4804-9E26-AA8CB39B7D10@virtualized.org</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>Kevin,<br><br>On Sep 13, 2013, at 5:20 PM, Kevin Kargel <<a rel="nofollow" ymailto="mailto:kkargel@polartel.com" target="_blank" href="mailto:kkargel@polartel.com">kkargel@polartel.com</a>> wrote:<br>> A traceroute would only satisfy an initial test. Trivially easy to set one up, get your allocation, and then move the network to where you really wanted it.<br><br>Yes. However, if this subterfuge was noticed, the policy would give ARIN the capability to do something about it (if necessary), just like other ARIN policies.<br><br>> Just like ARIN follows up
on the utilization requirement? <br><br>I've been told ARIN has revoked address space for violation of policy.<br><br>> Anti-grandfather means that the
restrictions should equally apply to existing allocations, and current allocations that are operating outside of the ARIN region should be required to obtain allocations from their region and return the ARIN allocation. <br><br>My understanding of the policy proposal was that it was to apply to future allocations because the out-of-region requests appear to be increasing with the exhaustion of various RIR free pools. Historically, it has been ... challenging to retroactively apply policy to pre-existing allocations. If such retroactive application were desired (not going to comment one way or another on that aspect), I'd suggest it should be a different policy proposal.<br><br>Regards,<br>-drc<br><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: signature.asc<br>Type: application/pgp-signature<br>Size: 495 bytes<br>Desc: Message signed with OpenPGP using GPGMail<br>URL: <<a rel="nofollow"
target="_blank" href="http://lists.arin.net/pipermail/arin-ppml/attachments/20130913/aa305473/attachment.bin">http://lists.arin.net/pipermail/arin-ppml/attachments/20130913/aa305473/attachment.bin</a>><br><br>------------------------------<br><br>_______________________________________________<br>ARIN-PPML mailing list<br><a rel="nofollow" ymailto="mailto:ARIN-PPML@arin.net" target="_blank" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a><br><a rel="nofollow" target="_blank" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br><br>End of ARIN-PPML Digest, Vol 99, Issue 9<br>****************************************<br><br><br></div> </div> </div> </div></div></div><br><br></div> </div> </div> </div></body></html>