Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd
Craig Schwartz <craig@ftld.com> Thu, 06 June 2019 18:52 UTC
Return-Path: <craig@ftld.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 8EE0A120114 for <dmarc@ietfa.amsl.com>; Thu, 6 Jun 2019 11:52:40 -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=ftld.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 pPXxdgIxyApa for <dmarc@ietfa.amsl.com>; Thu, 6 Jun 2019 11:52:38 -0700 (PDT)
Received: from mail-it1-x129.google.com (mail-it1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 9628D1200C1 for <dmarc@ietf.org>; Thu, 6 Jun 2019 11:52:38 -0700 (PDT)
Received: by mail-it1-x129.google.com with SMTP id x22so1645033itl.2 for <dmarc@ietf.org>; Thu, 06 Jun 2019 11:52:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ftld.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KDs8Qgi+4JW4cSriyg7N2+ZC3qQSn5n0lgKM7nl3pG4=; b=T2zSTUO7z1aQfkFV9o/ciEPTMdkljdmREynd+1Sw1NMbSt9zJ6+N5vRYH47MK0ZStt WfxP8BqENcBvvUOM+sC1RKouAqZOEYaUqQf+7fFDZet/MfnvCgFIZgR8TqBjhqqi36XD XK4lTIHJTerjR0hcUyNjOeZA0UnmehzM3DssQ=
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=KDs8Qgi+4JW4cSriyg7N2+ZC3qQSn5n0lgKM7nl3pG4=; b=XufOkffp7F4PTzfl+KAF+4a4JhJUQlm8MwQY4XRecQCJONALTXjjXHMiPgOhB/s+p9 sly8iNXxg7CL/qtVEXU25PudPuPLwzL8njGSrhI3xzCFSudqybJHStpsHA9wVOyFqtbE bmdPXzOpPltCRuT+EO6Fa7oOHSDyCU13FxwOXrUrOX1EcXA+ZXaB3APgMz/xQfHMN1JZ GHlWrgAxrsO+J0djzY2pf+y23owoqql72RH15kiOUFlRKh881gCcRtme3wpohbbZorN7 lPil5JrYi2T9aMmrZ7Y9IL0g9JplecSqu809Y8E30nhgimFbsNJOuwg1QlhrnOJv9aaS L2KA==
X-Gm-Message-State: APjAAAW00yVAYUetvrdkWnYRCHdQU0DZATt4GJ9NW/y+raVb/RVdmzQU MadJKweR89qnCNYpjnxJ3XJF6tsP1wCmfx68qQ/xYt8I
X-Google-Smtp-Source: APXvYqwOxVOnHKVyb5nV6y3bIdnU/nJ2DIKKGYdRU/gRaqF78Hu8gAgnWn5a/oVFKKiivYjtLGlTJOrPWYM0s52u47o=
X-Received: by 2002:a24:3556:: with SMTP id k83mr1231605ita.19.1559847157528; Thu, 06 Jun 2019 11:52:37 -0700 (PDT)
MIME-Version: 1.0
References: <5130c7f40b444b97ab95864e6fc243ce@verisign.com>
In-Reply-To: <5130c7f40b444b97ab95864e6fc243ce@verisign.com>
From: Craig Schwartz <craig@ftld.com>
Date: Thu, 06 Jun 2019 14:52:26 -0400
Message-ID: <CAJ+U=1oa1jWbc00-+r=btA_4Tn9zx_rkpq7W4oEEngD674y9JA@mail.gmail.com>
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000baaeef058aac37e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-NIqG_S65sW9NEONuyLZuIuEgHg>
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: Thu, 06 Jun 2019 18:52:40 -0000
>On Thursday, June 6, 2019 at 1:12 PM EDT Scott Hollenbeck wrote: >I recently had a chance to read through draft-ietf-dmarc-psd. If I understand it correctly (and I'm not sure that I do), the document suggests that it's possible for a TLD like ".com" >to be a PSD and a TXT record like "_dmarc.com" can be published in the com zone. I found this part of the draft confusing because it's not possible to add TXT records like that >to the com zone. It might help to explicitly note somewhere (perhaps in Section 2.2) that there may be policy restrictions in place that disallow the publication of DMARC policy >records in some DNS zones, including some top-level domain zones. The purpose of the document is to convey technically how PSD DMARC can be accomplished rather than who can or cannot undertake this due to policy considerations. As the operator of .BANK and .INSURANCE, fTLD initiated this stream of work with the IEFT because of the explicit prohibition by ICANN from inserting TXT records in the DNS. The goal is to get to an RFC that specifies the technical aspect of PSD DMARC and ultimately seek ICANN's approval to allow publication of such a record in the DNS. In contrast, gTLDs not under contract with ICANN such as .MIL and .GOV, who are both involved in this work, do not have a contractual relationship with ICANN and thus are not prohibited from this activity, and the same goes for ccTLDs. Craig *--* Craig Schwartz Managing Director fTLD Registry Services | .BANK & .INSURANCE Office: +1 202 589 2532 Mobile: +1 202 236 1154 Skype: craig-schwartz www.fTLD.com On Thu, Jun 6, 2019 at 1:12 PM Hollenbeck, Scott <shollenbeck= 40verisign.com@dmarc.ietf.org> wrote: > I recently had a chance to read through draft-ietf-dmarc-psd. If I > understand it correctly (and I'm not sure that I do), the document suggests > that it's possible for a TLD like ".com" to be a PSD and a TXT record like > "_dmarc.com" can be published in the com zone. I found this part of the > draft confusing because it's not possible to add TXT records like that to > the com zone. It might help to explicitly note somewhere (perhaps in > Section 2.2) that there may be policy restrictions in place that disallow > the publication of DMARC policy records in some DNS zones, including some > top-level domain zones. > > Scott > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc >
- [dmarc-ietf] PSDs in draft-ietf-dmarc-psd Hollenbeck, Scott
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd Craig Schwartz
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd Hollenbeck, Scott
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd Scott Kitterman
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd Kurt Andersen (b)
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd Hollenbeck, Scott
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd Murray S. Kucherawy
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd John Levine
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd Hollenbeck, Scott
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd John Levine
- Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd John Levine