Re: [dmarc-ietf] Rethinking DMARC for PSDs

Tim Wicinski <tjw.ietf@gmail.com> Tue, 09 April 2019 02:46 UTC

Return-Path: <tjw.ietf@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 11EAD12010C for <dmarc@ietfa.amsl.com>; Mon, 8 Apr 2019 19:46:40 -0700 (PDT)
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_PASS=-0.001, URIBL_BLOCKED=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 cuD0LoWyOQWS for <dmarc@ietfa.amsl.com>; Mon, 8 Apr 2019 19:46:38 -0700 (PDT)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (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 0B4CF1200CC for <dmarc@ietf.org>; Mon, 8 Apr 2019 19:46:38 -0700 (PDT)
Received: by mail-oi1-x22c.google.com with SMTP id j132so12300681oib.2 for <dmarc@ietf.org>; Mon, 08 Apr 2019 19:46:38 -0700 (PDT)
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=vt+2Lg95Fr7v7mxHuPqTpd8hDQGP3v913iWUadWwLOw=; b=p8b7BHlTDedQEnqItAxuw2mTEbenSCKUE5paYwdQZlu+9Z2s6KfSWEOCqCt7/jXtMG GY6icms+SgBIoOb7NopUtJmkh3EygXi0jR8ZnpAecT/3O0Q4noQiBUpfD0S2RuSbPfnZ Wn1QFZuK/8h4OYzkhoRIFlp+rq6mM7zMuwKB6cDC3L2o1OTFrQ/IOOX6Ah3TC5AX8V9D 2YHRHGoNTwVsbvDhY6juNf9g7Ww8wS6Ng28KNY461hjmy1SQEFRAvbCiBdxfgIO07scf 6ud8neylxGyicEVla9dru3+ilOGIAD4oZxUvDMszZnWYaPxI970wkfBAZ1N7ku/0vxi7 8krA==
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=vt+2Lg95Fr7v7mxHuPqTpd8hDQGP3v913iWUadWwLOw=; b=lRr/rB6eK7ZwbdPNRhqdZC5Xmz4fitSz8IRo1bq7lLYvpYwir3REN8hD8UCCRSP1BW DoR7aFjdGEh76A1ufxE0/1l8OA4oXWAjVTnkptB/F5JuKbujr4A5wOGTAozE0oT/KBAq vp/kzyOWjayf5oW5KVkGNlritQ5uSDS3pcpWruhJHNOFUDT6QrDyhqADtcx44CsCcA1R eHCQGPSuxED59mGF/qiTsLuJjEbzRrpnlHFfATHijE72uUbt93wJ49bIE5zWYjWs6zNi Bs3cAALWj2IT2F2CR9MyXSB+73N/eE1xWXX1eVfNaePGz3b3cDy+jnT+geUhPSNOyHxw csog==
X-Gm-Message-State: APjAAAVpo49B6XLwnw5s0gYHpIU0t1ecwTO2fnVBXWHal+TGok84yx82 Etx5VJGYxV/svbimIrtf0vGM7HEM3l8bPRfUPz8=
X-Google-Smtp-Source: APXvYqzeLDPr9CCXp1PyChIQK1D0FEUZsmwAzqrsr23W1eNY8cdXJNSmdSn6Zn5sQTK8npz7V1vR3sxYhW9zt2CaEGg=
X-Received: by 2002:aca:be07:: with SMTP id o7mr6198097oif.118.1554777997439; Mon, 08 Apr 2019 19:46:37 -0700 (PDT)
MIME-Version: 1.0
References: <08252783d22443e79b707537df97c872@bayviewphysicians.com> <CABuGu1qdU4TbL3okQnNMn6yr+xODFfBG6o9ZOwJ1SgdjGJ95nA@mail.gmail.com> <08693A61-D3AD-448D-B64C-B36262756C65@kitterman.com> <3e3a5997f71544f1a29fca8845fcbf60@bayviewphysicians.com> <CAL0qLwbOw3hUqPZB7hQsUjHonW-jffMSvRLXUdZMeY+xe8As1g@mail.gmail.com>
In-Reply-To: <CAL0qLwbOw3hUqPZB7hQsUjHonW-jffMSvRLXUdZMeY+xe8As1g@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Mon, 8 Apr 2019 22:46:25 -0400
Message-ID: <CADyWQ+FBUmwP0vGeS5hEeRWnBjJ+-KwU1bKMbPV0_vRjhUGNiw@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: fosterd@bayviewphysicians.com, IETF DMARC WG <dmarc@ietf.org>, Scott Kitterman <sklist@kitterman.com>
Content-Type: multipart/alternative; boundary="0000000000003df7d105860ff6ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Vb7oDM0CFz2e_t2RaOXyDNVda_o>
Subject: Re: [dmarc-ietf] Rethinking DMARC for PSDs
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, 09 Apr 2019 02:46:40 -0000

+1 on moving the discussion elsewhere

Tim

On Mon, Apr 8, 2019 at 10:27 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> <chair hat on>
>
> On Mon, Apr 8, 2019 at 5:27 PM Douglas E. Foster <
> fosterd@bayviewphysicians.com> wrote:
>
>> Scott, you misunderstand what this type of standard would look like.   It
>> would defines Use Cases that the device should address, with some
>> acknowledgement to the tradeoffs between perceived risk and perceived
>> difficulty of implementation.
>>
>
> If what you're looking to do is drum up interest for working on this and,
> if there's critical mass to do the work, getting something published, I
> suggest any of the following:
>
> ietf-822@ietf.org (message format discussions)
> ietf-smtp@ietf.org (SMTP discussions)
> art@ietf.org (ART area general discussions)
> dispatch@ietf.org (once you have an actual proposal for work that needs a
> home)
>
> ....possibly others, but those spring immediately to mind.  However, I
> believe Scott is correct that this work is not currently within our
> charter, and thus it's off-topic for this list.  I don't believe there's
> any working group currently chartered to produce something like what's
> being proposed here; EXTRA probably comes closest, and I think it's
> off-topic there too.
>
> Some years ago Dave Crocker and I assembled RFC 6647 about greylisting,
> which was an applicability statement over email in general that talked
> about how to implement greylisting.  You could follow that model if you
> like, which merits standards track publication, though that means you'll
> need to convince an AD to sponsor it or form a working group to develop it.
>
> If my co-chair concurs, then it's appropriate that this conversation be
> moved elsewhere.
>
> -MSK
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>