Re: [dmarc-ietf] Do is need a new ptype? Was Re: New authentication method, DNSWL

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 11 November 2019 07:48 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82720120844 for <dmarc@ietfa.amsl.com>; Sun, 10 Nov 2019 23:48:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eaRYWyr2jbGA for <dmarc@ietfa.amsl.com>; Sun, 10 Nov 2019 23:48:13 -0800 (PST)
Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8780C12083B for <dmarc@ietf.org>; Sun, 10 Nov 2019 23:48:13 -0800 (PST)
Received: by mail-vk1-xa30.google.com with SMTP id u79so2940595vke.4 for <dmarc@ietf.org>; Sun, 10 Nov 2019 23:48:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sfkq57pnt47iaJFB02j0M0T7kjl4EcB+x3nDfmPjcmM=; b=HRB+aGntlR5SI+Nhw9w12rMt4jOTwJ78XjeR+Hwbz/0UlLiAZ7Qb+Uk3awpvf5cw2C SBOO0JYXHxFJ/lInM/v9aquF627v1yXuGk9LsTyJ2ttfwmCtVwEBAxvIVFKwM50VEbzd 74PFlRt6UCGi2zTZmtztIE20sX69STalO8hQi1ZOxEiFr+TmdV0QpRVJJjt2xy/WfMR1 CtrOU6slSASrJVVEm68H5WxL9o9bAGSqRyOXzb9+ALV84kT0z68ic2HbKMF0SgeZ0ZGF l8sFWeEFEPezoDrkHJSprR6JxRdKo3uCl56Ih6CA7LBKZKLfjbKU7w76sa/Wo6mTogd9 y72w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sfkq57pnt47iaJFB02j0M0T7kjl4EcB+x3nDfmPjcmM=; b=Io5BlgSz2ysCjJF+Fjp5jUVvHYFcwhQDH2Fe6MsJh5/XvvRiMGckN7P8N45lg3hgyc W/8s8irl3utct75S+rNn/4adaF4lDm5xQ+HjZ0aX8anQ7XzQ3GK6MnZlmuTJtr8ctMCe hG86mVqp6e0M8WNPHFh4sX4H9OsuNh33kjWA64cSbXwu3uBp5sojKhfQLQXSfawIBgkD p0ciRwqZrhEfuHWT9kVrKHV26kZ0vKRHkUYwnTs5SIScH9YbS6R97PaGGMbOmPIde97Y rm0LcDtIUfpKzZU8FoLOhjAMStL/a8SAPNo9MWhYBr6AVlzIYtlI/4bC6OOkMXEMiHCd QIUg==
X-Gm-Message-State: APjAAAXw/Raa9GDZ4Us+N32m9PWea6iql1V2ZhnDBNKdsypOlmzF6Adf FoiM58eRL/YVj7I2cPby6WiMCBBgYgDHuA2tbRs=
X-Google-Smtp-Source: APXvYqwv4OL3hYyODUOuklpUHkia1b9Nowo+B1EeskL/G9K84psUsJxAOevYyn5mmldXgDhqBo/WzrmA8+pS6Lfinec=
X-Received: by 2002:a1f:2a82:: with SMTP id q124mr17087963vkq.8.1573458492506; Sun, 10 Nov 2019 23:48:12 -0800 (PST)
MIME-Version: 1.0
References: <e580ada3-d9b5-0e5b-9ac3-eade41ac92d2@tana.it> <CAL0qLwa5yR5dVzkDSD48MDgpUa11+ri=KOwrNSqOxi8fB2i6PA@mail.gmail.com> <eabefc6b-7542-1a46-4272-b786433ed0b5@tana.it> <4783309.BXR8ZdE9c3@l5580> <CAL0qLwb5FAaYZ7AX_H=aeUFkv8cvY+xd1bQ5uCDp4tmrbx2CQg@mail.gmail.com> <7a21b80b-e6bb-d8b9-cf63-601a8d1e47e7@tana.it> <C1E711A8-F3A6-4A20-B71D-53FA773A61D9@kitterman.com> <aca25d30-3b01-4eaf-6d0b-3bae6f3f796b@tana.it> <CABuGu1ogeUjW181MMOv3kApZR5njMMH6_84EnHxF0tDq6bhBkA@mail.gmail.com> <db4b1289-31cc-9b9e-bb5c-01bf8d6a37b3@tana.it> <CAL0qLwZcBGL8syD8FyOUkVqMzsmj4=uYM0NaSU2O3hte02AZVg@mail.gmail.com> <e45b7175-713e-da69-cc18-d0e4b59410c3@tana.it> <CAL0qLwZEEzvdvydrUUrBRRDfB-+3_7_9HB244qRC-+361cgwSg@mail.gmail.com>
In-Reply-To: <CAL0qLwZEEzvdvydrUUrBRRDfB-+3_7_9HB244qRC-+361cgwSg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sun, 10 Nov 2019 23:48:01 -0800
Message-ID: <CAL0qLwbo1AtJ6LG1UuSSoBC-GwjdQsc5CA2h6q5VqMxH=dxK5w@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000083c8b605970d5a1a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YCf_twL0ezY5a46LEmtCnCV6Ce8>
Subject: Re: [dmarc-ietf] Do is need a new ptype? Was Re: New authentication method, DNSWL
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2019 07:48:15 -0000

On Sun, Nov 10, 2019 at 10:30 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Mon, Oct 21, 2019 at 7:54 AM Alessandro Vesely <vesely@tana.it> wrote:
>
>> On Wed 07/Aug/2019 17:16:29 +0200 Murray S. Kucherawy wrote:
>> >
>> >> If the definition of ptype smtp were "a parameter of the SMTP session
>> used
>> >> to relay the message" it would be perfect.  I'd propose that
>> policy.iprev
>> >> be deprecated and smtp.remote-ip used instead>>
>> >
>> > Given that RFC8601 was published just last month, it'll probably be a
>> while
>> > before this happens.
>>
>> Wouldn't an accepted erratum be enough to change the wording in the IANA
>> page?
>>
>
> That's not what the RFC Editor erratum system is for.  The document
> reflects what the WG intended to publish at the time, so this isn't an
> erratum, it's a new change to the specification.
>

Just to be clear: The policy for changes to that registry is "Expert
Review", but since the action that put it there was a document with IETF
consensus, I'm pretty hesitant about just approving this change based on a
formal request.  I'd rather at least see some consensus discussion about
it, or even better, a revision/update to RFC8601.

-MSK, this time as DE