[{"author": "Murray Kucherawy", "text": "draft-ietf-avtext-framemarking is now in \"AD Evaluation\".
", "time": "2022-03-25T09:07:42Z"}, {"author": "Murray Kucherawy", "text": "I just lost audio
", "time": "2022-03-25T09:08:07Z"}, {"author": "Ted Hardie", "text": "Murray, did audio come back?
", "time": "2022-03-25T09:08:42Z"}, {"author": "Murray Kucherawy", "text": "No
", "time": "2022-03-25T09:08:47Z"}, {"author": "Murray Kucherawy", "text": "Going to try reconnecting
", "time": "2022-03-25T09:08:51Z"}, {"author": "Murray Kucherawy", "text": "No good. Audio is fine locally (e.g., playing something on YouTube).
", "time": "2022-03-25T09:10:25Z"}, {"author": "Meetecho", "text": "Murray, can you see if refreshing the page helps?
", "time": "2022-03-25T09:11:02Z"}, {"author": "Murray Kucherawy", "text": "I did once and it didn't help, but it's fine after a second refresh.
", "time": "2022-03-25T09:11:50Z"}, {"author": "Sergio Garcia Murillo", "text": "where would that \"concurrent CC algorithms\" work be done? seems the efforts are spread in different groups
", "time": "2022-03-25T09:16:04Z"}, {"author": "Jonathan Lennox", "text": "As an individual, I'd suggest probably starting in ICCRG?
", "time": "2022-03-25T09:18:00Z"}, {"author": "Colin Perkins", "text": "ICCRG will be you useful feedback; it won't produce something that can be a standard quickly
", "time": "2022-03-25T09:18:31Z"}, {"author": "Roni Even", "text": "about congestion how about transport level one like https://datatracker.ietf.org/doc/html/draft-pan-tsvwg-hpccplus-02
", "time": "2022-03-25T09:21:54Z"}, {"author": "Mo Zanaty", "text": "+1 Colin, ICCRG will tell you what you did wrong, and what others have already tried, but not converge quickly on any deployable solution.
", "time": "2022-03-25T09:26:06Z"}, {"author": "Roni Even", "text": "there is https://datatracker.ietf.org/doc/html/draft-miao-iccrg-hpccplus in iccrg
", "time": "2022-03-25T09:26:24Z"}, {"author": "Spencer Dawkins", "text": "@Colin, when I'm speaking in AVTCORE, could you make your comment about getting new congestion controller quickly? I'd LOVEfor us to talk about that in a meeting ...
", "time": "2022-03-25T09:27:18Z"}, {"author": "Colin Perkins", "text": "HPCC++ needs link changes, IIRC, so may not be the easiest to deploy wide area
", "time": "2022-03-25T09:27:52Z"}, {"author": "Colin Perkins", "text": "Happy to try to remember
", "time": "2022-03-25T09:28:32Z"}, {"author": "Roni Even", "text": "there wa s also a side meeting about 802.1 congestion control https://mailarchive.ietf.org/arch/browse/rdma-cc-interest/
", "time": "2022-03-25T09:32:02Z"}, {"author": "Richard Barnes", "text": "SHALL - the most officious part of RFC 2119
", "time": "2022-03-25T09:34:27Z"}, {"author": "Ted Hardie", "text": "FYI, I sent a request for access to \"Secure Communication Interoperability Protocol (SCIP) over Real-time Transport Protocol (RTP)\" ncia.cis3@ncia.nato.int and never got a reply. So I assume that any work on this should proceed with the understanding that the actual spec will not be available. At a minimum, that would need to be called it in last call.
", "time": "2022-03-25T09:34:37Z"}, {"author": "Roni Even", "text": "it is more about data centers
", "time": "2022-03-25T09:34:48Z"}, {"author": "Ted Hardie", "text": "If others did get access, I will withdraw that comment, of course; it's possible that mine was dropped for some specific reasons.
", "time": "2022-03-25T09:35:15Z"}, {"author": "Murray Kucherawy", "text": "Non-availability of references has been a problem for the IESG in the past, so I agree with Ted. We're also looking at reviewing and revising the BCPs to provide guidance about this.
", "time": "2022-03-25T09:39:03Z"}, {"author": "Roni Even", "text": "agree with Cullen. we had such black box encryption in the circuit switch video conferencing
", "time": "2022-03-25T09:46:59Z"}, {"author": "Ted Hardie", "text": "Spec unavailability being called out similar to a downref, but it is not exactly the same. That's not blocking.
", "time": "2022-03-25T09:49:07Z"}, {"author": "Richard Barnes", "text": "All I meant was that there is a section in the media type registration called \"Published specification\" that cites NSA specs, which it sounds like are not actually published.
", "time": "2022-03-25T09:49:16Z"}, {"author": "Ted Hardie", "text": "So when I requested them, they were not delivered.
", "time": "2022-03-25T09:50:15Z"}, {"author": "Murray Kucherawy", "text": "It's easier, at least, if they're informative references. If they're normative and unavailable, reviewers don't have any way to check that their use is correct.
", "time": "2022-03-25T09:50:40Z"}, {"author": "Lucas Pardue", "text": "I think you probably need to reference the QUIC bit grease sped in 7983bis
", "time": "2022-03-25T09:54:56Z"}, {"author": "Ted Hardie", "text": "I think Lucas's point is the right; v2 is a greasing release.
", "time": "2022-03-25T09:56:21Z"}, {"author": "Murray Kucherawy", "text": "Makes sense there's a QUIC v2, given how old QUIC is.
", "time": "2022-03-25T09:56:53Z"}, {"author": "Lucas Pardue", "text": "specifically https://datatracker.ietf.org/doc/html/draft-ietf-quic-bit-grease-02
", "time": "2022-03-25T09:57:37Z"}, {"author": "Lucas Pardue", "text": "The second-to-most significant bit of the first byte in every QUIC
packet is defined as having a fixed value in QUIC version 1 [QUIC].
The purpose of having a fixed value is to allow intermediaries and
endpoints to efficiently distinguish between QUIC and other
protocols; see [DEMUX] for a description of a scheme that QUIC can
integrate with as a result. As this bit effectively identifies a
packet as QUIC, it is sometimes referred to as the \"QUIC Bit\".
", "time": "2022-03-25T09:57:56Z"}, {"author": "Jonathan Lennox", "text": "Lucas, do you want to speak at the mic, and/or have me relay that?
", "time": "2022-03-25T09:58:12Z"}, {"author": "Lucas Pardue", "text": "please relay
", "time": "2022-03-25T09:58:38Z"}, {"author": "Lucas Pardue", "text": "yes that would be good enough
", "time": "2022-03-25T09:59:27Z"}, {"author": "Magnus Westerlund", "text": "And the version 2 spec is this one: https://datatracker.ietf.org/doc/draft-ietf-quic-v2/
", "time": "2022-03-25T09:59:34Z"}, {"author": "Lucas Pardue", "text": "don't shoot yourself with it :)
", "time": "2022-03-25T09:59:39Z"}, {"author": "Colin Perkins", "text": "We should add the references to quic-v2 and quic-bit-grease
", "time": "2022-03-25T10:02:22Z"}, {"author": "Cullen Jennings", "text": "+1
", "time": "2022-03-25T10:03:07Z"}, {"author": "Ted Hardie", "text": "https://github.com/SpencerDawkins/sdp-rtp-quic-issues/issues to make the slide url clickable.
", "time": "2022-03-25T10:04:13Z"}, {"author": "Benson Muite", "text": ":100:
", "time": "2022-03-25T10:06:14Z"}, {"author": "Colin Perkins", "text": "+1 to Cullen (on all aspects)
", "time": "2022-03-25T10:17:05Z"}, {"author": "Richard Barnes", "text": "QAVPF
", "time": "2022-03-25T10:17:46Z"}, {"author": "Cullen Jennings", "text": "I like to point out that if all you want is the payload type, what you really want is that not to be a dynamic number but instead just be an IANA registry with 16 bits for the PayloadType
", "time": "2022-03-25T10:18:50Z"}, {"author": "Colin Perkins", "text": "RTP -> RTQ ?
", "time": "2022-03-25T10:19:06Z"}, {"author": "Cullen Jennings", "text": "RTQ == MoQ ???
", "time": "2022-03-25T10:19:24Z"}, {"author": "Ted Hardie", "text": "Meanwhile, MoQ is talking about multicase models, so you may get all of that back in a new form.
", "time": "2022-03-25T10:19:29Z"}, {"author": "Ted Hardie", "text": "s/multicase/multicast/
", "time": "2022-03-25T10:19:41Z"}, {"author": "Colin Perkins", "text": "@cullen: or use the media type name directly
", "time": "2022-03-25T10:19:42Z"}, {"author": "Cullen Jennings", "text": "an SFU is application level multicast in RTP :-)
", "time": "2022-03-25T10:19:53Z"}, {"author": "Roni Even", "text": "to stephan comment like RFC4571 rtp over tcp
", "time": "2022-03-25T10:20:01Z"}, {"author": "Stephan Wenger", "text": "indeed.
", "time": "2022-03-25T10:20:13Z"}, {"author": "Cullen Jennings", "text": "@colin - if we do string names, someone is going to make me change them to unicode and then I will have no clue how to compare them :-)
", "time": "2022-03-25T10:21:45Z"}, {"author": "Jonathan Lennox", "text": "We've been doing media type comparisons for http forever so hopefully this isn't so much harder
", "time": "2022-03-25T10:22:46Z"}, {"author": "Colin Perkins", "text": "Content-type: video/:film_projector:
", "time": "2022-03-25T10:23:17Z"}, {"author": "Cullen Jennings", "text": "I'm sold
", "time": "2022-03-25T10:23:27Z"}, {"author": "Joerg Ott", "text": "It's active
", "time": "2022-03-25T10:23:42Z"}, {"author": "Joerg Ott", "text": "this is just so we know what we talking about
", "time": "2022-03-25T10:24:23Z"}, {"author": "Joerg Ott", "text": "Happy to, this is the plan anywaty
", "time": "2022-03-25T10:24:39Z"}, {"author": "Joerg Ott", "text": "not yet :-)
", "time": "2022-03-25T10:25:06Z"}, {"author": "Roni Even", "text": "there is echo when cullen speaks
", "time": "2022-03-25T10:26:43Z"}, {"author": "Roni Even", "text": "no echo cancellation :smiley:
", "time": "2022-03-25T10:27:16Z"}, {"author": "Suhas Nandakumar", "text": "@roni .. we use the echo as a RTX mechanism
", "time": "2022-03-25T10:27:34Z"}, {"author": "Giles Heron", "text": "LOL @Suhas
", "time": "2022-03-25T10:28:19Z"}, {"author": "Richard Barnes", "text": "@jonathan echo is back
", "time": "2022-03-25T10:29:00Z"}, {"author": "Jonathan Lennox", "text": "It's not my laptop - Meetecho can you take a look?
", "time": "2022-03-25T10:29:28Z"}, {"author": "Lucas Pardue", "text": "the hand bone's connected to the ... MBONE
", "time": "2022-03-25T10:29:50Z"}, {"author": "Richard Barnes", "text": "is it possible to just mute the room?
", "time": "2022-03-25T10:29:51Z"}, {"author": "rohan", "text": "+1 on muting the room
", "time": "2022-03-25T10:30:05Z"}, {"author": "Jonathan Lennox", "text": "Not in my controls but possibly in meetecho's
", "time": "2022-03-25T10:30:17Z"}, {"author": "Meetecho", "text": "Heading there
", "time": "2022-03-25T10:30:18Z"}, {"author": "Murray Kucherawy", "text": "Darth Jennings
", "time": "2022-03-25T10:30:39Z"}, {"author": "Joerg Ott", "text": "but Cullen sounds nicely mystic this way
", "time": "2022-03-25T10:30:42Z"}, {"author": "Stephan Wenger", "text": "@Cullen: AOM may also be interested if you don't want to go to MPEG
", "time": "2022-03-25T10:36:06Z"}, {"author": "Cullen Jennings", "text": "oh interesting - I did not realize that. thanks
", "time": "2022-03-25T10:36:45Z"}, {"author": "Hang Shi", "text": "AOM stands for Alliance for Open Media?
", "time": "2022-03-25T10:39:01Z"}, {"author": "Roni Even", "text": "I am not sure if it is related but for H.323 we used rtp for FECC regitering a media subtype in rfc4573.
", "time": "2022-03-25T10:40:04Z"}, {"author": "Stephan Wenger", "text": "@Hang SHi: yes
", "time": "2022-03-25T10:40:23Z"}, {"author": "Rohan Mahy", "text": "To Jonathan's comment, this is no different than what we did in geopriv, where IETF invited domain experts
", "time": "2022-03-25T10:40:29Z"}, {"author": "Roni Even", "text": "+1 to MO and Bernard
", "time": "2022-03-25T10:44:35Z"}, {"author": "Hang Shi", "text": "Is this related to webtransport? If webtransport can transmit any TLV in the datagram, do we still map it to RTP?
", "time": "2022-03-25T10:45:21Z"}, {"author": "Suhas Nandakumar", "text": "+1 on time synchronization with RTP
", "time": "2022-03-25T10:45:28Z"}, {"author": "Rohan Mahy", "text": "Bernard said exactly what I was going to say
", "time": "2022-03-25T10:45:31Z"}, {"author": "Richard Barnes", "text": "even QUIC is not quick
", "time": "2022-03-25T10:45:39Z"}, {"author": "Spencer Dawkins", "text": "It does sound like we need to reopen RTCWeb and recharter it as the IETF media complaint department ... :grin:
", "time": "2022-03-25T10:45:48Z"}, {"author": "Ted Hardie", "text": "Dirty, on the other hand...
", "time": "2022-03-25T10:45:53Z"}, {"author": "Hang Shi", "text": "If we map it to the RTP then webtransport is widely support, do we need to do game state over RTP over webtransport over HTTP/3 over QUIC?
", "time": "2022-03-25T10:46:27Z"}, {"author": "Ted Hardie", "text": "@Spencer RTCWeb is actually currently open, and as one of its current chairs: No, thanks.
", "time": "2022-03-25T10:46:50Z"}, {"author": "Sergio Garcia Murillo", "text": "have we given up trying to synchronize dc messages with rtp timestamps?
", "time": "2022-03-25T10:48:03Z"}, {"author": "Roni Even", "text": "For cullen sake not like CLUE
", "time": "2022-03-25T10:48:17Z"}, {"author": "Richard Barnes", "text": "TLV-over-RTP
", "time": "2022-03-25T10:49:32Z"}, {"author": "Sergio Garcia Murillo", "text": "RTMP SharedObject over RTP (just partially joking)
", "time": "2022-03-25T10:50:32Z"}, {"author": "Pete Resnick", "text": "+1 Suhas
", "time": "2022-03-25T10:50:42Z"}, {"author": "Colin Perkins", "text": "This seems a good fit for the current AVT charter, to me
", "time": "2022-03-25T10:51:22Z"}, {"author": "Pete Resnick", "text": "Agree it's within charter.
", "time": "2022-03-25T10:51:27Z"}, {"author": "Magnus Westerlund", "text": "I think the new format part is border line but you can go either way. So lets do it. But it is this part of the charter we are talking about:
", "time": "2022-03-25T10:53:31Z"}, {"author": "Magnus Westerlund", "text": "3. To specify and maintain payload formats for use with RTP. The working
group will develop RTP payload formats for new media codecs, review and
revise existing payload formats to advance those that are especially
useful to Internet Standard, and declare others Historic. The group will
follow the guidelines established in \"Guidelines for Writers of RTP
Payload Format Specifications\" [BCP 36] and \"How to Write an RTP Payload
Format\" (RFC 8088), and is responsible for maintaining those guidelines.
", "time": "2022-03-25T10:53:32Z"}, {"author": "Simon Romano", "text": "This is a nice proposal. I'd love to contribute. Thanks @Cullen for bringing this to the table.
", "time": "2022-03-25T10:55:08Z"}, {"author": "Hang Shi", "text": "Agree. This work fits in the charter.
", "time": "2022-03-25T10:55:44Z"}, {"author": "Giles Heron", "text": "I've read it
", "time": "2022-03-25T10:56:36Z"}, {"author": "Suhas Nandakumar", "text": "+1 on read the draft
", "time": "2022-03-25T10:56:37Z"}, {"author": "Roni Even", "text": "when we hear about games we are interested :smiley:
", "time": "2022-03-25T10:57:49Z"}, {"author": "Rohan Mahy", "text": "so long and thanks for all the fish!
", "time": "2022-03-25T10:59:41Z"}, {"author": "Richard Barnes", "text": "i would be interested in a short tags call
", "time": "2022-03-25T10:59:49Z"}, {"author": "Cullen Jennings", "text": "https://eprint.iacr.org/2015/477.pdf
", "time": "2022-03-25T10:59:57Z"}, {"author": "Cullen Jennings", "text": "Paper by Magnus and Mattsson
", "time": "2022-03-25T11:00:11Z"}, {"author": "Suhas Nandakumar", "text": "+1 on short tags call
", "time": "2022-03-25T11:00:18Z"}, {"author": "Cullen Jennings", "text": "Thank you everyone for input on game moves
", "time": "2022-03-25T11:01:05Z"}]