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
smime.p7s
Description: S/MIME Cryptographic Signature
