[address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy

gert at space.net (Gert Doering) wrote:

> Microallocations are PI in disguise - end users get address space directly
> from a RIR.  If that's not PI, then what else is?

Actually, the people (who argue to be) in need of v6 microallocations do not
care what the baby is called. And there's no valid presumption they are not
LIRs already. But AFAIR there's still a 200-customer problem which an end
site (RIR-wise) cannot solve.

Nonetheless they want to multihome, and they want to _really_ multihome,
being that anycast instances are usually scattered all over the globe.
This implies that there must be a way to get a (however big) routable
block that's unlikely to be filtered - well, the proposal has it all.

And frankly, I do not care whether it's a /32, /35, /48 or /64, as long
as it's accepted and (if </32) well-known. Swamp anyone? ;-)

Local multihoming with a PA /48 from one of the transits, and informing
the other transits of it, has not been a problem yet (at least, not for us).

Elmar.

--

"Begehe nur nicht den Fehler, Meinung durch Sachverstand zu substituieren."
                          (PLemken, <bu6o7e$e6v0p$2 at ID-31.news.uni-berlin.de>)

--------------------------------------------------------------[ ELMI-RIPE ]---