Judgemental alpaca has been retired?!
", "time": "2022-07-25T14:00:31Z"}, {"author": "Robert Sparks", "text": "@Murray Kucherawy
\n\n\nI have no responsibilities here whatsoever
\n
You wish...
", "time": "2022-07-25T14:02:06Z"}, {"author": "Murray Kucherawy", "text": "Cullen at the mic.
", "time": "2022-07-25T14:02:54Z"}, {"author": "Pete Resnick", "text": "Jumping about at the mic...
", "time": "2022-07-25T14:03:24Z"}, {"author": "Murray Kucherawy", "text": "\"...will be resolved by the end of the week\" just in time. ;)
", "time": "2022-07-25T14:04:46Z"}, {"author": "Pete Resnick", "text": "Not authorized probably indicates some problem with the datatracker login redirect.
", "time": "2022-07-25T14:04:49Z"}, {"author": "Bron Gondwana", "text": "Confirm Barry 's issue, can't scroll participant list on Android
", "time": "2022-07-25T14:05:06Z"}, {"author": "Jim Fenton", "text": "Likewise with Firefox on Mac
", "time": "2022-07-25T14:05:49Z"}, {"author": "Richard Barnes", "text": "Anyone else getting audio dropouts from Kristy?
", "time": "2022-07-25T14:06:26Z"}, {"author": "Jabber", "text": "cabo: Not too bad
", "time": "2022-07-25T14:06:58Z"}, {"author": "Bron Gondwana", "text": "She's clear in the room
", "time": "2022-07-25T14:07:01Z"}, {"author": "Murray Kucherawy", "text": "It's good in the room, don't know about the live stream
", "time": "2022-07-25T14:07:03Z"}, {"author": "Adam Roach", "text": "Richard -- I'm not getting dropouts
", "time": "2022-07-25T14:07:52Z"}, {"author": "Richard Barnes", "text": "probably local network issues, then, thanks.
", "time": "2022-07-25T14:09:22Z"}, {"author": "Richard Barnes", "text": "are there slides? not seeing anything in MeetEcho
", "time": "2022-07-25T14:09:42Z"}, {"author": "Deb Cooley", "text": "Yes, there are slides
", "time": "2022-07-25T14:09:57Z"}, {"author": "Bron Gondwana", "text": "Yes there are slides
", "time": "2022-07-25T14:10:00Z"}, {"author": "Murray Kucherawy", "text": "Yes, they're visible in the room at least
", "time": "2022-07-25T14:10:03Z"}, {"author": "Jonathan Lennox", "text": "We have slides in the room
", "time": "2022-07-25T14:10:04Z"}, {"author": "Jabber", "text": "cabo: Slides are shown
", "time": "2022-07-25T14:10:06Z"}, {"author": "Andrew Campling", "text": "There are slides, working in Meetecho for me
", "time": "2022-07-25T14:10:14Z"}, {"author": "Richard Barnes", "text": "oh there they are after reload
", "time": "2022-07-25T14:10:14Z"}, {"author": "Bron Gondwana", "text": "Zulip on my laptop is failing to sync up, this is a real regression in reliability since previous
", "time": "2022-07-25T14:10:57Z"}, {"author": "Richard Barnes", "text": "CBOR is not an apt comparison
", "time": "2022-07-25T14:11:46Z"}, {"author": "Jabber", "text": "cabo: Statements about CBOR seem confused.
", "time": "2022-07-25T14:12:17Z"}, {"author": "Bron Gondwana", "text": "there seem to be two streams, a \"MeetEcho\" stream and a \"jabber\" stream
", "time": "2022-07-25T14:13:09Z"}, {"author": "Richard Barnes", "text": "cabo: you agree that CBOR doesn't require prior agreement on the schema, right? i.e., you can parse it without prior context.
", "time": "2022-07-25T14:14:33Z"}, {"author": "Jabber", "text": "cabo: Yes.
", "time": "2022-07-25T14:14:57Z"}, {"author": "Richard Barnes", "text": "i think that's what he means by \"contains the schema\"
", "time": "2022-07-25T14:15:03Z"}, {"author": "Jabber", "text": "cabo: I think he is trying to do a PER for CBOR's BER :-)
", "time": "2022-07-25T14:16:05Z"}, {"author": "Jabber", "text": "cabo: cbor2 is a fine python package.
", "time": "2022-07-25T14:16:39Z"}, {"author": "Richard Barnes", "text": "cabo: no, he wants something that is not parsable without context, a la TLS syntax
", "time": "2022-07-25T14:16:42Z"}, {"author": "Robert Stepanek", "text": "the volume of the speakers mic in the room is quite low. could you please increase it?
", "time": "2022-07-25T14:16:53Z"}, {"author": "Richard Barnes", "text": "BARE is basically TLS syntax + 10%
", "time": "2022-07-25T14:16:56Z"}, {"author": "Richard Barnes", "text": "like almost byte-exact
", "time": "2022-07-25T14:17:08Z"}, {"author": "John Levine", "text": "I originally mentioned CBOR as an alternative, but there are a zillion of these without a built-in schema, starting with XDR
", "time": "2022-07-25T14:17:08Z"}, {"author": "Adam Roach", "text": "Right, I thought of TLS's encoding when I skimmed this.
", "time": "2022-07-25T14:17:13Z"}, {"author": "Jabber", "text": "cabo: Right
", "time": "2022-07-25T14:17:18Z"}, {"author": "Christian Ams\u00fcss", "text": "A preconfigured-schema CBOR might make sense, I'd just like it to use the same information model.
", "time": "2022-07-25T14:17:21Z"}, {"author": "Jabber", "text": "cabo: OK, I haven't looked at that.
", "time": "2022-07-25T14:17:29Z"}, {"author": "Robert Sparks", "text": "Bron Gondwana said:
\n\n\nthere seem to be two streams, a \"MeetEcho\" stream and a \"jabber\" stream
\n
Not separate streams - just different topics in the dispatch stream.
", "time": "2022-07-25T14:18:15Z"}, {"author": "Ted Hardie", "text": "Protobufs have a specification (https://developers.google.com/protocol-buffers/docs/reference/proto3-spec), even though it is maintained by a single party.
", "time": "2022-07-25T14:18:24Z"}, {"author": "Richard Barnes", "text": "As I said on the list this morning, my bid here would be to treat this as \"TLS + 10%\" and do WG on that basis
", "time": "2022-07-25T14:18:36Z"}, {"author": "Robert Sparks", "text": "it is better to use the jabber topic for this meeting (that is what will be bridged to jabber,
", "time": "2022-07-25T14:18:40Z"}, {"author": "Mike Bishop", "text": "Is being bridged to Jabber a concern? The IETF chat page talks only about Zulip and doesn't indicate any ongoing support of Jabber.
", "time": "2022-07-25T14:21:00Z"}, {"author": "Robert Sparks", "text": "We are bridging to jabber as a transition for this meeting. We expect not to do so for future meetings.
", "time": "2022-07-25T14:21:34Z"}, {"author": "Robert Sparks", "text": "fwiw - messages to any topic in the stream will appear on the MeetEcho client. Messages from the MeetEcho client for this meeting go to the Jabber topic.
", "time": "2022-07-25T14:22:44Z"}, {"author": "Martin Thomson", "text": "This topics business is really user-hostile. Why did we pick a tool that has this property?
", "time": "2022-07-25T14:24:11Z"}, {"author": "Bron Gondwana", "text": "Robert Sparks said:
\n\n\nBron Gondwana said:
\n\n\nthere seem to be two streams, a \"MeetEcho\" stream and a \"jabber\" stream
\nNot separate streams - just different topics in the dispatch stream.
\n
in the web interface they don't merge, so you have to switch between them
", "time": "2022-07-25T14:24:23Z"}, {"author": "Murray Kucherawy", "text": "Cullen in the queue after Eric.
", "time": "2022-07-25T14:24:23Z"}, {"author": "Murray Kucherawy", "text": "Richard is breaking up.
", "time": "2022-07-25T14:24:55Z"}, {"author": "Robert Sparks", "text": "select the whole stream instead of a given topic and you will see messages in all topis
", "time": "2022-07-25T14:25:01Z"}, {"author": "Jim Fenton", "text": "rather badly.
", "time": "2022-07-25T14:25:25Z"}, {"author": "Richard Barnes", "text": "Kristy: Correct summary
", "time": "2022-07-25T14:25:47Z"}, {"author": "Kirsty Paine", "text": "Richard, can you clarify if you wanted a WG to standardise the TLS syntax aspects, or this protocol generally?
", "time": "2022-07-25T14:26:19Z"}, {"author": "Richard Barnes", "text": "Minor amendment: Focused WG to align this with TLS syntax and address the difference
", "time": "2022-07-25T14:26:23Z"}, {"author": "Kirsty Paine", "text": "Thank you.
", "time": "2022-07-25T14:26:28Z"}, {"author": "Andrew Campling", "text": "The sound in the room from the queue mic could be louder
", "time": "2022-07-25T14:27:08Z"}, {"author": "Pete Resnick", "text": "@Meetecho: Remote people report that audio from the room is a bit quiet. Any way to increase the gain?
", "time": "2022-07-25T14:27:22Z"}, {"author": "Richard Barnes", "text": "To EKR's question -- MLS is basically a customer of this spec, since we needed optional<T> in TLS syntax
", "time": "2022-07-25T14:27:24Z"}, {"author": "Murray Kucherawy", "text": "Thanks Pete
", "time": "2022-07-25T14:27:31Z"}, {"author": "Lorenzo Miniero", "text": "Pete: I'll relay :+1:
", "time": "2022-07-25T14:27:42Z"}, {"author": "Richard Barnes", "text": "\"customer of this spec\" in the sense of \"needed TLS syntax with more tools\"
", "time": "2022-07-25T14:27:45Z"}, {"author": "Lorenzo Miniero", "text": "*Peter
", "time": "2022-07-25T14:27:47Z"}, {"author": "Adam Roach", "text": "I don't know how it is in the room itself, the but side conversations are being picked up by the mic and interfering with hearing the discussion
", "time": "2022-07-25T14:28:06Z"}, {"author": "Jonathan Rosenberg", "text": "I concur with ekr - this work should wait until there are multiple vendors who want to implement this because they see some issues with the existing technologies
", "time": "2022-07-25T14:28:25Z"}, {"author": "Bron Gondwana", "text": "room is fine, there's no other sound coming in
", "time": "2022-07-25T14:28:37Z"}, {"author": "Murray Kucherawy", "text": "@adam: Has that stopped now?
", "time": "2022-07-25T14:28:42Z"}, {"author": "Adam Roach", "text": "Murray -- Yes, thanks
", "time": "2022-07-25T14:28:56Z"}, {"author": "Samuel Weiler", "text": "@Adam Roach I'm in the room, and I don't hear side conversations. There's a little noise from the hall outside.
", "time": "2022-07-25T14:29:09Z"}, {"author": "Richard Barnes", "text": "+1 Cullen, this is what i meant
", "time": "2022-07-25T14:30:00Z"}, {"author": "Jim Fenton", "text": "I disagree with need to have a large company implementing something as an adoption criterion. OTOH, I don't find this proposal particularly compelling.
", "time": "2022-07-25T14:30:03Z"}, {"author": "Richard Barnes", "text": "in other words, we've gotten some mileage out of CBOR, this would cover the schema-ful case
", "time": "2022-07-25T14:30:32Z"}, {"author": "Kirsty Paine", "text": "cutting the queue now
", "time": "2022-07-25T14:30:52Z"}, {"author": "Richard Barnes", "text": "this is not CBOR. this is not CBOR. this is not CBOR. this is not CBOR. this is not CBOR.
", "time": "2022-07-25T14:31:29Z"}, {"author": "Adam Roach", "text": "Jim -- I don't think that was EKR's point -- I think the point was that protobuf has been widely disseminated because of its sponsorship by a large org, and that a new encoding needs to have some substantial benefits over status quo to be the thing we take onboard to standardize
", "time": "2022-07-25T14:31:41Z"}, {"author": "Richard Barnes", "text": "just because it's binary doesn't mean it's the same thing, folks
", "time": "2022-07-25T14:31:47Z"}, {"author": "Mike Bishop", "text": "I'll agree with previous comments, I think a WG to take TLS syntax and this, chartered to produce a unified syntax that can be reused by MLS et al. would be reasonable.
", "time": "2022-07-25T14:32:02Z"}, {"author": "Andrew Campling", "text": "Requiring a large company to implement something as a prequisit for adoption seems like a really bad idea, would further entrench the position of large companies
", "time": "2022-07-25T14:32:05Z"}, {"author": "Adam Roach", "text": "Agree with Richard. Saying we should have run this by CBOR is like saying JSON should have been run by XML experts first.
", "time": "2022-07-25T14:32:26Z"}, {"author": "Jim Fenton", "text": "@Adam Roach Agree with the need to have substantial benefits over status quo. That's what I don't find compelling about this.
", "time": "2022-07-25T14:32:58Z"}, {"author": "Mark Nottingham", "text": "+1 to a forum / discussion rather than a bake-off or choosing a winner
", "time": "2022-07-25T14:34:22Z"}, {"author": "Alex Chernyakhovsky", "text": "FWIW my understanding of why protobuf never was presented for standardization was mostly because protobuf was designed to allow for wire format evolution and compatibility as schemas evolve, which is somewhat a different goal than standardizing things for interop or whatever
", "time": "2022-07-25T14:34:31Z"}, {"author": "Mark Nottingham", "text": "Is that feedback from the room?
", "time": "2022-07-25T14:35:09Z"}, {"author": "Carsten Bormann", "text": "Yes
", "time": "2022-07-25T14:35:15Z"}, {"author": "John Klensin", "text": "Kristy is breaking up fairly badly. Was ok earlier
", "time": "2022-07-25T14:35:25Z"}, {"author": "Mark Nottingham", "text": "Meetecho, can you please look into that?
", "time": "2022-07-25T14:35:33Z"}, {"author": "Adam Roach", "text": "I'm having no problem hearing her
", "time": "2022-07-25T14:35:35Z"}, {"author": "Murray Kucherawy", "text": "Also in the room
", "time": "2022-07-25T14:35:37Z"}, {"author": "Adam Roach", "text": "But, yes, the room noise definitely picked up
", "time": "2022-07-25T14:35:49Z"}, {"author": "Robert Sparks", "text": "Can people sign on with the onsite tool in dispatch yet?
", "time": "2022-07-25T14:35:59Z"}, {"author": "Robert Sparks", "text": "Someone please retry and report?
", "time": "2022-07-25T14:36:10Z"}, {"author": "Murray Kucherawy", "text": "It was quiet in here when she was talking, that was odd
", "time": "2022-07-25T14:36:21Z"}, {"author": "Jonathan Lennox", "text": "I had no problem signing on with the onsite tool.
", "time": "2022-07-25T14:36:55Z"}, {"author": "Ted Hardie", "text": "I have a scope question: is A to multiple parties in scope or out of scope to the desire?
", "time": "2022-07-25T14:36:59Z"}, {"author": "Murray Kucherawy", "text": "@robert: I'm using the normal browser tool if that's what you mean
", "time": "2022-07-25T14:37:09Z"}, {"author": "Adam Roach", "text": "Did I miss the draft for this?
", "time": "2022-07-25T14:37:40Z"}, {"author": "Robert Sparks", "text": "I mean the onsite tool that people in the room should join through to be on the bluesheets
", "time": "2022-07-25T14:37:44Z"}, {"author": "Robert Sparks", "text": "what cullen was complaining about at the beginning of the meeting
", "time": "2022-07-25T14:37:53Z"}, {"author": "Jonathan Lennox", "text": "Robert: Yes, I joined that just fine, I didn't run into the problem at Cullen had.
", "time": "2022-07-25T14:38:37Z"}, {"author": "Richard Barnes", "text": "Adam: No draft AFAIK
", "time": "2022-07-25T14:38:47Z"}, {"author": "Kirsty Paine", "text": "Adam: there is no draft for this.
", "time": "2022-07-25T14:38:47Z"}, {"author": "Robert Sparks", "text": "So chairs: be sure to ask people in the room to use the QR code again now - it should work. Theory is that the wifi in the room was in the road at the beginning of the session.
", "time": "2022-07-25T14:39:08Z"}, {"author": "Jonathan Lennox", "text": "I did it from the agenda rather than the QR code, and from my laptop not my phone, if that makes a difference.
", "time": "2022-07-25T14:39:40Z"}, {"author": "Richard Barnes", "text": "this seems like a good opportunity to revive SHTTP (RFC 2660)
", "time": "2022-07-25T14:40:09Z"}, {"author": "Mark Nottingham", "text": "Standardise a format for the encrypted data, specify a fragment identifier to carry the key, boom - done.
", "time": "2022-07-25T14:40:34Z"}, {"author": "Deb Cooley", "text": "Looks like S/MIME to me...
", "time": "2022-07-25T14:40:55Z"}, {"author": "Erik Nygren", "text": "Also see OOB Encoding as somewhat related, but a somewhat different set of use-cases: https://tools.ietf.org/id/draft-reschke-http-oob-encoding-12.html
", "time": "2022-07-25T14:41:19Z"}, {"author": "Richard Barnes", "text": "see also https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-encryption-encoding-09
", "time": "2022-07-25T14:42:36Z"}, {"author": "Christian Ams\u00fcss", "text": "Fragment identifier is tempting; if the URI's resource is in a known encrypted content format, the authors are at liberty to describe how the fragment identifier would contain the key.
", "time": "2022-07-25T14:42:36Z"}, {"author": "Richard Barnes", "text": "but i think the OOB-encoding / RFC 8188 approach entails more change ?
", "time": "2022-07-25T14:43:23Z"}, {"author": "Christian Veenman", "text": "Wouldn't S/MIME solve the problem of HTML links being visible to intermediaries? Or is there a reason to not adopt S/MIME and implement something like this?
", "time": "2022-07-25T14:44:41Z"}, {"author": "Erik Nygren", "text": "(but yes, even with OOB-encoding there are key privacy properties it can't provide but wasn't really part of the scope)
", "time": "2022-07-25T14:44:47Z"}, {"author": "Christian Ams\u00fcss", "text": "If this were to step on 8188 Content-Encoding, the fragment identifiers might conflict with the plaintext's semantics
", "time": "2022-07-25T14:44:51Z"}, {"author": "Mark Nottingham", "text": "8188 doesn't seem like a clean fit for me, because the content-encoding doesn't specify the fragment identifier.
", "time": "2022-07-25T14:45:40Z"}, {"author": "Richard Barnes", "text": "Mark: What i was thinking is: OOB in the email, 8188 in the download
", "time": "2022-07-25T14:47:29Z"}, {"author": "Richard Barnes", "text": "might be a useful discussion for MIMI this afternoon, since this is something all the messengers have already done
", "time": "2022-07-25T14:48:11Z"}, {"author": "Mark Nottingham", "text": "urgh
", "time": "2022-07-25T14:48:13Z"}, {"author": "Ted Hardie", "text": "I think you can do this inside the URI, but the security properties amount to \"not much\"
", "time": "2022-07-25T14:48:21Z"}, {"author": "Adam Roach", "text": "Okay, is see the value here in a limited set of use cases, but this definitely suffered from not having a draft.
", "time": "2022-07-25T14:48:22Z"}, {"author": "Christian Ams\u00fcss", "text": "RB: The encrypted URI could redirect to one that semantically relates to the plaintext (but then is 8188 encrypted, and at that time the client has the key from being a fragment identifier on the encrypted URI)
", "time": "2022-07-25T14:48:52Z"}, {"author": "Mark Nottingham", "text": "Ted - yes. It'd be good to see the simple approach written up with enumerated security properties, so we can evaluate
", "time": "2022-07-25T14:49:00Z"}, {"author": "Ted Hardie", "text": "It's not clear that the additional privacy issues (that something got dereferenced) is worth \"not much\".
", "time": "2022-07-25T14:49:38Z"}, {"author": "John Klensin", "text": "While I have no trouble recognizing some of the people in the in-room mic line, I really wish people would do better at identifying themselves when the start speaking
", "time": "2022-07-25T14:50:18Z"}, {"author": "Pete Resnick", "text": "John, are you not seeing the queue in Meetecho? And Kirsty is trying to identify everyone as they speak.
", "time": "2022-07-25T14:51:38Z"}, {"author": "Kirsty Paine", "text": "I am saying full names to introduce people and it's also in the notes being taken: https://notes.ietf.org/notes-ietf-114-dispatch?edit
", "time": "2022-07-25T14:52:04Z"}, {"author": "Mike Bishop", "text": "OOB doesn't address this, since it's about Party A returning an HTTP response, not a simple URL. However, the Encrypted Content-Encoding seems very much on-point. Revive and advance that draft, then define a way to embed the key in the URI and we're done, no?
", "time": "2022-07-25T14:52:43Z"}, {"author": "Hang Shi", "text": "Wow, glad to see that RSS is relavent
", "time": "2022-07-25T14:52:51Z"}, {"author": "Bron Gondwana", "text": "Thanks everyone :)
", "time": "2022-07-25T14:53:47Z"}, {"author": "Adam Roach", "text": "Bron: FWIW, there are at least a couple of times I can think of in my career where I've deployed something very much like what you showed, and having an RFC would have been useful from a design perspective.
", "time": "2022-07-25T14:56:30Z"}, {"author": "Jabber", "text": "cabo: mnot: Zoom in to video might unfreeze it
", "time": "2022-07-25T14:56:42Z"}, {"author": "Murray Kucherawy", "text": "@Mark: You can send me the non-WG list request and I'll stamp it.
", "time": "2022-07-25T14:56:47Z"}, {"author": "Mark Nottingham", "text": "pause / unpause worked, thanks!
", "time": "2022-07-25T14:57:12Z"}, {"author": "John Levine", "text": "Agree Mark's thing is useful, there's a lot of quiet RSS use
", "time": "2022-07-25T14:57:29Z"}, {"author": "Lucas Pardue", "text": "could integrste web readers with PPM approach perhaps?
", "time": "2022-07-25T14:57:52Z"}, {"author": "Adam Roach", "text": "+1 to starting a list and seeing how much energy there is
", "time": "2022-07-25T14:57:56Z"}, {"author": "Jim Fenton", "text": "Agree, also hope this will get people thinking about RSS more
", "time": "2022-07-25T14:58:02Z"}, {"author": "Mark Nottingham", "text": "I'm thinking something generic like feeds@ietf.org (i.e., not just privacy necessarily)
", "time": "2022-07-25T14:58:28Z"}, {"author": "Adam Roach", "text": "We have no presenter camera
", "time": "2022-07-25T14:58:42Z"}, {"author": "Jim Fenton", "text": "Generic is good
", "time": "2022-07-25T14:58:53Z"}, {"author": "Ben Campbell", "text": "+1 for a list (and I still use RSS on a daily basis :-) )
", "time": "2022-07-25T14:58:57Z"}, {"author": "Murray Kucherawy", "text": "@Meetecho: front presenter camera is not sending
", "time": "2022-07-25T14:59:07Z"}, {"author": "Murray Kucherawy", "text": "fixed, thanks
", "time": "2022-07-25T14:59:38Z"}, {"author": "Lucas Pardue", "text": "this work seems valuable if only for UUIDv7
", "time": "2022-07-25T15:08:44Z"}, {"author": "Kirsty Paine", "text": "Lucas, want to make that point at the mic?
", "time": "2022-07-25T15:09:01Z"}, {"author": "Lucas Pardue", "text": "thanks Kirsty
", "time": "2022-07-25T15:09:44Z"}, {"author": "Robert Sparks", "text": "(someone quietly nudge cullen back into IM for me please?)
", "time": "2022-07-25T15:09:52Z"}, {"author": "Murray Kucherawy", "text": "RFC 4122 was AD-sponsored by Ted.
", "time": "2022-07-25T15:10:00Z"}, {"author": "David Schinazi", "text": "WG sounds good to me
", "time": "2022-07-25T15:10:01Z"}, {"author": "Cullen Jennings", "text": "hk
", "time": "2022-07-25T15:10:15Z"}, {"author": "Adam Roach", "text": "Agree that WG is the path
", "time": "2022-07-25T15:10:34Z"}, {"author": "Adam Roach", "text": "I think what I heard was more along the lines of whether it should be a one-and-done WG or something for the long-term care and feeding of UUIDs, with a bias to the latter
", "time": "2022-07-25T15:11:02Z"}, {"author": "Murray Kucherawy", "text": "We'll need charter developers. We can call for volunteers on the DISPATCH list.
", "time": "2022-07-25T15:11:31Z"}, {"author": "Pete Resnick", "text": "@Murray Kucherawy : Voluntell anyone who supported the proposal.
", "time": "2022-07-25T15:11:40Z"}, {"author": "Jim Fenton", "text": "Maybe we need training on charter writing to develop more charter writers
", "time": "2022-07-25T15:12:52Z"}, {"author": "Murray Kucherawy", "text": "@jim: Good suggestion.
", "time": "2022-07-25T15:14:53Z"}, {"author": "Jim Fenton", "text": "It was mostly my unfamiliarity with charter writing that stopped me from volunteering.
", "time": "2022-07-25T15:15:39Z"}, {"author": "Murray Kucherawy", "text": "I thought you'd done some.
", "time": "2022-07-25T15:16:06Z"}, {"author": "Jim Fenton", "text": "Contributed to some, but never wrote one. BTW, do we have rough consensus on the 1-and-done vs long-term WG question?
", "time": "2022-07-25T15:16:58Z"}, {"author": "Kirsty Paine", "text": "No, currently an open question
", "time": "2022-07-25T15:17:18Z"}, {"author": "Brad Peabody", "text": "Fwiw, whatever work Kyzer and I can do on this for a UUID WG we're totally willing to do. If we need to propose something in order to save writing time, etc. - if that would be helpful we can do that.
", "time": "2022-07-25T15:17:41Z"}, {"author": "Pete Resnick", "text": "Is this proposal being presented at AVTCORE? Trying to figure out why we wouldn't dispatch to them.
", "time": "2022-07-25T15:19:19Z"}, {"author": "Kirsty Paine", "text": "Pete: Some folks on the list were unsure if the work should proceed in its current form.
", "time": "2022-07-25T15:20:18Z"}, {"author": "Pete Resnick", "text": "Kirsty: Still seems like the people who could reasonably assess that are in AVTCORE.
", "time": "2022-07-25T15:21:03Z"}, {"author": "Pete Resnick", "text": "(deleted)
", "time": "2022-07-25T15:21:13Z"}, {"author": "Adam Roach", "text": "Assess?
", "time": "2022-07-25T15:21:38Z"}, {"author": "Jonathan Lennox", "text": "I agree this work is clearly in scope of AVTCore, and the people with the expertise to figure out whether it's a good idea are all there.
", "time": "2022-07-25T15:21:55Z"}, {"author": "Roni Even", "text": "My understanding is that in order to identify dropping priority in networking with the current security like quic it will be useful to have such information available to not in the rtp layer so maybe not in avtcore
", "time": "2022-07-25T15:22:14Z"}, {"author": "Adam Roach", "text": "+1 to AVTCORE
", "time": "2022-07-25T15:22:19Z"}, {"author": "Pete Resnick", "text": "Adam Roach said:
\n\n\nAssess?
\n
Couldn't find it in my brain.
", "time": "2022-07-25T15:22:37Z"}, {"author": "Jonathan Lennox", "text": "Though the DSCP parts would need some network-layer expertise. And the question of how a router reliably detects RTP is hard.
", "time": "2022-07-25T15:22:40Z"}, {"author": "Hang Shi", "text": "This work is not proposing modification to RTP, instead it maps RTP payload field to DSCP code point
", "time": "2022-07-25T15:22:41Z"}, {"author": "Kirsty Paine", "text": "Good discussion here, please bring those points to the mic when the queue opens!
", "time": "2022-07-25T15:22:47Z"}, {"author": "Hang Shi", "text": "DSCP part may go to TSVwg
", "time": "2022-07-25T15:23:11Z"}, {"author": "James Gruessing", "text": "Another +1 to taking this to AVTCORE
", "time": "2022-07-25T15:23:42Z"}, {"author": "Pete Resnick", "text": "I'll put myself in the queue to say that out loud.
", "time": "2022-07-25T15:23:54Z"}, {"author": "Roni Even", "text": "This is not rtp. It is transport and avtcore does not have the expertise
", "time": "2022-07-25T15:24:51Z"}, {"author": "Pete Resnick", "text": "Finish first.
", "time": "2022-07-25T15:25:06Z"}, {"author": "Adam Roach", "text": "Roni -- it's cross-disciplinary. E.g., the question of doing a direct mapping versus mapping based on a normalized RTP header extension is definitely an AVTCORE question
", "time": "2022-07-25T15:25:46Z"}, {"author": "Roni Even", "text": "the avtcore work is done in frame marking draft. The question is how to make it available in the transport level
", "time": "2022-07-25T15:27:16Z"}, {"author": "Roni Even", "text": "agree with Mo
", "time": "2022-07-25T15:29:33Z"}, {"author": "Murray Kucherawy", "text": "That mic is very low, and crosstalk from the other rooms is starting to bleed in.
", "time": "2022-07-25T15:32:01Z"}, {"author": "Andrew Campling", "text": "Volume from room mike is very low (or the current speaker is very quiet)
", "time": "2022-07-25T15:32:15Z"}, {"author": "Adam Roach", "text": "I'm a little lost -- server-to-edge is typically adaptive, but inside the network, you usually see SVC, which assumes a fair amount of overcapacity
", "time": "2022-07-25T15:32:17Z"}, {"author": "Kirsty Paine", "text": "I'm hearing that the use case needs clarifying, and that gains in performance need demonstrating (also from the list). Dispatch outcome: Update these aspects, and take to AVTCore and TSVWG for the DSCP-specific aspects.
", "time": "2022-07-25T15:33:19Z"}, {"author": "Adam Roach", "text": "Sounds right.
", "time": "2022-07-25T15:33:59Z"}, {"author": "Adam Roach", "text": "Honestly, there are probably some ART errata that were filed against SIP and its pantheon under TSV
", "time": "2022-07-25T15:39:55Z"}, {"author": "Adam Roach", "text": "s/errata/untriaged errata/
", "time": "2022-07-25T15:40:30Z"}, {"author": "Robert Sparks", "text": "adam is volunteering
", "time": "2022-07-25T15:43:37Z"}, {"author": "Robert Sparks", "text": "@Barry Leiba secdir chooses not to review documents. genart would be a better \"reviews everything\" team to point to.
", "time": "2022-07-25T15:44:43Z"}, {"author": "Adam Roach", "text": "MIMI, right?
", "time": "2022-07-25T15:46:09Z"}, {"author": "Kirsty Paine", "text": "Thank you, I forgot!
", "time": "2022-07-25T15:46:33Z"}, {"author": "Adam Roach", "text": "Rohan -- will there be remote participation?
", "time": "2022-07-25T15:48:25Z"}, {"author": "Richard Barnes", "text": "Adam - Rohan sent Webex details earlier today
", "time": "2022-07-25T15:48:45Z"}, {"author": "Adam Roach", "text": "Thanks! I'll go looking for them.
", "time": "2022-07-25T15:48:56Z"}]