Re: [Vcon] Email metadata in vCon

Orie Steele <orie@transmute.industries> Wed, 27 March 2024 21:47 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 E1FABC14CEFA for <vcon@ietfa.amsl.com>; Wed, 27 Mar 2024 14:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-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 HAV81LRI0xJC for <vcon@ietfa.amsl.com>; Wed, 27 Mar 2024 14:47:44 -0700 (PDT)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (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 35FB3C14F698 for <vcon@ietf.org>; Wed, 27 Mar 2024 14:47:44 -0700 (PDT)
Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1e034607879so2839205ad.0 for <vcon@ietf.org>; Wed, 27 Mar 2024 14:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1711576063; x=1712180863; 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=Wh5W8xnyTbFmbZTJea0y1yxmIYsXNSWaSvDUsXuxekE=; b=PrGTcrGY1kr4/Tba82COXwv1cFJzNHL1FOU4L9QBCzC+36YhqkgpL6FhnbtnMJZYWk cMRDkthcZdGYOIyPpKn0oN28zJA4ya2zBZd1tA/tGAfG7hVHZ3ZwIbQPeJOqPxd9Pd8i qhcd4qghc1isP4jjlFJ/8ZLImImeahgcFvVd/TFexdGWCT/q6kRRNgSZsWM0p89F9iWr xjlzWIvx3zWpzZoAClBeHrH4UotO38KfaZIPoHPxQ48dLhkphBzHBXMrxsPIc1XeTX+Q 3iKPvyUcBGtezWnWfdtEcT6BPyb7O7Tkw0C1DFe/FDgbgc7o258lqqqVUNBPVE3Uowi+ bj5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711576063; x=1712180863; 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=Wh5W8xnyTbFmbZTJea0y1yxmIYsXNSWaSvDUsXuxekE=; b=fdgnu7ymN67e1H1E8CKSJasD1tnwHNqKV3kHt/1q8eqHbqGNMNJqRqmeWOaR73+nd9 /Imn2YTiu6Ttqhqo5Kln/lNItB36gg+Ocflp0TaoRhClyHiEXPnowfMrPPhyZ9ofr9PM lQ2aicvo5xNMWT0TOz4ZVWs7ryzfVVMFv/VGyBe59wvjhteWqlXYh2PQ2OSFBwQJ6GR0 4RwU9USbGO9RFx7M42BAyb/BwyFPz1KRGUb+WUdxqKF8Pv4bMRPq6sGROZ8QGiMOQSGv xddau+OadVy8xR4uby4S/sYZyiRwS44JYYtKLm+ycG6lQkPhxvM8FNJ+2+ysulLW9k2F YbfQ==
X-Gm-Message-State: AOJu0YyUMN4kpEtKMC5NYqzCbZkn0MfRbPUDPRaat+mdXzkOYo4uyt5M VP0qbSGB69kytU7ExcJPGgop44Zr0GAy3KkCCuNsLX8E5Ne6RoScJ4N/zfFndfrO6x/hanrlGik roJPHCn49aUzGc456gIQDMW9caS76gsgOegpAnA==
X-Google-Smtp-Source: AGHT+IEYSJNHwDxsID7716QyA/Gf2Q8insuphuPVlByP7Z8wWrdNhddGKF7SRG6PetILkLLo0uWg8cm/afUsghp2XRs=
X-Received: by 2002:a17:903:11c6:b0:1e0:62bc:68d4 with SMTP id q6-20020a17090311c600b001e062bc68d4mr1217656plh.14.1711576063508; Wed, 27 Mar 2024 14:47:43 -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>
In-Reply-To: <CAN8C-_LqL_UWW+5NPJ0QzFzOOFtqoP61wU_HEwW9rGOWq9iefw@mail.gmail.com>
From: Orie Steele <orie@transmute.industries>
Date: Wed, 27 Mar 2024 14:47:32 -0700
Message-ID: <CAN8C-_JZXGZzVQVsY50qNtyQ5Te-55vSTrtj-0O0=C=0_kfaGw@mail.gmail.com>
To: Dan Petrie <dan.ietf@sipez.com>
Cc: vCon WG <vcon@ietf.org>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/related; boundary="00000000000045c1300614ab5b48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/vcon/nyq5RV3AsVabKaLvSTw6srwN0s8>
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: Wed, 27 Mar 2024 21:47:48 -0000

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>