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:RFC9564$4e183ad4293d | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Faster Than Light Speed Protocol (FLIP) | Faster Than Light Speed Protocol (FLIP) | monolingualtext | ||||
STD:IETF:RFC9564$8c5c6d68f6e5 | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Blanchet | M. Blanchet | string | ||||
STD:IETF:RFC9564$b0e122400cd5 | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9564 | https://www.rfc-editor.org/rfc/rfc9564 | url | ||||
STD:IETF:RFC9564$b965116e3ca8 | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9564$b965116e3ca8 | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9564$d99b7f4dfb65 | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9565$1fbedc1b9fc6 | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Boucadair | M. Boucadair | string | ||||
STD:IETF:RFC9565$2f610a7b1d4b | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9565 | https://www.rfc-editor.org/rfc/rfc9565 | url | ||||
STD:IETF:RFC9565$4c4105e37219 | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 7125 revised the tcpControlBits IP Flow Information Export (IPFIX) Information Element that was originally defined in RFC 5102 to reflect changes to the TCP header control bits since RFC 793. However, that update is still problematic for interoperability because some flag values have subsequently been deprecated. ... | RFC 7125 revised the tcpControlBits IP Flow Information Export (IPFIX) Information Element that was originally defined in RFC 5102 to reflect changes to the TCP header control bits since RFC 793. However, that update is still problematic for interoperability because some flag values have subsequently been deprecated. ... | monolingualtext | ||||
STD:IETF:RFC9565$5a06a3c70fd9 | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9565$62199a98d8a9 | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC7125 | RFC7125 | wikibase-item | ||||
STD:IETF:RFC9565$b4dbd85fd7a1 | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | monolingualtext | ||||
STD:IETF:RFC9565$d1377851afa6 | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9565$e6f9b01217ee | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9565$e6f9b01217ee | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9565$e9b93aa3cc2c | IETF | STD:IETF:RFC9565 | An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9566$035dbf6d448d | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9566$035dbf6d448d | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9566$079001056519 | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes how the DetNet IP data plane can support the Packet Replication, Elimination, and Ordering Functions (PREOF) built on the existing MPLS PREOF solution defined for the DetNet MPLS data plane and the mechanisms defined by MPLS-over-UDP technology. | This document describes how the DetNet IP data plane can support the Packet Replication, Elimination, and Ordering Functions (PREOF) built on the existing MPLS PREOF solution defined for the DetNet MPLS data plane and the mechanisms defined by MPLS-over-UDP technology. | monolingualtext | ||||
STD:IETF:RFC9566$2c256ba7c188 | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9566 | https://www.rfc-editor.org/rfc/rfc9566 | url | ||||
STD:IETF:RFC9566$3818217f6866 | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Farkas | J. Farkas | string | ||||
STD:IETF:RFC9566$6dca42081a5c | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9566$8ec259b1a01e | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Malis | A. Malis | string | ||||
STD:IETF:RFC9566$a112e7cdc011 | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9566$e3d74816bf47 | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | B. Varga | B. Varga | string | ||||
STD:IETF:RFC9566$e9f021e0f44d | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | monolingualtext | ||||
STD:IETF:RFC9566$f8bf787047c6 | IETF | STD:IETF:RFC9566 | Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9567$45e32be69757 | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9567$720610c13f34 | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | DNS Error Reporting | DNS Error Reporting | monolingualtext | ||||
STD:IETF:RFC9567$8479e61ba1b1 | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Arends | R. Arends | string | ||||
STD:IETF:RFC9567$8edf242f9e72 | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9567$af167d427d4a | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | DNS error reporting is a lightweight reporting mechanism that provides the operator of an authoritative server with reports on DNS resource records that fail to resolve or validate. A domain owner or DNS hosting organization can use these reports to improve domain hosting. The reports are based on extended DNS errors a... | DNS error reporting is a lightweight reporting mechanism that provides the operator of an authoritative server with reports on DNS resource records that fail to resolve or validate. A domain owner or DNS hosting organization can use these reports to improve domain hosting. The reports are based on extended DNS errors a... | monolingualtext | ||||
STD:IETF:RFC9567$b0d69a36852a | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9567$b0d69a36852a | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9567$cfd3d89ed4f0 | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9567 | https://www.rfc-editor.org/rfc/rfc9567 | url | ||||
STD:IETF:RFC9567$de2c41c4d57c | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Larson | M. Larson | string | ||||
STD:IETF:RFC9567$f2a25d2c8f6a | IETF | STD:IETF:RFC9567 | DNS Error Reporting | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9568$16899990e9db | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9568$51adef0221c9 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Dogra | A. Dogra | string | ||||
STD:IETF:RFC9568$6eb7202cbd56 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | monolingualtext | ||||
STD:IETF:RFC9568$a21c69efd391 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9568$a9e0103f6441 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9568$d3c058c71120 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC5798 | RFC5798 | wikibase-item | ||||
STD:IETF:RFC9568$d7764b16b9cc | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Lindem | A. Lindem | string | ||||
STD:IETF:RFC9568$e2e207ed87f9 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9568 | https://www.rfc-editor.org/rfc/rfc9568 | url | ||||
STD:IETF:RFC9568$e78799f92383 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines version 3 of the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It obsoletes RFC 5798, which previously specified VRRP (version 3). RFC 5798 obsoleted RFC 3768, which specified VRRP (version 2) for IPv4. VRRP specifies an election protocol that dynamically assigns responsibility f... | This document defines version 3 of the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It obsoletes RFC 5798, which previously specified VRRP (version 3). RFC 5798 obsoleted RFC 3768, which specified VRRP (version 2) for IPv4. VRRP specifies an election protocol that dynamically assigns responsibility f... | monolingualtext | ||||
STD:IETF:RFC9568$e9dcf55f3691 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9568$e9dcf55f3691 | IETF | STD:IETF:RFC9568 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9569$0af7c55a4e65 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | "Application-Layer Traffic Optimization (ALTO) Protocol" (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource, one at a time. RFC 8895, whi... | "Application-Layer Traffic Optimization (ALTO) Protocol" (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource, one at a time. RFC 8895, whi... | monolingualtext | ||||
STD:IETF:RFC9569$0ec1bc294300 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9569 | https://www.rfc-editor.org/rfc/rfc9569 | url | ||||
STD:IETF:RFC9569$36b85b0cc7c5 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Gao | K. Gao | string | ||||
STD:IETF:RFC9569$77e2bfed7af7 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9569$77e2bfed7af7 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9569$a46593883721 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Keller | L. Keller | string | ||||
STD:IETF:RFC9569$c0b091ca950f | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Schott | R. Schott | string | ||||
STD:IETF:RFC9569$e87cc8577a11 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9569$ea48ab5fa7d7 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. R. Yang | Y. R. Yang | string | ||||
STD:IETF:RFC9569$f19dc92943c5 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | monolingualtext | ||||
STD:IETF:RFC9569$f4d814a3aa2e | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9569$f7c9cb4c3f6c | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9569$fa629878fd23 | IETF | STD:IETF:RFC9569 | The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Delwiche | L. Delwiche | string | ||||
STD:IETF:RFC9570$089b49bca2ec | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The MPLS echo request and MPLS echo response messages, defined in RFC 8029, "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures" (usually referred to as LSP ping), are encapsulated in IP packets with headers that include a Router Alert Option (RAO). In actual deployments, the RAO was neither required nor... | The MPLS echo request and MPLS echo response messages, defined in RFC 8029, "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures" (usually referred to as LSP ping), are encapsulated in IP packets with headers that include a Router Alert Option (RAO). In actual deployments, the RAO was neither required nor... | monolingualtext | ||||
STD:IETF:RFC9570$279065e0350d | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9570$2bff58acd56e | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9570$38f3d4ef206d | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Kompella | K. Kompella | string | ||||
STD:IETF:RFC9570$3c9db99d74a3 | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Deprecating the Use of Router Alert in LSP Ping | Deprecating the Use of Router Alert in LSP Ping | monolingualtext | ||||
STD:IETF:RFC9570$7e6b5703c8be | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9570$9cbf68b1a16c | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9570$9cbf68b1a16c | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9570$a89330f89395 | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Bonica | R. Bonica | string | ||||
STD:IETF:RFC9570$aa2d261e8f79 | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9570$b0f3df46aabf | IETF | STD:IETF:RFC9570 | Deprecating the Use of Router Alert in LSP Ping | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9570 | https://www.rfc-editor.org/rfc/rfc9570 | url | ||||
STD:IETF:RFC9571$02d915ed27c3 | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9571$03c2a4ad51ef | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9571 | https://www.rfc-editor.org/rfc/rfc9571 | url | ||||
STD:IETF:RFC9571$2a1d3e77b81c | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 6374 describes methods of making loss and delay measurements on Label Switched Paths (LSPs) primarily as they are used in MPLS Transport Profile (MPLS-TP) networks. This document describes a method of extending the performance measurements (specified in RFC 6374) from flows carried over MPLS-TP to flows carried ov... | RFC 6374 describes methods of making loss and delay measurements on Label Switched Paths (LSPs) primarily as they are used in MPLS Transport Profile (MPLS-TP) networks. This document describes a method of extending the performance measurements (specified in RFC 6374) from flows carried over MPLS-TP to flows carried ov... | monolingualtext | ||||
STD:IETF:RFC9571$40d827aa9fbb | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9571$40d827aa9fbb | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9571$5e5641390bb1 | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | monolingualtext | ||||
STD:IETF:RFC9571$63f068d0165a | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9571$6a1ac4b54710 | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Bryant | S. Bryant | string | ||||
STD:IETF:RFC9571$911e0493852a | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9571$9db82a098e23 | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9571$b639c7965189 | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Chen | M. Chen | string | ||||
STD:IETF:RFC9571$cf6dc14778a0 | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Swallow | G. Swallow | string | ||||
STD:IETF:RFC9571$e75537bfceb4 | IETF | STD:IETF:RFC9571 | Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Fioccola | G. Fioccola | string | ||||
STD:IETF:RFC9572$06452df29095 | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies updated procedures for handling Broadcast, Unknown Unicast, or Multicast (BUM) traffic in Ethernet VPNs (EVPNs), including selective multicast and segmentation of provider tunnels. This document updates RFC 7432. | This document specifies updated procedures for handling Broadcast, Unknown Unicast, or Multicast (BUM) traffic in Ethernet VPNs (EVPNs), including selective multicast and segmentation of provider tunnels. This document updates RFC 7432. | monolingualtext | ||||
STD:IETF:RFC9572$1edc5c8334e6 | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9572$46c03eb99f8b | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | monolingualtext | ||||
STD:IETF:RFC9572$9d2e8e035557 | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9572$aa02d62c846c | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9572$aa02d62c846c | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9572$ae9c6302e01e | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9572$bbef62f19412 | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sajassi | A. Sajassi | string | ||||
STD:IETF:RFC9572$c97c5672740c | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Lin | W. Lin | string | ||||
STD:IETF:RFC9572$ca4aea71286b | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Patel | K. Patel | string | ||||
STD:IETF:RFC9572$dc04d3060177 | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9572$dc626fb0c5ce | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9572 | https://www.rfc-editor.org/rfc/rfc9572 | url | ||||
STD:IETF:RFC9572$f6be41394e12 | IETF | STD:IETF:RFC9572 | Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9573$02740b90aa4f | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | IJ. Wijnands | IJ. Wijnands | string | ||||
STD:IETF:RFC9573$03572c8dcdff | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9573 | https://www.rfc-editor.org/rfc/rfc9573 | url |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.