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 ]

rodolfo.garciapenas at telefonica.es rodolfo.garciapenas at telefonica.es
Tue Jul 19 15:46:48 CEST 2011

ipv6-wg-admin at ripe.net escribió el 19/07/2011 15:29:19:

> 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.

http://www.ripe.net/training/material/IPv6-for-LIRs-Training-Course/IPv6-for-LIRs-Training-Slides.pdf
 (page 65)

> jan
>

• 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 ]