Hi John,

That RFC 2050 stuff is just FUD.

I was saying that Plzak declared in court that ARIN's policies did not apply to legacy space. But you have said that they do. On the other hand, RIPE ERX has been transferable without need because of its legacy status.

The statement you extracted was tangential and distracting to the needs-based discussion. It was made simply in the context of demonstrating that such a needs-free market has existed for some time without evidence of speculation.

If I were to re-write it, I would leave you out, since I am guilty of the same distraction.

Regards,
Mike


-----Original Message----- From: John Curran
Sent: Monday, June 09, 2014 2:55 PM
To: Mike Burns
Cc: Owen DeLong ; [email protected]
Subject: Re: [arin-ppml] About needs basis in [email protected] List ([email protected]);

On Jun 9, 2014, at 2:36 PM, Mike Burns <[email protected]> wrote:

What's more, like ARIN's previous CEO and unlike ARIN's current CEO, RIPE never took the position that RIPE policy applies to legacy space.

Mike -

Your statement is factually incorrect in multiple ways; you probably are unaware that adherence to the needs-based assignment criteria for purpose of transfers actually originates in RFC 2050 ("INTERNET REGISTRY IP ALLOCATION GUIDELINES"), dated November 1996 (and before my involvement in the Internet registry system.) The document authors are staff from RIPE, APNIC, and InterNIC and assert it to be an accurate representation of the current practice of the IP address registries
at that time.  From <http://tools.ietf.org/rfc/rfc2050.txt> -

"   7.  The transfer of IP addresses from one party to another must be
      approved by the regional registries.  The party trying to obtain
      the IP address must meet the same criteria as if they were
      requesting an IP address directly from the IR."

When the ARIN community developed an explicit transfer policy, the more recent community set policy took precedence. The needs-based requirements in NRPM 8.3
remain in place because the ARIN community has not seen to remove them; i.e.
they are under the control of this community via the policy development process
and that has little to do with the staff or Board views on this matter.

FYI,
/John

John Curran
President and CEO
ARIN
_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to