Important IPv6 Policy Issue -- Your Input Requested

Thu Nov 11 16:01:41 UTC 2004

On Thu, 2004-11-11 at 09:36 -0600, Adi Linden wrote:
<SNIP>

> > Having to NAT RfC1918 addresses to reach the internet, does not imply
> > that I have to have RfC1918 to be able to do NAT.
> 
> What are my options today to obtain ip address space? My requirements are
> well met by a /27 subnet. ARIN won't give me a globally unique /27 for
> personal use. So the /27 comes from my service provider, which has several
> caveats. I cannot multi-home. I cannot keep my address space when changing
> providers. I most likely cannot keep my address space moving to a
> different city but staying with the same provider.

A /27 will be nicely filtered out at most ISP's anyway, thus it doesn't
make sense to announce that in the global routing table and adding
another useless entry,

A /27 contains at most 32 hosts (even less when doing proper broadcast
etc), thus I don't see the problem in renumbering there actually ;)

Unfortunately not everybody is big enough to play along in the big
routing game. If you where a big enough fish you would also be able to
get a nice spot in the routing tables, but you will need to have at
least a /24 at the moment...

I guess you also want to announce a /64 into the IPv6 BGP tables ?
Everybody else would want to, and then we have to expand to 32bit ASN's,
hey wait IPv4 is 32bit, and then we are using 32bit ASN's to route IPv6,
thus basically we are using the IPv4 addresses to route IPv6, there is a
limit somewhere I hope ;) Though as long as we keep with 16bit ASN's
there should not be a huge problem as long as every ASN only announces
one prefix, then we would be at 65k prefixes maximum, which is 1/3rd of
the current IPv4 space. Currently there are only ~650 prefixes in the
IPv6 global routing tables, thus it can grow a bit for some while.

Greets,
 Jeroen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 240 bytes
Desc: This is a digitally signed message part
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20041111/2df5d9d4/attachment.sig>