Re: [apps-discuss] Accept-Post HTTP header field

Graham Klyne <gk@ninebynine.org> Thu, 08 May 2014 07:14 UTC

Return-Path: <gk@ninebynine.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7DB1A010A for <apps-discuss@ietfa.amsl.com>; Thu, 8 May 2014 00:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xsAIYKvWw0os for <apps-discuss@ietfa.amsl.com>; Thu, 8 May 2014 00:14:31 -0700 (PDT)
Received: from relay12.mail.ox.ac.uk (relay12.mail.ox.ac.uk [129.67.1.163]) by ietfa.amsl.com (Postfix) with ESMTP id 2920F1A0032 for <apps-discuss@ietf.org>; Thu, 8 May 2014 00:14:31 -0700 (PDT)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay12.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <gk@ninebynine.org>) id 1WiIXB-0004SJ-d7; Thu, 08 May 2014 08:14:25 +0100
Received: from 94.197.120.224.threembb.co.uk ([94.197.120.224] helo=[192.168.43.120]) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <gk@ninebynine.org>) id 1WiIXA-0002qo-8j; Thu, 08 May 2014 08:14:25 +0100
Message-ID: <536B2ECA.4050804@ninebynine.org>
Date: Thu, 08 May 2014 08:14:18 +0100
From: Graham Klyne <gk@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Erik Wilde <dret@berkeley.edu>
References: <53697AD6.2030504@berkeley.edu>
In-Reply-To: <53697AD6.2030504@berkeley.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/8exGHsRkLsWbSo47qhlKsnmgnwg
Cc: Steve K Speicher <sspeiche@us.ibm.com>, John Arwe <johnarwe@us.ibm.com>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, Arnaud Le Hors <lehors@us.ibm.com>
Subject: Re: [apps-discuss] Accept-Post HTTP header field
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 08 May 2014 07:14:33 -0000

Eric,

If the W3C spec is published on REC track, that would be sufficient to allow 
permanent registration in the header field registry (W3C being a "recognized 
standards organization" for this purpose).  Until it gets to REC track 
publication, I'd suggest going for an interim provisional registration.

Assuming this is a REC track specification, my suggestion would be, rather than 
going the RFC publication route, to include the registration template in an IANA 
consideration section in the W3C spec, and cite that in a request to IANA when 
the document is W3C-approved for CR/PR/REC publication. Also, notify the IANA 
header field discussion list (and maybe IETF apps-discuss) when the document 
goes to last call at the W3C.

#g
--


On 07/05/2014 01:14, Erik Wilde wrote:
> hello.
>
> http://www.w3.org/TR/ldp/#header-accept-post (the "Linked Data Platform") is a
> current W3C document in last call WD status, and it introduces/uses the
> Accept-Post header field proposed in a current draft:
>
> http://tools.ietf.org/html/draft-wilde-accept-post
>
> we have publicized this proposed header field on this list, and the latest draft
> also includes a list of known implementations of this header field:
>
> http://tools.ietf.org/html/draft-wilde-accept-post-02#section-6
>
> after making the specification available for a while, and listing known
> implementations, we are wondering about next steps. what it would take to get
> this draft moving towards an experimental RFC (apart from some references that
> will need to be updated).
>
> thanks a lot and kind regards,
>
> dret.
>