W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: [access-control] Header definitions

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 14 Jan 2009 13:00:43 +0100
To: "Nikunj Mehta" <nikunj.mehta@oracle.com>, public-webapps@w3.org
Message-ID: <op.unqwzhex64w2qv@annevk-t60.oslo.opera.com>

On Mon, 20 Oct 2008 17:32:03 +0200, Nikunj Mehta <nikunj.mehta@oracle.com>  
wrote:
> The headers defined in this specification must be registered with IANA.  
> See permanent [1] managed by IETF under RFC 3864 [2]. Ideally, this  
> specification would have gone to IETF, but it looks like this WG has  
> defined that there is no problem in going ahead with the work in W3C.

The headers are provisionally registered. They will be in the permanent  
registry when the specification reaches a more stable state. Could you  
elaborate on why you think this specification should be done by the IETF?

The reason for doing this work at the W3C is that it has close ties with  
other specifications developed here and the specifications it is intended  
for, e.g. XMLHttpRequest, CSS, and HTML5, are all also at the W3C.


> [1] http://www.iana.org/assignments/message-headers/perm-headers.html
> [2] http://www.rfc-editor.org/rfc/rfc3864.txt



-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Wednesday, 14 January 2009 12:01:34 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:29 GMT