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:RFC9743$3b9ca2520afe | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9743$435691032a6a | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | M. Duke | M. Duke | string | ||||
STD:IETF:RFC9743$67654db4aef2 | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | G. Fairhurst | G. Fairhurst | string | ||||
STD:IETF:RFC9743$8cbdae2198f9 | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9743$b4701c810a75 | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC5033 | RFC5033 | wikibase-item | ||||
STD:IETF:RFC9743$d33a83e650bc | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9743$f3d28f837729 | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9743 | https://www.rfc-editor.org/rfc/rfc9743 | url | ||||
STD:IETF:RFC9743$f6871537cd23 | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 5033 discusses the principles and guidelines for standardizing new congestion control algorithms. This document obsoletes RFC 5033 to reflect changes in the congestion control landscape by providing a framework for the development and assessment of congestion control mechanisms, promoting stability across diverse ... | RFC 5033 discusses the principles and guidelines for standardizing new congestion control algorithms. This document obsoletes RFC 5033 to reflect changes in the congestion control landscape by providing a framework for the development and assessment of congestion control mechanisms, promoting stability across diverse ... | monolingualtext | ||||
STD:IETF:RFC9744$1e11b17c648d | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9744$2f6f428eca02 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9744$2f6f428eca02 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9744$33ab37374098 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9744$3428a8229039 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9744$495cb36730e5 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Drake | J. Drake | string | ||||
STD:IETF:RFC9744$49c6a6394a98 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sajassi | A. Sajassi | string | ||||
STD:IETF:RFC9744$5c40a5942432 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9744 | https://www.rfc-editor.org/rfc/rfc9744 | url | ||||
STD:IETF:RFC9744$769ce1ca0209 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Uttaro | J. Uttaro | string | ||||
STD:IETF:RFC9744$8af5c97ebcb5 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | monolingualtext | ||||
STD:IETF:RFC9744$a0ee0753a3ff | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9744$a8ac780cc90b | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Brissette | P. Brissette | string | ||||
STD:IETF:RFC9744$cefb763794ba | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Boutros | S. Boutros | string | ||||
STD:IETF:RFC9744$e5bfa1bd8899 | IETF | STD:IETF:RFC9744 | EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a new EVPN Virtual Private Wire Service (VPWS) service type specifically for multiplexing multiple attachment circuits across different Ethernet Segments (ESs) and physical interfaces into a single EVPN-VPWS service tunnel and still providing Single-Active and All-Active multi-homing. This new ... | This document describes a new EVPN Virtual Private Wire Service (VPWS) service type specifically for multiplexing multiple attachment circuits across different Ethernet Segments (ESs) and physical interfaces into a single EVPN-VPWS service tunnel and still providing Single-Active and All-Active multi-homing. This new ... | monolingualtext | ||||
STD:IETF:RFC9745$0b0cc521161f | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The Deprecation HTTP Response Header Field | The Deprecation HTTP Response Header Field | monolingualtext | ||||
STD:IETF:RFC9745$177838ee7a18 | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Deprecation HTTP response header field is used to signal to consumers of a resource (identified by a URI) that the resource will be or has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides further information about planned or existing deprecation. It may ... | The Deprecation HTTP response header field is used to signal to consumers of a resource (identified by a URI) that the resource will be or has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides further information about planned or existing deprecation. It may ... | monolingualtext | ||||
STD:IETF:RFC9745$385d8c179726 | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9745 | https://www.rfc-editor.org/rfc/rfc9745 | url | ||||
STD:IETF:RFC9745$4165834303e5 | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9745$78068dea333a | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9745$78068dea333a | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9745$8f2ad7c33001 | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Wilde | E. Wilde | string | ||||
STD:IETF:RFC9745$a19e1b020756 | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9745$a82363c698ec | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9745$a9183e0d710c | IETF | STD:IETF:RFC9745 | The Deprecation HTTP Response Header Field | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Dalal | S. Dalal | string | ||||
STD:IETF:RFC9746$004841094f25 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Nagaraj | K. Nagaraj | string | ||||
STD:IETF:RFC9746$1ac0eed2e5d1 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Lin | W. Lin | string | ||||
STD:IETF:RFC9746$2174faae897c | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9746$2451e89853d2 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9746$3b9aaee361f6 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9746$90ca63960e89 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9746$90ca63960e89 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9746$c3acdcaa8777 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sajassi | A. Sajassi | string | ||||
STD:IETF:RFC9746$c40c8f15901e | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9746$cbe419d658d8 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9746 | https://www.rfc-editor.org/rfc/rfc9746 | url | ||||
STD:IETF:RFC9746$df7018baee54 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | An Ethernet Virtual Private Network (EVPN) is commonly used with Network Virtualization Overlay (NVO) tunnels as well as with MPLS and Segment Routing (SR) tunnels. The multihoming procedures in EVPN may vary based on the type of tunnel used within the EVPN Broadcast Domain. Specifically, there are two multihoming spli... | An Ethernet Virtual Private Network (EVPN) is commonly used with Network Virtualization Overlay (NVO) tunnels as well as with MPLS and Segment Routing (SR) tunnels. The multihoming procedures in EVPN may vary based on the type of tunnel used within the EVPN Broadcast Domain. Specifically, there are two multihoming spli... | monolingualtext | ||||
STD:IETF:RFC9746$e8c9427e43b9 | IETF | STD:IETF:RFC9746 | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | monolingualtext | ||||
STD:IETF:RFC9747$1736f68b8090 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9747$1b8018557361 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | X. Min | X. Min | string | ||||
STD:IETF:RFC9747$2729b18aab8e | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Wang | R. Wang | string | ||||
STD:IETF:RFC9747$2f0746115a74 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | monolingualtext | ||||
STD:IETF:RFC9747$32b6576c34e1 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Cheng | W. Cheng | string | ||||
STD:IETF:RFC9747$7dd1c41d6726 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9747$7dd1c41d6726 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9747$8d46a2207fce | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9747 | https://www.rfc-editor.org/rfc/rfc9747 | url | ||||
STD:IETF:RFC9747$a9c7195795c5 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9747$ab88122f3368 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies an extension to the Bidirectional Forwarding Detection (BFD) protocol that enables the use of the BFD Echo function without the need for an associated BFD control session. This "Unaffiliated BFD Echo" mechanism allows rapid detection of forwarding path failures in networks where establishing BFD... | This document specifies an extension to the Bidirectional Forwarding Detection (BFD) protocol that enables the use of the BFD Echo function without the need for an associated BFD control session. This "Unaffiliated BFD Echo" mechanism allows rapid detection of forwarding path failures in networks where establishing BFD... | monolingualtext | ||||
STD:IETF:RFC9747$b31867d11a5d | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Boddireddy | R. Boddireddy | string | ||||
STD:IETF:RFC9747$e0c910e04076 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9747$ef3a93df5561 | IETF | STD:IETF:RFC9747 | Unaffiliated Bidirectional Forwarding Detection (BFD) Echo | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Rahman | R. Rahman | string | ||||
STD:IETF:RFC9748$25548a266d5f | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9748$4361922428a1 | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9748$61eec4d8e21a | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Updating the NTP Registries | Updating the NTP Registries | monolingualtext | ||||
STD:IETF:RFC9748$977d7f7e6855 | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9748$977d7f7e6855 | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9748$b24d732710cd | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Salz | R. Salz | string | ||||
STD:IETF:RFC9748$b970c844a1e7 | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9748$cf454dc60717 | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9748 | https://www.rfc-editor.org/rfc/rfc9748 | url | ||||
STD:IETF:RFC9748$fc8ad5b3d1a8 | IETF | STD:IETF:RFC9748 | Updating the NTP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Network Time Protocol (NTP) and Network Time Security (NTS) documents define a number of registries, collectively called the NTP registries. Some registries are correct, but some include incorrect assignments and some don't follow common practice. For the sake of completeness, this document reviews all NTP and NTS... | The Network Time Protocol (NTP) and Network Time Security (NTS) documents define a number of registries, collectively called the NTP registries. Some registries are correct, but some include incorrect assignments and some don't follow common practice. For the sake of completeness, this document reviews all NTP and NTS... | monolingualtext | ||||
STD:IETF:RFC9749$13054e3f3db7 | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Gultsch | D. Gultsch | string | ||||
STD:IETF:RFC9749$3518a3fa37ed | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9749$73d9e9968c1c | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9749$92743b5abce7 | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9749 | https://www.rfc-editor.org/rfc/rfc9749 | url | ||||
STD:IETF:RFC9749$92dfd791f1cc | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9749$a11dfdc6adf8 | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | monolingualtext | ||||
STD:IETF:RFC9749$a268bba45688 | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9749$a268bba45688 | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9749$b7c9423abf23 | IETF | STD:IETF:RFC9749 | Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a method for JSON Meta Application Protocol (JMAP) servers to advertise their capability to authenticate Web Push notifications using the Voluntary Application Server Identification (VAPID) protocol. | This document defines a method for JSON Meta Application Protocol (JMAP) servers to advertise their capability to authenticate Web Push notifications using the Voluntary Application Server Identification (VAPID) protocol. | monolingualtext | ||||
STD:IETF:RFC9750$15fb1017cf71 | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9750$2434cf9efc24 | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9750$3176578b0f27 | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Messaging Layer Security (MLS) protocol (RFC 9420) provides a group key agreement protocol for messaging applications. MLS is designed to protect against eavesdropping, tampering, and message forgery, and to provide forward secrecy (FS) and post-compromise security (PCS). This document describes the architecture f... | The Messaging Layer Security (MLS) protocol (RFC 9420) provides a group key agreement protocol for messaging applications. MLS is designed to protect against eavesdropping, tampering, and message forgery, and to provide forward secrecy (FS) and post-compromise security (PCS). This document describes the architecture f... | monolingualtext | ||||
STD:IETF:RFC9750$7119042a9830 | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Duric | A. Duric | string | ||||
STD:IETF:RFC9750$72e126737bc6 | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9750 | https://www.rfc-editor.org/rfc/rfc9750 | url | ||||
STD:IETF:RFC9750$8a68d6dddafc | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9750$94e8ab63e503 | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9750$94e8ab63e503 | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9750$9d92d4f0d3e4 | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Inguva | S. Inguva | string | ||||
STD:IETF:RFC9750$a6e9cb228d6c | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | The Messaging Layer Security (MLS) Architecture | The Messaging Layer Security (MLS) Architecture | monolingualtext | ||||
STD:IETF:RFC9750$a9802ea0b5ac | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | B. Beurdouche | B. Beurdouche | string | ||||
STD:IETF:RFC9750$a988fb19fccd | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Rescorla | E. Rescorla | string | ||||
STD:IETF:RFC9750$db92b69ca64d | IETF | STD:IETF:RFC9750 | The Messaging Layer Security (MLS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Omara | E. Omara | string | ||||
STD:IETF:RFC9751$2d8c8345e2ac | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9751$48932ae2150a | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9751$5608397d88c1 | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The working group process and the authors of RTP payload formats have sometimes failed to ensure that the media types are registered in the IANA "RTP Payload Format Media Types" registry as recommended by RFC 8088. To simplify the process and rely only on the "Media Types" registry, this document closes the RTP payloa... | The working group process and the authors of RTP payload formats have sometimes failed to ensure that the media types are registered in the IANA "RTP Payload Format Media Types" registry as recommended by RFC 8088. To simplify the process and rely only on the "Media Types" registry, this document closes the RTP payloa... | monolingualtext | ||||
STD:IETF:RFC9751$581e427805ac | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9751 | https://www.rfc-editor.org/rfc/rfc9751 | url | ||||
STD:IETF:RFC9751$965e4ca05a40 | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Closing the RTP Payload Format Media Types Registry | Closing the RTP Payload Format Media Types Registry | monolingualtext | ||||
STD:IETF:RFC9751$9811a608a160 | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9751$9811a608a160 | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9751$b1b6b729316c | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Westerlund | M. Westerlund | string | ||||
STD:IETF:RFC9751$ecf6b2d5399c | IETF | STD:IETF:RFC9751 | Closing the RTP Payload Format Media Types Registry | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9752$1d2f64abdb6d | IETF | STD:IETF:RFC9752 | Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9752 | https://www.rfc-editor.org/rfc/rfc9752 | url | ||||
STD:IETF:RFC9752$363dba91119f | IETF | STD:IETF:RFC9752 | Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies extensions to the Path Computation Element
Communication Protocol (PCEP) that enable the inclusion of
vendor-specific information in stateful Path Computation Element
(PCE) operations. These extensions allow vendors to incorporate
proprietary data within PCEP messages, facilitating enhanced netw... | This document specifies extensions to the Path Computation Element
Communication Protocol (PCEP) that enable the inclusion of
vendor-specific information in stateful Path Computation Element
(PCE) operations. These extensions allow vendors to incorporate
proprietary data within PCEP messages, facilitating enhanced netw... | monolingualtext | ||||
STD:IETF:RFC9752$3ccd96ebad22 | IETF | STD:IETF:RFC9752 | Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Zheng | H. Zheng | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.