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] AAAA lookup misbehaviour
- Previous message (by thread): [dns-wg] AAAA lookup misbehaviour
- Next message (by thread): [dns-wg] AAAA lookup misbehaviour
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jaap Akkerhuis
jaap at NLnetLabs.nl
Wed Sep 8 14:38:51 CEST 2004
So, other than the hall of shame, what options do we have to encourage people to fix their software? Call the Internet Police :-). Effectively, there are not a lot of options other than make the problem know, Working with vendors of DNS solutions is certainly a good idea, and the dns-wg's name could be useful when convincing vendors to take action. Publishing a Ripe document identifying the problem and the solutions there to might help to convince the RIPE members to take action; have this in the RIPE course material where appropriate (LIR course ?); bring it under attention of the IPv6 working group and other IPv6 groups. Another possibility would be to recommend that when problem DNS servers are found, then they should be considered lame and so dropped from the advertised list of NSs for a zone. Recommend to who? To the parent is I guess your answer. We are dabbling into policy space here if you don't watch it (expecially when the parent is "." :-). Any other ideas? Call the local papers :-). No, honestly, publisch it. You might ask Ole whether he thinks it is useful for the Protocol Journal. jaap
- Previous message (by thread): [dns-wg] AAAA lookup misbehaviour
- Next message (by thread): [dns-wg] AAAA lookup misbehaviour
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]