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:RFC9653$d62f52f32135 | IETF | STD:IETF:RFC9653 | Zero Checksum for the Stream Control Transmission Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9653$e40c134d2d0a | IETF | STD:IETF:RFC9653 | Zero Checksum for the Stream Control Transmission Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Tüxen | M. Tüxen | string | ||||
STD:IETF:RFC9653$f4b28e603183 | IETF | STD:IETF:RFC9653 | Zero Checksum for the Stream Control Transmission Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Stream Control Transmission Protocol (SCTP) uses a 32-bit checksum in the common header of each packet to provide some level of data integrity. If another method used by SCTP already provides the same or a higher level of data integrity, computing this checksum does not provide any additional protection but does co... | The Stream Control Transmission Protocol (SCTP) uses a 32-bit checksum in the common header of each packet to provide some level of data integrity. If another method used by SCTP already provides the same or a higher level of data integrity, computing this checksum does not provide any additional protection but does co... | monolingualtext | ||||
STD:IETF:RFC9654$1177f4a5a34e | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9654$2727b85435b0 | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 8954 imposed size constraints on the optional Nonce extension for the Online Certificate Status Protocol (OCSP). OCSP is used to check the status of a certificate, and the Nonce extension is used to cryptographically bind an OCSP response message to a particular OCSP request message. Some environments use cryptogr... | RFC 8954 imposed size constraints on the optional Nonce extension for the Online Certificate Status Protocol (OCSP). OCSP is used to check the status of a certificate, and the Nonce extension is used to cryptographically bind an OCSP response message to a particular OCSP request message. Some environments use cryptogr... | monolingualtext | ||||
STD:IETF:RFC9654$5e6d676ab058 | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9654 | https://www.rfc-editor.org/rfc/rfc9654 | url | ||||
STD:IETF:RFC9654$71a3669fba1e | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Sharma | H. Sharma | string | ||||
STD:IETF:RFC9654$9ddeb90569a7 | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9654$a4cdd40a38ef | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Online Certificate Status Protocol (OCSP) Nonce Extension | Online Certificate Status Protocol (OCSP) Nonce Extension | monolingualtext | ||||
STD:IETF:RFC9654$aac84580da03 | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9654$ab95ea69d2aa | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC8954 | RFC8954 | wikibase-item | ||||
STD:IETF:RFC9654$b548074818a9 | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9654$b548074818a9 | IETF | STD:IETF:RFC9654 | Online Certificate Status Protocol (OCSP) Nonce Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9655$02f7dc759820 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Nainar | N. Nainar | string | ||||
STD:IETF:RFC9655$0d48963f0168 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The MPLS ping and traceroute mechanisms described in RFC 8029 and the related extensions for Segment Routing (SR) defined in RFC 8287 are highly valuable for validating control plane and data plane synchronization. In certain environments, only some intermediate or transit nodes may have been upgraded to support these ... | The MPLS ping and traceroute mechanisms described in RFC 8029 and the related extensions for Segment Routing (SR) defined in RFC 8287 are highly valuable for validating control plane and data plane synchronization. In certain environments, only some intermediate or transit nodes may have been upgraded to support these ... | monolingualtext | ||||
STD:IETF:RFC9655$16e9637eb4b7 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9655 | https://www.rfc-editor.org/rfc/rfc9655 | url | ||||
STD:IETF:RFC9655$31abd03729f3 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9655$61acc53ddfa3 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | monolingualtext | ||||
STD:IETF:RFC9655$8e4cbaa80c3d | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9655$8ffac7caa7dd | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9655$9a91af013ed1 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9655$9a91af013ed1 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9655$b0c182183540 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Hegde | S. Hegde | string | ||||
STD:IETF:RFC9655$c90c8598a01c | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Ali | Z. Ali | string | ||||
STD:IETF:RFC9655$d1dd32c8236b | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Arora | K. Arora | string | ||||
STD:IETF:RFC9655$f62a29c80964 | IETF | STD:IETF:RFC9655 | Egress Validation in Label Switched Path Ping and Traceroute Mechanisms | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Rathi | D. Rathi | string | ||||
STD:IETF:RFC9656$05e67f67e5c3 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a YANG data model to describe microwave and millimeter-wave radio links in a network topology. | This document defines a YANG data model to describe microwave and millimeter-wave radio links in a network topology. | monolingualtext | ||||
STD:IETF:RFC9656$07aafbb95635 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Spreafico | D. Spreafico | string | ||||
STD:IETF:RFC9656$2b9cb8b0bf45 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9656$34e074a180bf | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Ahlberg | J. Ahlberg | string | ||||
STD:IETF:RFC9656$4c4e55d079e1 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9656$4c4e55d079e1 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9656$4f6005f00a35 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Mansfield | S. Mansfield | string | ||||
STD:IETF:RFC9656$7426733d2e28 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Ye | M. Ye | string | ||||
STD:IETF:RFC9656$77698e75b3ee | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9656$80721c576495 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9656$b2b239aa6946 | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | X. Li | X. Li | string | ||||
STD:IETF:RFC9656$c9cc81b0120d | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9656 | https://www.rfc-editor.org/rfc/rfc9656 | url | ||||
STD:IETF:RFC9656$fcff89a44bea | IETF | STD:IETF:RFC9656 | A YANG Data Model for Microwave Topology | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A YANG Data Model for Microwave Topology | A YANG Data Model for Microwave Topology | monolingualtext | ||||
STD:IETF:RFC9657$2b7a09d55855 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document introduces use cases where Time-Variant Routing (TVR) computations (i.e., routing computations that take into consideration time-based or scheduled changes to a network) could improve routing protocol convergence and/or network performance. | This document introduces use cases where Time-Variant Routing (TVR) computations (i.e., routing computations that take into consideration time-based or scheduled changes to a network) could improve routing protocol convergence and/or network performance. | monolingualtext | ||||
STD:IETF:RFC9657$4920735ab72a | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Y. Qu | Y. Qu | string | ||||
STD:IETF:RFC9657$4a30b4ce1c46 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Time-Variant Routing (TVR) Use Cases | Time-Variant Routing (TVR) Use Cases | monolingualtext | ||||
STD:IETF:RFC9657$5fc220a98e30 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Birrane, III | E. Birrane, III | string | ||||
STD:IETF:RFC9657$6ed88611b8f6 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | N. Kuhn | N. Kuhn | string | ||||
STD:IETF:RFC9657$9fc4941f4789 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | L. Zhang | L. Zhang | string | ||||
STD:IETF:RFC9657$c8c7570dbc94 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | R. Taylor | R. Taylor | string | ||||
STD:IETF:RFC9657$cab74cea1c2e | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9657$d97f6d43adb0 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9657$da320c01c775 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9657 | https://www.rfc-editor.org/rfc/rfc9657 | url | ||||
STD:IETF:RFC9657$eb1268e7d61e | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9657$eb1268e7d61e | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9657$fe56ed8a0b02 | IETF | STD:IETF:RFC9657 | Time-Variant Routing (TVR) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9658$1482b002246c | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9658 | https://www.rfc-editor.org/rfc/rfc9658 | url | ||||
STD:IETF:RFC9658$32e30643c99e | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9658$392ec4ba9053 | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | IJ. Wijnands | IJ. Wijnands | string | ||||
STD:IETF:RFC9658$52bdff435b55 | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Multipoint LDP Extensions for Multi-Topology Routing | Multipoint LDP Extensions for Multi-Topology Routing | monolingualtext | ||||
STD:IETF:RFC9658$561f3378320b | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9658$8032ae0cd86e | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Raza | K. Raza | string | ||||
STD:IETF:RFC9658$886137188388 | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9658$886137188388 | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9658$a8f877a0ffca | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Multi-Topology Routing (MTR) is a technology that enables service differentiation within an IP network. The Flexible Algorithm (FA) is another mechanism for creating a sub-topology within a topology using defined topology constraints and computation algorithms. In order to deploy Multipoint LDP (mLDP) in a network th... | Multi-Topology Routing (MTR) is a technology that enables service differentiation within an IP network. The Flexible Algorithm (FA) is another mechanism for creating a sub-topology within a topology using defined topology constraints and computation algorithms. In order to deploy Multipoint LDP (mLDP) in a network th... | monolingualtext | ||||
STD:IETF:RFC9658$a9dd9c1950c9 | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9658$bbf805f14838 | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Gulko | A. Gulko | string | ||||
STD:IETF:RFC9658$c6f543923dbe | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Mishra | M. Mishra | string | ||||
STD:IETF:RFC9658$dd3a98a78ad3 | IETF | STD:IETF:RFC9658 | Multipoint LDP Extensions for Multi-Topology Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9659$198d3b83bccd | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9659$2967cc47aa75 | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | N. Jaju | N. Jaju | string | ||||
STD:IETF:RFC9659$3236505e348c | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Deployments of Zstandard, or "zstd", can use different window sizes to limit memory usage during compression and decompression. Some browsers and user agents limit window sizes to mitigate memory usage concerns, thereby causing interoperability issues. This document updates the window size limit in RFC 8878 from a re... | Deployments of Zstandard, or "zstd", can use different window sizes to limit memory usage during compression and decompression. Some browsers and user agents limit window sizes to mitigate memory usage concerns, thereby causing interoperability issues. This document updates the window size limit in RFC 8878 from a re... | monolingualtext | ||||
STD:IETF:RFC9659$421dd823694a | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | W. F. Handte | W. F. Handte | string | ||||
STD:IETF:RFC9659$479812e14f81 | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9659$479812e14f81 | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9659$5db8dc5585c5 | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9659$6fb63c26d424 | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Window Sizing for Zstandard Content Encoding | Window Sizing for Zstandard Content Encoding | monolingualtext | ||||
STD:IETF:RFC9659$94b8f960498a | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9659$a753f4fb3879 | IETF | STD:IETF:RFC9659 | Window Sizing for Zstandard Content Encoding | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9659 | https://www.rfc-editor.org/rfc/rfc9659 | url | ||||
STD:IETF:RFC9660$0b6c326cef72 | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The DNS ZONEVERSION option is a way for DNS clients to request, and for authoritative DNS servers to provide, information regarding the version of the zone from which a response is generated. The SERIAL field from the Start of Authority (SOA) resource record (RR) is a good example of a zone's version, and it is the onl... | The DNS ZONEVERSION option is a way for DNS clients to request, and for authoritative DNS servers to provide, information regarding the version of the zone from which a response is generated. The SERIAL field from the Start of Authority (SOA) resource record (RR) is a good example of a zone's version, and it is the onl... | monolingualtext | ||||
STD:IETF:RFC9660$26196b48d9cf | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9660 | https://www.rfc-editor.org/rfc/rfc9660 | url | ||||
STD:IETF:RFC9660$6e9c42f3dd50 | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9660$7a594bbbbf4b | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The DNS Zone Version (ZONEVERSION) Option | The DNS Zone Version (ZONEVERSION) Option | monolingualtext | ||||
STD:IETF:RFC9660$b248f4cbe846 | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Wessels | D. Wessels | string | ||||
STD:IETF:RFC9660$b88d0cc931e1 | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9660$be7d72c1a365 | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9660$c2779e059eae | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9660$c2779e059eae | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9660$edafd6edf04d | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Vergara | M. Vergara | string | ||||
STD:IETF:RFC9660$ef59f617f22f | IETF | STD:IETF:RFC9660 | The DNS Zone Version (ZONEVERSION) Option | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Salgado | H. Salgado | string | ||||
STD:IETF:RFC9661$2992363a3d0e | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9661$53a5c5fb27e4 | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9661$62a37ce8cfcf | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | monolingualtext | ||||
STD:IETF:RFC9661$6ec7bebbca65 | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9661$76411b2d2f9b | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9661$76411b2d2f9b | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9661$9c8aec52671a | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Murchison | K. Murchison | string | ||||
STD:IETF:RFC9661$e7ef6d608591 | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies a data model for managing Sieve scripts on a server using the JSON Meta Application Protocol (JMAP). Clients can use this protocol to efficiently search, access, organize, and validate Sieve scripts. | This document specifies a data model for managing Sieve scripts on a server using the JSON Meta Application Protocol (JMAP). Clients can use this protocol to efficiently search, access, organize, and validate Sieve scripts. | monolingualtext | ||||
STD:IETF:RFC9661$f5f8fe88d874 | IETF | STD:IETF:RFC9661 | The JSON Meta Application Protocol (JMAP) for Sieve Scripts | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9661 | https://www.rfc-editor.org/rfc/rfc9661 | url | ||||
STD:IETF:RFC9662$0125c3168e7b | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFCs 5425 and 6012 describe using TLS and DTLS to securely transport syslog messages. This document updates the cipher suites required by RFC 5245 (TLS Transport Mapping for Syslog) and RFC 6012 (DTLS Transport Mapping for Syslog). It also updates the protocol recommended by RFC 6012 for secure datagram transport. | RFCs 5425 and 6012 describe using TLS and DTLS to securely transport syslog messages. This document updates the cipher suites required by RFC 5245 (TLS Transport Mapping for Syslog) and RFC 6012 (DTLS Transport Mapping for Syslog). It also updates the protocol recommended by RFC 6012 for secure datagram transport. | monolingualtext | ||||
STD:IETF:RFC9662$1f96020a68f6 | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9662 | https://www.rfc-editor.org/rfc/rfc9662 | url | ||||
STD:IETF:RFC9662$2d5717dbcc12 | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9662$3814f8c19484 | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Updates to the Cipher Suites in Secure Syslog | Updates to the Cipher Suites in Secure Syslog | monolingualtext | ||||
STD:IETF:RFC9662$3edc5953c812 | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Salowey | J. Salowey | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.