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] Solving lameness in the reverse zones
- Previous message (by thread): [dns-wg] Solving lameness in the reverse zones
- Next message (by thread): [dns-wg] Solving lameness in the reverse zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Fri Oct 23 12:11:56 CEST 2009
Michael, On Thu, 2009-10-22 at 17:22 -0500, Michael Graff wrote: > Are lame delegations really such a problem that we need to take drastic > action? How often would this be checked, and how much liability would > be here in modifying what is published? I'd hate to see the papers when > a large content provider lost due to a temporary outage on one name > server... This approach is based on the assumption that lameness is in itself a problem, and must be fixed. Also note that we are talking about the reverse DNS in this case, so nobody is going to lose revenue if we a delegation is removed. -- Shane
- Previous message (by thread): [dns-wg] Solving lameness in the reverse zones
- Next message (by thread): [dns-wg] Solving lameness in the reverse zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]