Re: [Uri-review] draft-larmouth-oid-iri-02

Alfred Hönes <ah@TR-Sys.de> Sun, 11 October 2009 19:54 UTC

Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0B7D3A6808 for <uri-review@core3.amsl.com>; Sun, 11 Oct 2009 12:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.851
X-Spam-Level: ***
X-Spam-Status: No, score=3.851 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
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 4l8ju+8A4OSu for <uri-review@core3.amsl.com>; Sun, 11 Oct 2009 12:54:32 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id B87FB3A681B for <uri-review@ietf.org>; Sun, 11 Oct 2009 12:53:01 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA214840557; Sun, 11 Oct 2009 21:49:17 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id VAA16553; Sun, 11 Oct 2009 21:48:01 +0200 (MESZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <200910111948.VAA16553@TR-Sys.de>
To: j.larmouth@btinternet.com
Date: Sun, 11 Oct 2009 21:48:00 +0200
In-Reply-To: <4AD22269.10103@btinternet.com> from John Larmouth at Oct "11, " 2009 "07:22:33" pm
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 8bit
Cc: uri-review@ietf.org
Subject: Re: [Uri-review] draft-larmouth-oid-iri-02
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Oct 2009 19:54:33 -0000

John,
firstly, ACK for the -02
which has appeared in the archives in the meantime!


John Larmouth wrote:

> Thanks for this Ira - I will go for "provisional".

I do not believe that this makes much sense, since the 'oid'
URI/IRI Scheme registration is based on ITU-T Recommendations,
which should be considered a rather stable reference with much
support behind it.  -- Or did I overlook something?


>
> I guess I do not need to refer to Graham by name.

Indeed; unlike for URN Namespace ID registrations, RFC 4395 has
made the Designated Expert for URI Scheme review a subsidiary of
IANA (page 10, item 3 of 2nd blocj of steps in section 5.2:
    "IANA requests Expert Review ..."

So the basice step is forwarding the registration document
(or the registration template with a pointer to the draft)
to IANA (loc. cit.)

> Roughly how long would it take for this to get convered to
> "permanent" (assuming that the "provisional" gets approved")?
>
> It seems to depend on it being conververted to a full RFC, which
> sometimes seems to take a long time.  What would be an optimistic
> and a pessimistic estimate, assuming no major objections?
>
> (Just to help with our planning.)

I guess the effort for a later 'upgrade' would be the same
as for a direct attempt to get "permanent" registration.

Independent of the target status, IMO publication as an RFC
would be very useful to have a stable document that can be
referenced, and thus should be attempted.

I expect that one of your aim is to make the 'oid' URI scheme
available for (normative) use in future IETF Standards.
In this case, as far as I can see a Standards Track RFC would be
needed anyway, to avoid the creation of normative downreferences!

Thus, it might even be attractive to immediately try Standards Track.
That would not exclude using the current draft as a registration
document for "provisional" in the interim, and pursuing its
publication as an RFC in parallel.

To go for Proposed Standard, an AD would have to initially support
the draft and ususally personally 'shepherd' it through the IESG,
including the IETF Last Call (LC) procedure.
Thus, support by the responsible AD would be essential.

You should preferably seek early advice from the responsible APP Area
Director (AD), which I assume will be Lisa Dusseault (otherwise she
certainly will quickly refer to her co-AD, Alexey Melnikov).

Note: The most recent contact information for all IESG members ist
  listed on <http://www.IETF.ORG/iesg/members.html> .

The AD may be able to also give you a more realistical estimation
of the time needed for approval as Proposed Standard, given current
workload of the AD and the entire IESG, -- of course only in the
absence theoretically possible significant objections from the IETF
at large, during LC.

Should problems arise, stepping back to a less rigid procedure,
to arrive at a lower level, will be easier than to entirely restart
with a 'higher-grade' procedure .

>
> Thanks.
>
> John L
>
> ...


Kind regards,
  Alfred Hönes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+