Re: [Sidrops] Request early IANA code point assignment for draft-ietf-sidrops-rpki-prefixlist

Russ Housley <housley@vigilsec.com> Mon, 29 January 2024 18:52 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9035C151542 for <sidrops@ietfa.amsl.com>; Mon, 29 Jan 2024 10:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 NKEn7_IodTkK for <sidrops@ietfa.amsl.com>; Mon, 29 Jan 2024 10:52:37 -0800 (PST)
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 C9BA4C15153E for <sidrops@ietf.org>; Mon, 29 Jan 2024 10:52:37 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id DFD851CCA19; Mon, 29 Jan 2024 13:52:36 -0500 (EST)
Received: from smtpclient.apple (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 D24ED1CC6EB; Mon, 29 Jan 2024 13:52:36 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <C51B370B-FBD9-43A2-8608-1DC2B1315AFD@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DE753A8D-6D10-416D-91D4-80606E0CE1EC"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Date: Mon, 29 Jan 2024 13:52:26 -0500
In-Reply-To: <4E8D2E9C-B46F-485C-AF1D-FCA86FB30D23@vigilsec.com>
Cc: Warren Kumari <warren@kumari.net>
To: IETF SIDRops <sidrops@ietf.org>
References: <4E8D2E9C-B46F-485C-AF1D-FCA86FB30D23@vigilsec.com>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/3XzlzaDYYNjiH4Yp2m43vYqPlcQ>
Subject: Re: [Sidrops] Request early IANA code point assignment for draft-ietf-sidrops-rpki-prefixlist
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jan 2024 18:52:41 -0000

IANA has made the code point assignment.

https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#security-smime-1

  id-ct-rpkiSignedPrefixList OBJECT IDENTIFIER ::=
    { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
      pkcs-9(9) id-smime(16) id-ct(1) 50 }

Russ


> On Jan 11, 2024, at 1:46 PM, Russ Housley <housley@vigilsec.com> wrote:
> 
> Warren:
> 
> RFC 7120 provide four conditions for early code point assignment:
> 
>   a.  The code points must be from a space designated as "RFC
>       Required", "IETF Review", or "Standards Action".  Additionally,
>       requests for early assignment of code points from a
>       "Specification Required" registry are allowed if the
>       specification will be published as an RFC.
> 
>   b.  The format, semantics, processing, and other rules related to
>       handling the protocol entities defined by the code points
>       (henceforth called "specifications") must be adequately described
>       in an Internet-Draft.
> 
>   c.  The specifications of these code points must be stable; i.e., if
>       there is a change, implementations based on the earlier and later
>       specifications must be seamlessly interoperable.
> 
>   d.  The Working Group chairs and Area Directors (ADs) judge that
>       there is sufficient interest in the community for early (pre-RFC)
>       implementation and deployment, or that failure to make an early
>       allocation might lead to contention for the code point in the
>       field.
> 
> draft-ietf-sidrops-rpki-prefixlist meets all of these requirements.
> 
>   a.  The registry in question is https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#security-smime-1
>        The registry allocation rule is  "Specification Required".
> 
>   b.  The format, semantics, processing, and other rules related to
>        the content-type are in the Internet-Draft.
> 
>   c.  Several people want to implement the Internet-Draft.
> 
>   d.  The Working Group chairs judge that there is sufficient interest.
> 
> As the AD for the SIDRops WG, please request early assignment by IANA.
> 
> For the SIDRops WG Chairs,
> Russ
>