Re: [apps-discuss] Revised DMARC working group charter proposal

Dave Crocker <dhc@dcrocker.net> Tue, 16 April 2013 03:36 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7553121F910B for <apps-discuss@ietfa.amsl.com>; Mon, 15 Apr 2013 20:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 QBaIohJxxWfH for <apps-discuss@ietfa.amsl.com>; Mon, 15 Apr 2013 20:36:21 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AC37C21F8F5B for <apps-discuss@ietf.org>; Mon, 15 Apr 2013 20:36:21 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3G3aKWW020266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Apr 2013 20:36:21 -0700
Message-ID: <516CC734.6050303@dcrocker.net>
Date: Mon, 15 Apr 2013 20:36:20 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>
References: <CAL0qLwbcH-yOj0MxfGghQZPwGMt5mRBY5U5zBxdXc1oX6SogHA@mail.gmail.com> <3121454.RJqk1xG6s9@scott-latitude-e6320> <516C9824.6040503@dcrocker.net> <8990489.xAljaCmULD@scott-latitude-e6320>
In-Reply-To: <8990489.xAljaCmULD@scott-latitude-e6320>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 15 Apr 2013 20:36:21 -0700 (PDT)
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Revised DMARC working group charter proposal
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 03:36:22 -0000

On 4/15/2013 6:35 PM, Scott Kitterman wrote:
> I think that if a draft is submitted as a candidate working group work item
> and the sponsors don't like the result of the chartering discussion and that
> draft is suddenly an independent submission, that's pretty well, by definition,
> an end around the working group process.


That's the same as saying that when one starts a negotiation, one is 
obligated to make a contract.

The initial chartering process is a negotiation between those bringing 
the work into the IETF and the IETF community.  Either side is free to 
agree or disagree with whatever terms they wish.

And free to walk away when there is not a sufficient meeting of the 
minds doing the negotiating.

The IETF does not have a 'right' to the work that is brought to it.

The ISE mechanism is for stuff that is relevant to the community, but 
isn't going through IETF or IRTF processing.  As a body of documents, 
the RFC series is larger than the IETF.


Work that is brought to the IETF has different levels of completeness 
and maturity, and different timings for having achieved those levels.

When the IETF charters a group and includes existing material, the 
charter can cast the role of that material in very different ways:

      It can treat it as nor more than a set of ideas, to be used or 
ignored;

      It can treat it as a basic design, with all of the actual details 
still fluid;

      It can treat it as a rough draft, to be massively revised;

      It can treat it as a solid specification that merely needs review, 
refinement and maybe enhancement;

      It can treat it as a deployed technology that should try to 
protect its installed base, but will tolerate some disruption;

      It can treat it as a deployed technology that /must/ protect its 
installed base and must ensure that core interoperability is retained 
with that installed base.


No doubt there are some other variations I've missed, but I hope this is 
enough to make clear that the choice of language in a working group 
charter, to constrain or not constrain the working group can make an 
enormous difference.

Equally, those bringing technology to the IETF do so at different points 
in the maturity of their work.  Any of the above might make sense, 
depending upon that maturity, the extent of deployment, and the timing 
of the investment made by the installed base.

When technology is brand new, with at most some prototypes done as 
proofs of concept, then significant changes to the spec won't 
necessarily add much to the development cost.  On the other extreme, a 
mature, deployed market can be almost cavalier about the freedom of a 
working group charter, because a working group that gets silly can be 
ignored: that is, the installed base is sufficiently well-established 
and unified in what it will accept, so that it's leverage is clear.

However, immediately after the development investment is made -- and 
especially when there has been considerable initial deployment, but 
still room for quite a bit more -- the installed and potential base will 
not take kindly to disruptive standards work; in fact such work can 
seriously damage adoption.

DKIM had almost no deployed base.  Jabber had quite a bit of deployed 
and mature base.

DMARC has a very large, newly-deployed base that just made the 
investment.  Making any changes that render the base not fully 
interoperable will a) piss of the folk who just made the investment, and 
b) possibly sour the folk considering deployment.  It typically at least 
causes the potential adopters to delay, sometime for years.

The charter that was originally submitted was tuned to the reality of 
DMARC's maturity and deployment.  Since that caused so much heartache to 
a few folk, the new draft charter removes the base spec from the current 
equation.  When deployment settles down and initial investment costs 
have been recovered, it will make sense to review the status of the base 
specification.


d/

ps.  I'm merely speaking for myself, of course, and not on behalf of the 
DMARC consortium.
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net