[james woodyatt]

The purpose of ULA-C/G, as near as I can tell, is to mitigate the risk of
an already vanishingly low probability collision--  ...
[Paul Vixie]
nope.
[james woodyatt]
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.

Perhaps you haven't read or understood what I've written previously. The purpose of ULA-G is to allow RIRs to allocate private address space in a non-discriminatory manner to organizations who wish to use it outside of the DFZ. As stated previously, the rules for getting PI space are based on the expectation that PI blocks can be announced into the DFZ. The proposed rules for ULA-G space are based on the expectation that ULA-G blocks will not be announced into the DFZ, and that they will be allocated out of a single global netblock, identified in an RFC, that everyone knows can and should be filtered. As stated quite clearly by Joe Abley in the "Why ULA-* will not harm the DFZ" thread, that difference in expectation, and ease in filtering when desired or necessary, makes it possible to give out ULA-G space in a non-discriminatory manner (which is simply not prudent for PI space today).


-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to