Last Call Review of draft-ietf-httpbis-p4-conditional-25

Request Review of draft-ietf-httpbis-p4-conditional
Requested rev. no specific revision (document currently at 26)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2013-12-17
Requested 2013-10-21
Authors Roy Fielding, Julian Reschke
Draft last updated 2013-12-03
Completed reviews Genart Last Call review of -25 by Meral Shirazipour (diff)
Opsdir Telechat review of -24 by Menachem Dodge (diff)
Secdir Last Call review of -24 by Klaas Wierenga (diff)
Secdir Early review of -?? by Klaas Wierenga
Assignment Reviewer Meral Shirazipour 
State Completed
Review review-ietf-httpbis-p4-conditional-25-genart-lc-shirazipour-2013-12-03
Reviewed rev. 25 (document currently at 26)
Review result Ready with Nits
Review completed: 2013-12-03


I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at



Please resolve any Last Call comments you may receive.



Document: draft-ietf-httpbis-p4-conditional-25

Reviewer: Meral Shirazipour

Review Date: 2013-11-18/2013-12-02

IETF LC End Date: End of November (special deadline)

IESG Telechat date: 2013-12-19





This draft is almost ready to be published as Proposed Standard but I have some comments.



Major issues:




Minor issues:




Nits/editorial comments:

Part 4 of:

draft-ietf-httpbis-p1-messaging (82 pages)

draft-ietf-httpbis-p2-semantics (98 pages)

*draft-ietf-httpbis-p4-conditional (27 pages)

draft-ietf-httpbis-p5-range (24 pages) 

draft-ietf-httpbis-p6-cache (41 pages)

draft-ietf-httpbis-p7-auth (18 pages)

draft-ietf-httpbis-method-registrations (7 pages)

draft-ietf-httpbis-authscheme-registrations (5 pages)


-[Page 4], Introduction, it would make the draft clearer if we give 1-2 every day examples of when conditions are used/useful.


-[Page 10], "filesystem"---->"file system"


-General comment: since mostly used with caching, why not considered merging with part 6?


- [Page 22], Security section, as mentioned in my other reviews, would it be better to have a separate draft to discuss all security issues related to HTTP?


Best Regards,




Meral Shirazipour

Ericsson Research