Avri, On Sep 12, 2014, at 3:46 AM, Avri Doria <avri@acm.org> wrote: > Both of the contentful, if somewhat derisive, answers sort of skirted > the questions by telling me anyone can use any numbers they want. Actually, no derisiveness nor skirting of answers intended. Apologies if that was the impression. > I am asking about whether they can register numbers that are within the > current set of number that IANA + the RIRs call the Internet (using > legacy v4 and not yet assigned v6 allocations) . As I pointed out in my message, yes they can. The primary requirement is justifying a need for those addresses. > Not a separate private net of some sort. That is well known. Not private nets. Perhaps you misunderstood my point. Let me try it a different way. Suppose an entity with non-trivial market presence (could be a company or a country) decided they wanted to make use of (say) 3000::/6. They would start announcing that prefix to the ISPs they peer/transit with. Some (sadly, not all) of those ISPs would likely say “That prefix is not yours. Stop that!”. If that entity cared enough, they could probably sit down with those ISPs and negotiate bilateral agreements (e.g., “we’ll pay you $X million if you propagate that prefix” or “if you don’t propagate that prefix, you can’t access our zillions of customers.”) that would ensure customers of those ISPs would be able to send/receive traffic to 3000::/6. End result: 3000::/6 has been effectively “allocated” without _any_ recourse to IANA+RIRs. ICANN’s Board or the RIRs could stomp their feet and say “hey, that’s a violation of policy” but ultimately, what _really_ matters is what the ISPs of the world do/don’t do. The service ICANN and the RIRs provide is a way of short-circuiting the need for every ISP in the world to do that bilateral negotiation. > I find the answer that if you prove you need them then IANA will give the v6 addresses interesting. To be clear, under current policy the IANA Internet Numbering function can only allocate to RIRs. Regards, -drc
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail