Re: [secdir] review of draft-crocker-id-adoption-05

"Klaas Wierenga (kwiereng)" <> Fri, 17 January 2014 16:07 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7998B1AE169; Fri, 17 Jan 2014 08:07:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Qi4LsN6eF0sq; Fri, 17 Jan 2014 08:07:27 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 9A9411AE14E; Fri, 17 Jan 2014 08:07:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=6332; q=dns/txt; s=iport; t=1389974835; x=1391184435; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=7s+NGf4yLXbAjLyCjXKJ7H0LnMAHhOqRFMUCdViwVtM=; b=XVj4cC87qGXwsQRoF/SyEtkIEl/l4Go3qvoNfjBj166PV8FCZQhAP2SH CUObNWAxDiqs0/P/UXl3g9AFqKqCaF0oDaJOIxNhFPrQJxd6/MlNbC8bk shHfiC6cDhbvdROdVuA50flZNtKhg28YmOa9vPCV9RTyv8VVAR1QN9Vrw Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.95,674,1384300800"; d="scan'208";a="297843688"
Received: from ([]) by with ESMTP; 17 Jan 2014 16:07:14 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id s0HG7EO8030552 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 17 Jan 2014 16:07:14 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Fri, 17 Jan 2014 10:07:14 -0600
From: "Klaas Wierenga (kwiereng)" <>
To: Dave Crocker <>
Thread-Topic: review of draft-crocker-id-adoption-05
Thread-Index: AQHPE5I77i18p0U40EKrtcrrUBqywpqJdMeAgAAFB4A=
Date: Fri, 17 Jan 2014 16:07:13 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>, "" <>, "" <>
Subject: Re: [secdir] review of draft-crocker-id-adoption-05
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 17 Jan 2014 16:07:30 -0000

On Jan 17, 2014, at 4:49 PM, Dave Crocker <>


> Thanks for your thoughtful comments.
> On 1/17/2014 6:41 AM, Klaas Wierenga (kwiereng) wrote:
>> - I think the title "Creating an IETF Working Group Draft" is a
>> misnomer, at least it led me to believe that it would be a guide for
>> creating a draft, i.e. what template, what sections, how to use the
>> tools etc. Something like "the lifecycle of an IETF WG Draft" seems
>> more appropriate.
> Well, the scope of the document did expand, over iterations.  At this point I'm probably too deep in the details to have a good sense of a good title, though I always appreciate efforts at better titles.  If folks think the document really is broad enough to cover wg doc lifecycle, that's fine with me.
> Adrian?
>> - Since this is a document that aims to document the actual way the
>> WG drafts are handled I wonder whether you should mention that
>> reality is not always what is put on paper. For example whereas
>> change control lies with the WG rather then the author, in reality
>> the author often has a strong influence on what is being published.
> I thought there were enough qualifiers in the document, to this point. So please suggest specific addition/changes.  Sometimes too much of that kind of commentary can overload a doc to the point of distraction, but that's not likely for this case.  So you point and suggest text and I'll add it.  (Adrian has also been easy-going about such things with the draft.)

;-) ok, I'll go through it again (probably not today as the week is coming to an end for me)

>> 1.1:
>> - since in section 5.1 the individual submissions pops up, it may
>> make sense to add a  note here that says something like: "NOTE: in
>> addition to WG drafts each individual can also independently submit a
>> draft (that may at a later stage either or not be adopted by a WG)"
> How's this (adding after <wgname>):
> 1.1 What is a Working Group Draft?
> Documents under development in the IETF community are distributed as Internet Drafts (I-D) [ID-Info]. Working groups use this mechanism for producing their official output, per Section 7.2 of [RFC2418] and Section 6.3 of [Tao]. The convention for identifying an I-D formally under the ownership of a working group is by the inclusion of "ietf" in the second field of the I-D filename and the working group name in the third field, per Section 7 of [ID-Guidelines]. That is:
> draft-ietf-<wgname>-...
> Individual submissions are drafts being created and pursued outside of a working group, although a working group might choose to adopt the draft later, as discussed below. Anyone is free to create an individual submission at any time. Such documents are typically distinguished through the use of the author's last name, in the style of:
> draft-<lastname>-...
> Responsibility for direct revision of a working group I-D is assigned to its editors and authors. See Section 3 for discussion about their selection and role.


>> 2.1:
>> - I usually (especially with relative newcomers) explicitly make the
>> authors of a submitted draft aware of the fact that they give up
>> change control for their love baby to the WG.
> What is the specific change you want?

between bullit 2 and 3 add:

- verify that the draft submitters are aware that they transfer change control for the document to the WG (and the IETF)

(not trying to be picky, but this particular point I have seen go wrong often, leading to rubber stamp discussions etc)

>> 2.2:
>> - Also in other sections, but especially when it is about adopting a
>> draft and/or determining whether it fits in the charter there is
>> often quite a bit of involvement from the AD's, I think you need to
>> at least mention the role of the AD wrt the WG process.
> I think this varies quite a bit, and suggest we be careful about saying anything that sounds like a requirement for this, especially since there is a long-standing desire to /reduce/ AD load, not increase it.
> In formal terms, I believe the AD is /not/ part of the draft adoption process.  They can interact about anything in the wg, of course, but noting any specific like this could too easily confuse folk that it is necessary.

Ehm, yes I understand what you are saying. But I think the AD has a formal role in approving a recharter, right?
>> - I usually also try to judge if we have a reasonable expectation of
>> finishing up the to be adopted work (workload WG, research character
>> etc.)
> So add to Criteria:
>   o Is the draft likely to be completed in a timely manner?
> That's more generic than you've suggested, but I figure the whole point of such a bullet is simply to get folk to think about the going-forward pragmatics.

yes, better than my suggestion

>> - "is a simple modification to the charter feasible and warranted",
>> how about large modifications, are they ever feasible and warranted?
> I think the first bullet implies this issue well enough:
>   o Is there a charter milestone that explicitly calls for such a document?
> We need to be careful that the list isn't too picky with details.

ok, agreed

>> - "Group, not chairs:   Concerning the draft, the position of the
>> working group chairs has no special authority.", I think that is only
>> true wrt technical content, the chair does have special authority to
>> make sure that WG consensus is properly represented, that due process
>> is followed etc.
>   Concerning the draft, the position of the working group chairs has
>   no special authority, except to assess working group consensus.


>> 3:
>> - Typo in the sentence: "A simplistic rule of thumb is that editors
>> tend to do the mechanics of incorporating working group detail,
>> whereas tend to create the detail, subject to working group
>> approval."
>> whereas tend to =>> whereas authors tend to
> ack. tnx.