Re: [Ietf-dkim] Proposals for tolerating mailing list modifications

Michael Thomas <mike@mtcc.com> Sat, 05 August 2023 16:15 UTC

Return-Path: <mike@fresheez.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 66DB7C151711 for <ietf-dkim@ietfa.amsl.com>; Sat, 5 Aug 2023 09:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.848
X-Spam-Level:
X-Spam-Status: No, score=-6.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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 (2048-bit key) header.d=mtcc.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 4eIjQC9zOOV3 for <ietf-dkim@ietfa.amsl.com>; Sat, 5 Aug 2023 09:14:55 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 C0450C151709 for <ietf-dkim@ietf.org>; Sat, 5 Aug 2023 09:14:55 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-686f25d045cso2231799b3a.0 for <ietf-dkim@ietf.org>; Sat, 05 Aug 2023 09:14:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; t=1691252095; x=1691856895; h=in-reply-to:subject:from:references:cc:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=P8Cs+l1i7twHp45dXw4iuv4YcXsPZxgIR5qQYL8NZi4=; b=AHwqEtkrbUBMrE4PXjY3q/PQWFUBYFHplFEXnnqpHAa75g1plW/1P4YUHIOJDjpTs/ 3ds8Ly3GqEKhvoTQaAAeXvBoAdG94d0whe0o/Lj9HgsHX9LPv7NM46rsUj+kPTAJJfPS 8cq/j8A2MLdxeBKl0ygTp5+bA2599WC4ogNIYPUhUwtlZ6MKAizaHi1u0fF8J3O82R6z kAxEjU9lZUh9wkX4ZkyI17SN82tiaBg6X2N7rz2LS5pwRgzKxlpVZinKkdh2aY2YcDLo PyP7i3BbMmSbEKA2KzVtsTS0IBqqzsYPEqC3rAilBiKJpeUXbiI5OheA1xzlYO4ayC1P nBGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691252095; x=1691856895; h=in-reply-to:subject:from:references:cc:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=P8Cs+l1i7twHp45dXw4iuv4YcXsPZxgIR5qQYL8NZi4=; b=kcaqYHMENJFM9rv7ij1shfB+EEhI31VuYy3JBmp+y9W4bhYZLjKztf6nM8NHsHPmLW AUJoh8fK1B3N79lP3TvwtSPjm2UDFvc6rKhlg3S7Lsr5DSa/abHZS6m56YIbYgHFn0ys vskTjjkZmJossRMx1Lme4rF471AjUzKLCuccIvyjlNp4f+kuG1wj9Qgb7siW6C+oBwUD R18YO4ZL71cT2Wb7qwAhEq1QgxpVISoZGR+zWkjEM6RJuggST+XVjse4YFdX2IVVyEf9 iOO9Rp9kyyWKaiJg0f7aXbPscuoovwlWEylI7bxuL4CZj+7TEHMTOfVyBdGgv+CXlAgN HEAA==
X-Gm-Message-State: AOJu0YzeFCA+bUA8tuef/cr1ZufK4Ck/MhankLZNB4MbzFskwTM86m6Q Ej9kbwsXSirqbboH+X45eRG72Q==
X-Google-Smtp-Source: AGHT+IE4vEqVuAT3m/u+ArBZxtS0wPt1GE1yoEcJ/VC5WVB/MAfvHPn8h2xuJY3FSaM81ug8IESEeg==
X-Received: by 2002:a17:902:d4c3:b0:1bb:c7bc:ceb4 with SMTP id o3-20020a170902d4c300b001bbc7bcceb4mr3953604plg.60.1691252094798; Sat, 05 Aug 2023 09:14:54 -0700 (PDT)
Received: from [192.168.1.201] ([206.107.197.106]) by smtp.gmail.com with ESMTPSA id r2-20020a17090a2e8200b00260cce91d20sm3199721pjd.33.2023.08.05.09.14.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 05 Aug 2023 09:14:54 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------JuDeRdlTz4TuJtztR47Vpm0o"
Message-ID: <4397fc60-a1a1-3df1-a7a1-7f1528cf9d42@mtcc.com>
Date: Sat, 05 Aug 2023 09:14:53 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.12.0
Content-Language: en-US
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: ietf-dkim@ietf.org
References: <CAAFsWK3uzVT3Kr7A03DXKTYEe6g+Ww0vX1tK7V3exogyjeek+A@mail.gmail.com> <760b4c18-46fa-f23d-88fa-100418aaeb72@mtcc.com> <CADyWQ+EK3pP_rfRoh+_dLFzWE5cw7ATwT-LLah=012pDQRPR9Q@mail.gmail.com> <9DEDECE4-4CA2-49E9-9502-95179ABE2EAF@bluepopcorn.net> <e532131a-20a0-d7e4-aad1-1478cd38bf0a@dcrocker.net> <F5B66298-C886-4873-807B-DB37D0AB84FC@bluepopcorn.net> <721103d5-afd8-a98c-6efa-95f82b661c7c@bbiw.net> <1FB729B8-543D-401E-AFB5-0779C2126DE1@bluepopcorn.net> <080b2574-0904-d819-e4c2-da62c2a46e07@mtcc.com> <CAL0qLwYp-9MrsugTtxDBf1KkF_LeJaCR-7SZ=R_NikgkTQBSAA@mail.gmail.com> <3608f591-c768-97b0-583a-724a92c3880d@mtcc.com> <CAL0qLwbCD5OYY+it4sfytDLEAGD+k0=tQ++2vfsXdfih3nEHng@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
In-Reply-To: <CAL0qLwbCD5OYY+it4sfytDLEAGD+k0=tQ++2vfsXdfih3nEHng@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/uXNBrE7hk5Bvlf6U8yAvyw9B9cQ>
Subject: Re: [Ietf-dkim] Proposals for tolerating mailing list modifications
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: Sat, 05 Aug 2023 16:15:00 -0000

On 8/5/23 9:05 AM, Murray S. Kucherawy wrote:
> On Fri, Aug 4, 2023 at 2:46 PM Michael Thomas <mike@mtcc.com> wrote:
>
>     Well, for starters ARC doesn't have broad deployment. But the
>     author doesn't say why ARC is needed or relevant. That is the
>     point here. *All* changes need to be justified including any
>     imported mechanisms. The less rat holes the better. Same with the
>     mailing list modification draft. Why is that even relevant?
>
>
> With respect to ARC: There's a difference between asking for 
> justification and demanding that the discussion be stopped before it 
> even starts.  One of those is not okay.

Ok, justify it. Even the author says ARC brings nothing to the table. 
That is not OK. Peddle the ARC agenda in a more appropriate venue.

>
> With respect to the MLM draft: Since this is the only IETF list that 
> covers DKIM specifically, that makes it a reasonable venue for raising 
> DKIM-related ideas that might exceed the charter.  I would agree that 
> this WG shouldn't take up any DKIM topics not related to the replay 
> problem, but I don't see an issue with announcing in this venue that 
> you have an idea and invite discussion off-list or in some other venue 
> for as long as this list is allocated to an active working group.
>
By all means, let's make this a cesspool of irrelevant junk. Especially 
for junk that clearly has no clue about the history of DKIM.

Mike