Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd

Craig Schwartz <> Tue, 04 February 2020 00:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DE5FE1200B1 for <>; Mon, 3 Feb 2020 16:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eaW8bkuyu2uS for <>; Mon, 3 Feb 2020 16:25:20 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 90291120025 for <>; Mon, 3 Feb 2020 16:24:43 -0800 (PST)
Received: by with SMTP id m16so20673221wrx.11 for <>; Mon, 03 Feb 2020 16:24:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XKl+Ub2r4X8f9e/3j+IQMF+ImMKGU0zKD6Ek6vOi3uM=; b=QZIw6jRf7cJel1dgNJIGN2vxkKcKJOOHaU9b5Cs23TFPm96JU4bC1X5FqEbKhDHWnU ygjGPznFmvUJ+55KOYSIUYGigG1rmUHkZKx8QsUbqdzTizm8mF5uY+xlDD4Coq5zG3Bb UG2PkNVpmqcsqdCBMubh9xlNJVsHP/FUn+MkA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XKl+Ub2r4X8f9e/3j+IQMF+ImMKGU0zKD6Ek6vOi3uM=; b=rY6CF8GoWQYxoUsFA/GsK4K8ulLzQtyGOungbVNU5ZEGEPbXsn3DlcZyIqwNguJeSx sV83qnz9Dlfky2Ax0cVU/21Jt6nz78OzQTCtuVGY79rSJ57BKCEUgjuXEjT/VlnnAszU es1N2wx132cSojeaSqwtmO6RX53WnuVsBI1azVT66VusxsGsShafls9qeetmqdliXFtd 0mNkSIGuDzQvja7yy2iyRLLMchLfO/qH6KMJnAa0c5RNBSR1SbsYd/zHUsGMwbRqNw6C jz8jIoLNTdXNHS6AQQD+ThMDhGVIWgfxTngk6W9R87dKd5bifBqNNo32VnoGAhY1BOjs Ib3Q==
X-Gm-Message-State: APjAAAW0PphOv7CgCYT3Rwet7bbqbNi7iRuDPqTYk05LuaiZ2rVQ5gSa iulvpbjIwx/24Y7VfjRxEXUZptyw4tGCa/iDayfxOw==
X-Google-Smtp-Source: APXvYqxdcTZDlUugM3Eqie+6azBb2zfuSjdvObSW/Rwthf265XlxuRfACX1WsRGJQRizt1EzMC5N9fZHyMK7uv5hRMQ=
X-Received: by 2002:a5d:61cb:: with SMTP id q11mr19361436wrv.71.1580775882067; Mon, 03 Feb 2020 16:24:42 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Craig Schwartz <>
Date: Mon, 3 Feb 2020 19:21:25 -0500
Message-ID: <>
To: "Murray S. Kucherawy" <>
Cc: Dave Crocker <>, IETF DMARC WG <>, Alexey Melnikov <>
Content-Type: multipart/alternative; boundary="000000000000eba6b8059db51018"
Archived-At: <>
Subject: Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Feb 2020 00:25:23 -0000

Hi Murray,

<<<The chairs will not accept hearsay replies or opinions, or expressions
of needing this work but not knowing how to engage; you either give your
feedback on the list or privately to the chairs or Area Directors, or you
are along for whatever ride results.  Please indicate, as soon as possible,
where your support lies given the above.>>>

In my capacity as managing director of fTLD Registry Services (fTLD),
registry operator of the .BANK and .INSURANCE TLDs, I believe PSD would
provide invaluable threat intelligence to domain registrants and to TLD
administrators like ourselves for NXDOMAINs. PSD has tremendous value to
specialized TLDs including, but not limited to, .BRANDS, community-based
domains, high-security domains, governments, etc. and as such I believe PSD
should proceed. I’ve previously posted to this list expressing this view
and while fTLD cannot participate in experimentation due to a prohibition
by ICANN, we remain committed to supporting and seeing this work continue.



Craig Schwartz
Managing Director
fTLD Registry Services | .BANK & .INSURANCE
Office: +1 202 589 2532
Mobile: +1 202 236 1154
Skype: craig-schwartz

On Mon, Feb 3, 2020 at 1:48 PM Murray S. Kucherawy <>

> Dave,
> On Fri, Jan 17, 2020 at 8:44 AM Dave Crocker <> wrote:
>> Nothing I've worked on at the IETF with such a label is something I would
>> necessarily stand behind as Internet-scalable.
>> Such as?
> RFC 6541 comes to mind.  To the best of my knowledge, it's an experiment
> that never even ran.  Implementations shipped, but its use on the open
> Internet was never detected or reported.  And I had my doubts about the
> scalability of the second DNS check that was added to it, but it didn't
> seem like it could go forward without.
> One that wasn't mine: RFC 6210, an experiment to prove how bad something
> can be.
>> But I would probably expect something at Informational probably to scale,
>> and anything with "Standard" in it certainly to scale.
>> Laying any general expectation on an IETF Informational RFC would be a
>> mistake, because there is so much variety in their content and intent.
> Why would the expectations for Experimental be higher than for
> Informational?  LMTP is Informational, and it certainly needs to succeed.
>> So: Can you propose any sort of specific restructuring of the document or
>> the experiment that achieves the same goal as the current version while
>> also resolving your concerns?
>> I'm pretty sure I've raised fundamental concerns about this work and that
>> those concerns have not been addressed.  The simple summary is that the way
>> to restructure this work is to go back to first principles.  But there
>> doesn't seem to be any interest in having that sort of discussion.
> I thought we were having that sort of a discussion right here.
> Your position as I recall is that we have no choice but to take all of
> this back to first principles and separate DMARC from the determination of
> Organizational Domain (i.e., make them separate documents) before PSD can
> proceed.  Since that will take months, I've proposed a compromise, because
> I don't think that's strictly necessary to allow the data collection work
> to proceed.  The proposed compromise, then, is to do the work in hand, then
> rip the experiment down and apply whatever we learn from it to standards
> track DMARC, which is the next milestone.  That will include the separation
> of function you proposed, because we agree it's an improvement.  I believe
> the set of likely participants in the experiment are present on the list,
> and it can be made clear to them that they should have no expectation of
> the mechanism it describes surviving past the termination of the
> experiment.  So the path forward here comes down to whether the working
> group achieves consensus on that compromise, or whether the asserted risk
> of the experiment's structure leaking into the permanent deployed base
> warrants shutting it down before it starts.
> Now, to the working group as a whole:
> The chairs note that we have a duly and properly completed WGLC in hand.
> Still, Dave's concerns have validity, so they need to be considered by the
> working group.  Since we need to do *something*, we are now putting the
> question back to the working group, and we need to see some answers.  The
> chairs will not accept hearsay replies or opinions, or expressions of
> needing this work but not knowing how to engage; you either give your
> feedback on the list or privately to the chairs or Area Directors, or you
> are along for whatever ride results.  Please indicate, as soon as possible,
> where your support lies given the above.  We're not going to let this go
> additional months (probably not even weeks) without progress in some
> direction.
> I will also say for the record that we don't find compelling the assertion
> that resources will not be dedicated to the experiment absent a document in
> the RFC Editor queue.  That constraint is fully external to the IETF, and
> it will carry no weight in the decision made here.  It should indeed be
> possible to run an experiment based on a document in any state at all.
> We're entertaining publication not because it must happen, but because that
> action (currently) has consensus, and it's our job to act on consensus.
> Dave also made an additional observation, that experiments expected to
> fail are not generally what the IETF produces.  I would quibble some with
> that wording: The working group doesn't expect the experiment to "fail",
> but rather expects it to be ephemeral.  Were we to refer to
> chapter-and-verse, there's nothing in RFC2026 (which defines "Experimental"
> as a document status) that precludes what the working group appears to be
> trying to do here.  As for whether the IETF generally should produce an
> Experimental document describing something ephemeral, I would claim that a
> working group or its chairs are below the pay grade where authoritative
> claims like those are made; it's the kind of thing about which the IESG
> makes proclamations.  Accordingly, I've Cc'd our current Area Director to
> see what he thinks might happen if we were to send this up, and give him a
> chance to provide guidance in case that's the decision (but we won't wait
> long for that either).
>> The real challenge for most IETF specs is community engagement, not
>>> engineering adequacy.
>> Interestingly I would claim we have clearly achieved the former here,
>> though obviously not the latter.
>> My sense is -- as has become common in the IETF -- an extremely small
>> core of folk interesting in promoting this work, rather than extensive
>> community interest.
> That's probably true, but by that argument we should just terminate most
> of the email-related working groups because the critical mass we can get
> today is a fraction of what it used to be.
> Those sorts of existential questions can't be answered at this level,
> however.  I would claim the working group was chartered with the
> understanding that the participation here won't be like it was for, say,
> DKIM, or DRUMS, etc.  We're not in a position to fix that here.  We have a
> job to do, and we need to get moving again.
> -MSK
> _______________________________________________
> dmarc mailing list