Re: [Ietf-message-headers] Permanent or provisional? (was: Jabber-ID header field)

Bruce Lilly <blilly@erols.com> Mon, 02 October 2006 05:23 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUGHD-0007wH-5A; Mon, 02 Oct 2006 01:23:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUGHB-0007w9-CE for ietf-message-headers@ietf.org; Mon, 02 Oct 2006 01:23:37 -0400
Received: from smtp02.lnh.mail.rcn.net ([207.172.157.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUGH9-0002qx-WB for ietf-message-headers@ietf.org; Mon, 02 Oct 2006 01:23:37 -0400
Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 02 Oct 2006 01:23:36 -0400
X-IronPort-AV: i="4.09,242,1157342400"; d="scan'208"; a="312141267:sNHT73489584"
Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.7.5a-GA) with ESMTP id HDN44348; Mon, 2 Oct 2006 01:23:34 -0400 (EDT)
Received: from 24-181-225-106.dhcp.oxfr.ma.charter.com (HELO mail.blilly.com) ([24.181.225.106]) by smtp01.lnh.mail.rcn.net with ESMTP; 02 Oct 2006 01:23:30 -0400
X-IronPort-AV: i="4.09,242,1157342400"; d="scan'208"; a="286297681:sNHT27010808"
Received: from marty.blilly.com (marty.blilly.com [192.168.99.98]) by mail.blilly.com with ESMTP id k925NRFt004041(8.13.6/8.13.6/mail.blilly.com /etc/sendmail.mc.mail 1.28 2006/06/11 04:26:23) (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) ; Mon, 2 Oct 2006 01:23:27 -0400
Received: from marty.blilly.com (localhost [127.0.0.1]) (authenticated (0 bits)) by marty.blilly.com with ESMTP id k925NPD9004040(8.13.6/8.13.6/blilly.com submit.mc 1.3 2005/04/08 12:29:31) (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) ; Mon, 2 Oct 2006 01:23:26 -0400
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
To: ietf-message-headers@ietf.org
Subject: Re: [Ietf-message-headers] Permanent or provisional? (was: Jabber-ID header field)
Date: Mon, 2 Oct 2006 01:23:07 -0400
User-Agent: KMail/1.9.4
References: <45071704.6020400@jabber.org> <451C528C.2680@xyzzy.claranet.de> <451CE474.9030604@ninebynine.org>
In-Reply-To: <451CE474.9030604@ninebynine.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <200610020123.14093@mail.blilly.com>
X-Junkmail-Status: score=10/50, host=mr08.lnh.mail.rcn.net
X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090206.4520A234.0008,ss=1,fgs=0, ip=207.172.4.11, so=2006-05-09 23:27:51, dmn=5.2.113/2006-07-26
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sic <ietf-message-headers@lists.ietf.org>
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

On Fri September 29 2006 05:16, Graham Klyne wrote:
> [This message is more about reviewing RFC3864 than the specific Jabber-id header]
> 
> Frank Ellermann wrote:
> >> Why not start with registration in the provisional registry
> > 
> > Permanent and RFC is better for MUA implementors.
> 
> Sure, ...
> 
> But, in general, I note that requesting a provisional registration in no way
> precludes moving later to a permanent registration.
> 
> And the barrier for provisional registration being so much lower (this the
> Jabber-ID draft would be sufficient), it's easy to get a record of its intended
> purpose published where developers can find it.  I would expect that a header
> destined for the standards track would be provisionally registered pretty much
> as soon as it is first published.

Agreed so far.

> In this case, it looks as things might move quite quickly, so going straight for
> the permanent registry saves some administration.

I'm not so sure -- there seem to be a significant number of issues that need
to be resolved; at minimum, starting with provisional would give interested
parties an opportunity to work out the bugs before moving to permanent, while
reserving the field name.

> I'd like to think it can be 
> done as soon as IESG approves the draft for standards-track publication.  Hmmm,
> checking [http://www.rfc-editor.org/rfc/rfc3864.txt]:
> 
> [[
>       The assignment policy for
>       such registration is "Specification Required", as defined by RFC
>       2434 [3], where the specification must be published in an RFC
>       (standards-track, experimental, informational or historic), or as
>       an "Open Standard" in the sense of RFC 2026, section 7 [1].
> ]]
> 
> That text is a bit limiting... maybe also add ", or has been approved for such
> publication".

As 3864's primary co-author, you are of course in a better position than I am
to interpret the intent of 3864 as written.   That said, I read it as "RFC first
(with all of the discourse and review required for that), then assignment".
Indeed, all but two of the existing Internet Message Format field assignments in
the permanent registry are for fields which have long been defined in published
RFCs.

[The converse is another story; RFC 4021 omitted a number of RFC-defined fields.
Draft-lilly-legacy-fields is (was?) an attempt to resolve some of those, but it
seems to have gotten bogged down...  Those who look at the archive or who have
been watching this list since its inception may recall that that draft was
written in April 2005 as announced here.]

The case under discussion here differs from all of those legacy fields.  It is
also somewhat of a test case, as it appears to be the first non-legacy field to
be discussed on this list [Martin Duerst made an inquiry nearly seven months ago,
but that seems to have evoked no discussion].  I think the discussion is good; a
number of relevant issues have been raised.  Compare that to the two new Internet
Message Format fields that have been registered in the permanent registry without
discussion here; neither is particularly useful and both have either syntax or
semantics problems that might have been resolved had the fields been discussed
here.

> Looking over the text I'd also be inclined to indicate more explicitly that the
> IESG also has discretion to approve registration of any entry in the permanent
> registry, to avoid potential wrangling over such small points.

"Discretion to approve" is fine, but there still needs to be an approved open
specification and a registration template.

BCP 90 (RFC 3864) also says that the registration templates should be sent to this
discussion list (section 4.3) or incorporated in a defining RFC.

Given the aforementioned issues, I'd prefer to see discussion here required even
if the registration template is (presumably subsequently) published in a defining
RFC.

_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers