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]/
[address-policy-wg] 2008-05 Anycast for DLV zones
- Previous message (by thread): [address-policy-wg] 2008-05 Anycast for DLV zones
- Next message (by thread): [address-policy-wg] 2008-05 Anycast for DLV zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Mon Jun 22 13:11:12 CEST 2009
* Jim Reid: > It is. Compare and contrast the effort needed to setup DLV (and make > it work) on a DNS server with that needed for an ENUM lookup. Now do > the same thing for on-going maintenance and administration of both > technologies. Why this discussion has popped up in address-policy-wg > and not dns-wg is "interesting".... You claimed that ENUM is a critical service and therefore deserves special treatment as far as addressing policy is concerned. I think this is just wishful thinking. ENUM (in the public e164.arpa tree) hasn't got a significant user base. Certainly, it's not critical Internet infrastructure, and so it doesn't need special treatment for address allocation. -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- Previous message (by thread): [address-policy-wg] 2008-05 Anycast for DLV zones
- Next message (by thread): [address-policy-wg] 2008-05 Anycast for DLV zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]