IETF Logo Mail Archive

Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd

"Kurt Andersen (b)" <kboth@drkurt.com> Tue, 11 June 2019 01:08 UTC

Return-Path: <kurta@drkurt.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 1B9B412008D for <dmarc@ietfa.amsl.com>; Mon, 10 Jun 2019 18:08:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=drkurt.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 2POJljVsedYv for <dmarc@ietfa.amsl.com>; Mon, 10 Jun 2019 18:08:13 -0700 (PDT)
Received: from mail-it1-x131.google.com (mail-it1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 D68E7120048 for <dmarc@ietf.org>; Mon, 10 Jun 2019 18:08:12 -0700 (PDT)
Received: by mail-it1-x131.google.com with SMTP id x22so2156121itl.2 for <dmarc@ietf.org>; Mon, 10 Jun 2019 18:08:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W51H/9j5Y6XNIc2dqE5DJyJuXOd893BdWwXJIFIUFDY=; b=U9NFrKuz2wrzhRW0HBgNj3UNmPGa2r8kDkHJwU51XohvhMWxonjgHArpsfMqgHwxZJ YkMzMTBACKAGYfiDY/pYEmuysiv3nbuzF75kunnGz0vUo7tjo7tSBXVE48phvqOky/84 IN7aonceBZQi5mZB0tBbeklOyuY9n4w0fuzeQ=
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=W51H/9j5Y6XNIc2dqE5DJyJuXOd893BdWwXJIFIUFDY=; b=pCbi99PVkQ+8YqpI8vUBjxqsUThHMhZEcylDHUptx9XKhJRQMYF/lP2uvUiOLgUTt8 wDWbsmvzHHAGIVnTNUSq4AfXI0huSCQ2iOF0oDJLARCR3jGBPoM9Zxsx86uBIzgi9f1w zKQAPwbK7mX4H+ltH55zlPBeZQk9BO3qm9lniYEQQg3wsrOMFmS12kBBk3tYMwTqOqKu pjBmTl62NDRGsmr0NdWQgG2s9WED2ZJMxw6cS8zzqTwbbF4g2qEbz2TqgYKR/TVcNHmn fXDaCwNPP4TTk1z/fGzrjMJpdgUfn8tnnftdFASDDSmEWtjXF0BlevUL7lIE9yVv51R2 ufcw==
X-Gm-Message-State: APjAAAX17Ss9mB5kPfON476hmJl6e97PuGhqvFjwOB7K4dYP73xJR9gY +MLexQptr9psBy2y9efuitp4DKkLOgR2mhCTHGjMfQ==
X-Google-Smtp-Source: APXvYqwKG2p5wdJco2mksay6wMfdaOiG153BqgKKMej1x2wAG1sNY5Vu8fRX5CjQVN33TYHujII/kEt1SPTDz6R+MSM=
X-Received: by 2002:a02:1649:: with SMTP id a70mr49180495jaa.116.1560215291770; Mon, 10 Jun 2019 18:08:11 -0700 (PDT)
MIME-Version: 1.0
References: <5130c7f40b444b97ab95864e6fc243ce@verisign.com> <CAJ+U=1oa1jWbc00-+r=btA_4Tn9zx_rkpq7W4oEEngD674y9JA@mail.gmail.com> <bb2dff4230404b0c8845f0a78d943e3a@verisign.com> <2221039.c73XDibtHi@l5580>
In-Reply-To: <2221039.c73XDibtHi@l5580>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Tue, 11 Jun 2019 09:07:59 +0800
Message-ID: <CABuGu1rcqHvX0rNS=GGEhWBJdbhwa9=65_rYNAQbMLw-89ViiA@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003d733e058b01eeb8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/CsCLZi5h0-P3cLDaW0PbHsjHBJA>
Subject: Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd
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: Tue, 11 Jun 2019 01:08:15 -0000

On Tue, Jun 11, 2019 at 6:31 AM Scott Kitterman <sklist@kitterman.com>
wrote:

> On Friday, June 7, 2019 7:02:59 AM EDT Hollenbeck, Scott wrote:
> >
> > It would be helpful to the reader if the draft were either clear about
> > potential limitations to deployment or more descriptive about the domains
> > for which the approach can work. Right now, PSD DMARC cannot be deployed
> > ubiquitously. That reality should not be overlooked.
>
> I see your point, but I think it's probably out of scope.  This is an IETF
> document and such restrictions are outside the IETF's control.  Also, keep
> in
> mind that once an RFC is published, it is immutable.  If that guidance
> changes, then there would be no way to correct the document without
> spinning
> up a whole new RFC process.
>
> Is there a public, stable reference that describes the restrictions?  If
> so,
> it might make sense to reference it.  If we can, I think that would be
> much
> better than 'hard coding' the current external policy in an RFC.
>

Including this information in the draft would be counter-productive. A
large part of this effort is to document the desired handling so that the
RFC can be used as documentation to support a change in ICANN policy.

--Kurt

v2.23.0 | Report a Bug | By Email