Hypertext Transfer Protocol (HTTP/1.1): Range Requests
draft-ietf-httpbis-p5-range-26
Yes
(Barry Leiba)
No Objection
(Adrian Farrel)
(Benoît Claise)
(Brian Haberman)
(Jari Arkko)
(Joel Jaeggli)
(Martin Stiemerling)
(Pete Resnick)
(Spencer Dawkins)
(Stewart Bryant)
Note: This ballot was opened for revision 24 and is now closed.
Barry Leiba Former IESG member
Yes
Yes
(for -24)
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
(for -25)
Unknown
Benoît Claise Former IESG member
No Objection
No Objection
(for -25)
Unknown
Brian Haberman Former IESG member
No Objection
No Objection
(for -25)
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(for -25)
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
(for -25)
Unknown
Martin Stiemerling Former IESG member
No Objection
No Objection
(for -25)
Unknown
Pete Resnick Former IESG member
No Objection
No Objection
(for -25)
Unknown
Richard Barnes Former IESG member
No Objection
No Objection
(2013-12-18 for -25)
Unknown
COMMENT 1: In Section 3.2: It would be helpful to clarify that the interpretation of the date in an If-Range header is effectively the same as with If-Unmodified-Since. NEW: "When an HTTP-date value is present in an If-Range header field, the precondition verified by the server is that the representation has not changed since that date (as with the If-Unmodified-Since)." COMMENT 2: In Section 6.1: This may be outlandish, but is it possible that in some cases, requesting bytes past the end of a file might cause a buffer overflow or similar?
Sean Turner Former IESG member
No Objection
No Objection
(2013-12-19 for -25)
Unknown
*) I'll not repeats the OWS discuss point from p1. If it gets changed there I assume it will get changed here. If not then this can be ignored. 0) Abstract: Maybe would add stateless in front of protocol in the description. 1) s2.1: might be good to have the ABNF match the text; The last-byte-pos value gives the byte-offset of the last byte, which is OPTIONAL, in the range; that is, the byte positions specified are inclusive. 2) s5.4.1: Please add a pointer to the sec cons of this draft instead of "none".
Spencer Dawkins Former IESG member
No Objection
No Objection
(for -25)
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
(2013-12-18 for -25)
Unknown
- 3.2: Is an HTTP-date value a valid value for an entity-tag? If so, I assume that an If-Range value is interpreted as a date. Do you need to say that?
Stewart Bryant Former IESG member
No Objection
No Objection
(for -25)
Unknown