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/[email protected]/
[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 ]
Jan Zorz - Go6
jan at go6.si
Thu Jul 27 18:19:49 CEST 2017
On 27/07/2017 17:58, Rob Evans wrote: > 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? :-) Hey, Thnx for this comment. Usually (RIPE-501, 554, 631) RIPE NCC staff does the language check and fine-tunes the grammar before publishing the document (and we are more than grateful for that ;) ) I hope that this will be true also in this case... Cheers and thnx, Jan -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3976 bytes Desc: S/MIME Cryptographic Signature URL: </ripe/mail/archives/ipv6-wg/attachments/20170727/a9b9b686/attachment.p7s>
- 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 ]