[Ietf-message-headers] Re: HTTP header registration question

Anne van Kesteren wrote:

> 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?

The given specification apparently only covers Access-Control
in an "Editor Draft".  Do you plan to add the other two later
in your draft ?

Maybe use three separate templates for the submission to IANA,
after the two weeks review here, less chances that something
goes wrong.  

For status: standard you have to wait until the specification
actually is a W3C standard.  You could use status: provisional
before, and later send an update to IANA when it's a standard.

> Also, does the specification itself need to include anything
> that points back to the header registry

No.

> does it need to include the template, etc.?

Of course it can, but that's more interesting for IETF RFCs:

IANA has a seat in the IESG, and can so check what they're
supposed to do before an IETF RFC is approved by the IESG.

BTW, your draft uses the ugly RFC 2616 "LWS" construct.
Maybe check with the 2616bis folks what they intend to do
with "LWS".  The 2616bis list is ietf-http-wg @ w3.org 

 Frank 

(I like your text/xml flame, Olivier hit me with it on the
 validator list ;-)

_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers