Good evening all. I hope this is going to be useful. Looking forward to hearing what is intended for this work. Or I should have gone to bed...
", "time": "2023-03-29T00:30:29Z"}, {"author": "Robert Moskowitz", "text": "I am too tired to take meaningful minutes. But then even awake my minute taking always leaves a lot to be desired. :(
", "time": "2023-03-29T00:32:32Z"}, {"author": "Francesca Palombini", "text": "Identifying yourself is also helpful for the closed captions :)
", "time": "2023-03-29T00:39:21Z"}, {"author": "Robert Moskowitz", "text": "I am not seeing the slides to download so I can get the URLs that Spenser had up.
", "time": "2023-03-29T00:43:40Z"}, {"author": "Francesca Palombini", "text": "", "time": "2023-03-29T00:44:36Z"}, {"author": "Barry Leiba", "text": "Silo Killer\u2026 qu\u2019est-que c\u2019est\u2026
", "time": "2023-03-29T00:44:43Z"}, {"author": "Hans-J\u00f6rg Happel", "text": "I do not quite understand the issue in the migration case. If I want to move data between two devices I own, I did not quite understand what vCon would add here, that i currently missing
", "time": "2023-03-29T00:57:34Z"}, {"author": "Pete Resnick", "text": "@Hans-J\u00f6rg Happel If I understand correctly: The applications on the two devices, and more importantly the online services that each of the apps might use, might have no a priori relationship. It would be good if passing data between the two devices doesn't expose all of that data to intermediaries.
", "time": "2023-03-29T01:02:02Z"}, {"author": "Robert Moskowitz", "text": "If I am groking this, it has many uses in aviation. Depending on where things are going, I will see how to get interest for participation.
", "time": "2023-03-29T01:06:21Z"}, {"author": "Hans-J\u00f6rg Happel", "text": "@Pete Resnick Well, moving data will either require a trusted intermediary, direct API access vendor2vendor (which I understand is not what vCon is about?) or data import/export (via a shared format).So I guess we talk about the latter here? If so, I then wonder if that's not something developed in MIMI? (as this came from Rohan, it would be interesting to clarify the interrelation vCon vs MIMI?)
", "time": "2023-03-29T01:07:41Z"}, {"author": "Pete Resnick", "text": "I'm not clear that he's understanding Mallory's question. Someone may wish to help.
", "time": "2023-03-29T01:09:13Z"}, {"author": "Sebastian Benthall", "text": "How does one get on the queue to comment?
", "time": "2023-03-29T01:09:50Z"}, {"author": "Hans-J\u00f6rg Happel", "text": "@Sebastian: click raise hand icon in Meetecho
", "time": "2023-03-29T01:10:19Z"}, {"author": "Pete Resnick", "text": "In the Meetecho tool, raise your hand. If you're in the room: https://meetecho.ietf.org/conference/lite-agent.html?group=vcon
", "time": "2023-03-29T01:10:23Z"}, {"author": "Jon Peterson", "text": "I mean if you have any req for integrity, you will be deep in the keys / crypto anyway
", "time": "2023-03-29T01:10:23Z"}, {"author": "Jon Peterson", "text": "... so you're going to provide that chain of custody w/o integrity
", "time": "2023-03-29T01:12:34Z"}, {"author": "Pete Resnick", "text": "+1 to Jonathan's comment: The use cases need some \"combing\" to separate the IETF work items (interoperability needs) from the other stuff (internal vendor stuff). There's IETF work here (I think), but it definitely needs some clarification.
", "time": "2023-03-29T01:15:32Z"}, {"author": "Robert Moskowitz", "text": "I can see IETF work here. But I am falling asleep. Too much energy spent in meetings today. I raise my hand for a wg and will participate and try to get others in aviation interested, Hopefully see you at the plenary. Bye.
", "time": "2023-03-29T01:19:10Z"}, {"author": "Pete Resnick", "text": "I think Jonathan just volunteered for charter writing help. :wink:
", "time": "2023-03-29T01:21:22Z"}, {"author": "Jonathan Rosenberg", "text": "The VCON format will support encryption of the objects enclosed within it, in order to provide confidentality of the data independent of transport. The keying is out of scope.
", "time": "2023-03-29T01:27:24Z"}, {"author": "Cullen Jennings", "text": "+1 JDR
", "time": "2023-03-29T01:28:58Z"}, {"author": "Cullen Jennings", "text": "I did want to get the idea that different data could be secured with different keys to control access.
", "time": "2023-03-29T01:29:47Z"}, {"author": "Adam Wiethuechter", "text": "https://en.wikipedia.org/wiki/XACML is at least part of this somehow I feel
", "time": "2023-03-29T01:32:11Z"}, {"author": "Jonathan Rosenberg", "text": "Suggested text (which I will also send to the list):
\nUse Case 1: Privacy and Cutomer Data Protection
\nVendors and services which record conversations (such as contact centers), have a requirement to convey access logs to other vendor applications which analyze those access logs. By access logs, we refer to information about who accessed the recording, when they accessed it, and for what purposed it was accessed. Examples of \"purposes\" include - listening to a recording for purposes of quality assurance for a contact center call, or transcription of a recording to generate a text transcript.
", "time": "2023-03-29T01:35:13Z"}, {"author": "Adam Wiethuechter", "text": "If we are only about data elements and structures - use CDDL and then let implementors choose JSON or CBOR or whatever
", "time": "2023-03-29T01:41:05Z"}, {"author": "Jonathan Rosenberg", "text": "Use Case 2: Recording Exchange
\nAnother target use case is for exchange of recordings between different vendors. Today, it is common for vendors of contact center software, to send call recordings to third party services for the purposes of \"quality management\". In quality management, a human listens to the recording and rates the performance of the contact center agent. Today, the exchange of these recordings between vendors is done through raw audio files, with meta-data (such as time of the call and identity of the agent) exchanged out of bands. The goal with VCON is to enable a standardized exchange format between these vendors.
", "time": "2023-03-29T01:47:35Z"}, {"author": "Francesca Palombini", "text": "Jari clarifying question?
", "time": "2023-03-29T01:51:41Z"}, {"author": "Jaime Jimenez", "text": "I do not know if this is a valid use case but there are many APIs out there that allow to \"retrieve conversations\", it would be good to know how can vCON be applied on them to, for example, offer to the API consumer some insights about where was the conversation shared, proof of deletion, etc.
", "time": "2023-03-29T01:55:12Z"}, {"author": "Pete Resnick", "text": "I think you got the answer to \"what else would make it well-defined\" from Jari.
", "time": "2023-03-29T01:56:27Z"}, {"author": "Pete Resnick", "text": "It would be good to hear from the people who said \"no\" on the third question if they haven't said their piece before.
", "time": "2023-03-29T01:59:55Z"}, {"author": "Mallory Knodel", "text": "I couldn\u2019t find any visibility for the work in w3c fwiw. Plenty of reasons I would have missed it but still
", "time": "2023-03-29T02:00:51Z"}, {"author": "Alistair Woodman", "text": "Too much uncertainty to determine whether the direction is good or not
", "time": "2023-03-29T02:07:56Z"}, {"author": "Alistair Woodman", "text": "Too early to tell
", "time": "2023-03-29T02:09:05Z"}, {"author": "Pete Resnick", "text": "@Alistair Woodman +1, with the amendment that I suspect it will get to a reasonable place.
", "time": "2023-03-29T02:09:05Z"}, {"author": "Pete Resnick", "text": "Bob Moskowitz also mentioned earlier that he saw good use in the aviation industry for this.
", "time": "2023-03-29T02:12:37Z"}, {"author": "Francesca Palombini", "text": "Thank you Spencer for a very nicely run BoF!
", "time": "2023-03-29T02:19:06Z"}]