HTTP Header Field Registrations
RFC 4229
Yes
No Objection
Note: This ballot was opened for revision 05 and is now closed.
(Scott Hollenbeck; former steering group member) Yes
(Bert Wijnen; former steering group member) No Objection
It seems to me that none of the keywords from RFC2119 are used and so section 1.1 plus the normative reference [2] are (I think) irrelevant to this document.
(Bill Fenner; former steering group member) No Objection
A minor comment: I was confused by Related information: spoof in 2.1.3; after reading the reference I realized that it was because it was defined in an April 1 RFC; when I first read it I thought maybe it was warning that this header was vulnerable to spoofing, or some such thing.
(Brian Carpenter; former steering group member) No Objection
(David Kessens; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Ted Hardie; former steering group member) No Objection