W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC

From: Cullen Jennings <fluffy@cisco.com>
Date: Fri, 17 Dec 2010 16:45:49 -0700
Cc: httpbis Group <ietf-http-wg@w3.org>
Message-Id: <DAF9B2D0-43A1-472C-8B19-12E2C96B320A@cisco.com>
To: The IETF <ietf@ietf.org>

I'm pretty surprised to see this in IETF LC - its not at the level where it is ready to have a WG start working on the idea. 

It's unclear what this draft is for, who wants it, or how it would work. Consider a HTTP request going to something like GAE. First some front end web gets the message, call this server A, it probably forwards on to separate web server running the python system, call this B, this pass on to a framework like say django, call this C, which passes on to end application call this D. It's really unclear what software is responsible for knowing which header each of A, B, C, and D supports or how the proposed header would get filled out in the response.  It gets even more unclear as you start adding in caches, TLS accelerators, and such. It's not clear to me what the client would be able to do even if it had this information. 

I don't think this should be published until it has actually been discussed in the appropriate WG. 




On Dec 13, 2010, at 6:28 AM, The IESG wrote:

> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - ''Headers-Not-Recognized' HTTP Header Field'
>  <draft-yevstifeyev-http-headers-not-recognized-08.txt> as an
> Experimental RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-01-14. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-yevstifeyev-http-headers-not-recognized/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-yevstifeyev-http-headers-not-recognized/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
Received on Friday, 17 December 2010 23:45:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:34 GMT