You are here: Home > Participate > Join a Discussion > Mailman Archives
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: FW: ENUM test registrar operational

  • To: "FOUQUART Philippe FTRD/DAC/ISS" < >
  • From: Michael Haberler < >
  • Date: Thu, 27 Feb 2003 11:24:48 +0100

Dear Philippe,

in a sense, the whole DNS as it stands now is outside the golden tree... .com, .net, .at and all...

You will surely agree that testing software in isolated environments is a good thing. Crash test dummies save our lives in a similar way.

So, e164.at is the crash test dummy for the SOFTWARE DEVELOPERS. It is an isolated environent, because nobody except a software developer will refer to it. It is not intended to be used for OPERATIONAL purposes.

Once the software (clients, switches, gateways, proxies, whatever) works, operators will configure them to use the golden tree because they want the stuff to WORK - as you rightly observe there is no interoperability between e164.at and e164.arpa, therefore no working service and hence no money to be made.

-Michael


At 11:04 27.02.2003 +0100, FOUQUART Philippe FTRD/DAC/ISS wrote:

> Finally we may set up in .at what we want, this is a national issue
> (BTW, did you complain about e164.com from netnumber?). So you may use
> it or leave it, at your discretion ;-)

Hi Richard,

I think we're all aware that initiatives outside the so-called golden
tree can't be prevented but I didn't understand Marco's point this way.
I have indeed the same difficulty in understanding how we can on one
hand promote "interoperability of European ENUM trials" and on the other
set up something that can jeopardise consistency of Enum data in these
trials.

Could you please clarify?

Best,

Philippe Fouquart
FTR&D/DAC/CAR
+33 (0) 1 45 29 58 13


-----Original Message-----
From: Stastny Richard [
] Sent: Thursday, February 27, 2003 10:43 AM To: bill; Marco Bernardi Subject: RE: ENUM test registrar operational Hi Bill and Marco, this is just a test domain for client designers and developers, kind of a playground. Since we have a lot of client developers out of Austria (e.g. UK and US), and since they cannot get an 3.4.e164.arpa entry because they do not have a phone number in Austria, and since they also cannot get an entry in their own country, but want on the other hand to modify their NAPTR records on their own for testing purposes, we have set up this domain. This domain will NEVER go into commerical service and is also NOT intended as competition to e164.arpa (you do not have to explain this to me), and may and will be shut down at any time. Finally we may set up in .at what we want, this is a national issue (BTW, did you complain about e164.com from netnumber?). So you may use it or leave it, at your discretion ;-) regards Richard > -----Original Message----- > From: bill [
] > Sent: Thursday, February 27, 2003 10:27 AM > To: Marco Bernardi > > Subject: Re: ENUM test registrar operational > > > Is there any necessity to set up such a domain for ENUM trial? It is > not in the golden tree, I think. > > -bill > > 2003/02/27 > > > > All, > > > > > > our ENUM test registrar at http://enum.nic.at/registrar/ is now > > > operational for the test domain "e164.at" (in terms that if you > > > register a domain there, it shows up in the public DNS tree). > > > > > > Note: There's no support yet for the "official" e164.arpa- > > Domain. We > > > will add support for at least 3.4.e164.arpa soon. > > > > > > Current features: You may add (nearly) any number (even > numbers with > > > non-existing country codes), activate the according > e164.AT domain, > > > and put NAPTR records into that domain using the supplied web > > > provisioning interface. Records and domains may be > deleted again as > > > well, contact information may be added to the registered numbers. > > > > > > Your feedback is as always welcome. Please contact me if you > > have any > > > questions, or if you find any bugs. > > > > > > cheers > > > > > > Alex Mayrhofer > > > > > >

  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>