IPv6 Address Planning

[Dan Reeder]

> - it's inconvenient because you need to do (some) binary math to 
> determine which addresses go together. With a /124 you can use the  last 
> digit for this, so that's easier

easy to do in php, which is what the web-based tunnelbroker is built on in 
the first place - simple.

> - doesn't accommodate for the 128 reserved anycast addresses, but a / 120 
> does

why is there a need for anycast on a peer-to-peer link? there should be no 
data on that link except data sent specifically from one end to the other.

> - you need to keep track of which router has which address. with  eui-64 
> addressing and a /64 you don't (whether this is useful depends  on whether 
> you need to refer to the other side's address elsewhere.  for customers 
> you generally do to route their /48 or what have you to  them, for 
> internal stuff you don't, routing protocols take care of it)

not required in a ptp link, with all references to the routing for the two 
addresses (/128) and the end user allocation (/48) in question already taken 
care of by php, mysql, and quagga.

Honestly folks, talk about storm in a teacup. Its logical, its simple, 
nothing is broken: it just works.

Dan

----- Original Message ----- 
From: "Iljitsch van Beijnum" <iljitsch at muada.com>
To: "Dan Reeder" <dreeder at ipv6.net.au>
Cc: <ipv6-ops at lists.cluenet.de>
Sent: Saturday, August 13, 2005 9:43 PM
Subject: Re: IPv6 Address Planning


> On 13-aug-2005, at 13:34, Dan Reeder wrote:
>
>> the /126 is between the the customer and the isp. Two usable  addresses 
>> for the point to point.
>
> Actually it's three usable addresses.  :-)
>
> You can't use the all-zeros address because it's supposed to be the 
> subnet all-routers anycast address, but the all-ones address is fair 
> game.
>
>> The customer gets a /48 assigned to them to do whatever they want.
>> You ask why /126? I ask you: why not?
>
> Since you ask...
>
> - it's inconvenient because you need to do (some) binary math to 
> determine which addresses go together. With a /124 you can use the  last 
> digit for this, so that's easier
>
> - doesn't accommodate for the 128 reserved anycast addresses, but a / 120 
> does
>
> - you need to keep track of which router has which address. with  eui-64 
> addressing and a /64 you don't (whether this is useful depends  on whether 
> you need to refer to the other side's address elsewhere.  for customers 
> you generally do to route their /48 or what have you to  them, for 
> internal stuff you don't, routing protocols take care of it)
>
>
>