Re: Enough DMARC whinging

Miles Fidelman <mfidelman@meetinghouse.net> Sat, 03 May 2014 17:55 UTC

Return-Path: <mfidelman@meetinghouse.net>
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 E505B1A00F1 for <ietf@ietfa.amsl.com>; Sat, 3 May 2014 10:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 3LCuK2czb1PK for <ietf@ietfa.amsl.com>; Sat, 3 May 2014 10:55:58 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 97C6A1A00ED for <ietf@ietf.org>; Sat, 3 May 2014 10:55:58 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 1D851CC0C0 for <ietf@ietf.org>; Sat, 3 May 2014 13:55:55 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4UbuUYzS+11V for <ietf@ietf.org>; Sat, 3 May 2014 13:55:46 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 3C550CC0B6 for <ietf@ietf.org>; Sat, 3 May 2014 13:55:46 -0400 (EDT)
Message-ID: <53652DA1.2060805@meetinghouse.net>
Date: Sat, 03 May 2014 13:55:45 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF general list <ietf@ietf.org>
Subject: Re: Enough DMARC whinging
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.c om> <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com> <CAA=duU3scwm=j2BJ6jq4k5zRQPkXOVOR1UscQqZZ8tG5HEZTwQ@mail.gmail.c om> <536113B1.5070309@bbiw.net> <CAMm+LwiXoW3p5uCmML4kAWXnbrrAnSCK9x5U2qeHJdVgR2r_Gg@mail.gmail.com> <E3A7C677B18263C8DF6DD316@JcK-HP8200.jck.com> <5362943D.2020907@bluepopcorn.net> <536295E5.3080502@dcrocker.net> <5362B4C6.10904@meetinghouse.net> <20140501215106.D05031512788@rock.dv.isc.org> <53651C59.4070801@bbiw.net>
In-Reply-To: <53651C59.4070801@bbiw.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xpMUqtDVh2QInm91Oog-hr6tAGY
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: Sat, 03 May 2014 17:56:00 -0000

Dave Crocker wrote:
> On 5/1/2014 2:51 PM, Mark Andrews wrote:
>> In message <5362B4C6.10904@meetinghouse.net>, Miles Fidelman writes:
>>> Dave Crocker wrote:
>>>>>      5. The IESG has concluded that this document extends an IETF protocol
>>>>>         in a way that requires IETF review and should therefore not be
>>>>>         published without IETF review and IESG approval.
>>>> Since DMARC does not extend any existing IETF protocol, how is that
>>>> reference useful here?
>>> Sure looks to me like DMARC extends both SMTP and DNS.
>> And DKIM.
>
> No, No, and No.
>
> Don't confuse 'use' with 'extend'.
>
> TCP "uses" IP.  It does not "extend" it.  That's what architectural
> layering is about.  Functions above a layer do not extend the lower
> layer; they use it.
>
> DMARC /uses/ DKIM (and SPF).  It does not alter (extend) either of them.
>
> As for any claim that DMARC 'extends' SMTP or DNS, it's difficult to
> imagine the technical logic behind such an assertion.

1. DMARC essentially species a change to the behavior of mail 
reception.  It sure looks to me like an extension to the state machine 
model for mail processing, at the SMTP level.  Arguably, the same can be 
said for what forwarders (including mailing list processors) do.

2. As to DNS: There's a long standing argument about the use of TXT 
records for purposes beyond holding "descriptive data."  Last time I 
looked (just now) there has been nothing since RFC1035, which states 
"TXT RRs are used to hold descriptive text" and RF1464, about storing 
arbitrary string attributes, and remains experimental. DKIM, SPF, and 
DMARC both define and use TXT RRs in ways that go beyond their defined 
scope.
>
> d/
>
> ps.  The original note was from Jim Fenton and it was him I was asking
> to explain his reference.  He seemed to be making a point and I was
> asking him to provide it explicitly.
>
Yes.  I'm agreeing with Jim, and providing some backup to his point.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra