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] additional IPv6 allocation (ripe-512 issues)

Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ivan Pepelnjak ipepelnjak at gmail.com
Tue Jul 19 18:45:07 CEST 2011

No, you don't. The only protocol that needs /64 is SLAAC.

/64 on the connection is a __BEST PRACTICE__ (allowing CPE router to use SLAAC), no more, no less.

> -----Original Message-----
> From: ipv6-wg-admin at ripe.net [mailto:ipv6-wg-admin at ripe.net] On Behalf Of
> rodolfo.garciapenas at telefonica.es
> 
> > On 7/19/11 3:22 PM, Ivan Pepelnjak wrote:
> > > Don't pull ND into this discussion. How do you make subnets smaller
> > > than /64 work on Ethernet links between Cisco routers?
> > >
> > > SLAAC does depend on /64.
> >
> > Discussion was end user assignments, not r2r connection segments.
> 
> IMHO, the remote router could be the customer xDSL router. And you need a
> */64* for the link.

Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]