Return-Path: X-Original-To: spasm@ietfa.amsl.com Delivered-To: spasm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1003E120020; Thu, 8 Aug 2019 05:36:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org 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 GYkTkY02mpw2; Thu, 8 Aug 2019 05:36:53 -0700 (PDT) Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF848120046; Thu, 8 Aug 2019 05:36:52 -0700 (PDT) Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x78Camtn035041; Thu, 8 Aug 2019 08:36:48 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu x78Camtn035041 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1565267809; bh=i0rpauXYFqT9TUlUMTl/SsAXcen3K6vlvA2q9D5VBRQ=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=OlSCvqN/sdyU9Hd2xP27t7OHdRkenaEJsp4J2dlhNVCQNugt+R8tBSXnNXyEMFlet HOfAzTkXABhGr7vlZ4KEkF8xX3E8xlTv+2y47qGedTqspc1hxLGvRHyKUm0y72OqLx yryGaQA68ceQsF1omRCflznv1xj59mZoZPSc0VBE= Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x78CajS8039227; Thu, 8 Aug 2019 08:36:45 -0400 Received: from MARCHAND.ad.sei.cmu.edu ([10.64.28.251]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0439.000; Thu, 8 Aug 2019 08:36:45 -0400 From: Roman Danyliw To: Alexey Melnikov , The IESG CC: "draft-ietf-lamps-cms-shakes@ietf.org" , "lamps-chairs@ietf.org" , SPASM , Russ Housley Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-lamps-cms-shakes-15: (with DISCUSS) Thread-Index: AQHVSchz8oL0fspzZEem3qSCsBcW26bws2CAgADGQwD//74A0A== Date: Thu, 8 Aug 2019 12:36:44 +0000 Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B340168E@marchand> References: <156481532800.6108.1633834009578124669.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFC01B3400EB1@marchand> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.64.22.6] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [lamps] Alexey Melnikov's Discuss on draft-ietf-lamps-cms-shakes-15: (with DISCUSS) X-BeenThere: spasm@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2019 12:36:55 -0000 Hi! > -----Original Message----- > From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm] > Sent: Thursday, August 8, 2019 8:31 AM > To: Roman Danyliw ; The IESG > Cc: draft-ietf-lamps-cms-shakes@ietf.org; lamps-chairs@ietf.org; SPASM > ; Russ Housley > Subject: Re: Alexey Melnikov's Discuss on draft-ietf-lamps-cms-shakes-15: > (with DISCUSS) >=20 > Hi Roman, >=20 > On Thu, Aug 8, 2019, at 5:50 AM, Roman Danyliw wrote: > > > > > -----Original Message----- > > > From: iesg [mailto:iesg-bounces@ietf.org] On Behalf Of Alexey > > > Melnikov via Datatracker > > > Sent: Saturday, August 3, 2019 2:55 AM > > > To: The IESG > > > Cc: draft-ietf-lamps-cms-shakes@ietf.org; lamps-chairs@ietf.org; > > > spasm@ietf.org; housley@vigilsec.com > > > Subject: Alexey Melnikov's Discuss on > > > draft-ietf-lamps-cms-shakes-15: (with > > > DISCUSS) > > > > > > Alexey Melnikov has entered the following ballot position for > > > draft-ietf-lamps-cms-shakes-15: 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-lamps-cms-shakes/ > > > > > > > > > > > > -------------------------------------------------------------------- > > > -- > > > DISCUSS: > > > -------------------------------------------------------------------- > > > -- > > > > > > This is a fine document, but I have one quick question: > > > > > > Values TBD1..TBD4 are not listed in the IANA Considerations section. > > > Should they be? > > > > I don't think so. This document and draft-ietf-lamps-pkix-shakes both > > need the same OIDs (but have no other dependence). This latter draft > > is with the RFC Editor and does register these OIDs. >=20 > Ok, I understand now. >=20 > > The current text, > > "[I-D.ietf-lamps-pkix-shake] [ EDNOTE: Update reference with the RFC > > when it is ready ]", was intended to guide the editor to replace > > TBD1-4 the OIDs when ietf-lamps-pkix-shake got published. However, in > > re-reading the text now, the EDNOTE should actually read "Updated the > > TBD1-2 reference when the RFC is published". >=20 > There are 2 places TBD1-2 and TBD3-4. But yes, something like that. > > I read the current text as just an instruction to change the draft name t= o the > corresponding RFC number, so clarifying it would be great. Exactly. There are two places where this update needs to be made. Thanks, Roman > > > > Make sense? >=20 > Best Regards, > Alexey