[arin-ppml] FYI -- RIPE-605 Services toLegacyInternetResourceHolders

[John Curran]

On Feb 15, 2014, at 10:10 AM, Steven Ryerse <SRyerse at eclipse-networks.com<mailto:SRyerse at eclipse-networks.com>> wrote:

But real life is that short of congress acting, unless you have 100% of all the large block holders it will never happen. Therefore the prudent action is to accept reality.  Ripe 605 does just that.

Steve -

    It is quite likely that normal market dynamics over time will result in many of
    the underutilized address blocks being transferred and ending up under an
    agreement (in ARIN or another region) - that's precisely what Keith was
    noting in his posting.

    Furthermore, 100% is not necessary and may not be desired by some parties,
    since many legacy address holders probably just want to have their registration
    services and be otherwise undisturbed.  Note that Ripe-605 doesn't actually
    change anything in that respect, in fact, it parallels ARIN's existing practices
    for those without formal agreement -

>From <http://www.ripe.net/ripe/docs/ripe-605> -

"2.6 No relationship
      In case no formal relationship has been established in support of a particular legacy resource, the RIPE NCC

• will continue to provide any registry service element already provided in support of each Legacy Internet Resource involved;
• will have no obligation to begin to provide any registry service element not already provided in support of a particular Legacy Internet Resource, even in case the service element is provided in support of any other Legacy Internet Resource held by the same or another Resource Holder;
• and may update the related entries in the RIPE Database from time to time to correspond to the current actual situation."

    It would be most helpful if you could fully explain the problem you are trying to
    solve, and then which section of RIPE 605 addresses it.   Simply indicating that
    it is prudent (because of lack of 100% LRSA adoption) does not explain why.

Thanks!
/John

John Curran
President and CEO
ARIN



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20140215/6da7e5a1/attachment.htm>