The use cases for this draft are highly speculative and unproven, even for
something aspiring to be Experimental. I haven't seen any implementers express
interest in it.
The draft does not cover what it means for a server to "recognise" a header,
yet it places a MUST level requirement on this; e.g., if a server doesn't
actively use the "Via" header, should it list it as not recognised? What about
X-Forwarded-For? Deploying this on a server as-is means that a lot of extra
bytes will be sent in responses (and not just because the field-name is so
long, although that doesn't help). If the client sends a 'Range' header but the
server chooses not to sent a partial response, should it be listed? And so on...
It's also under-specified; e.g, I haven't seen any analysis on the interaction
of this mechanism with hop-by-hop headers, nor with content negotiation, nor
with caching.
Furthermore, the draft enables implementation of an anti-pattern for HTTP, by
offering an alternative to the 'must ignore' pattern. I understand that the
intent of the header is to enable debugging, but if it gains deployment, it
will be very tempting for developers to build on top of it.
Therefore, I recommend that this draft NOT be published as an RFC (of any kind).
Regards,
Begin forwarded message:
From: The IESG <iesg-secretary(_at_)ietf(_dot_)org>
Date: 14 December 2010 12:28:08 AM AEDT
To: IETF-Announce <ietf-announce(_at_)ietf(_dot_)org>
Subject: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt>
('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC
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(_at_)ietf(_dot_)org mailing lists by 2011-01-14. Exceptionally, comments
may be
sent to iesg(_at_)ietf(_dot_)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(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-announce
--
Mark Nottingham http://www.mnot.net/
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf