Re: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0

"Conroy, Lawrence (SMTP)" <[email protected]>
Newsgroups gmane.ietf.enum,gmane.ietf.provreg
Message-ID <[email protected]>
Hi Scott, Bernie, folks,
   Hmm...
 From a quick look at the proposed validation EPP extension, this has
b*gg*r all to do with the epp-e164 draft.

This adds a tag for some opaque validation ID, together with a 
registrar ID.
That one, on the other hand, allowed some NAPTR content data to be 
piggy-backed
along with the domain object EPP transaction.

Now, YMMV, but I can understand why validation check data would be used 
in a
domain transaction, whilst I still have no idea why one would want to 
pass zone
content data along with the registration.

There is a reference to the main EPP documents in Bernie's draft, so I 
don't
understand the annoyance either. It must be me.

There have been considerable efforts in testing ENUM around the World 
->for real<-
(i.e. in most places with real delegations in e164.arpa.), and 
Validation Tokens
have been considered at least in those I've been tracking, particularly 
in the UK.

I'm completely unaware of those trials including Zone content in the 
registration
flow, so I'd opine that these extensions are indeed separable.

Whether or not the current validation token proposal is sufficient is 
another matter.

all the best,
   Lawrence


On 24 Sep 2004, at 19:27, Scott wrote:
>> I am looking forward to your comments and proposals for improvement.
>
> <annoyance>
> It's customary to include an acknowledgements section, especially when 
> much
> of the text is clearly copied from earlier work done by someone else.
> </annoyance>
>
> I'll review this in more detail when I have more time, but I'm not 
> sure I
> understand how this can work without also using the ENUM extension [1] 
> I've
> been working on.  Wouldn't an <info> response, for example, also need 
> to
> return the <info> data described in my draft once the domain exists in 
> the
> registry?  At first glance I think there needs to be some text in your
> document explaining the relationship to my document.
>
> -Scott-
>
> [1]
> http://www.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-05.txt

In response to Bernie's announcement mail:
> Hi!
>
> I have just submitted a new I/D: draft-hoeneisen-enum-validation-epp-00
>
> Abstract:
>
>  This document describes an EPP extension for mapping information about
>  the validation process the ENUM Registrar has applied for the E.164
>  number (or number range), which the ENUM domain name is based on.
>  Specified in XML, this mapping extends the EPP domain name mapping to
>  provide an additional feature required for the provisioning of E.164 
> numbers.
>
>
> Until it appears in the archives, you can download it from the 
> following URLs:
>
>   * http://ietf.hoeneisen.ch/draft-hoeneisen-enum-validation-epp-00.txt
>   * 
> http://ietf.hoeneisen.ch/draft-hoeneisen-enum-validation-epp-00.html
>
>
> I am looking forward to your comments and proposals for improvement.
>
> Have fun!
>
> cheers,
>  Bernie
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.