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/dns-wg@ripe.net/
[dns-wg] DNS Misbehavior Doc
- Previous message (by thread): [dns-wg] DNS Misbehavior Doc
- Next message (by thread): [dns-wg] DNS Misbehavior Doc
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Olaf M. Kolkman
olaf at NLnetLabs.nl
Tue Feb 21 13:18:50 CET 2006
On Feb 6, 2006, at 10:14 PM, David Malone wrote: > o prevent introducing more DNS servers with such issues, testing > of new DNS equipment should include checking that the response for > records is in accordance with the RFCs (in particular [RFC1035], > [RFC3597] and [RFC4074] mentioned above). Hmmm... I'd say this recommendation is a little to "narrow". For IPv6 misbehavior these 3 RFCs are probably sufficient but there are also other DNS extensions that new implementations should be able to deal with. Most particular the middleboxes like load balancers should know about protocol extensions such as EDNS0 and DNSSEC. I understand that this document is IPv6 specific but maybe being a little more generic here might help implementors to realize they have to do more. --Olaf ----------------------------------------------------------- Olaf M. Kolkman NLnet Labs http://www.nlnetlabs.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 227 bytes Desc: This is a digitally signed message part URL: </ripe/mail/archives/dns-wg/attachments/20060221/9c045cce/attachment.sig>
- Previous message (by thread): [dns-wg] DNS Misbehavior Doc
- Next message (by thread): [dns-wg] DNS Misbehavior Doc
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]