<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title type="text">I-D list for Virtualized Conversations RSS Feed</title>
    <subtitle type="text">Document changes</subtitle>
    <id>urn:uuid:ead1efa5-8227-5f80-911b-700bceb91b3e</id>
    <updated>2026-03-12T14:02:07.144715+00:00</updated>
    <link rel="alternate" type="text/html" hreflang="en" href="https://datatracker.ietf.org/"/>
    <link rel="self" type="application/atom+xml" href="https://datatracker.ietf.org/group/vcon/documents/feed/"/>

    
    <entry>
        
        <title>vCon Lawful Basis</title>
        

        <link href="/doc/draft-howe-vcon-lawful-basis/"/>

        <id>urn:datatracker-ietf-org:event:1126849</id>
        
        <updated>2026-03-02T19:29:19.128052+00:00</updated>
        
        <published>2026-03-02T19:29:19.128052+00:00</published>
        
        <author>
            <name>Thomas McCarthy-Howe</name>
        </author>

        <content type="html">New version available: &lt;b&gt;draft-howe-vcon-lawful-basis-01.txt&lt;/b&gt;</content>

        <ietf xmlns="http://ietf.org/atom/datatracker/community">
          <type>new_revision</type>
          
          <group>none</group>
          
          
          
          <state type="draft">active</state>
          
          <state type="draft-iesg">idexists</state>
          
          
	  
	  <abstract>   This document defines a lawful basis extension for Virtualized
   Conversations (vCon) that provides standardized mechanisms for
   recording, verifying, and managing the lawful basis for processing
   data within conversation containers.  The lawful basis extension
   addresses privacy compliance challenges through structured attachment
   metadata, including the specific lawful basis being asserted,
   temporal validity periods where applicable, and cryptographic proof
   mechanisms.

   The extension is designed as a Compatible vCon extension that
   introduces lawful basis management capabilities without altering
   existing vCon semantics.  It defines a &quot;lawful_basis&quot; attachment type
   with structured records for each of the six lawful bases defined in
   regulations like GDPR, including consent, contract, legal obligation,
   vital interests, public task, and legitimate interests.

   Key features include automated lawful basis detection during
   conversation processing, auditable records with cryptographic proofs,
   granular purpose-based permissions for all lawful bases, documented
   justifications for other lawful bases, and integration with privacy
   regulations including GDPR, CCPA, and HIPAA.
</abstract>
	  <version>01</version>
	  
        </ietf>
    </entry>
    
    <entry>
        
        <title>vCon Lawful Basis</title>
        

        <link href="/doc/draft-howe-vcon-lawful-basis/"/>

        <id>urn:datatracker-ietf-org:event:1126848</id>
        
        <updated>2026-03-02T19:29:19.124576+00:00</updated>
        
        <published>2026-03-02T19:29:19.124576+00:00</published>
        
        <author>
            <name>Thomas McCarthy-Howe</name>
        </author>

        <content type="html">New version accepted (logged-in submitter: Thomas McCarthy-Howe)</content>

        <ietf xmlns="http://ietf.org/atom/datatracker/community">
          <type>new_submission</type>
          
          <group>none</group>
          
          
          
          <state type="draft">active</state>
          
          <state type="draft-iesg">idexists</state>
          
          
	  
        </ietf>
    </entry>
    
    <entry>
        
        <title>vCon Lawful Basis</title>
        

        <link href="/doc/draft-howe-vcon-lawful-basis/"/>

        <id>urn:datatracker-ietf-org:event:1126847</id>
        
        <updated>2026-03-02T19:29:19.063942+00:00</updated>
        
        <published>2026-03-02T19:29:19.063942+00:00</published>
        
        <author>
            <name>Thomas McCarthy-Howe</name>
        </author>

        <content type="html">Uploaded new revision</content>

        <ietf xmlns="http://ietf.org/atom/datatracker/community">
          <type>new_submission</type>
          
          <group>none</group>
          
          
          
          <state type="draft">active</state>
          
          <state type="draft-iesg">idexists</state>
          
          
	  
        </ietf>
    </entry>
    
    <entry>
        
        <title>The vCon - Conversation Data Container - Overview</title>
        

        <link href="/doc/draft-ietf-vcon-overview/"/>

        <id>urn:datatracker-ietf-org:event:1126536</id>
        
        <updated>2026-03-02T16:24:04.608788+00:00</updated>
        
        <published>2026-03-02T16:24:04.608788+00:00</published>
        
        <author>
            <name>Thomas McCarthy-Howe</name>
        </author>

        <content type="html">New version available: &lt;b&gt;draft-ietf-vcon-overview-01.txt&lt;/b&gt;</content>

        <ietf xmlns="http://ietf.org/atom/datatracker/community">
          <type>new_revision</type>
          <stream>ietf</stream>
          <group>vcon</group>
          
          
          
          <state type="draft">active</state>
          
          <state type="draft-iesg">idexists</state>
          
          <state type="draft-stream-ietf">wg-doc</state>
          
          
	  
	  <abstract>   A vCon is the container for data and information relating to a real-
   time, human conversation.  It is analogous to a [vCard] which enables
   the definition, interchange and storage of an individual&#x27;s various
   points of contact.  The data contained in a vCon may be derived from
   any multimedia session, traditional phone call, video conference, SMS
   or MMS message exchange, webchat or email thread.  The data in the
   container relating to the conversation may include Call Detail
   Records (CDR), call meta data, participant identity information (e.g.
   STIR PASSporT), the actual conversational data exchanged (e.g. audio,
   video, text), realtime or post conversational analysis and
   attachments of files exchanged during the conversation.  A
   standardized conversation container enables many applications,
   establishes a common method of storage and interchange, and supports
   identity, privacy and security efforts (see [vCon-white-paper])
</abstract>
	  <version>01</version>
	  
        </ietf>
    </entry>
    
    <entry>
        
        <title>The vCon - Conversation Data Container - Overview</title>
        

        <link href="/doc/draft-ietf-vcon-overview/"/>

        <id>urn:datatracker-ietf-org:event:1126535</id>
        
        <updated>2026-03-02T16:24:04.605375+00:00</updated>
        
        <published>2026-03-02T16:24:04.605375+00:00</published>
        
        <author>
            <name>Thomas McCarthy-Howe</name>
        </author>

        <content type="html">New version accepted (logged-in submitter: Thomas McCarthy-Howe)</content>

        <ietf xmlns="http://ietf.org/atom/datatracker/community">
          <type>new_submission</type>
          <stream>ietf</stream>
          <group>vcon</group>
          
          
          
          <state type="draft">active</state>
          
          <state type="draft-iesg">idexists</state>
          
          <state type="draft-stream-ietf">wg-doc</state>
          
          
	  
        </ietf>
    </entry>
    
    <entry>
        
        <title>The vCon - Conversation Data Container - Overview</title>
        

        <link href="/doc/draft-ietf-vcon-overview/"/>

        <id>urn:datatracker-ietf-org:event:1126534</id>
        
        <updated>2026-03-02T16:24:04.542251+00:00</updated>
        
        <published>2026-03-02T16:24:04.542251+00:00</published>
        
        <author>
            <name>Thomas McCarthy-Howe</name>
        </author>

        <content type="html">Uploaded new revision</content>

        <ietf xmlns="http://ietf.org/atom/datatracker/community">
          <type>new_submission</type>
          <stream>ietf</stream>
          <group>vcon</group>
          
          
          
          <state type="draft">active</state>
          
          <state type="draft-iesg">idexists</state>
          
          <state type="draft-stream-ietf">wg-doc</state>
          
          
	  
        </ietf>
    </entry>
    
    
</feed>
