On Tue, 2008-12-30 at 08:49 +1300, Jasper Bryant-Greene wrote:
On 30/12/2008, at 7:56 AM, Joe Abley wrote:
> Am I missing something, or is enum a nice technical solution which
> can, almost by definition, never be deployed?
enum itself can easily be deployed: there's no
reason an alternative
enum registry couldn't be built under e164.*.nz without needing any
permission from anyone.
You're correct, it can be easily deployed - I had a test bed e.164 zone
while I was doing some work on ENUM a few years ago. There is also a
shared secondary domain that anyone can register phone numbers in:
I haven't registered any zones in e164.org
yet - my crappy ADSL router
locks up whenever I do ENUM lookups over it (but DNSSEC works, go
figure). A replacement is on the cards.
The only drawback is that software wouldn't be
preconfigured to look
there, but how much software already looks at 4.6.e164.arpa anyway? I
don't work with VoIP every day, so maybe e164 has been widely deployed
while I wasn't looking, but I'd be surprised...
Most software that I've played with can be told which zone (or multiple
zones) to look in. If you're used ENUM for internal call routing for a
PBX then you'll have an internal zone as well as e164.arpa (or
Wellington, New Zealand
At home: andrew(a)etc.gen.nz | This space intentionally
| left blank.