Re: [Wish] I-D Action: draft-ietf-wish-whip-09.txt

[Juliusz Chroboczek <[e-mail]>]

Thanks for the new draft, Sergio.  Looking at the new requirements.

> WHIP resources MUST ignore any entity-tag value sent by the WHIP client
> when ICE session matching is not required, as in the HTTP DELETE request.

I'm not a specialist, but does that not violate HTTP semantics?  The
document already says that the client SHOULD NOT send DELETE with
If-Match, but if the client does so anyway, I'd expect the server to
process it according to usual HTTP semantics.  What about people who
implement WHIP over an HTTP framework that does not allow easily
overriding HTTP semantics?

> When this situation is detected by the WHIP Client, it MUST send a new
> ICE ICE restart request to the server.

That used to be SHOULD.  Does that mean that supporting ICE restarts is
only optional for the server, and mandatory for the client?  (No objection
if that's the case, but that's not entirely clear from the document.)

Does the MUST apply even if the server did not return an ETag with the
initial SDP?

-- Juliusz