[Ietf-message-headers] Provisional registration of 5 X-Device-* HTTP Header fields for use in content transformation guidelines
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ietf-message-headers] Provisional registration of 5 X-Device-* HTTP Header fields for use in content transformation guidelines



Hi,

Please find below the registration template for 5 HTTP header fields the W3C Mobile Web Best Practices Working Group would like to provisionally register for use in the "Guidelines for Web Content Transformation Proxies" specification it is currently working on.

Note on the presence of the "X-" prefix: names were chosen on the basis that there are a already existing and deployed convention. Since there is no easy way to transition out of a situation where an "X-" prefix has been used for other purpose than a purely experimental one, the W3C Mobile Web Best Practices Working Group acknowledges that these HTTP header field names are already in use and requests that the "X-" prefix be (exceptionally) kept.


-----
Header field names:
X-Device-User-Agent (request header)
X-Device-Accept (request header)
X-Device-Accept-Charset (request header)
X-Device-Accept-Encoding (request header)
X-Device-Accept-Language (request header)

Applicable protocol:
http

Status:
provisional

Author/Change controller:
W3C Mobile Web Best Practices Working Group
http://www.w3.org/2005/MWI/BPWG/

Specification document(s):
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/latest
(Editor's Draft)
http://www.w3.org/TR/ct-guidelines/ (Working Draft)

See section "4.1.5.5 Original Header Fields" in the documents.
-----


I will submit the above template to the designated IANA e-mail address beginning of August, unless some explicit disagreement is made on this list.

Regards,

On behalf of the W3C Mobile Web Best Practices Working Group,
Francois Daoust,
W3C Staff Contact for the group.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.