This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg at ripe.net] What is a site?
- Previous message (by thread): [ipv6-wg at ripe.net] What is a site?
- Next message (by thread): [ipv6-wg at ripe.net] What is a site?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Mon May 9 13:16:48 CEST 2005
On 9-mei-2005, at 13:05, Gert Doering wrote: >> host1 host2 >> +---------------+ +--------------------+ | / >> |ISP dial-up box+-ppp-+customer dial-up box+---customer subnet >> +---------------+ +--------------------+ | \ >> host4 host3 > This is not the scenario where /128 would be used for. Right, I got the /64 and /128 problems mixed up. The above shows that a /64 is problematic. :-) But how would a /128 work? > +---------------+ +---------------------+ > |ISP dial-up box+-ppp-+customer dial-up HOST+ > +---------------+ +---------------------+ Stateless autoconfiguration only works on /64s because it needs a 64 bit interface identifier. DHCPv6 would probably not work either, because the router and the local address need to share a subnet.
- Previous message (by thread): [ipv6-wg at ripe.net] What is a site?
- Next message (by thread): [ipv6-wg at ripe.net] What is a site?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]