Re: comments on draft-ietf-http-v11-spec-rev-03

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Daniel Hellerstein: "what is the scope of accept-range"
• Previous message: Dave Kristol: "comments on draft-ietf-http-v11-spec-rev-03"
• In reply to: Dave Kristol: "comments on draft-ietf-http-v11-spec-rev-03"

> 
> 14.26 If-None-Match
>     I was disappointed that the pseudo-code didn't make it.  OTOH,
>     there are now disclaimers about mixing various conditional
>     headers, which accomplishes the same thing.
> 
>     I would like to see stronger advice in 13.3.4 about what
>     combinations of conditional headers a client can send reliably to a
>     server (or which combinations it must not send).
> 

I was/am opposed to having two independent specifications present in the 
same document; it leads to questions about which is correct. I felt it 
was better to clarify the text to remove the ambiguity.

I would not oppose publishing the pseudo-code as an informational RFC
document, with a disclaimer that the base specification rules.
				- Jim

• Next message: Daniel Hellerstein: "what is the scope of accept-range"
• Previous message: Dave Kristol: "comments on draft-ietf-http-v11-spec-rev-03"
• In reply to: Dave Kristol: "comments on draft-ietf-http-v11-spec-rev-03"