Re: [apps-discuss] draft-saintandre-xdash-considered-harmful-01

Graham Klyne <GK@ninebynine.org> Tue, 26 October 2010 11:15 UTC

Return-Path: <GK@ninebynine.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 093EE3A694A for <apps-discuss@core3.amsl.com>; Tue, 26 Oct 2010 04:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.348
X-Spam-Level:
X-Spam-Status: No, score=-6.348 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 11wx4Uhc+70e for <apps-discuss@core3.amsl.com>; Tue, 26 Oct 2010 04:15:30 -0700 (PDT)
Received: from relay3.mail.ox.ac.uk (relay3.mail.ox.ac.uk [163.1.2.165]) by core3.amsl.com (Postfix) with ESMTP id 7E48D3A6938 for <apps-discuss@ietf.org>; Tue, 26 Oct 2010 04:15:30 -0700 (PDT)
Received: from smtp1.mail.ox.ac.uk ([129.67.1.207]) by relay3.mail.ox.ac.uk with esmtp (Exim 4.71) (envelope-from <GK@ninebynine.org>) id 1PAhWl-0005xC-BF; Tue, 26 Oct 2010 12:17:15 +0100
Received: from tinos.zoo.ox.ac.uk ([129.67.24.47]) by smtp1.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1PAhWl-0007Ia-3l; Tue, 26 Oct 2010 12:17:15 +0100
Message-ID: <4CC693BE.7050302@ninebynine.org>
Date: Tue, 26 Oct 2010 09:39:26 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "Thomson, Martin" <Martin.Thomson@andrew.com>
References: <201010212030.WAA26704@TR-Sys.de> <DFFD2700-C4DF-4256-BA20-03C45F5BAB54@standardstrack.com> <4CC4D9D3.2060003@att.com> <0077AC96FF0947F4AE87DFA7@PST.JCK.COM> <3F3180D3-2925-47E9-92FD-3ED11FAD6D34@standardstrack.com> <8B0A9FCBB9832F43971E38010638454F03F31EAE5F@SISPE7MB1.commscope.com> <4CC608C4.8040209@stpeter.im> <8B0A9FCBB9832F43971E38010638454F03F31EAE68@SISPE7MB1.commscope.com>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F03F31EAE68@SISPE7MB1.commscope.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635@OX.AC.UK
Cc: Discuss Apps IETF <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] draft-saintandre-xdash-considered-harmful-01
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Oct 2010 11:15:32 -0000

Thomson, Martin wrote:
> A provisional registration would be similar to IP-R.  The only different is that two people can compete for the same name with IP-R; provisional registrations still have exclusivity.

Actually, for message headers they don't:

[[
    The main requirements for a header field to be included in the
    provisional repository are that it MUST have a citable specification,
    and there MUST NOT be a corresponding entry (with same field name and
    protocol) in the **permanent** header field registry.
]]
-- http://tools.ietf.org/html/rfc3864#section-4.2 (note my ** emphasis).

>>> * An standards track registration - or something similarly strong -
>>> causes existing registrations for the same name get swept away.  The
>>> review process can determine if this is appropriate.
>> Fun. :)
> 
> Can you think of a better reason?

FWIW:
[[
    When a new entry is recorded in the permanent message header field
    registry, IANA will remove any corresponding entries (with the same
    field name and protocol) from the provisional registry.
]]
-- http://tools.ietf.org/html/rfc3864#section-4.3

(The main point here, as I recall, was that the provisional registry can't be 
used to make an unsupported "land grab" on the namespace:  community review trumps.

#g
--