statement_id stringlengths 26 83 | source stringclasses 6
values | subject_id stringlengths 3 70 | subject_label stringlengths 0 250 | subject_description stringlengths 0 250 | subject_instance_of_ids stringlengths 0 139 | subject_instance_of_labels stringlengths 0 310 | property_id stringlengths 2 6 | property_label stringlengths 0 80 | value_id stringlengths 1 1.9k | value_label stringlengths 0 1.9k | value_type stringclasses 8
values | qualifier_property_id stringclasses 948
values | qualifier_property_label stringclasses 947
values | qualifier_value_id stringlengths 0 686 | qualifier_value_label stringlengths 0 205 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
STD:IETF:RFC9806$55739c1e2b05 | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Mongrain | D. Mongrain | string | ||||
STD:IETF:RFC9806$55d5024bc5c1 | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | monolingualtext | ||||
STD:IETF:RFC9806$d601ae84bc2c | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9806$f0ceedebc2ea | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9807$1f73cba93144 | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the OPAQUE protocol, an Augmented (or Asymmetric) Password-Authenticated Key Exchange (aPAKE) protocol that supports mutual authentication in a client-server setting without reliance on PKI and with security against pre-computation attacks upon server compromise. In addition, the protocol provi... | This document describes the OPAQUE protocol, an Augmented (or Asymmetric) Password-Authenticated Key Exchange (aPAKE) protocol that supports mutual authentication in a client-server setting without reliance on PKI and with security against pre-computation attacks upon server compromise. In addition, the protocol provi... | monolingualtext | ||||
STD:IETF:RFC9807$2d60af9b0c67 | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9807$2efe8540a4bb | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9807$59f6ab354e06 | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9807$59f6ab354e06 | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9807$5a96cd9dacb4 | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | monolingualtext | ||||
STD:IETF:RFC9807$65b55c80c03f | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9807$7a9d1783d270 | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Bourdrez | D. Bourdrez | string | ||||
STD:IETF:RFC9807$becd0f96a87f | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. A. Wood | C. A. Wood | string | ||||
STD:IETF:RFC9807$c81b7c3a1a1f | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | K. Lewi | K. Lewi | string | ||||
STD:IETF:RFC9807$ce51552efe63 | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | H. Krawczyk | H. Krawczyk | string | ||||
STD:IETF:RFC9807$e31dac02aaa1 | IETF | STD:IETF:RFC9807 | The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9807 | https://www.rfc-editor.org/rfc/rfc9807 | url | ||||
STD:IETF:RFC9808$04a60b0cbac8 | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Ryan | A. Ryan | string | ||||
STD:IETF:RFC9808$61cabdf23ed1 | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9808$6e6de2dbaa0e | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This specification defines a set of additional Capability Objects that provide information about current downstream CDN (dCDN) utilization and specified usage limits to the delegating upstream CDN (uCDN) in order to inform traffic delegation decisions. This document supplements the CDNI Capability Objects, defined in ... | This specification defines a set of additional Capability Objects that provide information about current downstream CDN (dCDN) utilization and specified usage limits to the delegating upstream CDN (uCDN) in order to inform traffic delegation decisions. This document supplements the CDNI Capability Objects, defined in ... | monolingualtext | ||||
STD:IETF:RFC9808$7102672bfa77 | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Rosenblum | B. Rosenblum | string | ||||
STD:IETF:RFC9808$79d4ebe773d9 | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9808$79d4ebe773d9 | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9808$b65b04005284 | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9808$c07936ac4951 | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | monolingualtext | ||||
STD:IETF:RFC9808$cfe2c55f1e6b | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Sopher | N. Sopher | string | ||||
STD:IETF:RFC9808$d2841bf4c5fe | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9808 | https://www.rfc-editor.org/rfc/rfc9808 | url | ||||
STD:IETF:RFC9808$d5ad908ebfd3 | IETF | STD:IETF:RFC9808 | Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9809$6da65cbf10ac | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | monolingualtext | ||||
STD:IETF:RFC9809$767b69ae667b | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Goltzsche | D. Goltzsche | string | ||||
STD:IETF:RFC9809$786d588c66dd | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9809$86641e589816 | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9809$8c2c319954b0 | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Brockhaus | H. Brockhaus | string | ||||
STD:IETF:RFC9809$a244f21f306d | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9809$a63d55a14834 | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9809 | https://www.rfc-editor.org/rfc/rfc9809 | url | ||||
STD:IETF:RFC9809$cce2862164ee | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9809$cce2862164ee | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9809$fd1b52f30504 | IETF | STD:IETF:RFC9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 5280 defines the Extended Key Usage (EKU) extension and specifies several extended key purpose identifiers (KeyPurposeIds) for use with that extension in X.509 certificates. This document defines KeyPurposeIds for general-purpose and trust anchor configuration files, for software and firmware update packages, and ... | RFC 5280 defines the Extended Key Usage (EKU) extension and specifies several extended key purpose identifiers (KeyPurposeIds) for use with that extension in X.509 certificates. This document defines KeyPurposeIds for general-purpose and trust anchor configuration files, for software and firmware update packages, and ... | monolingualtext | ||||
STD:IETF:RFC9810$11edd9783faf | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocol (CMP). Protocol messages are defined for X.509v3 certificate creation and management. CMP provides interactions between client systems and PKI components such as a Registration Authority (RA) and a Certification A... | This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocol (CMP). Protocol messages are defined for X.509v3 certificate creation and management. CMP provides interactions between client systems and PKI components such as a Registration Authority (RA) and a Certification A... | monolingualtext | ||||
STD:IETF:RFC9810$3db464695ed9 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Ounsworth | M. Ounsworth | string | ||||
STD:IETF:RFC9810$450b51a4eaa9 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9810$6214a54f72c3 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC4210 | RFC4210 | wikibase-item | ||||
STD:IETF:RFC9810$6b0379d704dd | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. von Oheimb | D. von Oheimb | string | ||||
STD:IETF:RFC9810$8d57f2898eae | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9810$9607a76db8c9 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9810 | https://www.rfc-editor.org/rfc/rfc9810 | url | ||||
STD:IETF:RFC9810$a309bd8fd527 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Brockhaus | H. Brockhaus | string | ||||
STD:IETF:RFC9810$b2c6835210a8 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC9480 | RFC9480 | wikibase-item | ||||
STD:IETF:RFC9810$c1fae5528b90 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | monolingualtext | ||||
STD:IETF:RFC9810$c3f426791f00 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9810$e05e5cd5191f | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9810$e05e5cd5191f | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9810$f4f5308239d0 | IETF | STD:IETF:RFC9810 | Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Gray | J. Gray | string | ||||
STD:IETF:RFC9811$041a9c53b553 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC9480 | RFC9480 | wikibase-item | ||||
STD:IETF:RFC9811$273d80e52030 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9811$484c384aefa7 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. von Oheimb | D. von Oheimb | string | ||||
STD:IETF:RFC9811$5eab73d14544 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9811$63e492a49532 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9811$63e492a49532 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9811$7017ae13c352 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9811$762b4c7da2b5 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Brockhaus | H. Brockhaus | string | ||||
STD:IETF:RFC9811$959718fd05fe | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Ounsworth | M. Ounsworth | string | ||||
STD:IETF:RFC9811$a5c2936a2054 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Gray | J. Gray | string | ||||
STD:IETF:RFC9811$a6f9c5b0c9a7 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC6712 | RFC6712 | wikibase-item | ||||
STD:IETF:RFC9811$b9b1e0583ec0 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | monolingualtext | ||||
STD:IETF:RFC9811$be7da7e24897 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes how to layer the Certificate Management Protocol (CMP) over HTTP. It includes the updates to RFC 6712 specified in Section 3 of RFC 9480; these updates introduce CMP URIs using a well-known prefix. It obsoletes RFC 6712; and, together with RFC 9810, it also obsoletes RFC 9480. | This document describes how to layer the Certificate Management Protocol (CMP) over HTTP. It includes the updates to RFC 6712 specified in Section 3 of RFC 9480; these updates introduce CMP URIs using a well-known prefix. It obsoletes RFC 6712; and, together with RFC 9810, it also obsoletes RFC 9480. | monolingualtext | ||||
STD:IETF:RFC9811$e1ccda363762 | IETF | STD:IETF:RFC9811 | Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9811 | https://www.rfc-editor.org/rfc/rfc9811 | url | ||||
STD:IETF:RFC9812$2fbe611f35b5 | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | D. Farmer | D. Farmer | string | ||||
STD:IETF:RFC9812$3aa0f54b8dcb | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9812$54f54ab74f11 | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9812 | https://www.rfc-editor.org/rfc/rfc9812 | url | ||||
STD:IETF:RFC9812$81f972b8cdf1 | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | B. Carpenter | B. Carpenter | string | ||||
STD:IETF:RFC9812$88af4a9d2737 | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9812$8ca39316e5de | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9812$8ca39316e5de | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9812$a0113b4937bb | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | S. Krishnan | S. Krishnan | string | ||||
STD:IETF:RFC9812$b17cd34e0ad9 | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | Clarification of IPv6 Address Allocation Policy | Clarification of IPv6 Address Allocation Policy | monolingualtext | ||||
STD:IETF:RFC9812$e6c6a5c59657 | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies the approval process for changes to the "IPv6
Address Space" registry. It also updates RFC 7249. | This document specifies the approval process for changes to the "IPv6
Address Space" registry. It also updates RFC 7249. | monolingualtext | ||||
STD:IETF:RFC9812$f496e20567b4 | IETF | STD:IETF:RFC9812 | Clarification of IPv6 Address Allocation Policy | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9813$0d9332936a5e | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document provides implementation and operational considerations for using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS/TLS (RFC 6614) and RADIUS/DTLS (RFC 7360). The purpose of the document is to help smooth the operational transition from the use of RADIUS/UDP to RADIUS/TLS. | This document provides implementation and operational considerations for using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS/TLS (RFC 6614) and RADIUS/DTLS (RFC 7360). The purpose of the document is to help smooth the operational transition from the use of RADIUS/UDP to RADIUS/TLS. | monolingualtext | ||||
STD:IETF:RFC9813$2206a660094a | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | A. DeKok | A. DeKok | string | ||||
STD:IETF:RFC9813$3866eeb30f21 | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9813$733c90b4eefe | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | monolingualtext | ||||
STD:IETF:RFC9813$8f9dfe881e17 | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9813$bb65d67f1bf9 | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9813 | https://www.rfc-editor.org/rfc/rfc9813 | url | ||||
STD:IETF:RFC9813$e79d5c06e5fd | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9813$ffe29fd2529b | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9813$ffe29fd2529b | IETF | STD:IETF:RFC9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9814$1790ac2fbbfd | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Fluhrer | S. Fluhrer | string | ||||
STD:IETF:RFC9814$3659a68022a6 | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9814$a4c44fd0057e | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Westerbaan | B. Westerbaan | string | ||||
STD:IETF:RFC9814$ad185a72b8de | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9814$ad185a72b8de | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9814$b385f6cace6a | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | SLH-DSA is a stateless hash-based signature algorithm. This document specifies the conventions for using the SLH-DSA signature algorithm with the Cryptographic Message Syntax (CMS). In addition, the algorithm identifier and public key syntax are provided. | SLH-DSA is a stateless hash-based signature algorithm. This document specifies the conventions for using the SLH-DSA signature algorithm with the Cryptographic Message Syntax (CMS). In addition, the algorithm identifier and public key syntax are provided. | monolingualtext | ||||
STD:IETF:RFC9814$c03113c95a45 | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Housley | R. Housley | string | ||||
STD:IETF:RFC9814$c680b2da36ca | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9814 | https://www.rfc-editor.org/rfc/rfc9814 | url | ||||
STD:IETF:RFC9814$cf4cbc38c0e5 | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Kampanakis | P. Kampanakis | string | ||||
STD:IETF:RFC9814$cf7e8d989b7a | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | monolingualtext | ||||
STD:IETF:RFC9814$ef78983e57cd | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9814$fd9ac9f35424 | IETF | STD:IETF:RFC9814 | Use of the SLH-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9815$118aab7f8119 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Patel | K. Patel | string | ||||
STD:IETF:RFC9815$25f5acb09b6c | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9815$26c2d8205114 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | monolingualtext |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.