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:RFC9360$a91dc37eaca3 | IETF | STD:IETF:RFC9360 | CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9360 | https://www.rfc-editor.org/rfc/rfc9360 | url | ||||
STD:IETF:RFC9360$da001ed070cf | IETF | STD:IETF:RFC9360 | CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9360$ece4d5e60501 | IETF | STD:IETF:RFC9360 | CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The CBOR Object Signing and Encryption (COSE) message structure uses references to keys in general. For some algorithms, additional properties are defined that carry parameters relating to keys as needed. The COSE Key structure is used for transporting keys outside of COSE messages. This document extends the way tha... | The CBOR Object Signing and Encryption (COSE) message structure uses references to keys in general. For some algorithms, additional properties are defined that carry parameters relating to keys as needed. The COSE Key structure is used for transporting keys outside of COSE messages. This document extends the way tha... | monolingualtext | ||||
STD:IETF:RFC9361$12ce99fb5467 | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | monolingualtext | ||||
STD:IETF:RFC9361$17e94ce5f0c4 | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9361$3d79a42f3d3a | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9361$55ca5cc570f0 | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9361 | https://www.rfc-editor.org/rfc/rfc9361 | url | ||||
STD:IETF:RFC9361$5fca4a148558 | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. Lozano | G. Lozano | string | ||||
STD:IETF:RFC9361$b225389b6194 | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9361$be0921317cdc | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9361$be0921317cdc | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9361$ed6c85e162c4 | IETF | STD:IETF:RFC9361 | ICANN Trademark Clearinghouse (TMCH) Functional Specifications | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the requirements, the architecture, and the interfaces between the ICANN Trademark Clearinghouse (TMCH) and Domain Name Registries, as well as between the ICANN TMCH and Domain Name Registrars for the provisioning and management of domain names during Sunrise and Trademark Claims Periods. | This document describes the requirements, the architecture, and the interfaces between the ICANN Trademark Clearinghouse (TMCH) and Domain Name Registries, as well as between the ICANN TMCH and Domain Name Registrars for the provisioning and management of domain names during Sunrise and Trademark Claims Periods. | monolingualtext | ||||
STD:IETF:RFC9362$5346fc97b30b | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Boucadair | M. Boucadair | string | ||||
STD:IETF:RFC9362$7a16fe7e2668 | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9362$7a16fe7e2668 | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9362$82eb5a76b95b | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9362$9c6a1f68ab5f | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | monolingualtext | ||||
STD:IETF:RFC9362$a1d9c2b74fdc | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9362$cc454397f6c9 | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Shallow | J. Shallow | string | ||||
STD:IETF:RFC9362$d898afd715c3 | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9362$e1e9f0a53bd6 | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9362 | https://www.rfc-editor.org/rfc/rfc9362 | url | ||||
STD:IETF:RFC9362$f3aa45bf0ed7 | IETF | STD:IETF:RFC9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies new DDoS Open Threat Signaling (DOTS) signal channel configuration parameters that can be negotiated between DOTS peers to enable the use of Q-Block1 and Q-Block2 Constrained Application Protocol (CoAP) options. These options enable robust and faster transmission rates for large amounts of data ... | This document specifies new DDoS Open Threat Signaling (DOTS) signal channel configuration parameters that can be negotiated between DOTS peers to enable the use of Q-Block1 and Q-Block2 Constrained Application Protocol (CoAP) options. These options enable robust and faster transmission rates for large amounts of data ... | monolingualtext | ||||
STD:IETF:RFC9363$1e95a8fc466a | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9363$21faef653896 | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9363$21faef653896 | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9363$299aecb33539 | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Toutain | L. Toutain | string | ||||
STD:IETF:RFC9363$5b97e0395d12 | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9363 | https://www.rfc-editor.org/rfc/rfc9363 | url | ||||
STD:IETF:RFC9363$60381427cf2a | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9363$744a52e75b16 | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A YANG Data Model for Static Context Header Compression (SCHC) | A YANG Data Model for Static Context Header Compression (SCHC) | monolingualtext | ||||
STD:IETF:RFC9363$8ab54788716a | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Minaburo | A. Minaburo | string | ||||
STD:IETF:RFC9363$eaaa50c8d326 | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a YANG data model for the Static Context Header Compression (SCHC) compression and fragmentation Rules. This document formalizes the description of the Rules for better interoperability between SCHC instances either to exchange a set of Rules or to modify the parameters of some Rules. | This document describes a YANG data model for the Static Context Header Compression (SCHC) compression and fragmentation Rules. This document formalizes the description of the Rules for better interoperability between SCHC instances either to exchange a set of Rules or to modify the parameters of some Rules. | monolingualtext | ||||
STD:IETF:RFC9363$fee6ce450f02 | IETF | STD:IETF:RFC9363 | A YANG Data Model for Static Context Header Compression (SCHC) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9364$11b4f94de2fc | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9364$122bc3d4828e | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the DNS Security Extensions (commonly called "DNSSEC") that are specified in RFCs 4033, 4034, and 4035, as well as a handful of others. One purpose is to introduce all of the RFCs in one place so that the reader can understand the many aspects of DNSSEC. This document does not update any of th... | This document describes the DNS Security Extensions (commonly called "DNSSEC") that are specified in RFCs 4033, 4034, and 4035, as well as a handful of others. One purpose is to introduce all of the RFCs in one place so that the reader can understand the many aspects of DNSSEC. This document does not update any of th... | monolingualtext | ||||
STD:IETF:RFC9364$1276de7a59e5 | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9364$1276de7a59e5 | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9364$175197f95103 | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | DNS Security Extensions (DNSSEC) | DNS Security Extensions (DNSSEC) | monolingualtext | ||||
STD:IETF:RFC9364$98a6c27ae60e | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9364$bdbe808e55d8 | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | P. Hoffman | P. Hoffman | string | ||||
STD:IETF:RFC9364$bed0547a8dfc | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9364 | https://www.rfc-editor.org/rfc/rfc9364 | url | ||||
STD:IETF:RFC9364$d33fdb28bb21 | IETF | STD:IETF:RFC9364 | DNS Security Extensions (DNSSEC) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9365$58868354002d | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | monolingualtext | ||||
STD:IETF:RFC9365$5990ccb20680 | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Jeong | J. Jeong | string | ||||
STD:IETF:RFC9365$6664cbf9c66a | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9365$6664cbf9c66a | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9365$76ce75f4934e | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9365 | https://www.rfc-editor.org/rfc/rfc9365 | url | ||||
STD:IETF:RFC9365$7eb3435e482c | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9365$924643f3a7aa | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document discusses the problem statement and use cases of IPv6-based vehicular networking for Intelligent Transportation Systems (ITS). The main scenarios of vehicular communications are vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X) communications. First, this documen... | This document discusses the problem statement and use cases of IPv6-based vehicular networking for Intelligent Transportation Systems (ITS). The main scenarios of vehicular communications are vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X) communications. First, this documen... | monolingualtext | ||||
STD:IETF:RFC9365$cae64402816f | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9365$cd88c0b7e088 | IETF | STD:IETF:RFC9365 | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9366$0a64bcb17394 | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9366$102c1426eb6b | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9366$10e9fa6faeac | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Multiple SIP Reason Header Field Values | Multiple SIP Reason Header Field Values | monolingualtext | ||||
STD:IETF:RFC9366$30de41fa8d1a | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Sparks | R. Sparks | string | ||||
STD:IETF:RFC9366$6a84ba1b5b37 | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The SIP Reason header field as defined in RFC 3326 allows only one Reason value per protocol value. Experience with more recently defined protocols shows it is useful to allow multiple values with the same protocol value. This document updates RFC 3326 to allow multiple values for an indicated registered protocol whe... | The SIP Reason header field as defined in RFC 3326 allows only one Reason value per protocol value. Experience with more recently defined protocols shows it is useful to allow multiple values with the same protocol value. This document updates RFC 3326 to allow multiple values for an indicated registered protocol whe... | monolingualtext | ||||
STD:IETF:RFC9366$9cc3bdd862a3 | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9366$9d73c6b86775 | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9366$9d73c6b86775 | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9366$a6c5e82c7557 | IETF | STD:IETF:RFC9366 | Multiple SIP Reason Header Field Values | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9366 | https://www.rfc-editor.org/rfc/rfc9366 | url | ||||
STD:IETF:RFC9367$03b108b90278 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9367$03b108b90278 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9367$0daacf9bde7c | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9367$21d054030f24 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9367 | https://www.rfc-editor.org/rfc/rfc9367 | url | ||||
STD:IETF:RFC9367$395916628a49 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Babueva | A. Babueva | string | ||||
STD:IETF:RFC9367$4109f6a94123 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | L. Nikiforova | L. Nikiforova | string | ||||
STD:IETF:RFC9367$484992d206f2 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9367$5c4e5bd67bdd | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9367$6d6507c3f7f7 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Alekseev | E. Alekseev | string | ||||
STD:IETF:RFC9367$97ae9ac9e06f | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | monolingualtext | ||||
STD:IETF:RFC9367$9cba04fb459b | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Smyshlyaev | S. Smyshlyaev | string | ||||
STD:IETF:RFC9367$d4861f9a2751 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Griboedova | E. Griboedova | string | ||||
STD:IETF:RFC9367$d98e47900785 | IETF | STD:IETF:RFC9367 | GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3 | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The purpose of this document is to make the Russian cryptographic standards available to the Internet community for their implementation in the Transport Layer Security (TLS) Protocol Version 1.3. This document defines the cipher suites, signature schemes, and key exchange mechanisms for using Russian cryptographic st... | The purpose of this document is to make the Russian cryptographic standards available to the Internet community for their implementation in the Transport Layer Security (TLS) Protocol Version 1.3. This document defines the cipher suites, signature schemes, and key exchange mechanisms for using Russian cryptographic st... | monolingualtext | ||||
STD:IETF:RFC9368$1104a638b13b | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9368$186aedb22bfe | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9368 | https://www.rfc-editor.org/rfc/rfc9368 | url | ||||
STD:IETF:RFC9368$4b3aba4c0f4a | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9368$4f07d8072086 | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Schinazi | D. Schinazi | string | ||||
STD:IETF:RFC9368$5721e29f08ee | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9368$7d7e37174d1e | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | QUIC does not provide a complete version negotiation mechanism but instead only provides a way for the server to indicate that the version the client chose is unacceptable. This document describes a version negotiation mechanism that allows a client and server to select a mutually supported version. Optionally, if th... | QUIC does not provide a complete version negotiation mechanism but instead only provides a way for the server to indicate that the version the client chose is unacceptable. This document describes a version negotiation mechanism that allows a client and server to select a mutually supported version. Optionally, if th... | monolingualtext | ||||
STD:IETF:RFC9368$96f2f7a33982 | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9368$96f2f7a33982 | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9368$bf5ae33d8fb4 | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Compatible Version Negotiation for QUIC | Compatible Version Negotiation for QUIC | monolingualtext | ||||
STD:IETF:RFC9368$d75de1ca38e3 | IETF | STD:IETF:RFC9368 | Compatible Version Negotiation for QUIC | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Rescorla | E. Rescorla | string | ||||
STD:IETF:RFC9369$1ca1217a47f9 | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9369 | https://www.rfc-editor.org/rfc/rfc9369 | url | ||||
STD:IETF:RFC9369$218e07a25c76 | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9369$36b554678a3e | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9369$a79b6c8daea5 | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | QUIC Version 2 | QUIC Version 2 | monolingualtext | ||||
STD:IETF:RFC9369$a8ced61dbe72 | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Duke | M. Duke | string | ||||
STD:IETF:RFC9369$a8f04ea56f10 | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies QUIC version 2, which is identical to QUIC version 1 except for some trivial details. Its purpose is to combat various ossification vectors and exercise the version negotiation framework. It also serves as a template for the minimum changes in any future version of QUIC. Note that "version 2" i... | This document specifies QUIC version 2, which is identical to QUIC version 1 except for some trivial details. Its purpose is to combat various ossification vectors and exercise the version negotiation framework. It also serves as a template for the minimum changes in any future version of QUIC. Note that "version 2" i... | monolingualtext | ||||
STD:IETF:RFC9369$c545dae226a4 | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9369$caa3ac1d36af | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9369$caa3ac1d36af | IETF | STD:IETF:RFC9369 | QUIC Version 2 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9370$00197c5b76bc | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Bartlett | G. Bartlett | string | ||||
STD:IETF:RFC9370$07af29752b6c | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Fluhrer | S. Fluhrer | string | ||||
STD:IETF:RFC9370$0b741c68b2ec | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | V. Smyslov | V. Smyslov | string | ||||
STD:IETF:RFC9370$289ab70e1c3c | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Van Geest | D. Van Geest | string | ||||
STD:IETF:RFC9370$2e3245b08b7a | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9370 | https://www.rfc-editor.org/rfc/rfc9370 | url | ||||
STD:IETF:RFC9370$364cfdf60ad1 | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes how to extend the Internet Key Exchange Protocol Version 2 (IKEv2) to allow multiple key exchanges to take place while computing a shared secret during a Security Association (SA) setup. This document utilizes the IKE_INTERMEDIATE exchange, where multiple key exchanges are performed when an IKE... | This document describes how to extend the Internet Key Exchange Protocol Version 2 (IKEv2) to allow multiple key exchanges to take place while computing a shared secret during a Security Association (SA) setup. This document utilizes the IKE_INTERMEDIATE exchange, where multiple key exchanges are performed when an IKE... | monolingualtext | ||||
STD:IETF:RFC9370$3f5f7ded123d | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9370$3f5f7ded123d | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9370$405354501a96 | IETF | STD:IETF:RFC9370 | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2) | monolingualtext |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.