[Ietf-dkim] Tolerating Mailing-List Modifications I-D

Wei Chuang <weihaw@google.com> Wed, 12 July 2023 14:27 UTC

Return-Path: <weihaw@google.com>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4292C169501 for <ietf-dkim@ietfa.amsl.com>; Wed, 12 Jul 2023 07:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.597
X-Spam-Level:
X-Spam-Status: No, score=-17.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 NdOcn7deSqhs for <ietf-dkim@ietfa.amsl.com>; Wed, 12 Jul 2023 07:27:09 -0700 (PDT)
Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 0C333C169513 for <Ietf-dkim@ietf.org>; Wed, 12 Jul 2023 07:27:09 -0700 (PDT)
Received: by mail-il1-x136.google.com with SMTP id e9e14a558f8ab-34592151636so145ab.1 for <Ietf-dkim@ietf.org>; Wed, 12 Jul 2023 07:27:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1689172028; x=1689776828; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=gMO0b20EH50H4Lycw1jCsMCXt9gQ8FDB7fYOEWQLx4s=; b=n/BxS4o8dp8whIKOzsDzx1rUr7VyL0/wbAauGJMNA9Xbjy6WuMCLG1J3rcHMrxx9D3 ZT19ykYUsUSZCDq9wQOHzq0fCx+AO5pIH7MVfp6HR4TpB8nFG3ykDWfhsVmSFpqYqQvo Bw+gqRnMhxCf6MNc67imriOmEgPfRifn30EViPpI04JjEafv6nem4v4XTtaM4StyFMwt Vpy26YOy0oj5Z6zdXHR+EM/ybdLmBh6WO5EQA4nsBC5kJu9n0rwXR7+/hLqP/oNs6YyE ACxb3EU5kxJd3LsyH1k8RDsDMle/hwdtUL1PHCmYkXfQaBHstm09VuaFO9SJRQbrFRbx zlwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689172028; x=1689776828; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=gMO0b20EH50H4Lycw1jCsMCXt9gQ8FDB7fYOEWQLx4s=; b=Mlz8ilFvHUw/8LA9VQegvsXnyhPud5vr9/7ax9Zc68nRtLHy9Hn12bMa0o/fcamjdG ctnQfywwLB3JWHz7BuMHWiRfXXrvmvV3yCKdzcCEo58h3ZQGLOzQcwrBxAbNEh52KBfd OqJeqmKH6SyiV8DXhOnMzkLbsF8ROunMGYj2atjeMlrLXXXKs6l4Ucaq0FLXBw/pZJKE P4fT684dqJAnuqlctPxB2LaAsD2P26OBnwBwr6t9Ih9ncTVT7YA7f0c92INe4LVDjraZ 38R1Mwv2b7RCqs6HfBmE43vK4Urh8Z7xUu8fYPmyfmJsbWMHbHH0FfdgmPdO16krgCti 2GlA==
X-Gm-Message-State: ABy/qLZNOFT2epvGU8hp9mhtUNpz7vAtwzmtbwnLCTBzP4RXfLv4m3eL eySXOvp5wEl6KrXNmIK8QmJewt3KccAiptVZvsq6++DRGBLDsYXMlIs7lQ==
X-Google-Smtp-Source: APBJJlHVia0UZDucMqPcyB3k5Ln7SYEeK+GXbvdnVPRcXTpaH+r23AlzSjmv+7h5dSurX6hmvorzwN7qdHu1X5POd9E=
X-Received: by 2002:a92:7d01:0:b0:346:57c7:3e7b with SMTP id y1-20020a927d01000000b0034657c73e7bmr90995ilc.1.1689172026843; Wed, 12 Jul 2023 07:27:06 -0700 (PDT)
MIME-Version: 1.0
From: Wei Chuang <weihaw@google.com>
Date: Wed, 12 Jul 2023 07:26:45 -0700
Message-ID: <CAAFsWK20SojKgKjQB2MEuPh42ac5ta5bOhnHL8xPsidAigSOhQ@mail.gmail.com>
To: "ietf-dkim@ietf.org" <Ietf-dkim@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a35d9c06004b0209"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/0eX01aFX_DMibjWN2vuBCqEZE-c>
Subject: [Ietf-dkim] Tolerating Mailing-List Modifications I-D
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2023 14:27:10 -0000

Hi folks,
Being able to reverse mailing-list message modifications to repair the
message and enable digital signature verification, would resolve a
significant roadblock for further DMARC deployment.  Potentially it would
allow better attribution of which party contributed which content in the
message.  I propose some ideas around reversible mailing-list message
modifications in:
https://datatracker.ietf.org/doc/html/draft-chuang-mailing-list-modifications-00.
These modifications are: 1) prepending a description string to the Subject
header, 2) rewriting the From header, 3) removing the original
DKIM-Signature and 4) appending a footer to the message body.  (Apologies
that -00 draft is still in a rough form)

The idea of tolerating mailing-list modification by applying a reversible
transform has been proposed before such as:
https://datatracker.ietf.org/doc/draft-kucherawy-dkim-transform/
The approach in draft-chuang-mailing-list-modifications is to take a
smaller subset of the mailing-list changes in the transform draft but add
more descriptive detail around the changes.  It also builds on top of ARC
to tolerate multiple mailing-lists and uses
draft-chuang-replay-resistant-arc to provide path authentication.

-Wei