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 ]

Jan Zorz @ go6.si jan at go6.si
Tue Jul 19 18:49:32 CEST 2011

On 7/19/11 6:45 PM, Ivan Pepelnjak wrote:
> 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.

Exactly. And I see no point in changing that. To be perfectly honest, 
you could use link-local for CPE to core communication, but that's 
another discussion.

What we are trying to prevent is ISPs assigning /64 as PD to customers 
instead of /56 or /48.

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