Re: [lamps] early assignment OID
Russ Housley <housley@vigilsec.com> Fri, 16 September 2022 17:37 UTC
Return-Path: <housley@vigilsec.com>
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 3D815C14CE41 for <spasm@ietfa.amsl.com>; Fri, 16 Sep 2022 10:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xUL-spuoWOIA for <spasm@ietfa.amsl.com>; Fri, 16 Sep 2022 10:37:25 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE6EDC14CF10 for <spasm@ietf.org>; Fri, 16 Sep 2022 10:37:24 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 5CA7D12906F; Fri, 16 Sep 2022 13:37:22 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [96.241.2.243]) (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 4B5EE128FFA; Fri, 16 Sep 2022 13:37:22 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <0100C644-1AB7-4886-AE3D-2A6059FA0BE6@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5BE45823-B822-401E-99C6-D4DBC58884D0"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Fri, 16 Sep 2022 13:37:22 -0400
In-Reply-To: <CADZyTknaF-TEU28GKe7AqZ20nMXF+J9dQHAhMr2Cx5BTeiNTYw@mail.gmail.com>
Cc: LAMPS <spasm@ietf.org>
To: Daniel Migault <mglt.ietf@gmail.com>
References: <CADZyTknaF-TEU28GKe7AqZ20nMXF+J9dQHAhMr2Cx5BTeiNTYw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-Scanned-By: mailmunge 3.09 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/r6Y6OlTao2WQQ5k99_1pMwpvzHQ>
Subject: Re: [lamps] early assignment OID
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2022 17:37:27 -0000
I assume that Daniel means draft-ietf-lamps-5g-nftypes. Note that this document is already in WG Last Call. Russ > On Sep 16, 2022, at 1:32 PM, Daniel Migault <mglt.ietf@gmail.com> wrote: > > Hi, > > We would like to generate examples for draft-housley-lamps-3g-nftypes, which requires OID to be assigned. I was wondering if one could proceed to an early assignment request? > > The iana section is just mentioned below: > For the NFType certificate extension in Section 4 <https://www.ietf.org/archive/id/draft-ietf-lamps-5g-nftypes-02.html#extn>, IANA is requested to assign an object identifier (OID) for the certificate extension. The OID for the certificate extension should be allocated in the "SMI Security for PKIX Certificate Extension" registry (1.3.6.1.5.5.7.1). <https://www.ietf.org/archive/id/draft-ietf-lamps-5g-nftypes-02.html#section-8-1> > For the ASN.1 Module in Section 5 <https://www.ietf.org/archive/id/draft-ietf-lamps-5g-nftypes-02.html#asn1-mod>, IANA is requested to assign an object identifier (OID) for the module identifier. The OID for the module should be allocated in the "SMI Security for PKIX Module Identifier" registry (1.3.6.1.5.5.7.0). > > Yours, > Daniel >
- [lamps] early assignment OID Daniel Migault
- Re: [lamps] early assignment OID Russ Housley
- Re: [lamps] early assignment OID Daniel Migault
- Re: [lamps] early assignment OID Tim Hollebeek
- Re: [lamps] early assignment OID Tim Hollebeek
- Re: [lamps] early assignment OID Roman Danyliw