Re: [dmarc-ietf] DMARC2 & SPF Dependency Removal

Barry Leiba <barryleiba@computer.org> Sat, 10 June 2023 02:20 UTC

Return-Path: <barryleiba@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 427ADC151B27 for <dmarc@ietfa.amsl.com>; Fri, 9 Jun 2023 19:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.547
X-Spam-Level:
X-Spam-Status: No, score=-1.547 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.096, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 ldtLagrLTrOG for <dmarc@ietfa.amsl.com>; Fri, 9 Jun 2023 19:20:27 -0700 (PDT)
Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.49]) (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 8E487C1519B7 for <dmarc@ietf.org>; Fri, 9 Jun 2023 19:20:22 -0700 (PDT)
Received: by mail-ej1-f49.google.com with SMTP id a640c23a62f3a-97467e06511so393948166b.2 for <dmarc@ietf.org>; Fri, 09 Jun 2023 19:20:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686363621; x=1688955621; h=content-transfer-encoding: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=Rc/Co9Xhd4RRAi8jjAsaIUu2/UkiVLffayM6PLJwJhk=; b=ALcOjvYXUW7457lxqCs2eBIhpG8IZXkCAxxw3PvxbeRJi/XoAm57hCkAAUUUR4JW/o q0vE+OO/8g91XyJVCtGH+yn7QQuOBOGasiRdsLqBSX7cP3R7rRSedyuUHLCZ16yY237f NSEGF48LfrUoGTMOqre8vOSWua+TcoNvgaDUtnJFXkvlMomgLr8Bkrmgx4o4yIBGKecH /xaRQJVzpvrZxcxljT3DSkW6INf5gxVWxE0OJhuy/gBiRozrR4mFi9gbvmd94ozozi6o UqxckN2L0HXZ3HS54T9zW1gXu7z2T/05+YTXJFHmm0iyIw2CVedJASqFZkkdKg6UL8T3 wRwA==
X-Gm-Message-State: AC+VfDwd1j3/4CDrlt4vNlEe19bmjqeD2PGyObdjIToYW/6IoxjMyW6c M3ljhmJyhEh9ZrN6bZxYGB2Gz2DFB+J6gqHsZ5c=
X-Google-Smtp-Source: ACHHUZ4LpPdA7EVKaMn5CUSnMXJLHKTbwPZnoNQ5n165aVhvvxZx6497HAZ2aoe4/ACfbtypKTZSEz/T7N+5Bd9kBmQ=
X-Received: by 2002:a17:907:26ca:b0:974:1e0e:9bd4 with SMTP id bp10-20020a17090726ca00b009741e0e9bd4mr3685280ejc.16.1686363620641; Fri, 09 Jun 2023 19:20:20 -0700 (PDT)
MIME-Version: 1.0
References: <30BB83B2-B454-41B8-992B-8E2569802D9C@1und1.de> <CAL0qLwbx6Y=kmB5pQZx8gNqD=rLBYz1vLOX6ngL=wUHHUm0Hjw@mail.gmail.com> <CAH48Zfz3jo6Jy7ByfS9EM8Luy5atEtuTMtvDfYuo56Gj9ryRcw@mail.gmail.com> <CALaySJ+obaK85BhemSBTJTxJCjMn++1vcTs8RyGJW5XCrtAHeg@mail.gmail.com> <CALaySJLn1eMLKOuEDARyD8smV7frZPXhU5rn4Uq_Oyh43djzjw@mail.gmail.com> <05589B27-AB12-4186-AF2E-EB5002332DD8@icloud.com> <CALaySJLQKSZNBBV=T5xFvReQo+YS=r9nvpwO9Ld5-KKsir9jnw@mail.gmail.com> <B042C5BA-4DE3-4CBE-BD6F-EBEC983D0114@isdg.net>
In-Reply-To: <B042C5BA-4DE3-4CBE-BD6F-EBEC983D0114@isdg.net>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 09 Jun 2023 22:20:08 -0400
Message-ID: <CALaySJLbUhBiTiA+X5J0wwR4usUzfeM0ed6UUUSut4RSyms6EQ@mail.gmail.com>
To: Hector Santos <hsantos=40isdg.net@dmarc.ietf.org>
Cc: dmarc@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/d9HakYG9Y38G-hHTYrsa_JpQZE4>
Subject: Re: [dmarc-ietf] DMARC2 & SPF Dependency Removal
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 10 Jun 2023 02:20:28 -0000

1. It is out of the scope of our charter to make any changes to SPF,
and that would include making it obsolete or Historic.

2. It is within the scope of our charter to make changes to DMARC, and
that would include removing SPF evaluation from it.  During the
process of making changes to DMARC we can also choose to change the
version number (or not).

We're discussing (2).  We will not discuss (1) at all, in any way.

Barry

On Fri, Jun 9, 2023 at 8:55 PM Hector Santos
<hsantos=40isdg.net@dmarc.ietf.org> wrote:
>
> Barry,
>
> Whoa! Take it easy.
>
> We are on the DMARC2 thread per topic - a proposal. Not anything for the current DMARCbis.
>
> Is the chair suggesting the current charter for DMARCbis should change to remove SPF? Was the charter changed for this?
>
> To be clear, DMARC2 is not DMARCbis right now, are you wishing this now?
>
> Hector
>
>
> > On Jun 9, 2023, at 8:27 PM, Barry Leiba <barryleiba@computer.org> wrote:
> >
> > Hector, did you not understand this?:
> >
> >>> We will *not* consider what should happen to
> >>> SPF outside of DMARC, and any discussion of that is *out of scope* for
> >>> this working group under its current charter.
> >
> > Please stop discussing it.
> >
> > Barry
> >
> > On Fri, Jun 9, 2023 at 8:23 PM Hector Santos <sant9442@icloud.com> wrote:
> >>
> >>> On Jun 9, 2023, at 4:41 AM, Barry Leiba <barryleiba@computer.org> wrote:
> >>>
> >>> Repeating this one point as chair, to make it absolutely clear:
> >>>
> >>> The proposal we're discussing is removing SPF authentication from
> >>> DMARC evaluation *only*.  We will *not* consider what should happen to
> >>> SPF outside of DMARC, and any discussion of that is *out of scope* for
> >>> this working group under its current charter.
> >>>
> >>> Barry, as chair
> >>
> >> For the record,  from a long time SMTP implementer standpoint, DMARC would be ignored, dropped, turned off, etc first before any consideration to stop SPF support.   As a Transporter, SPF works. As an Administrator - ADSP, I mean “Supper ADSP” aka DMARC has been horrible.  I, and most people, could easily deprecate Wildcat! DMARC with no harm and fact, less harm because the false positives will disappear.  My product add-on for wcSMTP, wcDMARC, never did honor the p=reject|quarantine. It was left for filters and no one hard any confidence to make it work.
> >>
> >> SPF on the other hand, I don’t see dropped in the name of DMARC.  So if it’s about sparate, but not abandon, that I can support - because it is already separate.  SPF preempts DMARC or any Payload protocol..
> >>
> >> Thanks
> >>
> >
> > _______________________________________________
> > dmarc mailing list
> > dmarc@ietf.org
> > https://www.ietf.org/mailman/listinfo/dmarc
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc