nanog mailing list archives
Re: Using /126 for IPv6 router links
From: Grzegorz Janoszka <Grzegorz () Janoszka pl>
Date: Tue, 26 Jan 2010 18:22:25 +0100
On 26-1-2010 1:33, Owen DeLong wrote:
- "Waste" of addresses - Peer address needs to be known, impossible to guess with 2^64 addressesMost of us use ::1 for the assigning side and ::2 for the non-assigning side of the connection. On multipoints, such as exchanges, the popular alternative is to use either the BCD of the ASN or the hex of the ASN for your first connection and something like ::1:AS:N for subsequent connections.
If you have shared racks with different customers within, you can use 16 or 32 bits out of 64 as customer ID, allowing the customer to use the rest, so in fact giving him trillions (possible) IP's for one server. It can be use with autoconfiguration which always has FF:FE in the middle - you just use some other bits here for your customer assignments. Thus you identify a customer just by looking at the IP address.
-- Grzegorz Janoszka
Current thread:
- Re: Using /126 for IPv6 router links, (continued)
- Re: Using /126 for IPv6 router links Dale W. Carder (Jan 27)
- Re: Using /126 for IPv6 router links David Barak (Jan 28)
- Re: Using /126 for IPv6 router links Igor Gashinsky (Jan 28)
- Re: Using /126 for IPv6 router links Bill Stewart (Jan 29)
- Re: Using /126 for IPv6 router links Leo Bicknell (Jan 25)
- Re: Using /126 for IPv6 router links Owen DeLong (Jan 25)
- Re: Using /126 for IPv6 router links Christopher Morrow (Jan 25)
- Re: Using /126 for IPv6 router links Mark Smith (Jan 26)
- Re: Using /126 for IPv6 router links David Barak (Jan 26)
- Re: Using /126 for IPv6 router links Mark Smith (Jan 26)
- Re: Using /126 for IPv6 router links Grzegorz Janoszka (Jan 26)
- Re: Using /126 for IPv6 router links Owen DeLong (Jan 26)