Return-Path: <kwiereng@cisco.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com
 (Postfix) with ESMTP id AAA5F1A0171; Mon, 20 Jan 2014 06:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.036
X-Spam-Level: 
X-Spam-Status: No,
 score=-15.036 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.535, SPF_PASS=-0.001,
 USER_IN_DEF_DKIM_WL=-7.5] 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 f_hwCSRgWhxg;
 Mon, 20 Jan 2014 06:16:08 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76])
 by ietfa.amsl.com (Postfix) with ESMTP id 7CFDD1A016A;
 Mon, 20 Jan 2014 06:16:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com;
 l=1473; q=dns/txt; s=iport; t=1390227369; x=1391436969;
 h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding:
 mime-version; bh=UncSiSwYNKuKHahwON4T5eUQp7wouVJXwHwDX9eERH4=;
 b=HlegLknh7tCaCSvQ89QsiQa/B4vqSONUPljRKM3fbvJ77sAT/QI36q6v
 nNDxyBD52LiBjDB5dSmHRKhxFc9EnyZWrXtJ8eBpYVJFBvM4G8q18F4gC
 swe8bpoCDylkcxQRUbBFHAqzphkkDiZzM3zA8K1BAfpsJbqGAJ5Ypdab2 c=; 
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAN4u3VKtJV2Y/2dsb2JhbABZgwuBDrs8gQ0WdIIlAQEBAwF5EAIBCA44MiUCBA6IAgjDYReOTDMHgySBFAEDiQ+PE5IYgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,691,1384300800"; d="scan'208";a="298461786"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by
 rcdn-iport-5.cisco.com with ESMTP; 20 Jan 2014 14:16:08 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by
 rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0KEG8Du011564
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
 Mon, 20 Jan 2014 14:16:08 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.104]) by
 xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003;
 Mon, 20 Jan 2014 08:16:08 -0600
From: "Klaas Wierenga (kwiereng)" <kwiereng@cisco.com>
To: Dave Crocker <dcrocker@bbiw.net>
Thread-Topic: review of draft-crocker-id-adoption-05
Thread-Index: AQHPE5I77i18p0U40EKrtcrrUBqywpqJdMeAgAAPmYD//6x+FYAAaKaAgAR4PoA=
Date: Mon, 20 Jan 2014 14:16:08 +0000
Message-ID: <D57D98B9-432D-4DD3-93B1-BC9F8D22A4D2@cisco.com>
References: <8D28F665-CDF8-4FAA-869E-CA5EF6E673D2@cisco.com>
 <52D950F9.7050909@bbiw.net>,
 <05a201cf13a3$7a2e10b0$6e8a3210$@olddog.co.uk>
 <C1C3F240-7C57-4D90-8C1D-4D068409A73E@cisco.com> <52D96FCB.5010002@bbiw.net>
In-Reply-To: <52D96FCB.5010002@bbiw.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.96.52]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F91456CA85981A4594789863F941AAAE@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-crocker-id-adoption.all@tools.ietf.org"
 <draft-crocker-id-adoption.all@tools.ietf.org>,
 "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, "iesg@ietf.org" <iesg@ietf.org>,
 "secdir@ietf.org" <secdir@ietf.org>
Subject: Re: [secdir] review of draft-crocker-id-adoption-05
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>,
 <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>,
 <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 14:16:09 -0000

[snip]

>>> While I would welcome suggestions of text on this point I am less
>>> that easy-going about documenting worst current practice. In fact,
>>> I think I take issue with what Klaas says: it may well be that
>>> document editors/authors have strong influence on the text that is
>>> generated, but if the WG is being denied the opportunity to review
>>> and object to the text (possibly after a revision of the I-D has
>>> been posted), then the WG is not being run well. So I am happy
>>> with the text as it stands.
>>=20
>> I think you misunderstand what I tried to say, I am in no way
>> advocating this, I am stating behavior that I observe. What I am
>> proposing text along the lines of "authors and/or editors may feel
>> like that they "own" the document and strongly influence the final
>> text. The WG chair will have to make sure that WG consensus is
>> properly reflected"
>=20
> I'm confused.  I would have thought that the existing paragraph:
>=20
> 1.2 Working Group Authority and Consensus
> ...
> At times, a document author/editor can appear to have considerable author=
ity over content, but this is (merely) for efficiency. That is, the chairs =
can permit authors and editors to proceed with an implied (default) working=
 group agreement, as long as the working group is comfortable with that mod=
e...
>=20
> and all of Section 3, deal with this concern sufficiently.

Yes, you are right, apologies.

Klaas=
