[ppml] draft-ietf-ipv6-ula-central-02.txt use cases

[Stephen Sprunk]

Thus spake "Scott Leibrand" <sleibrand at internap.com>
>> which wouldn't be nec'y if both of these networks were in some
>> new kind of PI space that was allocated out of a prefix designated
>> by IANA for non-DFZ use.  (i keep bringing the discussion back
>> to that point because asking IANA to designate such a prefix
>> ought to be the IETF's reaction to the ULA-C draft.)
>>
>> but i still digress, let's get to the meat of it:
>
> I'm not sure this is a digression.  What you're describing is
> exactly what I think ULA-C should be: a well-known block (that
> DFZ operators would filter announcements from) from which PI
> assignments can be made without the restrictions required on
> public PI space to avoid routing table bloat.

If this is what we mean by "private PI", then I'm against that too. 
Dressing up ULA-C with a different prefix and name but retaining all of the 
operational stupidity doesn't solve any problems.    A turd by any other 
name smells just as foul.

If we want to issue address space to folks for "private" use, it needs to be 
out of the same block(s) that the RIRs use to allocate space for "public" 
use, because sooner or later those "private" networks are going to end up 
being publicly routed.

If we are concerned that giving "real" PI space to every org that asks for 
it will result in the immediate death of the DFZ, then there needs to be 
some sort of tag attached to blocks that says whether or not the registrant 
has met whatever the current rules are for deserving a routing slot.  If 
routing certificates ever take off, they could contain a flag that gives the 
current public routability status, or the RIR could just not issue a 
certificate at all if someone hasn't met the bar.  That's an entirely 
separate matter from whether or not they get addresses.

One could also argue that the RIRs do not belong in the routability decision 
path at all, since their job is to ensure uniqueness, and some other 
quasi-public entity responsible for the health of the DFZ would produce 
"routability" certificates.  That also gives rise to the possibility of 
different models than we have today, like a market where people could buy 
and sell routing slots.

S

Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov