Markdown Version | Session Recording

Session Date/Time: 23 Jul 2025 09:30

vcon

Summary

The IETF vcon working group met to discuss the progress on VCon (Virtual Conversation Container) specifications. The session covered updates on document restructuring, core protocol specifications, extensions framework, consent management, and upcoming work items. Key presentations included an overview of VCon containers, the core JSON schema specification, contact center extensions, and a new consent attachment proposal.

Key Discussion Points

Document Restructuring

• The original VCon container document was successfully split into three separate documents:
  • Overview document: Informational document with use cases
  • Core document: Core protocols and JSON schema
  • Contact center extension: Specific extension model for contact centers
• All three documents are confirmed as working group items

Core Protocol Updates (Dan Petrie)

• Versioning approach: Decided to deprecate semantic versioning in favor of an extensions-based mechanism
• Extensions framework: Defined compatible vs incompatible extensions with "critical" parameter for extensions that must be understood
• Appended vs Amended: Changed "appended" to "amended" for deep copy operations; future "patched" object will handle incremental changes via separate extension
• New party identifiers: Added SIP URL and W3C Decentralized ID (DID) support
• Session ID: Added SIP session ID to dialogue objects

Technical Architecture Decisions

• JSON format: Confirmed JSON over CBOR for better application developer adoption
• Security forms: Three forms - unsigned (trusted environments), signed (data integrity), encrypted (data protection at rest)
• Content handling: Inline content for smaller files, external references for large files with hash verification
• Media type registration: In progress with IANA media type mailing list

Dialogue Content Scope Discussion

• Imagery in dialogues: Strong objection from Dan Petrie to including imagery in dialogue objects
• Transcribable content rule: Dialogue should only contain transcribable content; imagery should be attachments
• Edge cases: Discussion of fax communications and presentation slides as special cases
• Resolution: Defer to mailing list for further discussion on content categorization

Contact Center Extension

• Successfully extracted contact center-specific parameters into separate extension document
• Defined new parameters for dialogue and party objects specific to contact center use cases
• Extension mechanism validated through practical implementation

Consent Management (Thomas McCarthy)

• New standardized attachment: Proposed VCon consent attachment for structured consent management
• Required fields: Expiration, party identification, dialogue reference, consent array
• Optional enhancements: Terms of service reference, monitoring intervals, SCIT ledger integration, cryptographic proofs
• Integration with AI Prefs WG: Referenced AI preferences working group vocabulary for consent types

Decisions and Action Items

Decisions Made

1. Versioning: Adopt extensions-based versioning mechanism, deprecate semantic version parameter
2. Document status: All three split documents confirmed as working group items
3. Naming: Change "appended" to "amended" for deep copy operations
4. Extensions: Accept contact center extension as separate document
5. Core parameters: Keep dialogue application, disposition, and party UUID in core specification

Action Items

1. Dan Petrie:
   • Update core document with "amended" instead of "appended"
   • Add required encoding parameter guidance for dialogue objects
   • Resolve media type registration questions with IANA
2. Thomas McCarthy:
   • Upload new privacy primer version using extension framework
   • Address consent attachment feedback from Dan Petrie
3. Rowan May:
   • Upload updated MIMI messages document using extension framework
4. Jonathan Lennox:
   • Review extension mechanism against Q-Log precedent
   • Provide input on extension naming conventions
5. Working Group:
   • Continue dialogue vs attachment content discussion on mailing list
   • Review consent attachment proposal for extension vs attachment classification

Next Steps

1. Document reviews: Working group members to review updated core document and consent attachment proposal
2. Extension refinement: Finalize extension mechanism based on Q-Log review and community feedback
3. Consent framework: Address separation of SCIT-specific features from general consent mechanism
4. VCon lifecycle: Defer lifecycle document discussion to next meeting due to time constraints
5. Interoperability: Plan additional VCon interop events following successful April 2024 session
6. Implementation testing: Continue hackathon work on various VCon implementations and workflows