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 ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Mon Jun 22 14:08:07 CEST 2009
Florian Weimer wrote: > I think this is just wishful thinking. ENUM (in the public e164.arpa > tree) hasn't got a significant user base. FYI, ENUM concept to let callee side, who won't pay calling fee, determine the internet-PSTN gateway is broken from the beginning. Telcos managing telephone numbers of callees will, as a default gateways of callees, choose the most profitable (which is likely to be unnecessarily expensive to callers) gateway for the telcos and callees will be uninterested in the choice. ENUM could be fixed, if access telcos only are allowed to be delegated ENUM records and the telcos are forced to have gateways from which all subscribers of the telco can be reached at least expensive rate. Still, ENUM is not a very interesting concept. > Certainly, it's not > critical Internet infrastructure, and so it doesn't need special > treatment for address allocation. True. Just as PSTN does not need public IP addresses, the Internet does not need E.164 addresses. Masataka Ohta
- 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 ]