W3C home > Mailing lists > Public > public-html@w3.org > December 2008

Re: http-equiv

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 23 Dec 2008 01:03:11 +0000 (UTC)
To: Julian Reschke <julian.reschke@gmx.de>
Cc: "public-html@w3.org" <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0812230102160.24109@hixie.dreamhostps.com>

On Sat, 20 Dec 2008, Julian Reschke wrote:
> 
> feedback on "Define how to register new http-equiv values. (credit: ma) 
> (whatwg r2548)":
> 
> <http://www.whatwg.org/specs/web-apps/current-work/#other-pragma-directives>:
> 
> "...Such extensions must use a name that is identical to a 
> previously-registered HTTP header defined in an RFC, and must have 
> behavior identical to that described for the HTTP header...."
> 
> HTTP headers do not need to be defined in RFCs, there's a registry for 
> it. See <http://tools.ietf.org/html/rfc4229>, 
> <http://www.iana.org/assignments/message-headers/prov-headers.html>, and 
> <http://www.iana.org/assignments/message-headers/perm-headers.html>.

Right; the idea is to reduce the number of headers that are used here, by 
having a higher barrier to entry than just registration. (It's a bit like 
"RFC required" from RFC5226.)

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 23 December 2008 01:03:49 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:00 UTC