Re: [Vcon] Email metadata in vCon
Orie Steele <orie@transmute.industries> Thu, 04 April 2024 19:07 UTC
Return-Path: <orie@transmute.industries>
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 E3FE1C14F6A0 for <vcon@ietfa.amsl.com>; Thu, 4 Apr 2024 12:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, 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 (2048-bit key) header.d=transmute.industries
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 6WNQNikHGuVl for <vcon@ietfa.amsl.com>; Thu, 4 Apr 2024 12:07:25 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21192C151093 for <vcon@ietf.org>; Thu, 4 Apr 2024 12:05:56 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id 41be03b00d2f7-5d3912c9a83so925116a12.3 for <vcon@ietf.org>; Thu, 04 Apr 2024 12:05:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1712257555; x=1712862355; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ty4hX3B68KXeqpg1R+L5QhzrEy/U01OH13s822vSu9Y=; b=U300UTq/XtzglEo9NeGXPkyUtPUGlDg/8xlArnNJzcQGeil49GWY5bei0yFZFFdAyh hQf58zjS2xshIXdktcQozQi5SCkWEBjOg4eHPqU9syUSIl5JjOMBMSz8Oy7rq4oZlkoF 2+aMJuBTKurgoP8wXPwK93qeyQwt57NLXAb3KsTTTReJPR57HUsU5XmzmxhUSqdkPT6j E+QBNpmbcxK/CJ8VSwG5DDUrAagnGaWOtoYq8Tl8xb7TmP5jbJ8gdUecBcDR8lPOWr1R pcJga4fKIIlNhKu8dwJFMRuVO4cCejU7M8p4PErg1hdCJqCFYlCyIlS9wqT0+oZKdaca u1GQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712257555; x=1712862355; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ty4hX3B68KXeqpg1R+L5QhzrEy/U01OH13s822vSu9Y=; b=hTZDfPOr0E2R6TwzXiKwEmsIPx9APjER5IWsbqlVZxVrJxJbVlX6hy24yuU6nnT7O/ z9JEyN7l9Ug62rAoARUCPsfcdnH43EifZ93La2qqZxYWfMsvZOzE2dH77t31JLbXv2z5 wlwZIlfUyfwG5T/LGuCIGMu/pWzdMz3Ch2ouZFGMFyN7Q3umEOuso/XeG3OEn+FLf/2d X2xCID3uaOSC06HgIDB5p2ehEKEq9chOdf/0tz+9ADqkLJJmwQ6bxKt0c5TVRYsbCPP7 ocBTNBP1oDvn+fMekMXYaXHRh5L1pFkyJg2wog2eSIZ1+zsZAdke+AGhZkNc1SHoaIge h4zA==
X-Gm-Message-State: AOJu0YwwYkzBZPSRZcymZg77vkIBdJiW9y04Uwqy/rhlAAHzJOUFa5qz kzPPMJlNfpdfoykJPwjoqbMytorx8EQdz279rtYNc7tfo0D09HvFWWihr9scOp84uMO0vEe8TV7 tcnxu5oGyuY2MeARvH4SaZr+CxrwLwo2pQNnaM6htJ6kuMhbIhworsA==
X-Google-Smtp-Source: AGHT+IG02ksMtPg6qN4WqJQ922ELbqj4+qVctzb5xc6UxaPw153w05i5azeFa8dptF2gPgwVdPsvKslFWZFJdxZYuwM=
X-Received: by 2002:a17:90a:f510:b0:2a2:8065:899f with SMTP id cs16-20020a17090af51000b002a28065899fmr3089476pjb.41.1712257555193; Thu, 04 Apr 2024 12:05:55 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <CAN8C-_JZXGZzVQVsY50qNtyQ5Te-55vSTrtj-0O0=C=0_kfaGw@mail.gmail.com>
From: Orie Steele <orie@transmute.industries>
Date: Thu, 04 Apr 2024 14:05:43 -0500
Message-ID: <CAN8C-_L6AXGaPx_SE_4Cjk7=i8jUzwx=NcAGTZ1VhbBeQrfufA@mail.gmail.com>
To: Dan Petrie <dan.ietf@sipez.com>
Cc: vCon WG <vcon@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Content-Type: multipart/related; boundary="000000000000579de306154a0775"
Archived-At: <https://mailarchive.ietf.org/arch/msg/vcon/7D9aU_XYTvq-k2CikGwD6NLNJsQ>
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: Thu, 04 Apr 2024 19:07:30 -0000
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 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? 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 >>> >>> [image: Inline image] >>> >>> >>> >> >> -- >> >> >> ORIE STEELE >> Chief Technology Officer >> www.transmute.industries >> >> <https://transmute.industries> >> > > > -- > > > ORIE STEELE > Chief Technology Officer > www.transmute.industries > > <https://transmute.industries> > -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
- [Vcon] Email metadata in vCon Dan Petrie
- Re: [Vcon] Email metadata in vCon Orie Steele
- Re: [Vcon] Email metadata in vCon Orie Steele
- Re: [Vcon] Email metadata in vCon Orie Steele
- Re: [Vcon] Email metadata in vCon Dan Petrie
- Re: [Vcon] Email metadata in vCon Alexey Melnikov
- Re: [Vcon] Email metadata in vCon Alexey Melnikov
- Re: [Vcon] Email metadata in vCon Dan Petrie