[c-nsp] smaller PI

[tkapela at gmail.com]

Kinda OT for c-nsp, but I'll suggest:

-get an ipv6 allocation today, and maybe one day it'll be useful

-do not assume even /24 will be "uniquely reachable" in the DFZ, as this wasn't and isn't 100% true

-if the point of the exercise is to get an end-user site multihomed, explore other non-PI addressing options; many effective solutions exist for using coordinated PA space behind private-AS peerings via multi-providers without the need for a RIR allocation

-if the point is to have PI space for its own sake sake, or the "independence" it's thought to have or provide, then something larger is required. Special agreements could be saught for "size exemption" within a few transit providers' AS's to accept the route, which may provide some sort of access potential, however limited. I don't think anyone here can help change RIPE policy in a time scale approaching useful, so a commercial solution is indicated.

-Tk

-----Original Message-----
From: Jan Gregor <jan.gregor at chronix.org>
Sender: cisco-nsp-bounces at puck.nether.net
Date: Wed, 30 Jun 2010 14:39:43 
To: <pete.barnwell at whole.net.uk>
Cc: cisco-nsp at puck.nether.net<cisco-nsp at puck.nether.net>
Subject: Re: [c-nsp] smaller PI

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/