IETF Logo Mail Archive

Re: [Curdle] Alissa Cooper's Discuss on draft-ietf-curdle-gss-keyex-sha2-09: (with DISCUSS)

Alissa Cooper <alissa@cooperw.in> Mon, 24 June 2019 21:01 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 751D91200F7; Mon, 24 Jun 2019 14:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=fS8CbVMb; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=DM+eX2Eq
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 pz7VbcwFsJ-u; Mon, 24 Jun 2019 14:01:32 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4252E1200B3; Mon, 24 Jun 2019 14:01:32 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0BFB522452; Mon, 24 Jun 2019 17:01:31 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 24 Jun 2019 17:01:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=p LHVXoQlkb0wmin+Ut5gjPWPlkoNVqLhQnj4OFitC+4=; b=fS8CbVMbt96SHA9Iw bbFpWmiPAd6BYyo0TWPHxpcY9fe+xsDPgYwlB3bJKNiycQCgGa5eVSMpmT6KRmTr SeksTGSqaIv0L89ydClFYM9fVVzdDo7fRn6dSsvNb/a3H4lI1sMJWz3tJdGykBvD +j92VAeDfBJPWS4Sse7I0KVR6gZ4+4WIzJzZUj/jeRfxNhvTzR5oVK4iau7cwLkq ruqpXlb87eF4YzYN3jpsPCUEc8xunFmxXw1iVaFZn9JUHsEtiHxh2055DVSLOYcF 5KeyQf/rWWuEHW/QExHbj0Hg2CGxQp4G2ZcqB1b+b6F5IbNxVM9phigyLJiXjS76 fFwtQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=pLHVXoQlkb0wmin+Ut5gjPWPlkoNVqLhQnj4OFitC +4=; b=DM+eX2Eq8Gf/ZDFRSnPlTsg/i64/1fmHQ93nqJ5BMJLBcZgeJ+LsZdXig EQIRKK44pT2ScvLrXSInssLD3syYE1eGI+ayOHFjOEmYTbtFFGgkEGxUSfvTMPvE h/zUVfkFxL0HP7X7IGjFXR2r/RJbxCh+2OOlpf6tZtEQfgtDvFrcbhedcdzN/3MW Ntv6x/48ueq693MYgAyaQiM4YwXgGnz6IbwbkXJ4khmxGkROFMkeAJCNsnUv9T8c vcPlEYzkmU9UYBVs/pbXqyFGibej4hqRYPkg49oOLsY3DWHO+7OvUtmTO5gMNyl0 39CVhuQ5gU90ZbCK8uCLwXsL+yu5A==
X-ME-Sender: <xms:KjoRXTo1hZT4BpNA2gxTcrQfLyo9HWvM2Iv8GkPO6nhQXsky9bmUvw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddruddvgdduheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedrkedunecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsth gvrhfuihiivgeptd
X-ME-Proxy: <xmx:KjoRXZJYFOs2GK8V6MDH03qQeAw4Fd2Ya_kI7LIM0u33Sv2WHY_Rxw> <xmx:KjoRXWoMdif-QJ3-_OUpEaGoT7qsaL8zaZcHAFs0w2R3l8P0KCSzmA> <xmx:KjoRXRxCOG95rbRJTCY21k41nD2GRBFgMl5Vh6e6gSps4CsbM06wTw> <xmx:KzoRXTZMsnHF4YQZiIwe86RqUsNvbiNYZ2emDZiB3Ja8M9NhQx43kw>
Received: from rtp-vpn4-1540.cisco.com (unknown [173.38.117.81]) by mail.messagingengine.com (Postfix) with ESMTPA id CECCC80061; Mon, 24 Jun 2019 17:01:29 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <20190624201955.GD48838@kduck.mit.edu>
Date: Mon, 24 Jun 2019 17:01:28 -0400
Cc: IESG <iesg@ietf.org>, draft-ietf-curdle-gss-keyex-sha2@ietf.org, daniel.migault@ericsson.com, curdle-chairs@ietf.org, curdle@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F78AD47-6C9C-457E-9AA1-031EEBC9082F@cooperw.in>
References: <156140748841.17734.7894701055354347252.idtracker@ietfa.amsl.com> <20190624201955.GD48838@kduck.mit.edu>
To: Benjamin Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/inggo8nTY6KRvL42PUezBNxBpuA>
Subject: Re: [Curdle] Alissa Cooper's Discuss on draft-ietf-curdle-gss-keyex-sha2-09: (with DISCUSS)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 21:01:35 -0000


> On Jun 24, 2019, at 4:19 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> On Mon, Jun 24, 2019 at 01:18:08PM -0700, Alissa Cooper via Datatracker wrote:
>> Alissa Cooper has entered the following ballot position for
>> draft-ietf-curdle-gss-keyex-sha2-09: Discuss
>> 
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>> 
>> 
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-curdle-gss-keyex-sha2/
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>> 
>> "The IESG is considered to be the owner of all these key exchange
>>   methods; this does NOT imply that the IESG is considered to be the
>>   owner of the underlying GSS-API mechanism."
>> 
>> I don't understand this text. What does it mean for the IESG to be the owner of a method?
> 
> The IESG has change control for the SSH key exchange method; the IESG does
> not necessarily have change control for the underlying GSS-API mechanism.

Thanks. I think it would be clearer to say that than to talk about ownership. But given that the registry policy is IETF Review, is it really appropriate to say that the IESG has change control? Would s/IESG has change control/IETF has change control/ be more accurate?

Alissa

> 
> -Ben

v2.23.0 | Report a Bug | By Email