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] IPv6 Prefix delegation BCOP version 3 is out...

• Previous message (by thread): [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...
• Next message (by thread): [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...

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

Rob Evans rhe at nosc.ja.net
Thu Jul 27 17:58:20 CEST 2017

This highlighted something for me…

>> If we decide to use /127 for each point to point link, then it is also advisable to
>> allocate a /64 for each link and use just one /127 out of it to prevent the Neighbor Discovery
>> exhaustion attack (RFC6583).

The document could do with a pass by a good copy-editor (“we” is probably not the right language for a BCP).  Is that something ISOC could arrange if you’re facilitating the BCOPs? :-)

Cheers,
Rob

• Previous message (by thread): [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...
• Next message (by thread): [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...

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

[ ipv6-wg Archives ]