IPv6 Address Planning
Roger Jorgensen
rogerj at jorgensen.no
Mon Aug 15 15:52:43 CEST 2005
On Sun, 14 Aug 2005, Dan Reeder wrote:
>
> > - 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.
it's not really an options, it's the way it is, just accept it.
<snip>
> > - 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.
it don't juts work, the /128, /127, /126 is a good exampe of that, due to
change a /127 isn't usable over night :}
the only way you can be guaranatied it will work are to use /64, or /112
as everyone claim is okay...
---
------------------------------
Roger Jorgensen |
rogerj at stud.cs.uit.no | - IPv6 is The Key!
http://www.jorgensen.no | roger at jorgensen.no
-------------------------------------------------------
More information about the ipv6-ops
mailing list