Re: [Vcon] Email metadata in vCon

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 12 April 2024 16:45 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: vcon@ietfa.amsl.com
Delivered-To: vcon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E08CAC14F691 for <vcon@ietfa.amsl.com>; Fri, 12 Apr 2024 09:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.086
X-Spam-Level:
X-Spam-Status: No, score=-7.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjDrqTWVwNV7 for <vcon@ietfa.amsl.com>; Fri, 12 Apr 2024 09:45:25 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 48E5CC14F68E for <vcon@ietf.org>; Fri, 12 Apr 2024 09:45:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1712940322; d=isode.com; s=june2016; i=@isode.com; bh=9p2BtAPOKsxdfKb5CGUkATsk5m3Az8elHzolOmWoN5Y=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=DXB0dIX8DrbMmvGUTY3YPK5XnVTHHqEiChxqcZJfFQcrsO0rnmnu9sk7ahvp4l8oSeJGBv kBJDWr+ZYSRYxRiYx5ZmmfiNQLx9gn1+Y7SDu02LKl8K5vqGrJrqb4mIAfGl8ZTOOWuWo5 mmg4yMC78z0J+5cEopvmb3cAKw1HNwM=;
Received: from [192.168.1.222] ((unknown) [31.117.114.119]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <ZhllIQAKdgpn@waldorf.isode.com>; Fri, 12 Apr 2024 17:45:21 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <7827756e-9810-4dc8-bf2b-a1337e4aee36@isode.com>
Date: Fri, 12 Apr 2024 17:45:20 +0100
User-Agent: Mozilla Thunderbird
To: Orie Steele <orie@transmute.industries>, Dan Petrie <dan.ietf@sipez.com>
Cc: vCon WG <vcon@ietf.org>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
References: <923730760.1991278.1711573128213.ref@mail.yahoo.com> <923730760.1991278.1711573128213@mail.yahoo.com> <CAN8C-_LqL_UWW+5NPJ0QzFzOOFtqoP61wU_HEwW9rGOWq9iefw@mail.gmail.com> <CAN8C-_JZXGZzVQVsY50qNtyQ5Te-55vSTrtj-0O0=C=0_kfaGw@mail.gmail.com> <CAN8C-_L6AXGaPx_SE_4Cjk7=i8jUzwx=NcAGTZ1VhbBeQrfufA@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <CAN8C-_L6AXGaPx_SE_4Cjk7=i8jUzwx=NcAGTZ1VhbBeQrfufA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------9dowieF0gHUSyD6Fog3jOFrN"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/vcon/5j7UVeD7of-UZKbmVXrghtCG4pw>
Subject: Re: [Vcon] Email metadata in vCon
X-BeenThere: vcon@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: container for conversation data <vcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vcon>, <mailto:vcon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vcon/>
List-Post: <mailto:vcon@ietf.org>
List-Help: <mailto:vcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcon>, <mailto:vcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2024 16:45:30 -0000

Hi all,

On 04/04/2024 20:05, Orie Steele wrote:
> Following up on this, I was reading 
> https://www.rfc-editor.org/rfc/rfc4155.txt recently.
>
> I wonder if there are JSON Email representations that vCon might more 
> directly defer to?
I am not aware of a full JSON representation, but something like 
<https://schema.org/EmailMessage> might be useful for vCon?

> I was hoping there might be some JSON based email representation that 
> vCon could cite or otherwise use without redefining terms.
>
> I came across:
>
> https://datatracker.ietf.org/doc/draft-ietf-sml-structured-email/
>
> I wonder if JSON-LD for vCon had been previously discussed, or had 
> there been any conversation about how vCon and SML might fit together 
> or not?

SML WG is not chartered to define Email representation in JSON. SML is 
tasked with documenting JSON representations for specific objects like 
flight itinerar that can be included in regular email messages.

Best Regards,

Alexey

>
> OS
>
>
>
> On Wed, Mar 27, 2024 at 4:47 PM Orie Steele 
> <orie@transmute.industries> wrote:
>
>     Context for Dan and Alexey:
>
>     - https://datatracker.ietf.org/doc/charter-ietf-vcon
>     - https://datatracker.ietf.org/doc/draft-petrie-vcon
>
>     We had some hallway conversations at IETF 119, about using vCon &
>     SCITT for transparency and archival purposes.
>
>     Regards,
>
>     OS
>
>     On Wed, Mar 27, 2024 at 2:44 PM Orie Steele
>     <orie@transmute.industries> wrote:
>
>         Adding a few email experts (I am not an email expert).
>
>         These parameters look correct to me for vCon, but I am not
>         sure if there are additional email details that should be
>         considered for archival use cases.
>
>         I also wonder if there is any encryption or signing
>         information which might be retained in a useful way, such that
>         a holder of a vCon and some trust roots might confirm that
>         parts of a vCon have not been tampered with, without using the
>         custom JOSE approaches in the draft today.
>
>         I'm thinking specifically of the case where I might know that
>         a Party had a particular key at a point in time, and I might
>         be able to use that key to verify an email message that had
>         been archived in vCon.
>
>         I suppose there could also be DMARC / DKIM fields that we
>         might expect to see preserved per message.
>
>         Regards,
>
>         OS
>
>         On Wed, Mar 27, 2024 at 2:03 PM Dan Petrie
>         <dan.ietf@sipez.com> wrote:
>
>             Hi Orie:
>             You are probably swamped, catching up after IETF 119. 
>             When you have a few minutes, it would be great to have
>             your input on this.
>
>             I think that you have worked with email in a vCon more
>             than many people have so far.  However, if anyone else on
>             the list has any thoughts on this, I would greatly
>             appreciate your input too.
>
>             I have done a little work putting email messages into a
>             vCon, one message per dialog.  Mostly, my use was in some
>             simple unit tests and in generating examples for the I-D.
>             The table below maps the SMTP headers that I have put into
>             a vCon.
>
>             Are there any other SMTP header fields or metadata that
>             you think should be possible to include in a vCon?
>
>             Do you agree with the mapping from SMTP to vCon parameters?
>
>             Cheers,
>             Dan
>
>             Inline image
>
>
>
>
>         -- 
>
>
>         ORIE STEELEChief Technology Officerwww.transmute.industries
>
>         <https://transmute.industries>
>
>
>
>     -- 
>
>
>     ORIE STEELEChief Technology Officerwww.transmute.industries
>
>     <https://transmute.industries>
>
>
>
> -- 
>
>
> ORIE STEELEChief Technology Officerwww.transmute.industries
>
> <https://transmute.industries>
>