At 13:14 17/07/2003 +1200, James Spooner wrote:
I would assume we could get this done initially with private v6 ranges and then look toward getting a publicly routable range. However, in order to link back into the rest of the world someone would be required to put up bandwidth to do this and as such, it would be unfair to expect them to carry all the costs for everyone (hence a system to apportion cost, i.e - a billing system)
A point to consider here is that there _is no such thing_ as a 'private' IPV6 range in my understanding. When we began peering over MetaNet we used Freenet as an address broker, whether or not we intended on keeping our links to freenet active, as it was the only (somewhat) permenant way of getting addresses that other people arn't using.
the fe{c,d,e,f}x are reserved as site-local ranges and (according to the FAQ) were likened to the RFC1918 address space. [quote] 3.2.2. Site local address type These are addresses similar to the http://www.faqs.org/rfcs/rfc1918.htmlRFC 1918 / Address Allocation for Private Internets in IPv4 today, with the added advantage that everyone who use this address type has the capability to use the given 16 bits for a maximum number of 65536 subnets. Comparable with the 10.0.0.0/8 in IPv4 today. Another advantage: because it's possible to assign more than one address to an interface with IPv6, you can also assign such a site local address in addition to a global one. It begins with: fecx: <- most commonly used. fedx: feex: fefx: (where "x" is any hex character, normally "0") [/quote] taken from: http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/x479.html as such, I'd suggest possibly playing with these for a start and then working upward once people are familiar with the fact that a 128bit IP address is pretty much the same as a 32 bit one with more bits.. -- Steve.