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

Graham Klyne <GK@ninebynine.org> Mon, 25 October 2010 20:10 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 1D84D3A68E8 for <apps-discuss@core3.amsl.com>; Mon, 25 Oct 2010 13:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.147
X-Spam-Level:
X-Spam-Status: No, score=-6.147 tagged_above=-999 required=5 tests=[AWL=0.452, 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 myjY1pTXZfeN for <apps-discuss@core3.amsl.com>; Mon, 25 Oct 2010 13:09:59 -0700 (PDT)
Received: from relay6.mail.ox.ac.uk (relay6.mail.ox.ac.uk [163.1.2.167]) by core3.amsl.com (Postfix) with ESMTP id 025613A67B3 for <apps-discuss@ietf.org>; Mon, 25 Oct 2010 13:09:59 -0700 (PDT)
Received: from smtp0.mail.ox.ac.uk ([129.67.1.205]) by relay6.mail.ox.ac.uk with esmtp (Exim 4.71) (envelope-from <GK@ninebynine.org>) id 1PATOR-0008V5-LJ; Mon, 25 Oct 2010 21:11:43 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=Eskarina.local) by smtp0.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1PATOR-0001mo-0r; Mon, 25 Oct 2010 21:11:43 +0100
Message-ID: <4CC5E45C.6080505@ninebynine.org>
Date: Mon, 25 Oct 2010 21:11:08 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Andrew Sullivan <ajs@shinkuro.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> <4CC5CF18.1070606@ninebynine.org> <20101025190249.GZ45134@shinkuro.com>
In-Reply-To: <20101025190249.GZ45134@shinkuro.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Cc: 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: Mon, 25 Oct 2010 20:10:00 -0000

Hi Andrew,

Thanks for explaining this perception.

The "citable specification" does not have to be an RFC - any document, e.g., on 
the web would do (though I tend to remind registrants that that internet drafts 
time out after 6 months).

So it seems the problem is with interpretation of "citable specification".  It 
was not intended to be restricted to "formally citable specifications" or 
suchlike, just something that could be referenced and retrieved by anyone.

This should be easily fixable.  Or is there a deeper problem?

#g
--

Andrew Sullivan wrote:
> On Mon, Oct 25, 2010 at 07:40:24PM +0100, Graham Klyne wrote:
>> I keep wondering why RFC3864 [1] isn't more visible in this discussion:  
>> provisional registration is cheap and easy.  Where's the problem here 
>> that I'm not seeing?
>>
>> [[
>>    The main requirements for a header field to be included in the
>>    provisional repository are that it MUST have a citable specification,
>                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> People have come to think that getting an RFC actually published is
> hard, probably because we have made it hard.  For people who aren't
> used to the IETF, simply publishing something here is like being
> nibbled to death by ducks.
> 
> Note that I-Ds aren't citable specifications, according to the process
> rules.
> 
> A
>