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:RFC9486$a3d78fc56291 | IETF | STD:IETF:RFC9486 | IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9486$e01a953e499e | IETF | STD:IETF:RFC9486 | IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Bhandari | S. Bhandari | string | ||||
STD:IETF:RFC9486$ef19abbc6e8c | IETF | STD:IETF:RFC9486 | IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Brockners | F. Brockners | string | ||||
STD:IETF:RFC9486$f40d940d424e | IETF | STD:IETF:RFC9486 | IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document outlines how IOAM Data-Fields are encapsulated in IPv6. | In situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document outlines how IOAM Data-Fields are encapsulated in IPv6. | monolingualtext | ||||
STD:IETF:RFC9487$08656696b19b | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9487$146b2f440fe6 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document introduces new IP Flow Information Export (IPFIX) Information Elements (IEs) to identify a set of information related to Segment Routing over IPv6 (SRv6) such as data contained in a Segment Routing Header (SRH), the SRv6 control plane, and the SRv6 Endpoint behavior that traffic is being forwarded with. | This document introduces new IP Flow Information Export (IPFIX) Information Elements (IEs) to identify a set of information related to Segment Routing over IPv6 (SRv6) such as data contained in a Segment Routing Header (SRH), the SRv6 control plane, and the SRv6 Endpoint behavior that traffic is being forwarded with. | monolingualtext | ||||
STD:IETF:RFC9487$23ea04879030 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9487$23ea04879030 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9487$2ac75e944b28 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9487 | https://www.rfc-editor.org/rfc/rfc9487 | url | ||||
STD:IETF:RFC9487$5ba5d48534e7 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Graf | T. Graf | string | ||||
STD:IETF:RFC9487$8e3724ac0741 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | monolingualtext | ||||
STD:IETF:RFC9487$9d4700465953 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9487$aeb4d28ac997 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Claise | B. Claise | string | ||||
STD:IETF:RFC9487$bd9c162b4b96 | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Francois | P. Francois | string | ||||
STD:IETF:RFC9487$d394f6edaabe | IETF | STD:IETF:RFC9487 | Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9488$03c051abb3ac | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9488$531a89bd4e66 | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sidor | S. Sidor | string | ||||
STD:IETF:RFC9488$7df8a8527d6e | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | monolingualtext | ||||
STD:IETF:RFC9488$915fb5c71f11 | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Stone | A. Stone | string | ||||
STD:IETF:RFC9488$9e826c1c5c25 | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9488$b06b0eff984e | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sivabalan | S. Sivabalan | string | ||||
STD:IETF:RFC9488$b34c425b4fa5 | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9488$b34c425b4fa5 | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9488$c9e96ec8fca7 | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates RFC 5440 to clarify usage of the Local Protection Desired bit signaled in the Path Computation Element Communication Protocol (PCEP). This document also introduces a new flag for signaling protection enforcement in PCEP. | This document updates RFC 5440 to clarify usage of the Local Protection Desired bit signaled in the Path Computation Element Communication Protocol (PCEP). This document also introduces a new flag for signaling protection enforcement in PCEP. | monolingualtext | ||||
STD:IETF:RFC9488$dc4cf38ab1e7 | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9488$ecf64bd1544d | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9488 | https://www.rfc-editor.org/rfc/rfc9488 | url | ||||
STD:IETF:RFC9488$f41f1de35db5 | IETF | STD:IETF:RFC9488 | Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Aissaoui | M. Aissaoui | string | ||||
STD:IETF:RFC9489$1d53a98d213e | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9489$4788707c3474 | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | monolingualtext | ||||
STD:IETF:RFC9489$55bc2044bb09 | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Salam | S. Salam | string | ||||
STD:IETF:RFC9489$6647e77df6d5 | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9489$6647e77df6d5 | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9489$737c78187214 | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9489$7b8ba90912ad | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9489 | https://www.rfc-editor.org/rfc/rfc9489 | url | ||||
STD:IETF:RFC9489$9afdfa2a3b6b | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Boutros | S. Boutros | string | ||||
STD:IETF:RFC9489$a1bc3a795bbe | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9489$bd309b5effae | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sajassi | A. Sajassi | string | ||||
STD:IETF:RFC9489$c35ddf02d286 | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Label Switched Path (LSP) Ping is a widely deployed Operations, Administration, and Maintenance (OAM) mechanism in MPLS networks. This document describes mechanisms for detecting data plane failures using LSP Ping in MPLS-based Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN) networks. | Label Switched Path (LSP) Ping is a widely deployed Operations, Administration, and Maintenance (OAM) mechanism in MPLS networks. This document describes mechanisms for detecting data plane failures using LSP Ping in MPLS-based Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN) networks. | monolingualtext | ||||
STD:IETF:RFC9489$ce9339311348 | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Jain | P. Jain | string | ||||
STD:IETF:RFC9489$e55b19b6aa05 | IETF | STD:IETF:RFC9489 | Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9490$30ba01dd4194 | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9490$320080961c36 | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The "Management Techniques in Encrypted Networks (M-TEN)" workshop was convened by the Internet Architecture Board (IAB) from 17 October 2022 to 19 October 2022 as a three-day online meeting. The workshop was organized in three parts to discuss ways to improve network management techniques in support of even broader ad... | The "Management Techniques in Encrypted Networks (M-TEN)" workshop was convened by the Internet Architecture Board (IAB) from 17 October 2022 to 19 October 2022 as a three-day online meeting. The workshop was organized in three parts to discuss ways to improve network management techniques in support of even broader ad... | monolingualtext | ||||
STD:IETF:RFC9490$35f0a5ae1799 | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Knodel | M. Knodel | string | ||||
STD:IETF:RFC9490$4b8c9a7af001 | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9490$526e490dfaaf | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9490$688a64147d84 | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9490$7ac0ba8eb80e | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9490$7ac0ba8eb80e | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9490$df884fef70a9 | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9490 | https://www.rfc-editor.org/rfc/rfc9490 | url | ||||
STD:IETF:RFC9490$f6d257f2e757 | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | monolingualtext | ||||
STD:IETF:RFC9490$fe5e3be08d8a | IETF | STD:IETF:RFC9490 | Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | W. Hardaker | W. Hardaker | string | ||||
STD:IETF:RFC9491$109e038e5792 | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Guichard | J. Guichard | string | ||||
STD:IETF:RFC9491$139ffd43d498 | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9491$51a9a383e610 | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9491$6182b757f374 | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9491 | https://www.rfc-editor.org/rfc/rfc9491 | url | ||||
STD:IETF:RFC9491$6d7d4d1fa6df | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9491$6d7d4d1fa6df | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9491$95e4793e9ba2 | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | monolingualtext | ||||
STD:IETF:RFC9491$bc28b95cee43 | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9491$c283854337b7 | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9491$e95f3bb62030 | IETF | STD:IETF:RFC9491 | Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the integration of the Network Service Header (NSH) and Segment Routing (SR), as well as encapsulation details, to efficiently support Service Function Chaining (SFC) while maintaining separation of the service and transport planes as originally intended by the SFC architecture. Combining these... | This document describes the integration of the Network Service Header (NSH) and Segment Routing (SR), as well as encapsulation details, to efficiently support Service Function Chaining (SFC) while maintaining separation of the service and transport planes as originally intended by the SFC architecture. Combining these... | monolingualtext | ||||
STD:IETF:RFC9492$3859644ca044 | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9492$5b98f91c6cca | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9492$5e42c69be98d | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Ginsberg | L. Ginsberg | string | ||||
STD:IETF:RFC9492$6befe1898a8b | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9492$77b3578f9ba7 | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications such as Segment Routing (SR) Policy and Loop-Free Alternates (LFAs) that also make use of the link attribute advertisements h... | Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications such as Segment Routing (SR) Policy and Loop-Free Alternates (LFAs) that also make use of the link attribute advertisements h... | monolingualtext | ||||
STD:IETF:RFC9492$7b59df4edde4 | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Psenak | P. Psenak | string | ||||
STD:IETF:RFC9492$7e65f1d4d806 | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | OSPF Application-Specific Link Attributes | OSPF Application-Specific Link Attributes | monolingualtext | ||||
STD:IETF:RFC9492$8dc1ad9c1dfc | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9492$99b9051d4888 | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9492$99b9051d4888 | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9492$bb88fadb2121 | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Henderickx | W. Henderickx | string | ||||
STD:IETF:RFC9492$e3305e1897cc | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9492 | https://www.rfc-editor.org/rfc/rfc9492 | url | ||||
STD:IETF:RFC9492$fe6deab3e0be | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Drake | J. Drake | string | ||||
STD:IETF:RFC9492$ff4690498119 | IETF | STD:IETF:RFC9492 | OSPF Application-Specific Link Attributes | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC8920 | RFC8920 | wikibase-item | ||||
STD:IETF:RFC9493$29000fee236c | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9493 | https://www.rfc-editor.org/rfc/rfc9493 | url | ||||
STD:IETF:RFC9493$4a6e8d33c52a | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Jain | P. Jain | string | ||||
STD:IETF:RFC9493$6b0633c0eb90 | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9493$80d0cd6c8294 | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9493$80d0cd6c8294 | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9493$87c2a2c288f8 | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Scurtescu | M. Scurtescu | string | ||||
STD:IETF:RFC9493$984b3ccb00ec | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9493$98cfc6231d87 | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Security events communicated within Security Event Tokens may support a variety of identifiers to identify subjects related to the event. This specification formalizes the notion of Subject Identifiers as structured information that describes a subject and named formats that define the syntax and semantics for encodin... | Security events communicated within Security Event Tokens may support a variety of identifiers to identify subjects related to the event. This specification formalizes the notion of Subject Identifiers as structured information that describes a subject and named formats that define the syntax and semantics for encodin... | monolingualtext | ||||
STD:IETF:RFC9493$a2f1b8ed1930 | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Backman | A. Backman | string | ||||
STD:IETF:RFC9493$cc4ce00817fc | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Subject Identifiers for Security Event Tokens | Subject Identifiers for Security Event Tokens | monolingualtext | ||||
STD:IETF:RFC9493$dd12e170d4b3 | IETF | STD:IETF:RFC9493 | Subject Identifiers for Security Event Tokens | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9494$2399e760d783 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Chen | E. Chen | string | ||||
STD:IETF:RFC9494$23bb111eebf4 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9494 | https://www.rfc-editor.org/rfc/rfc9494 | url | ||||
STD:IETF:RFC9494$24cb3560f426 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Decraene | B. Decraene | string | ||||
STD:IETF:RFC9494$2e1fd1389c6d | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9494$3ed9a341180b | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Scudder | J. Scudder | string | ||||
STD:IETF:RFC9494$42be7668ec46 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document introduces a BGP capability called the "Long-Lived Graceful Restart Capability" (or "LLGR Capability"). The benefit of this capability is that stale routes can be retained for a longer time upon session failure than is provided for by BGP Graceful Restart (as described in RFC 4724). A well-known BGP commu... | This document introduces a BGP capability called the "Long-Lived Graceful Restart Capability" (or "LLGR Capability"). The benefit of this capability is that stale routes can be retained for a longer time upon session failure than is provided for by BGP Graceful Restart (as described in RFC 4724). A well-known BGP commu... | monolingualtext | ||||
STD:IETF:RFC9494$73fdf00f38e9 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Long-Lived Graceful Restart for BGP | Long-Lived Graceful Restart for BGP | monolingualtext | ||||
STD:IETF:RFC9494$8075afbaeb49 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9494$8075afbaeb49 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9494$91a2b1d3cd69 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9494$f1ee9efa25b3 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9494$f233f8243873 | IETF | STD:IETF:RFC9494 | Long-Lived Graceful Restart for BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Uttaro | J. Uttaro | string | ||||
STD:IETF:RFC9495$0f4da07eb8bf | IETF | STD:IETF:RFC9495 | Certification Authority Authorization (CAA) Processing for Email Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Bonnell | C. Bonnell | string | ||||
STD:IETF:RFC9495$1919fdc351d6 | IETF | STD:IETF:RFC9495 | Certification Authority Authorization (CAA) Processing for Email Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.