<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 9, 2009, at 11:21 AM, Julian Reschke wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>True, but there is no real "X-" prefix convention for HTTP headers.<br><br>But, there is a registration procedure, defined in RFC 3864. It defines two registries, a provisional, and a permanent. The latter (and only that) requires:<br><br> Registration of a new message header field starts with construction<br> of a proposal that describes the syntax, semantics and intended use<br> of the field. For entries in the Permanent Message Header Field<br> Registry, this proposal MUST be published as an RFC, or as an Open<br> Standard in the sense described by RFC 2026, section 7 [1].<br><br>(<<a href="http://tools.ietf.org/html/rfc3864#section-4.1">http://tools.ietf.org/html/rfc3864#section-4.1</a>>)<br><br>The HTML5 requirement goes further than the IETF requirement; I would consider that a bug.<br></div></blockquote></div><br><div>I think the HTML5 requirement should be changed to allow any header in the Permanent Message Header Field Registry. Effectively, this would require either an RFC or an Open Standard. This seems just as good for HTML5's purposes as requiring an RFC.</div><div><br></div><div>Regards,</div><div>Maciej</div><div><br></div></body></html>