James M Snell wrote: > > Updated version to fix a few typos in the original.... > > http://www.ietf.org/internet-drafts/draft-snell-http-prefer-01.txt >
This seems to overlap the functionality of the Opt header from RFC 2774 [1], which is already registered [2], and which I've seen in actual use. Anyway, I still think that adding a parameter to the application/atom+xml MIME type makes the most sense, because FeedSync is effectively a "must-understand" extension, and the "Accept" header is already used for content negotiation. Failing that, how about the "Accept-Feature" header from RFC 2295 [3], which is also already registered [2]?. [1] http://rfc.net/rfc2774.html#s4.1 [2] http://www.iana.org/assignments/message-headers/perm-headers.html [3] http://rfc.net/rfc2295.html#s8.2 - Brian
