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 ]
Jim Reid
jim at rfc1035.com
Wed Jul 7 09:36:22 CEST 2004
>>>>> "David" == David Malone <dwmalone at maths.tcd.ie> writes: David> The only feedback that I've got so far is from Peter, and David> I've made the changes that he suggested. The last paragraph David> mentions trying to automatically nag someone regarding David> problem servers - I'm not sure if we should be advocating David> this or if we should be saying it is a bad idea. Well if we don't get a consensus on this here, let's put the subject on the agenda for the next WG. We can always ask the meeting for a decision. Personally speaking, I'd support some sort of reminder though not a public naming and shaming. However this opens up a couple of other issues. What happens when there's no response to the email nagging (or whatever)? This is often how lame delegation reports get treated. It might also be sensible to include your AAAA recommendations in RIPE's delegation checks, especially for the new reverse delegation procedure that's being introduced. Perhaps the WG could make a decision about that too.
- 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 ]