[Sidrops] Request early IANA code point assignment for draft-ietf-sidrops-rpki-prefixlist
Russ Housley <housley@vigilsec.com> Thu, 11 January 2024 18:47 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 15D03C14F748 for <sidrops@ietfa.amsl.com>; Thu, 11 Jan 2024 10:47:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 hpVO4WdMyMS2 for <sidrops@ietfa.amsl.com>; Thu, 11 Jan 2024 10:47:14 -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 049B4C2D8F5F for <sidrops@ietf.org>; Thu, 11 Jan 2024 10:46:58 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id F0E241D12EA; Thu, 11 Jan 2024 13:46:56 -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 E01681D0FF5; Thu, 11 Jan 2024 13:46:56 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Message-Id: <4E8D2E9C-B46F-485C-AF1D-FCA86FB30D23@vigilsec.com>
Date: Thu, 11 Jan 2024 13:46:46 -0500
Cc: sidrops <sidrops@ietf.org>
To: Warren Kumari <warren@kumari.net>
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/BrRQ3lWHkCGkihZ2SGX7KzM5Jps>
Subject: [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: Thu, 11 Jan 2024 18:47:18 -0000
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
- [Sidrops] Request early IANA code point assignmen… Russ Housley
- Re: [Sidrops] Request early IANA code point assig… Sean Turner
- Re: [Sidrops] Request early IANA code point assig… Russ Housley
- Re: [Sidrops] Request early IANA code point assig… Job Snijders
- Re: [Sidrops] Request early IANA code point assig… Job Snijders
- Re: [Sidrops] Request early IANA code point assig… Russ Housley
- Re: [Sidrops] Request early IANA code point assig… Russ Housley