Now up to six of us here, plus Sean at the front!
", "time": "2022-07-27T17:30:22Z"}, {"author": "Adam Roach", "text": "Yo dawg, I heard you liked Internet...
", "time": "2022-07-27T17:31:18Z"}, {"author": "Juliusz Chroboczek", "text": "Was lunch any good?
", "time": "2022-07-27T17:31:19Z"}, {"author": "Sergio Garcia Murillo", "text": "hi everyone!
", "time": "2022-07-27T17:31:19Z"}, {"author": "Nils Ohlmeier", "text": "Does someone track the percentage of participants on site per WG? :-)
", "time": "2022-07-27T17:31:43Z"}, {"author": "Rajeev RK", "text": "Also, since meetecho uses webRTC(i pesume), we are also kind of dogfooding, using WebRTC to Evolve WebRTC
", "time": "2022-07-27T17:31:46Z"}, {"author": "Lorenzo Miniero", "text": "You presume well :)
", "time": "2022-07-27T17:31:59Z"}, {"author": "Adam Roach", "text": "HI SPENCER!
", "time": "2022-07-27T17:34:30Z"}, {"author": "Murray Kucherawy", "text": "WiFi just blipped here. :( I'll let the NOC know.
", "time": "2022-07-27T17:34:44Z"}, {"author": "Murray Kucherawy", "text": "Thank you for doing the early IANA review!
", "time": "2022-07-27T17:37:42Z"}, {"author": "Murray Kucherawy", "text": "+1
", "time": "2022-07-27T17:40:18Z"}, {"author": "Adam Roach", "text": "For the record, I agree with the decision not to fix the items on the \"Won't Fix\" slide, and agree with the rationale provided for each item.
", "time": "2022-07-27T17:41:31Z"}, {"author": "Jonathan Lennox", "text": "The text on the slide is very small in the room...
", "time": "2022-07-27T17:47:07Z"}, {"author": "Jonathan Lennox", "text": "I've pulled it up on my laptop
", "time": "2022-07-27T17:48:11Z"}, {"author": "Jonathan Lennox", "text": "https://datatracker.ietf.org/meeting/114/materials/slides-114-wish-whip-whep-02 for others
", "time": "2022-07-27T17:49:06Z"}, {"author": "Lorenzo Miniero", "text": "@Sean Turner there should be a screen on your desk to track the queue, you don't need your own laptop to see that
", "time": "2022-07-27T17:49:23Z"}, {"author": "Rajeev RK", "text": "Hmm, Chair's should be given dual screen setups, to allow for presentation and queue management in parallel... maybe we should put in a budget request :-D
", "time": "2022-07-27T17:49:32Z"}, {"author": "Murray Kucherawy", "text": "Unrelated: I just noticed in 6.1 that you're creating a new IANA registry (or maybe a sub-registry) but the rules for the registry aren't stated.
", "time": "2022-07-27T17:51:02Z"}, {"author": "Murray Kucherawy", "text": "Sorry, 6.2.
", "time": "2022-07-27T17:51:23Z"}, {"author": "Spencer Dawkins", "text": "My advice is for people to keep an eye on me in the HedgeDoc notes. NOTE WELL ...
", "time": "2022-07-27T17:57:21Z"}, {"author": "Lorenzo Miniero", "text": "I'm one of the ones that advocated for keeping OPTIONS there for STUN/TURN, but I agree with Sergio it shouldn't be a MUST: examples have been provided where it could be challenging
", "time": "2022-07-27T18:00:16Z"}, {"author": "Spencer Dawkins", "text": "I'm having a difficult time tracking the conversation in the notes. More eyes are good ...
", "time": "2022-07-27T18:05:47Z"}, {"author": "Adam Roach", "text": "I'm good with SHOULD
", "time": "2022-07-27T18:06:22Z"}, {"author": "Adam Roach", "text": "And a warning to client implementors about what happens if the server can't do so for whatever reason
", "time": "2022-07-27T18:06:54Z"}, {"author": "Juliusz Chroboczek", "text": "That's the issue we've just discussed.
", "time": "2022-07-27T18:10:00Z"}, {"author": "Juliusz Chroboczek", "text": "Sorry, I intervented too early.
", "time": "2022-07-27T18:11:02Z"}, {"author": "Adam Roach", "text": "Okay, I think 422 is what we want: https://datatracker.ietf.org/doc/html/rfc4918#section-11.2
", "time": "2022-07-27T18:19:54Z"}, {"author": "Juliusz Chroboczek", "text": "Isn't 422 specific to WebDA?
", "time": "2022-07-27T18:20:39Z"}, {"author": "Adam Roach", "text": "I already have a PR in for the PATCH code. :)
", "time": "2022-07-27T18:20:45Z"}, {"author": "Juliusz Chroboczek", "text": "The advantage of delaying it is that we might have some implementations by September.
", "time": "2022-07-27T18:21:19Z"}, {"author": "Adam Roach", "text": "422 is defined in WebDAV, but the semantics are a good match, and the text in RFC4918 explains why other codes don't fit the exact situation Sergio described. We should check with another HTTP expert, but I think 422 is the most semantically correct response.
", "time": "2022-07-27T18:21:56Z"}, {"author": "Juliusz Chroboczek", "text": "+1 Adam Roach
", "time": "2022-07-27T18:22:49Z"}]