On 16/02/2012 16:35, Martin Millnert wrote:
You seem to want me to believe that:
- there is a fixed set of networks, who are going to deploy either:
- a sucky IPv4 network, or,
- a less sucky IPv4 network,
- it would be entirely depending on the passing of this draft,
- the failure of passing of this draft somehow will exclude from these
networks the possibility of obtaining non-RFC1918 space in another way,
for example as I outlined
The latter two points seem a bit far-fetched.
Martin,
Far-fetched - like all straw men.
I'm curious how you can possibly have sufficient knowledge to make those
statements as *facts*, rather than opinions, informed as the may be (but
of limited scope -- I think it unlikely you've spoken to every network
on the planet).
More straw men. Look, we're adults here: please present good arguments.
The bottom line for this ID is that address space will be required for CGN,
and rfc1918 doesn't cut it for reasons described in the ID. This means
that the address space must come from somewhere else. The choices are:
1. one or more shared pools allocated by RIRs/IANA/whatever
2. private pools, each of which come from the carriers' own address blocks
option #1 is by definition more efficient than #2.
At least one of the RIRs has indicated that they cannot assign this space
due to charter problems.
There is no particular reason to allocate this space on a regional basis,
unless for some reason you believe that you can force carriers only to use
this shared address space for specific purposes - and I cannot see why you
think that this is remotely feasible for shared address space. Private
address space, perhaps. But certainly not shared address space.
The core function of a RIR is to guarantee that if they allocate you a
bunch of numbers, that they haven't allocated the same bunch of numbers to
someone else. Therefore by definition they have no particular authority
over the way that shared address space might be used internally by a carrier.
Incidentally, I support this draft.
Nick
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf