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] 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 ]
Niall O'Reilly
Niall.oReilly at ucd.ie
Thu Jul 15 13:48:11 CEST 2004
On 15 Jul 2004, at 11:07, Jim Reid wrote: > Another problem -- which won't apply to someone clueful like you -- is > that the introduction of CNAMEs increases the likelihood of looping or > very long CNAME chains. Or dangling CNAMEs that point at nothing. Even > without these administrative errors, the introduction of CNAMEs will > complicate ENUM lookups and could mean they take too long. This would > be somewhat annoying when someone picks up their ENUM-aware phone, > dials a number and then waits for an eternity while the resolver > chases down umpteen CNAME chains before making a phone ring. IMO it's > best not to give people access to that much rope to hang themselves. OTOH, there's a balance to be struck between allowing people to be responsible for their own mistakes and engaging in the diminishing-returns game of protecting them from everything. If registrars or T2 registries can't do their job, how long will they stay in business ? Best regards, Niall O'Reilly UCD Computing Services
- 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 ]