<p dir="ltr">This may seem a stupid question, but since we now want to accept that accuracy is a principle task of registries, what measure are we to use as an acceptable measure of an accurate 'whois' or at the macro level, ' an accurate registry service' ?......% of legacy holders participating on the registry?</p>
<p dir="ltr">Rudi Daniel <br>
(information technologist)<br>
784 430 9235</p>
<div class="gmail_quote">On Feb 22, 2014 7:10 PM, <<a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send ARIN-PPML mailing list submissions to<br>
<a 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 href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a 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 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. Update to Prop 203 (Martin Hannigan)<br>
2. Weekly posting summary for <a href="mailto:ppml@arin.net">ppml@arin.net</a> (Thomas Narten)<br>
3. ARIN Draft Policy 2014-2 Improving 8.4 Anti-Flip Language<br>
(Bill Darte)<br>
4. NANOG 61 - Bellevue - Call For Presentations is open! (Greg Dendy)<br>
5. 2014-2 8.4 Anti-flip Language (Owen DeLong)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 20 Feb 2014 14:16:23 -0500<br>
From: Martin Hannigan <<a href="mailto:hannigan@gmail.com">hannigan@gmail.com</a>><br>
To: Public Policy Mailing List <<a href="mailto:ppml@arin.net">ppml@arin.net</a>><br>
Subject: [arin-ppml] Update to Prop 203<br>
Message-ID:<br>
<<a href="mailto:CAMDXq5NhjJANcgctz3YfrRvJuivLSo8Gk0MjP5vAtLP%2Bm1YPiA@mail.gmail.com">CAMDXq5NhjJANcgctz3YfrRvJuivLSo8Gk0MjP5vAtLP+m1YPiA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Einar,<br>
<br>
Please update Section 203 Proposal with:<br>
<br>
<br>
<br>
Problem Statement<br>
<br>
The importance of maintaining accurate records in the ARIN database is<br>
recognized as the Registries principal task and is not being debated.<br>
The Registry is unable to responsibly fulfill this task. Many resource<br>
holders are not incented through mutual benefits to participate in the<br>
registry, the process or the community and instead operate<br>
successfully outside of its bounds further hampering the mission of<br>
accuracy.<br>
<br>
Intent<br>
<br>
To create a sustainable RIPE 605-like environment in the ARIN region that<br>
provides mutual benefits to legacy holders and ARIN and in support of<br>
vastly improved and accurate registry service.<br>
<br>
Policy Changes<br>
<br>
Section 1, Adds to "Principles"<br>
<br>
Accuracy<br>
<br>
The principle of Accuracy guarantees stakeholders that all reasonable<br>
and mutually beneficial steps will be take to insure that the Registry<br>
is as accurate as possible.<br>
<br>
Fairness<br>
<br>
The principle of Fairness guarantees stakeholders that they will be<br>
treated fairly with respect to whatever class of resources they hold,<br>
whether they are pre or post RIR assigned addresses.<br>
<br>
Value Add<br>
<br>
The principle of Value Add guarantees that the Registry, in its effort<br>
to insure that all of the principles are applied equitably, will seek<br>
to add value to all resource holders regardless of class by insuring<br>
such thing as rapid update functionalities and reasonably easy<br>
transfer administration.<br>
<br>
Mutual Benefit<br>
<br>
The principle of Mutual Benefit guarantees that ARIN will enter into<br>
or dissolve contracts related to legacy resource holders in like<br>
fashion of comparable Registries.<br>
<br>
<br>
Section 2, Adds to "Definitions"<br>
<br>
Legacy Internet Resource<br>
<br>
Any Internet Resource obtained prior to or otherwise outside the<br>
current system of hierarchical distribution (by allocation or<br>
assignment) through the Regional Internet Registries.<br>
<br>
Legacy Internet Resource Holder<br>
<br>
The holder of a Legacy Internet Resource. Either by receiving these<br>
resources directly or by receiving (part of) Legacy Internet Resources<br>
from a Legacy Internet Resource Holder.<br>
<br>
Registry Service Element<br>
<br>
In practice, any Legacy Resource Holder actually avails of a subset of<br>
the Registry Services mentioned above. Where it is necessary to<br>
distinguish between the entire class of Registry Services and the<br>
specific Registry Services actually provided in a particular case, the<br>
latter are described as Registry Service Elements.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 21 Feb 2014 00:53:02 -0500<br>
From: Thomas Narten <<a href="mailto:narten@us.ibm.com">narten@us.ibm.com</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: [arin-ppml] Weekly posting summary for <a href="mailto:ppml@arin.net">ppml@arin.net</a><br>
Message-ID: <<a href="mailto:201402210553.s1L5r2Sh013158@rotala.raleigh.ibm.com">201402210553.s1L5r2Sh013158@rotala.raleigh.ibm.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Total of 33 messages in the last 7 days.<br>
<br>
script run at: Fri Feb 21 00:53:02 EST 2014<br>
<br>
Messages | Bytes | Who<br>
--------+------+--------+----------+------------------------<br>
33.33% | 11 | 22.14% | 102922 | <a href="mailto:jcurran@arin.net">jcurran@arin.net</a><br>
24.24% | 8 | 18.42% | 85630 | <a href="mailto:hannigan@gmail.com">hannigan@gmail.com</a><br>
9.09% | 3 | 19.83% | 92205 | <a href="mailto:mlindsey@lb3law.com">mlindsey@lb3law.com</a><br>
9.09% | 3 | 13.33% | 61983 | <a href="mailto:john.sweeting@twcable.com">john.sweeting@twcable.com</a><br>
6.06% | 2 | 10.25% | 47633 | <a href="mailto:snoble@sonn.com">snoble@sonn.com</a><br>
6.06% | 2 | 4.30% | 19979 | <a href="mailto:drc@virtualized.org">drc@virtualized.org</a><br>
3.03% | 1 | 3.65% | 16949 | <a href="mailto:scottleibrand@gmail.com">scottleibrand@gmail.com</a><br>
3.03% | 1 | 3.35% | 15553 | <a href="mailto:keith@jcc.com">keith@jcc.com</a><br>
3.03% | 1 | 3.06% | 14222 | <a href="mailto:sryerse@eclipse-networks.com">sryerse@eclipse-networks.com</a><br>
3.03% | 1 | 1.68% | 7822 | <a href="mailto:narten@us.ibm.com">narten@us.ibm.com</a><br>
--------+------+--------+----------+------------------------<br>
100.00% | 33 |100.00% | 464898 | Total<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 21 Feb 2014 10:53:12 -0600<br>
From: Bill Darte <<a href="mailto:billdarte@gmail.com">billdarte@gmail.com</a>><br>
To: "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: [arin-ppml] ARIN Draft Policy 2014-2 Improving 8.4 Anti-Flip<br>
Language<br>
Message-ID:<br>
<CAMApp34bqyS=<a href="mailto:uQETQXsabBsO16x%2BTLz2qZfCMU%2B9WDkjFcmkkA@mail.gmail.com">uQETQXsabBsO16x+TLz2qZfCMU+9WDkjFcmkkA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
At the Advisory Council's meeting of Feb 20, discussion about Draft Policy<br>
2014-2 concluded that there is a real issue with transfer restrictions of<br>
address blocks between RIR jurisdictions for organizations having received<br>
a different block of addresses from ARIN within the last 12 months (per<br>
existing policy).<br>
<br>
The current Draft Policy language is as follows with only the last sentence<br>
being added from what is current ARIN policy:<br>
"Source entities within the ARIN region must not have received a transfer,<br>
allocation, or assignment of IPv4 number resources from ARIN for the 12<br>
months prior to the approval of a transfer request. This restriction does<br>
not include M&A transfers. Restrictions related to recent receipt of blocks<br>
shall not apply to inter-RIR transfers within the same organization and its<br>
subsidiaries."<br>
<br>
The last sentence of this language was added to mitigate the problems<br>
related by the author in the problem statement and from experience. The<br>
author supported this change, however, some concern has been expressed on<br>
the PPML and within the AC about the possibility of 'rinse and repeat'<br>
abuse associated with the ease of establishing new subsidiaries and using<br>
those transfers to get around the restrictions of the existing transfer<br>
policy.<br>
<br>
Three alternatives were primarily discussed and I wish to elicit feedback<br>
from the community relative to each.<br>
<br>
1. Use the existing last sentence as is and ask ARIN staff to be<br>
particularly watchful for seeming abuse and to bring such back to the<br>
community through regular Policy Experience Reports. There was discussion<br>
about this option suggesting that by the time abuse was recognized and<br>
reported, and given limited existing free pool stocks and the extended<br>
policy development cycle....this option may be moot.<br>
<br>
2. Remove the clause 'and its subsidiaries' or modify it in such a way as<br>
to mitigate the risk of a laundering of addresses through fraudulent<br>
transfers, but this may still potentially limit the utility to<br>
organizations who may have complex organizational structures in use<br>
internationally.<br>
<br>
3. Take an alternative tack and simply restrict transfers on a per-block<br>
rather than a per-organization basis. e.g. 'No block acquired within the<br>
past 24 months would be eligible for transfer.' (The time frame is of<br>
course an arbitrary number at this point.)<br>
<br>
If you believe this Draft Policy is improved most significantly by one of<br>
the above alternatives, or through another alternative you can pose....I,<br>
and the community would benefit from your input. Thanks,<br>
<br>
Bill Darte<br>
Policy Shepherd for 2014-2 and<br>
Advisory Council member<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20140221/77d17c87/attachment-0001.html" target="_blank">http://lists.arin.net/pipermail/arin-ppml/attachments/20140221/77d17c87/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 21 Feb 2014 21:20:54 -0800<br>
From: Greg Dendy <<a href="mailto:gdendy@equinix.com">gdendy@equinix.com</a>><br>
To: "North American Network Operators' Group" <<a href="mailto:nanog@nanog.org">nanog@nanog.org</a>>,<br>
"<a href="mailto:nanog-announce@nanog.org">nanog-announce@nanog.org</a>" <<a href="mailto:nanog-announce@nanog.org">nanog-announce@nanog.org</a>>,<br>
"<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>>, "<a href="mailto:ripe-list@ripe.net">ripe-list@ripe.net</a>"<br>
<<a href="mailto:ripe-list@ripe.net">ripe-list@ripe.net</a>><br>
Cc: NANOG Program Committee <<a href="mailto:nanogpc@nanog.org">nanogpc@nanog.org</a>>, "<a href="mailto:board@nanog.org">board@nanog.org</a>"<br>
<<a href="mailto:board@nanog.org">board@nanog.org</a>><br>
Subject: [arin-ppml] NANOG 61 - Bellevue - Call For Presentations is<br>
open!<br>
Message-ID: <<a href="mailto:5A388661-CDD4-4146-9F99-9EFD1ACAE3AE@equinix.com">5A388661-CDD4-4146-9F99-9EFD1ACAE3AE@equinix.com</a>><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
NANOG Community-<br>
<br>
I hope everyone enjoyed NANOG 60, NANOG?s largest attended winter meeting. Fresh off a great meeting, and post our NANOG Icelanta Reception, we are ready start the process for NANOG 61 in Bellevue. NANOG 61 will be NANOG?s 20th year serving the network operator community and helping to make the Internet better. If you have a topic you'd like to speak about, the program committee would love to consider it. Please read <a href="http://www.nanog.org/meetings/nanog61/callforpresentations" target="_blank">http://www.nanog.org/meetings/nanog61/callforpresentations</a> for more information.<br>
<br>
We will continue with the Monday-Wednesday format, with Tracks on Monday and Wednesday afternoons and Tutorials to be scheduled on Tuesday morning. The program will begin on Monday morning at 10:00AM followed by our popular Newcomers Lunch. The exact schedule layout can be found at <a href="http://www.nanog.org/meetings/nanog60/preagenda" target="_blank">http://www.nanog.org/meetings/nanog60/preagenda</a>, please take this into account as you plan travel. If you wish to submit a presentation, please keep these important dates in mind:<br>
<br>
* Presentation Abstracts and Draft Slides Due: April 7, 2014<br>
* Slides Due: May 5, 2014<br>
* Topic List Posted: April 21, 2014<br>
* Agenda Published: May 12, 2014<br>
<br>
Please submit your materials to <a href="http://pc.nanog.org" target="_blank">http://pc.nanog.org</a><<a href="http://pc.nanog.org/" target="_blank">http://pc.nanog.org/</a>>.<br>
<br>
Looking forward to seeing everyone in Bellevue!<br>
<br>
Thanks,<br>
<br>
Greg Dendy<br>
Chair, NANOG Program Committee<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20140221/e08292a6/attachment-0001.html" target="_blank">http://lists.arin.net/pipermail/arin-ppml/attachments/20140221/e08292a6/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sat, 22 Feb 2014 15:06:22 -0800<br>
From: Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>><br>
To: ARIN-PPML List <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: [arin-ppml] 2014-2 8.4 Anti-flip Language<br>
Message-ID: <<a href="mailto:2CB940E2-1465-4FED-A6F3-7172849A90EA@delong.com">2CB940E2-1465-4FED-A6F3-7172849A90EA@delong.com</a>><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Several options are being discussed regarding this proposal:<br>
<br>
1. Use the existing last sentence as is and ask ARIN staff to be particularly watchful for seeming abuse and to bring such back to the community through regular Policy Experience Reports. There was discussion about this option suggesting that by the time abuse was recognized and reported, and given limited existing free pool stocks and the extended policy development cycle....this option is mute.<br>
<br>
2. Remove the clause 'and its subsidiaries' and or modify it in such a way as to mitigate the risk of a laundering of addresses through fraudulent transfers, but potentially limit the utility of organizations who may have complex organizations structures in use internationally.<br>
<br>
3. Take an alternative tack and simply restrict the Inter-RIR re-org transfer of the 'recently issued block' only, allowing other existing blocks to be transferred without restriction by recent block acquisition. This alternative seems to have been expressed and supported in the recent Atlanta Public Policy Consultation.<br>
<br>
It is my opinion that option 3 is perilous in that it allows a large resource holder to sell off their address space out of region while backfilling from the ARIN free pool.<br>
<br>
As such, I am much more comfortable with option 2. One set of language that was suggested which I like is:<br>
<br>
??subsidiaries having been operational for a minimum of 18 months.?<br>
<br>
While this might not prevent all possible subsidiary-based rinse-repeat abuse scenarios, it would at least prevent the obvious subsidiary created for this purpose scenario and certainly provides better protections than proposal number 3.<br>
<br>
I think option 1 is probably an unfair burden for the ARIN staff and makes policy vague in a way that would be difficult, if not impossible, to reliably enforce and may be even harder to defend in the event of litigation. This is strictly my own opinion as a member of the community and I have not discussed the matter with legal council or even the other members of the AC.<br>
<br>
Owen<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20140222/ebff8f89/attachment.html" target="_blank">http://lists.arin.net/pipermail/arin-ppml/attachments/20140222/ebff8f89/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
<br>
End of ARIN-PPML Digest, Vol 104, Issue 41<br>
******************************************<br>
</blockquote></div>