Re: [Enum] Enumservice registrations

Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Sat, 03 March 2012 13:06 UTC

Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: enum@ietfa.amsl.com
Delivered-To: enum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18BA21F874F; Sat, 3 Mar 2012 05:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqeeM6iWPkg6; Sat, 3 Mar 2012 05:06:45 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by ietfa.amsl.com (Postfix) with ESMTP id DCFA921F8749; Sat, 3 Mar 2012 05:06:44 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.71) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1S3ofZ-0002w0-Ll; Sat, 03 Mar 2012 14:06:41 +0100
Date: Sat, 03 Mar 2012 14:06:41 +0100
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: Lawrence Conroy <lconroy@insensate.co.uk>
In-Reply-To: <2A45B5D5-FEAD-4813-96D3-55FA757ADD8C@insensate.co.uk>
Message-ID: <alpine.DEB.2.00.1203031330090.9676@softronics.hoeneisen.ch>
References: <2A45B5D5-FEAD-4813-96D3-55FA757ADD8C@insensate.co.uk>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Cc: IETF ENUM list <enum@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [Enum] Enumservice registrations
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/enum>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 13:06:46 -0000

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
> enum@ietf.org
> https://www.ietf.org/mailman/listinfo/enum
>