Re: Enumservice registrations

Hi Lawrence

Thanks for sharing your view on the Enumservice registration process wrt. 
draft-goix-appsawg-enum-sn-service-00.txt. And thanks Rich for spotting 
this I/D and forwarding it to the ENUM list.

It appears to me that the authors simply have not read RFC 6117 too 
thoroughly, and therefore don't follow the RFC-6117-process.

However, I am not worried at this point in time, as the I/D is a -00 
individual submission. Furthermore, before any Enumservice advances, it 
has to go through my hands, and I will ensure each proposal gets 
sufficient community review (in particular ENUM community), before any 
decision is made. Thus, not-follow-the-process simply results in delay, 
which the authors otherwise could avoid.

Should I happen to meet the authors in Paris, I'll talk to them about 
this.

I hope this addresses your concerns.

cheers,
  Bernie, IESG Designated Expert for ENUM


PS: And no, we are not intending to update RFC 6117 any time soon... ;-)

--

http://ucom.ch/
Tech Consulting for Internet Technology


On Sat, 3 Mar 2012, Lawrence Conroy wrote:

> Hi esteemed AD, ENUMers,
> As a process issue:

> - Section 4.1 of RFC6117 suggests that authors of Enumservices should 
> look for existing work in the Enum mailing list.
> - Section 6.3 of RFC6117 states that authors MUST send a mail to the 
> enum list with a link to the registration doc.
>
> In the current case, Richard forwarded the id-announce mail for 
> draft-goix-appsawg-enum-sn-service-00.txt to the list; the authors have 
> not.
>
> So ...
> Can someone ensure at least that I-Ds for Enumservices are 
> ALWAYS/Automatically sent to the enum mailing list? (i.e., if it's an 
> Enumservice, the enum mailing list is an interested party)
>
> The application detail for Enumservices may well be covered in other 
> WGs, but there must be a link the ENUM mailing list. Otherwise 6117 
> needs an update -- please, no!
>
> all the best,
>  Lawrence
>
> _______________________________________________
> enum mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/enum
>