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] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
- Previous message (by thread): [dns-wg] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
- Next message (by thread): [dns-wg] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Thu Jul 15 15:32:45 CEST 2004
>>>>> "Niall" == Niall O'Reilly <Niall.oReilly at ucd.ie> writes: Niall> OTOH, there's a balance to be struck between allowing Niall> people to be responsible for their own mistakes and Niall> engaging in the diminishing-returns game of protecting them Niall> from everything. Indeed. And in this case, sharp instruments need to be kept well away from the children. That means avoiding some of the obvious rat-holes when it comes to DNS administration. Note too Niall that lots of ISPs can't get RFC2317-style delegation right and these are the guys who should have DNS skills as a core competency. Niall> If registrars or T2 registries can't do their job, how long Niall> will they stay in business ? Long enough to kill off ENUM by making it seem less robust and dependable than it could be? Consumer confidence is going to be critical for ENUM to become widely used. Cheap calls over VoIP may get everyone's attention. But if DNS lookups fail and phones don't ring reliably, nobody's going to use it.
- Previous message (by thread): [dns-wg] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
- Next message (by thread): [dns-wg] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]