[Ietf-message-headers] HTTP header registration question

"Anne van Kesteren" <annevk@opera.com> Thu, 27 September 2007 12:06 UTC

Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ias89-0005UP-WB; Thu, 27 Sep 2007 08:06:10 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43) id 1Ias89-0005UG-Cz for ietf-message-headers-confirm+ok@megatron.ietf.org; Thu, 27 Sep 2007 08:06:09 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43) id 1Ias89-0005TM-0Z for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 08:06:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IarwG-0003Fh-A2 for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 07:53:52 -0400
Received: from sam.opera.com ([213.236.208.81]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iarw9-0003Yr-Tn for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 07:53:52 -0400
Received: from annevk-t60.oslo.opera.com (c5144430c.cable.wanadoo.nl [81.68.67.12]) (authenticated bits=0) by sam.opera.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l8RBrcXW008155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf-message-headers@lists.ietf.org>; Thu, 27 Sep 2007 11:53:39 GMT
Date: Thu, 27 Sep 2007 13:53:40 +0200
To: ietf-message-headers@lists.ietf.org
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software ASA
Content-Type: multipart/mixed; boundary=----------78YV1ita77pK5c7z83nEm3
MIME-Version: 1.0
Message-ID: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
User-Agent: Opera Mail/9.21 (Linux)
X-Virus-Scanned: ClamAV 0.91.1/4411/Wed Sep 26 21:43:35 2007 on sam.opera.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
X-TMDA-Confirmed: Thu, 27 Sep 2007 08:06:08 -0400
Cc:
Subject: [Ietf-message-headers] HTTP header registration question
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

Hi,

For a W3C specification "Enabling Read Access for Web Resources" the W3C  
WAF WG would like to register three HTTP headers: Access-Control,  
If-Method-Allowed, and Referer-Root (sic). Can I do that as attached or is  
it preferable to have three separate templates? Also, does the  
specification itself need to include anything that points back to the  
header registry, does it need to include the template, etc.? This did not  
became clear from reading RFC 	3864. Thanks for the information!

Kind regards,


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers