From nobody Thu Jan 13 09:21:36 2022 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 BDAAC3A1810 for ; Thu, 13 Jan 2022 09:21:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 F0q4LadaL4-3 for ; Thu, 13 Jan 2022 09:21:23 -0800 (PST) Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 52B7B3A1811 for ; Thu, 13 Jan 2022 09:21:23 -0800 (PST) Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 1304EC461D; Thu, 13 Jan 2022 12:21:21 -0500 (EST) Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id EDA16C44BD; Thu, 13 Jan 2022 12:21:20 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\)) From: Russ Housley In-Reply-To: Date: Thu, 13 Jan 2022 12:21:20 -0500 Cc: "Brockhaus, Hendrik" , LAMPS , "david.von.oheimb@siemens.com" , John Gray Content-Transfer-Encoding: quoted-printable Message-Id: <6C1CF309-D2EE-41FD-9EBC-0CB548E13930@vigilsec.com> References: <0E478455-1218-4D54-A256-44B9E318D251@vigilsec.com> To: "Roman D. Danyliw" X-Mailer: Apple Mail (2.3445.104.21) Archived-At: Subject: Re: [lamps] Allocation of OIDs for CRL update retrieval (draft-ietf-lamps-cmp-updates-13) 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, 13 Jan 2022 17:21:35 -0000 Roman: I think we can get the OIDs as the document goes through the approval = process. Russ > On Jan 13, 2022, at 11:25 AM, Roman Danyliw wrote: >=20 > Hi! >=20 > With apologies, I missed this request and took no action on requesting = early allocation. I see that draft-ietf-lamps-cmp-updates-17 moved to = the "Publication Requested" state yesterday. Does the WG want me to = pick-up this early allocation request or is it acceptable to wait until = the document move through the normal process? >=20 > If the WG wants early allocation to move as fast as possible, could I = please get a pointer to demonstrate WG consensus on this allocation per = Step #3 of Section 3.1 of RFC 7120. I wasn't able to find that = consensus in the IETF 112 meeting minutes that I believe are the = reference noted below as "As discussed on Monday, ..." >=20 > Roman >=20 >> -----Original Message----- >> From: Brockhaus, Hendrik >> Sent: Monday, November 15, 2021 10:32 AM >> To: Russ Housley ; Roman Danyliw >> Cc: LAMPS WG ; david.von.oheimb@siemens.com; John = Gray >> >> Subject: AW: Allocation of OIDs for CRL update retrieval = (draft-ietf-lamps-cmp- >> updates-13) >>=20 >> Russ >>=20 >> Thank you for starting the registration. >> As soon as the OIDs are assigned, I will add them to the document. >>=20 >> Hendrik >>=20 >>> Von: Russ Housley >>> Gesendet: Mittwoch, 10. November 2021 22:26 >>>=20 >>> Roman: >>>=20 >>> As discussed on Monday, the LAMPS WG would like to get early >>> (permanent) allocation of two OIDs from IANA. >>>=20 >>> The relevant part of draft-ietf-lamps-cmp-updates-13 is quoted = below. >>>=20 >>> The OID need to be allocated in SMI Security for PKIX CMP = Information >>> Types (1.3.6.1.5.5.7.4). >>> = (https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww. >>> iana.org%2Fassignments%2Fsmi-numbers%2Fsmi-numbers.xml%23smi- >>> numbers- >>>=20 >> 1.3.6.1.5.5.7.4&data=3D04%7C01%7Chendrik.brockhaus%40siemens.com% >>>=20 >> 7Ce429a066d36b4f2cf3da08d9a490ab14%7C38ae3bcd95794fd4addab42e149 >>>=20 >> 5d55a%7C1%7C0%7C637721763514579270%7CUnknown%7CTWFpbGZsb3d8 >>>=20 >> eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D >>>=20 >> %7C1000&sdata=3D9g3dUqOyT2qDNXWCBgw%2B7szmus2EI4jLWp0HTGC0 >>> zIM%3D&reserved=3D0) >>>=20 >>> Thanks, >>> Russ >>>=20 >>> =3D =3D =3D =3D =3D =3D =3D =3D =3D >>> 2.16. New Section 5.3.19.17 - CRL update retrieval >>>=20 >>> The following subsection introduces the PKI general message using = id- >>> it-crlStatusList and id-it-crls. Details are specified in the >>> Lightweight CMP Profile Section 4.3 >>> [I-D.ietf-lamps-lightweight-cmp-profile]. Insert this section = after >>> new Section 5.3.19.16: >>>=20 >>> 5.3.19.17. CRL update retrieval >>>=20 >>> This MAY be used by the client to get new CRLs, specifying the = source >>> of the CRLs and the thisUpdate value of the latest CRL it already >>> has, if available. A CRL source is given either by a >>> DistributionPointName or the GeneralNames of the issuing CA. The >>> server shall provide only those CRLs that are more recent than the >>> ones indicated by the client. >>>=20 >>> GenMsg: {id-it TBD1}, SEQUENCE SIZE (1..MAX) OF CRLStatus >>> GenRep: {id-it TBD2}, SEQUENCE SIZE (1..MAX) OF >>> CertificateList | < absent > >>>=20 >>> CRLSource ::=3D CHOICE { >>> dpn [0] DistributionPointName, >>> issuer [1] GeneralNames } >>>=20 >>> CRLStatus ::=3D SEQUENCE { >>> source CRLSource, >>> thisUpdate Time OPTIONAL } >=20 > _______________________________________________ > Spasm mailing list > Spasm@ietf.org > https://www.ietf.org/mailman/listinfo/spasm