[ACTION 912] Suggest some new wording on X-Device-* fields

The action is stated as "Suggest some new wording on X-Device-* HTTP header 
fields keeping the normative meaning but noting that we're working with IETF 
and may deprecate this in the future".

ACTION 912.

The modification is to be applied to section G.5 of the CT guidelines in its
current version (2008-11-07 1p), not taking into account several alterations to
the document still pending.

-----

At present HTTP does not provide a mechanism for communicating the original 
values of header fields modified in transit. The scheme based on X-Device 
prefixed fields described under 4.1.5 "Alteration of HTTP header values" records
and clarifies an approach used to achieve this effect by some content 
transformation proxies. This scheme relies upon non-standard HTTP fields, which 
are identified by their prefix as experimental according to IETF standards 
(notably RFC822 and RFC2076), and are not included in the IANA registry 
of HTTP header fields. While the mechanism defined in section 4.1.5, based on
current practice, applies to conforming transformation proxy deployments, the 
W3C shall, in collaboration with the IETF, reframe it rigorously in terms of 
existing and future standards. This implies that the specified X-Device prefixed
fields may, at some time, become deprecated in favour of new equivalent fields,
or of an entirely different approach replacing them.

-----

Whenever this action point is to be handled, I ask that action 897, discharged 
over a month ago as lists.w3.org/Archives/Public/public-bpwg/2009Feb/0000.html, 
be ticked off as well.


E.Casais

Received on Monday, 9 March 2009 09:05:46 UTC