Re: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)

S Moonesamy <sm+ietf@elandsys.com> Thu, 17 July 2014 00:24 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 043301A016B for <ietf@ietfa.amsl.com>; Wed, 16 Jul 2014 17:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level:
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
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 Nt8RYkBKlfVG for <ietf@ietfa.amsl.com>; Wed, 16 Jul 2014 17:24:31 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5505A1A03AF for <ietf@ietf.org>; Wed, 16 Jul 2014 17:24:31 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.144.75]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s6H0OCB9028359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Jul 2014 17:24:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1405556664; x=1405643064; bh=xf85kNGcwBVKrg+VnJLkxCitxv0Sx1JSNyq0PUkNjSg=; h=Date:To:From:Subject:In-Reply-To:References; b=3cj0HLtwJExJagj4TlbnMp6Hr7ViBhCEcUvt8ahEfWpqK6ObjhQUqaXSb1EwXRinn 0eSVIVFnL47hr3Y6mLkUz+VbmJSTkXtzdGuZ1uaLTvoMMJ8KWjduzkJE6t8ZNTwP0R gc2l4FrycpM4XAXq5A1LOCQMIU+c5AEK6ROkj4ZQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1405556664; x=1405643064; i=@elandsys.com; bh=xf85kNGcwBVKrg+VnJLkxCitxv0Sx1JSNyq0PUkNjSg=; h=Date:To:From:Subject:In-Reply-To:References; b=CXwxUceGaF2aA/YvoAU0d/1LV3sLqF4jUIKaeRubIsyReClJnkuVvHaKNqxQiCMxb fCoOR2RZBGf5K+Ih09hJcUUjU5dkHdu7VbQ7w1Ux8yhWpdoxFBjiCI+4CYdvO35AIf 1zhKB5F5uuWgcupovoWVGT9CU3yEJI33cirEKzfQ=
Message-Id: <6.2.5.6.2.20140716161255.0ac7a6f0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 16 Jul 2014 17:20:04 -0700
To: dcrocker@bbiw.net, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)
In-Reply-To: <53C70443.8020709@dcrocker.net>
References: <20140714164212.22974.20340.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140716100922.0ceba268@resistor.net> <53C70443.8020709@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BRQtBO4209m1AU4cXWYaP3yn2yw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2014 00:24:33 -0000

Hi Dave,
At 16:01 16-07-2014, Dave Crocker wrote:
>Yes, but how does (or should) your comment affect the draft charter text?

I did not suggest any change to that text.  I expressed an opinion.

>The draft charter text only notes the fact of submission and says
>nothing about the further processing that has, might or will take place.
>  The IESG assessment is part of the 'will'.

I'll quote from 
http://www.ietf.org/mail-archive/web/ietf-announce/current/msg13031.html

   "Existing deployment of DMARC has demonstrated utility at internet
    scale"

If I am not mistaken implementers are encouraged to request IETF 
protocol parameters assignments before deploying them at internet 
scale.  In my opinion an IESG assessment would be useful as the IESG 
is chartering a working group about DMARC.  I am taking a previous 
(IESG) conflict review into consideration 
(conflict-review-masotta-tftpexts-windowsize-opt).

>Yes, it does set a high bar.
>
>As for actions already taken by some operators, those certainly should
>provide interesting input for consideration.  However the mere fact of
>those choices having been made does not mean that they are preferred or
>even useful.  That's what the working group will (I hope) consider.

Ok.

>Yes, it's a challenge to figure out how to word that concisely and
>helpfully, given that the charter has already been criticized for being
>too long.
>
>So, the intent of the phrase is to distinguish between mechanisms that
>might provide author-to-recipient utility, either due to a
>'collaborative' effort by both the author's operator and the
>intermediary, or solely by the author's operator, with the intermediary
>instead being 'passive'.
>
>An example would be a mechanism that requires the intermediary to add
>its own signature, versus one that might survive the intermediary, even
>without the intermediary taking special action.

Thanks for the above explanation.

>That's the intent of the charter, except to the extent that the dmarc wg
>might develop some useful input to a separate public suffix effort.

I'll say okay to this one.

Regards,
S. Moonesamy