[Enum] [IANA #171390] FW: Revision of IANA Enumservice registry
"Michelle Cotton via RT" <iana-issues@icann.org> Wed, 15 October 2008 15:06 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 9BECC28C219; Wed, 15 Oct 2008 08:06:20 -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 93A093A6B01 for <enum@core3.amsl.com>; Tue, 14 Oct 2008 08:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level:
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 RekfMpgbUN6n for <enum@core3.amsl.com>; Tue, 14 Oct 2008 08:52:41 -0700 (PDT)
Received: from request.iana.org (request.iana.org [208.77.188.221]) by core3.amsl.com (Postfix) with ESMTP id 333293A6ACA for <enum@ietf.org>; Tue, 14 Oct 2008 08:52:41 -0700 (PDT)
Received: from request.iana.org (localhost.localdomain [127.0.0.1]) by request.iana.org (8.13.8/8.13.8) with ESMTP id m9EFpk3u014933; Tue, 14 Oct 2008 08:51:46 -0700
Received: (from apache@localhost) by request.iana.org (8.13.8/8.13.8/Submit) id m9EFpkxT014932; Tue, 14 Oct 2008 15:51:46 GMT
From: Michelle Cotton via RT <iana-issues@icann.org>
In-Reply-To: <rt-3.8.1-24868-1223642846-1100.171390-7-0@icann.org>
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>
Message-ID: <rt-3.8.1-23393-1223999506-238.171390-7-0@icann.org>
Precedence: bulk
X-RT-Loop-Prevention: IANA
RT-Ticket: IANA #171390
Managed-by: RT 3.8.1 (http://www.bestpractical.com/rt/)
RT-Originator: michelle.cotton@icann.org
MIME-Version: 1.0
X-RT-Original-Encoding: utf-8
Date: Tue, 14 Oct 2008 15:51:46 +0000
X-Mailman-Approved-At: Wed, 15 Oct 2008 08:06:19 -0700
Cc: enum@ietf.org, marc.blanchet@viagenie.ca, simon.perreault@viagenie.ca
Subject: [Enum] [IANA #171390] FW: Revision of IANA Enumservice registry
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: iana-issues@icann.org
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
Bernie, 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 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? - 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 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. - 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. - Some old-style registrations have no registration document. - Some old-style registrations have no type. On Fri Oct 10 12:47:26 2008, bernie@ietf.hoeneisen.ch wrote: > Hi Michelle > > Ist is feasible to get an example XML chunk by TODAY so that we > can work on it during the weekend? (see also below) > > cheers, > Bernie > > ---------- Forwarded message ---------- > > 1) > > > If someone writes a document to add a new registration to the enum- > services > > registry, it would be great if they included in their document an > XML chunk > > that IANA would simply cut and paste in the registry itself after > the > > registration is approved. The spec itself does not have to be in > XML. > > If you provide us with an example, we'd be more than happy to include > an XML > chunk to -13. (See also 5) further below) > > [...] > > 5) > > > Also, for the document, having the xml chunk for the registration > itself > > would be very useful. We can help with providing what that should > look like > > as we convert the registry in the next few weeks. > > As the IANA template of the Enumservice registry is about to change, I > recommend to wait. > > draft-hoeneisen-enum-enumservices-transition-01 is addressing these > changes for > the existing services. If we get an example of an XML chunk, we'll > publish a > revision of the enumservices-transition I-D, which will include all > existing > registrations (including the template changes) as XML chunks. > _______________________________________________ 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