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

[dns-wg] NCC reverse delegation criteria

Previous message (by thread): [dns-wg] NCC reverse delegation criteria
Next message (by thread): [dns-wg] NCC reverse delegation criteria

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

Antonio Prado antonio at prado.it
Wed Jun 12 21:46:21 CEST 2019

On 6/11/19 11:10 PM, Jonas Frey wrote:
> This whole BCP (whatever that includes in detail) is nowhere
> documented. 

hi,

to be honest there is a meaningful BCP about the topic: RFC 5358, BCP
140, Preventing Use of Recursive Nameservers in Reflector Attacks.

under "Recommended configuration" paragraph: In general, it is a good
idea to keep recursive and authoritative services separate as much as
practical.

--
antonio

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: </ripe/mail/archives/dns-wg/attachments/20190612/00858142/attachment.sig>

Previous message (by thread): [dns-wg] NCC reverse delegation criteria
Next message (by thread): [dns-wg] NCC reverse delegation criteria

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

[ dns-wg Archives ]