On Tue, 10 Jul 2007, james woodyatt wrote:
<snip>
Hmmm. I guess the alternative is that the purpose of ULA-C/G is to mitigate
the risk of collision when merging on the order of hundreds of thousands of
ULA networks in one routing realm... sort of like creating a "local DFZ" of a
sort.
Forgive me, but that sounds even more surreal. It's tough for me to imagine
how a real organization doing that could fail to qualify for a PI allocation,
or why such an organization would find it unacceptable to have to use a PI
allocation without advertising it to the public DFZ. Likewise, it's tough to
imagine how an organization that doesn't qualify for a PI allocation could be
merging enough ULA networks together that the risk of collision rises to a
level of any real significance.
Okay. Maybe the problem with PI allocations for this purpose is that
organizations doing all this network merging, i.e. extraordinarily paranoid
organizations, e.g. the Communist Party, want some kind of assurance from the
operators of the public Internet that their hundreds of thousands of local
networks aren't directly reachable from the public DFZ in the event a local
NOC configures a border router improperly. Obviously, ULA-C can do that
better than PI.
Is that the big driving factor here?
PI can be used for almost everything ULA-C/G can be used for, dont think
anyone disagree on that. The whole ULA-C/G is about the purpose of the
address space and what it can be used for both now and in the future.
Strictly internal/private networking right now and ID/LOC or whatever in
the future... or other thing we dont know about.
It is more about creating a address space that can be used for OTHER thing
than the DFZ-way of thinking Internet we have now.
And yes you have a good point, internal infrastructure like the above
operator but that is almost excacly what we (where I work) want to use it
for! .. just that we will also place some of our customers there to.
(and please dont start the rant about NAT or whatever we need to get them
onto internet because they are not suppose to be conneted directly to
internet)
--
------------------------------
Roger Jorgensen | - ROJO9-RIPE - RJ85P-NORID
[EMAIL PROTECTED] | - IPv6 is The Key!
-------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
