[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Private use of non-RFC1918 IP space
- Subject: Private use of non-RFC1918 IP space
- From: joelja at bogus.com (Joel Jaeggli)
- Date: Sun, 08 Feb 2009 23:42:18 -0800
- In-reply-to: <!&!AAAAAAAAAAAYAAAAAAAAAN5U5OuspydJheQZRk7Gfl7CgAAAEAAAABvCc9jLo4lEhdLwPQCHQGcBAAAAAA==@skeeve.org>
- References: <[email protected]> <[email protected]> <[email protected]> <!&!AAAAAAAAAAAYAAAAAAAAAN5U5OuspydJheQZRk7Gfl7CgAAAEAAAABvCc9jLo4lEhdLwPQCHQGcBAAAAAA==@skeeve.org>
Skeeve Stevens wrote:
> Owned by an ISP? It isn't much different than it is now.
>
> As long as you are multi-homed you can get a small allocation (/48),
> APNIC and ARIN have procedures for this.
>
> Yes, you have to pay for it, but the addresses will be yours, unlike
> the RFC1918 ranges which is akin to 2.4Ghz wireless.. lets just share
> and hope we never interconnect/overlap.
>
> I can't find a RFC1918 equivalent for v6 with the exception of
> 2001:0DB8::/32# which is the ranges that has been assigned for
> documentation use and is considered to NEVER be routable. In that
> /32 are 65536 /48's... way more than the RFC1918 we have now.
FD00::/8
ula-l rfc 4139
> If I was going to build a v6 network right now, that was purely
> private and never* going to hit the internet, and I could not afford
> to be a NIC member or pay the fees... then I would be using the
> ranges above.... I wonder if that will start a flame war *puts on
> fire suit*.