John, I have forwarded your comments to the appropriate list so that they can be archived. Please look at the ARIN announcement for details concerning these documents. Thanks, Ray
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of John Brown Sent: Monday, September 22, 2003 7:30 PM To: bmanning@karoshi.com Cc: nanog@merit.edu Subject: Re: comments on addressing futures....
YAO (yet another organization)
Seems the world is full of orgs and people wanting to create yet a new thing to solve the problem. Make it a new thing and we can fix the issues at hand.
I've seen enough of the BS between ICANN and ARIN (and other RIR's) to know that if both sides would really sit down and be constructive we wouldn't need YAO..
Now that ICANN has a bunch of new management (ergo LT and MLS are gone) maybe the RIR's and ICANN should put their hurt feeling (yes one hurt badly bruised feeling) away and figure out how to work within the structure that exists today. Ergo the ASO and ICANN
I personally am quite worried about the RIR"s creating a NRO (Is that Number Resource Org, or National Recon Org ??)
I don't see the "broken part here".
I don't see the masses screeming for the head(s) of the RIR on a platter, ala Verisign and wildcards.
I don't see the community pointing the finger en mass to the RIR's and saying ITS BROKE, Someone should take it away from them.
Heck, I don't even see the looneys out there really screaming that the RIR process is broken.
Since it doesn't really seem broken, why are we trying to 'fix' it ??
It does seem to me that a select few people want more control (term empire building comes to mind) of the IP space and for various non-operational (show me broken operational things wrt RIRs) reasons want to kill ICANN.
Killing ICANN in all seriousness isn't the right answer. Some months ago I finally gave up on them, figured it was a lost cause and that they should go the way of the dodo.
Well that was a wrong thought. If we don't have them things will be worse. They DO have to stand up to Verisign on this Wildcard thing, but they can't do it in one day.
Again, we the community should be helping ICANN get its act together.
They are after all trying to hire some senior technical managment people. Certainly there are qualified people on this list to fill that slot.
No, NRO is BAD, its bad like splitting the roots. Plain and simple as that.
On Mon, Sep 22, 2003 at 03:22:47PM -0700, bmanning@karoshi.com wrote:
this from the ARIN-PPL mailing list... it deserves broad
consideration,
even from NANOG :)
-------------------------------------------------------
william@elan.com writes:
Since ARIN has been sending new proposals today, they seem to have forgotten the most important one of all, that applies to all RIRs and how they deal with ICANN. The info is at http://lacnic.net/sp/draft-9-22.html
The four RIRs (Regional Internet Registries): APNIC, ARIN, LACNIC, and RIPE NCC have jointly worked on the preparation of a
-------------------------------------------------------------- --------- proposal concerning
the liaison among the RIRs as well as the structure through which the RIRs and their communities take part in ICANN.
As a consequence, three documents have been prepared:
- Proposal to execute an agreement between the four RIRs in order to create the Number Resource Organization (NRO). This organization will represent the interests of the IP addresses community before the national, international or public entities.
- Proposal of a Memorandum of Understanding between the RIRs, to act through the NRO and the ICANN in relation to the ASO (Address Supporting Organization), the ICANN section committed to the Internet Number Resources issues. The ASO was created through a previous Memorandum of Understanding, signed in 1999. The current proposal would replace the previous Memorandum, modifying the present ASO structure.
- Proposal of an Open Letter from the RIRs to the ICANN relative to the previous items.
The RIRs call for public comments from the community members in relation to these documents. As the comments will be jointly organized, they will be officially managed in English.