Going through the open issues on GitHub for the WHEP draft:

- Client / Server offer
  - Server offer proponents need to present a concrete PR
  - Once we have it, discuss on the mailing list again
- Server events
  - Juliusz: clarification regarding simulcast
  - Jonathan: idea to use the even channel for offer/answer
  - Nils: maybe defer event stream to another document for later
  - Juliusz: defer section 4.9 server events into a new experimental draft
  - Tim: switch to data channels instead, where m=application signals if it’s supported
  - Data channel is agreed on - Tim hopefully comes up with a PR
  - So data channel or server sent events could be used by a client to get events, but both are going to be optional
  - Both ways will only offer extendable frameworks so that we could move the actual event specifications into other specs
- Francesca: HTTP Dir review early please
- Whep URL’s
  - Not clear how to proceed: get help from HTTP experts?
- Extension failure
  - We need to specify the failure behavior, otherwise folks will use the loopholes in the spec to use undefined behavior