Re: [Enum] [IANA #171390] FW: Revision of IANA Enumservice registry
"Alexander Mayrhofer" <alexander.mayrhofer@nic.at> Wed, 15 October 2008 15:16 UTC
Return-Path: <enum-bounces@ietf.org>
X-Original-To: enum-archive@megatron.ietf.org
Delivered-To: ietfarch-enum-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B28128C246; Wed, 15 Oct 2008 08:16:13 -0700 (PDT)
X-Original-To: enum@core3.amsl.com
Delivered-To: enum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 368943A692A for <enum@core3.amsl.com>; Wed, 15 Oct 2008 08:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.229
X-Spam-Level:
X-Spam-Status: No, score=-9.229 tagged_above=-999 required=5 tests=[AWL=0.202, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g7TvCn01Du4e for <enum@core3.amsl.com>; Wed, 15 Oct 2008 08:16:11 -0700 (PDT)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [192.174.68.200]) by core3.amsl.com (Postfix) with ESMTP id 393BC28C236 for <enum@ietf.org>; Wed, 15 Oct 2008 08:15:36 -0700 (PDT)
Received: from localhost [127.0.0.1] by mail.sbg.nic.at with XWall v3.43 ; Wed, 15 Oct 2008 17:15:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 17:15:44 +0200
Message-ID: <8BC845943058D844ABFC73D2220D466507AA50D3@nics-mail.sbg.nic.at>
In-Reply-To: <rt-3.8.1-23393-1223999506-238.171390-7-0@icann.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Enum] [IANA #171390] FW: Revision of IANA Enumservice registry
Thread-Index: Acku18N3iWr3lV0xR2aIIryp5eHEggAAGwfQ
References: <RT-Ticket-171390@icann.org><alpine.DEB.0.82.0810101444180.11471@GIC-VDL-228-151.as16215.net><rt-3.8.1-24868-1223642846-1100.171390-7-0@icann.org> <rt-3.8.1-23393-1223999506-238.171390-7-0@icann.org>
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: iana-issues@icann.org
X-XWALL-BCKS: auto
Cc: enum@ietf.org, marc.blanchet@viagenie.ca, simon.perreault@viagenie.ca
Subject: Re: [Enum] [IANA #171390] FW: Revision of IANA Enumservice registry
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: enum-bounces@ietf.org
Errors-To: enum-bounces@ietf.org
> The XML chunk for the new version of the registry is not > quite completed yet but we are working to > have that done. We need some help answering some questions > to help transition from the current > registry to the revised registry. See below. > > Please let me know if I've missed something. We've been > exchanging lots of information and I want to > make sure that I'm not missing anything. Michelle, i'm one of the co-authors of the document. Please find my responses inline: > Here is a list of questions that must be answered before we > can convert > to the new style (i.e. draft-ietf-enum-enumservices-guide): > > - In the old style, registrations have a "Service Name". This > is absent > in the new style. It isn't clear if this is intentional. If so, do we > remove the column or do we leave it as optional? Please remove the column. It was never really specified, and the ENUM WG decided to remove it - it does not have any additional value. > - I'm having trouble understanding the following instruction from > Section 11.1.3: > > Each Enumservice starts with a caption, which is composed > of Type and > Subtype, separated by a colon; e.g. if the Type is "foo" and the > Subtype "bar", the resulting caption is "foo:bar". > > Do we need to create a new column such as the following? > > +---------------+--------+----------+-... > | Caption | Type | Subtype | > +---------------+--------+----------+-... > | "ifax:mailto" | "ifax" | "mailto" | > +---------------+--------+----------+-... > | ... | ... | ... | No, this is not needed for the registration - This was intended as a "display headline" for the registration. The "caption" can be created from Type and Subtype, as indicated in the text above. > - No registration in the old style have an "Enumservice > Class". This is > required in the new style. What do we do? Some ideas: > - Go to authors of old-style registrations and ask them to > define one. > - Assuming all previous registrations belong to the same > class, assign > this class. > - Make the class optional in the schema and trust IANA editors to > provide one for new registrations. This reduces the schema's > bug-catching power. We are working on a draft that assigns such Class information to all existing Enumservices - see http://tools.ietf.org/html/draft-hoeneisen-enum-enumservices-transition- 01 > - This note in Section 5.2 seems to contradict current IANA practices: > > Note: You MUST NOT put email addresses in the authors > field of an > IANA Registration. > > Does this mean one of the following? > - There will be no registration contact info. > - There will be separate columns "Author" and "Registrant", > the latter > containing contact info. > - Contact info is expected to be extracted from the > registration document. > - The note should be revised. Contact info is expected to be expected from the registration document. Please indicate if there are other preferences. > - Some old-style registrations have no registration document. Should be fixed by the transition draft. > - Some old-style registrations have no type. huh? Can you name one? thanks, Alex _______________________________________________ enum mailing list enum@ietf.org https://www.ietf.org/mailman/listinfo/enum
- [Enum] No IANA feedback for draft-ietf-enum-enums… Bernhard.Hoeneisen
- Re: [Enum] No IANA feedback for draft-ietf-enum-e… Jaap Akkerhuis
- Re: [Enum] [IANA #197380] No IANA feedback for dr… Bernhard.Hoeneisen
- [Enum] [IANA #171390] FW: Revision of IANA Enumse… Michelle Cotton via RT
- Re: [Enum] [IANA #171390] Revision of IANA Enumse… Bernie Hoeneisen
- Re: [Enum] [IANA #171390] Revision of IANA Enumse… Bernie Hoeneisen
- [Enum] [IANA #171390] FW: Revision of IANA Enumse… Michelle Cotton via RT
- Re: [Enum] [IANA #171390] FW: Revision of IANA En… Alexander Mayrhofer
- Re: [Enum] [IANA #171390] FW: Revision of IANA En… Simon Perreault
- Re: [Enum] [IANA #171390] Revision of IANA Enumse… Bernie Hoeneisen
- [Enum] [IANA #171390] FW: Revision of IANA Enumse… Michelle Cotton via RT
- Re: [Enum] [IANA #171390] FW: Revision of IANA En… Bernie Hoeneisen
- [Enum] [IANA #171390] FW: Revision of IANA Enumse… Michelle Cotton via RT