From 47a357bf7b864ef90171644d42ee225fa078539a Mon Sep 17 00:00:00 2001 From: mnot-bot Date: Mon, 6 Nov 2023 09:41:47 +0000 Subject: [PATCH] update var --- var/rfc-index.xml | 147 +++++++++++++++++++++++++++++++++++++++++ var/rfc-index.xml.etag | 2 +- var/rfcs.json | 38 +++++++++++ 3 files changed, 186 insertions(+), 1 deletion(-) diff --git a/var/rfc-index.xml b/var/rfc-index.xml index 762e278..45a9a44 100644 --- a/var/rfc-index.xml +++ b/var/rfc-index.xml @@ -133765,6 +133765,8 @@ RFC6712 + RFC9480 + RFC9481 PROPOSED STANDARD PROPOSED STANDARD @@ -192962,6 +192964,7 @@ draft-ietf-pkix-new-asn1-08 RFC6960 + RFC9480 INFORMATIONAL INFORMATIONAL @@ -220472,6 +220475,9 @@ RFC4210 + + RFC9480 + PROPOSED STANDARD PROPOSED STANDARD IETF @@ -321329,6 +321335,147 @@ metric.

lsr 10.17487/RFC9479 + + RFC9480 + Certificate Management Protocol (CMP) Updates + + H. Brockhaus + + + D. von Oheimb + + + J. Gray + + + November + 2023 + + + HTML + TEXT + PDF + XML + + 55 + + CMP + +

This document contains a set of updates to the syntax of Certificate Management Protocol (CMP) version 2 and its HTTP transfer mechanism. This document updates RFCs 4210, 5912, and 6712.

The aspects of CMP updated in this document are using EnvelopedData instead of EncryptedValue, clarifying the handling of p10cr messages, improving the crypto agility, as well as adding new general message types, extended key usages to identify certificates for use with CMP, and well-known URI path segments.

CMP version 3 is introduced to enable signaling support of EnvelopedData instead of EncryptedValue and signal the use of an explicit hash AlgorithmIdentifier in certConf messages, as far as needed.

 + draft-ietf-lamps-cmp-updates-23 + + RFC4210 + RFC5912 + RFC6712 + + PROPOSED STANDARD + PROPOSED STANDARD + IETF + sec + lamps + 10.17487/RFC9480 + + + RFC9481 + Certificate Management Protocol (CMP) Algorithms + + H. Brockhaus + + + H. Aschauer + + + M. Ounsworth + + + J. Gray + + + November + 2023 + + + HTML + TEXT + PDF + XML + + 28 +

This document describes the conventions for using several cryptographic algorithms with the Certificate Management Protocol (CMP). CMP is used to enroll and further manage the lifecycle of X.509 certificates. This document also updates the algorithm use profile from Appendix D.2 of RFC 4210.

 + draft-ietf-lamps-cmp-algorithms-15 + + RFC4210 + + PROPOSED STANDARD + PROPOSED STANDARD + IETF + sec + lamps + 10.17487/RFC9481 + + + RFC9482 + Constrained Application Protocol (CoAP) Transfer for the Certificate Management Protocol + + M. Sahni + Editor + + + S. Tripathi + Editor + + + November + 2023 + + + HTML + TEXT + PDF + XML + + 9 +

This document specifies the use of the Constrained Application Protocol (CoAP) as a transfer mechanism for the Certificate Management Protocol (CMP). CMP defines the interaction between various PKI entities for the purpose of certificate creation and management. CoAP is an HTTP-like client-server protocol used by various constrained devices in the Internet of Things space.

 + draft-ietf-ace-cmpv2-coap-transport-10 + PROPOSED STANDARD + PROPOSED STANDARD + IETF + sec + ace + 10.17487/RFC9482 + + + RFC9483 + Lightweight Certificate Management Protocol (CMP) Profile + + H. Brockhaus + + + D. von Oheimb + + + S. Fries + + + November + 2023 + + + HTML + TEXT + PDF + XML + + 83 +

This document aims at simple, interoperable, and automated PKI management operations covering typical use cases of industrial and Internet of Things (IoT) scenarios. This is achieved by profiling the Certificate Management Protocol (CMP), the related Certificate Request Message Format (CRMF), and transfer based on HTTP or Constrained Application Protocol (CoAP) in a succinct but sufficiently detailed and self-contained way. To make secure certificate management for simple scenarios and constrained devices as lightweight as possible, only the most crucial types of operations and options are specified as mandatory. More specialized or complex use cases are supported with optional features.

 + draft-ietf-lamps-lightweight-cmp-profile-21 + PROPOSED STANDARD + PROPOSED STANDARD + IETF + sec + lamps + 10.17487/RFC9483 + RFC9484 Proxying IP in HTTP diff --git a/var/rfc-index.xml.etag b/var/rfc-index.xml.etag index 0722a7c..6274433 100644 --- a/var/rfc-index.xml.etag +++ b/var/rfc-index.xml.etag @@ -1 +1 @@ -W/"d722e4-6093c4a4b03e6-gzip" +W/"d73dae-609699664fc6b-gzip" diff --git a/var/rfcs.json b/var/rfcs.json index 766aa86..e11a860 100644 --- a/var/rfcs.json +++ b/var/rfcs.json @@ -111361,6 +111361,44 @@ "title": "IS-IS Application-Specific Link Attributes", "wg": "lsr" }, + "RFC9480": { + "area": "sec", + "keywords": [ + "CMP" + ], + "level": "std", + "status": "current", + "stream": "ietf", + "title": "Certificate Management Protocol (CMP) Updates", + "wg": "lamps" + }, + "RFC9481": { + "area": "sec", + "keywords": [], + "level": "std", + "status": "current", + "stream": "ietf", + "title": "Certificate Management Protocol (CMP) Algorithms", + "wg": "lamps" + }, + "RFC9482": { + "area": "sec", + "keywords": [], + "level": "std", + "status": "current", + "stream": "ietf", + "title": "Constrained Application Protocol (CoAP) Transfer for the Certificate Management Protocol", + "wg": "ace" + }, + "RFC9483": { + "area": "sec", + "keywords": [], + "level": "std", + "status": "current", + "stream": "ietf", + "title": "Lightweight Certificate Management Protocol (CMP) Profile", + "wg": "lamps" + }, "RFC9484": { "area": "tsv", "keywords": [