Re: [Vcon] Email metadata in vCon

Orie Steele <orie@transmute.industries> Wed, 27 March 2024 21:45 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 B30B9C1D4A90 for <vcon@ietfa.amsl.com>; Wed, 27 Mar 2024 14:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_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 tjFnHJsmvvE0 for <vcon@ietfa.amsl.com>; Wed, 27 Mar 2024 14:44:56 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (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 23DEEC1D4A92 for <vcon@ietf.org>; Wed, 27 Mar 2024 14:44:56 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id 98e67ed59e1d1-29f9af2e0b7so260597a91.1 for <vcon@ietf.org>; Wed, 27 Mar 2024 14:44:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1711575895; x=1712180695; 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=jRKoQTMZyqYfNnNgng/DtmizUW1y5oDI01T0BDjpfe4=; b=O/OszXwSgxlOsnCywa5oiBPs1Nw98TkV803FSb8QL8A25cJ/Nb6O2+umMRbgH3hn68 W4hnDqabTViUF0iXyS4+a+cjCzo3kXKHiivddqGc9jUkghuxsDG0rcvrE+3TX3YrD9K4 SRgB6Xt+heT5Z21eAg9TJFRlDz0hdidVFLCpC6yal6kPXjSD1OINCnS0V+CypNtR4kSa TNsAGBa+Kn6m9ZGPz6Ji8I92BgNZl5N/PhF2bSXIsn8pSRSt/h7fwiLD4pRULpsffYsx Jc46NrAKk96gy0B/xJg65q6nbjJpAKP72iNBmlWlKvJocVjeA/Rp7zxk9r/xM39HqMDy UUHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711575895; x=1712180695; 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=jRKoQTMZyqYfNnNgng/DtmizUW1y5oDI01T0BDjpfe4=; b=n3mYciWzn7MuHNJxPp0K2Um1lBukOitZOGnGLq57lwkItP9RjVSrXvsa463KPPkMcy 31E1Gqkb1itqvD3xEcbZBbf36wb3hM1PSlpWydYbhTw9R/TBI98zQqQXZHi6tAQhaePX xN5BeKjxO5kc8kDx4Bd83R3Oga2d89240KRYYqh5lQHgu+hOmbn++Ci7BPjRVpDc8SBu AnCAtPWJVHDKS1KbfUUkswDMXtJIxPgJVAYahC/fkm1H2+bJyWATplIdsRO0tJjcM1u2 0fTThpBPirpeHLCg6JA0taqhQGpdA4Ltusxt2sdELt4gXL6pbuDvnwv16klCDVrvTzkW xflA==
X-Gm-Message-State: AOJu0YydzKrkv6H153jDCcR5zVixLGZhSzIJpmPdWdp8iXULDUeDeycc ZgXdN36nAI28dQNnShvDsHs3+wCgNHjbPERAGq7xyR31hwnotSPkDQ7b98ow2ZCE7meTesIc1Kx D8ERqIeljzwYFSoQmozZqbqPK+r87AOYhejPHSw==
X-Google-Smtp-Source: AGHT+IFO/RKZmGkvfiP7SCCl4zVk0XApUhiwrdha7ZzNEDuUWTxYUlGxl9rSAkwlWvnRSp6SdZdenZqZTE3w/f/skNE=
X-Received: by 2002:a17:90b:3a8d:b0:2a2:2fd:8bd8 with SMTP id om13-20020a17090b3a8d00b002a202fd8bd8mr8959pjb.15.1711575895179; Wed, 27 Mar 2024 14:44:55 -0700 (PDT)
MIME-Version: 1.0
References: <923730760.1991278.1711573128213.ref@mail.yahoo.com> <923730760.1991278.1711573128213@mail.yahoo.com>
In-Reply-To: <923730760.1991278.1711573128213@mail.yahoo.com>
From: Orie Steele <orie@transmute.industries>
Date: Wed, 27 Mar 2024 14:44:43 -0700
Message-ID: <CAN8C-_LqL_UWW+5NPJ0QzFzOOFtqoP61wU_HEwW9rGOWq9iefw@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="0000000000003d46d20614ab5123"
Archived-At: <https://mailarchive.ietf.org/arch/msg/vcon/CHVFrZj4faRilIUGMpsvQ2az39k>
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:45:00 -0000

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>