[enum-wg] ENUM Trial - Validation Processes of ENUM Registrants

Hi Otmar.

 

Thanks for your comment.

The RFC 4725 states the following: "The actual validation methods applied
may vary depending on, e.g., the particular party, available data sources,
Assignee's choice, and regulatory requirements. Validation methods are out
of scope of this document".

The RFC 5105 describes the ENUM Validation Token sent to the Registry on
successful completion of a validation.

So finally both RFCs are not that much of a help for the validation and
revalidation process between Registrant and the Validation Entity (VE).

 

Do you have currently any entity performing the VE role beyond the actual
telco operators?

 

Thanks again for your help.

 

Cheers.

Miguel Duarte

 

-----Original Message-----
From: Otmar Lendl [mailto:lendl at nic.at] 
Sent: quarta-feira, 1 de Junho de 2011 16:55
To: Miguel Duarte
Cc: enum-wg at ripe.net; gestao at voip.fccn.pt
Subject: Re: [enum-wg] ENUM Trial - Validation Processes of ENUM Registrants

 

On 01.06.2011 13:43, Miguel Duarte wrote:

 

> We are currently conducting an ENUM Trial together with the Portuguese 

> telecoms regulator ANACOM and several other Portuguese 

> telecommunications companies.

> 

> One of our first steps is gathering information about possible 

> validation and revalidation processes of ENUM registrants.

> 

 

> So all experience, implemented scenarios and/or ideas you might want 

> to share/discuss are more than welcome.

> 

 

Have a look at RFC 4725 (and perhaps 5105).

 

Our experience in Austria has been that an ENUM service independent of the
PSTN operator for the phone number has almost no market potential.

 

You need to integrate ENUM in commercial VoIP/phone services. And in that
case, validation is trivial as the ENUM registrar is the same entity that
allocated the number to the customer.

 

otmar

--

// Otmar Lendl < <mailto:lendl at nic.at> lendl at nic.at>, T: +43 1 5056416 - 33,
F: - 933 //

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.ripe.net/ripe/mail/archives/enum-wg/attachments/20110615/a67f504b/attachment.html>