Re: [dmarc-ietf] Charter improvements

"Murray S. Kucherawy" <superuser@gmail.com> Fri, 19 July 2013 18:25 UTC

Return-Path: <superuser@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 CF3CB21E80D2 for <dmarc@ietfa.amsl.com>; Fri, 19 Jul 2013 11:25:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level:
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPWFtUz6XT7E for <dmarc@ietfa.amsl.com>; Fri, 19 Jul 2013 11:25:39 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id F00C921F9DBA for <dmarc@ietf.org>; Fri, 19 Jul 2013 11:25:38 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id c10so947270wiw.2 for <dmarc@ietf.org>; Fri, 19 Jul 2013 11:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BQBJaNZTJIAYpu1XJF/bhnLrTqs9JAYewk8O8hGZA5Y=; b=CyGZeI0m5CZbqindGAGcW3mfQvyTFIJhr6eaZAaZO4hnALPLZ6V2n1hIyvLDEYVRRD hR3N6R1QXcH8G9akbxy0KvYQ/W8hI8OF7Y3+kL8XvUan5OdRBvBWhKAuKldJeB5TKPgm T56Y75UeRMJrk+GN8Qduz+9QnXSINo1EammAFA9bFimIQM88dk9qGscUvN/ztqfd1vTz zN3UW8RM0YkMRFewOPmtsu9hzYMM+5M9tHmMGPXOo548i79tdNf2wwWEKF2wX9lispw+ mJOwy7HAsMgQBVkKWvGp0gx13BPwA07NMLdASxMXyeWPr4WktFCZVGFUXrlkEQLFYWSf 5E9A==
MIME-Version: 1.0
X-Received: by 10.194.48.116 with SMTP id k20mr13317974wjn.23.1374258336945; Fri, 19 Jul 2013 11:25:36 -0700 (PDT)
Received: by 10.180.90.16 with HTTP; Fri, 19 Jul 2013 11:25:36 -0700 (PDT)
In-Reply-To: <51E56BAD.3060602@gmail.com>
References: <20130702052746.15876.qmail@joyce.lan> <51D3464D.2060502@sonnection.nl> <0A91244B-1CAE-491A-865B-E2BA64AFB366@tnpi.net> <51E56928.4020207@gmail.com> <51E56BAD.3060602@gmail.com>
Date: Fri, 19 Jul 2013 11:25:36 -0700
Message-ID: <CAL0qLwaiqXGU2G1RqHC7NHPjjTUuLu=OPLOM_OGxO3iHDoa+zg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Content-Type: multipart/alternative; boundary="047d7ba975e600dd5b04e1e174cd"
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, "J. Trent Adams" <jtrentadams@gmail.com>
Subject: Re: [dmarc-ietf] Charter improvements
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 19 Jul 2013 18:25:40 -0000

On Tue, Jul 16, 2013 at 8:50 AM, Dave Crocker <dcrocker@gmail.com> wrote:

>
>  -----
>> * a mechanism for mitigating the effect of failures of DMARC policy when
>> a message transits a mailing list
>> -----
>>
>> I recognize that there's definitely a counter-pressure against including
>> this topic as it seems to be a potentially quixotic quest. That being
>> said, even if we don't find the perfect solution, it does seem
>> reasonable to believe there is a way to provide something more than
>> nothing that does help in some meaningful way. I'm not presupposing a
>> solution, just that there have been a few possible options discussed at
>> the edges which are likely to be worth more rigorous exploration.
>>
>> QUESTION: Is there value in a WG such as this exploring possible
>> solutions to this issue and developing guidance that would potentially
>> help improve the utility of the base DMARC specification?
>>
>
> If the wg handles this carefully and pragmatically, there might be some
> benefit in at least documenting the topic, in terms of concerns and
> choices.  I believe there isn't an IETF published paper in this realm, in
> spite of the issue appearing regularly.
>

RFC6377 devotes quite a bit of time to the topic, at least in the context
of DKIM.  There's also mention of ADSP, which is particularly germane here.

We may reasonably be asked what's different now since the publication of
that draft that would warrant reopening the topic.

-MSK