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:RFC9856$32acc830dec0 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sathappan | S. Sathappan | string | ||||
STD:IETF:RFC9856$6ce4b7429748 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9856$8cea727332f7 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Kotalwar | J. Kotalwar | string | ||||
STD:IETF:RFC9856$a423743c547e | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Multicast Source Redundancy in EVPNs | Multicast Source Redundancy in EVPNs | monolingualtext | ||||
STD:IETF:RFC9856$b6d782ca6992 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9856$bf2021f4d7c6 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In Ethernet Virtual Private Networks (EVPNs), IP multicast traffic replication and delivery play a crucial role in enabling efficient and scalable Layer 2 and Layer 3 services. A common deployment scenario involves redundant multicast sources that ensure high availability and resiliency. However, the presence of redu... | In Ethernet Virtual Private Networks (EVPNs), IP multicast traffic replication and delivery play a crucial role in enabling efficient and scalable Layer 2 and Layer 3 services. A common deployment scenario involves redundant multicast sources that ensure high availability and resiliency. However, the presence of redu... | monolingualtext | ||||
STD:IETF:RFC9856$d453acc42004 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9856$d453acc42004 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9856$f9f10db57465 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9856$fa1a647e9595 | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9856 | https://www.rfc-editor.org/rfc/rfc9856 | url | ||||
STD:IETF:RFC9857$185a0dfae8d7 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Previdi | S. Previdi | string | ||||
STD:IETF:RFC9857$235bc596cf6b | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9857$2c2611fc1fac | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Gredler | H. Gredler | string | ||||
STD:IETF:RFC9857$5cf8bb915b1a | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9857$6c7334fd7b47 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9857$6c7334fd7b47 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9857$6fa09ad9d115 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9857$7bf9ce743520 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9857$a767e2aaecf9 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Advertisement of Segment Routing Policies Using BGP - Link State | Advertisement of Segment Routing Policies Using BGP - Link State | monolingualtext | ||||
STD:IETF:RFC9857$ba3eb2edd6b4 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9857$bb6b89bccd7b | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a mechanism used to collect Segment Routing (SR) Policy information that is locally available in a node and advertise it into BGP - Link State (BGP-LS) updates. Such information can be used by external components for path computation, reoptimization, service placement, network visualization, et... | This document describes a mechanism used to collect Segment Routing (SR) Policy information that is locally available in a node and advertise it into BGP - Link State (BGP-LS) updates. Such information can be used by external components for path computation, reoptimization, service placement, network visualization, et... | monolingualtext | ||||
STD:IETF:RFC9857$d45292f00002 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Dong | J. Dong | string | ||||
STD:IETF:RFC9857$e63edd3afe75 | IETF | STD:IETF:RFC9857 | Advertisement of Segment Routing Policies Using BGP - Link State | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9857 | https://www.rfc-editor.org/rfc/rfc9857 | url | ||||
STD:IETF:RFC9858$15cf11fac7c4 | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9858$29445dd6f466 | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9858 | https://www.rfc-editor.org/rfc/rfc9858 | url | ||||
STD:IETF:RFC9858$6cf37c9d46ce | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9858$9be140ad5bc3 | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9858$9be140ad5bc3 | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9858$aad4fe865560 | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | monolingualtext | ||||
STD:IETF:RFC9858$c1e319748bf8 | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document extends HSS/LMS (RFC 8554) by defining parameter sets that use alternative hash functions. These include hash functions that result in signatures with significantly smaller sizes than the signatures that use the RFC 8554 parameter sets and should have sufficient security. This document is a product of th... | This document extends HSS/LMS (RFC 8554) by defining parameter sets that use alternative hash functions. These include hash functions that result in signatures with significantly smaller sizes than the signatures that use the RFC 8554 parameter sets and should have sufficient security. This document is a product of th... | monolingualtext | ||||
STD:IETF:RFC9858$d2c4c99e8b0b | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9858$e4a937fbe206 | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Q. Dang | Q. Dang | string | ||||
STD:IETF:RFC9858$ec674133f5a5 | IETF | STD:IETF:RFC9858 | Additional Parameter Sets for HSS/LMS Hash-Based Signatures | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Fluhrer | S. Fluhrer | string | ||||
STD:IETF:RFC9859$0b14dc9984c6 | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Thomassen | P. Thomassen | string | ||||
STD:IETF:RFC9859$168a576a47b7 | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9859$1c0a27bb8cbb | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9859 | https://www.rfc-editor.org/rfc/rfc9859 | url | ||||
STD:IETF:RFC9859$218862f59e9c | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Levine | J. Levine | string | ||||
STD:IETF:RFC9859$29e713dcef4c | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document generalizes and extends the use of DNS NOTIFY (RFC 1996) beyond conventional zone transfer hints to allow other types of actions that were previously lacking a trigger mechanism to be triggered via the DNS. Notifications merely nudge the receiver to initiate a predefined action promptly (instead of on a s... | This document generalizes and extends the use of DNS NOTIFY (RFC 1996) beyond conventional zone transfer hints to allow other types of actions that were previously lacking a trigger mechanism to be triggered via the DNS. Notifications merely nudge the receiver to initiate a predefined action promptly (instead of on a s... | monolingualtext | ||||
STD:IETF:RFC9859$51df5df083d1 | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9859$577a6b370c60 | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9859$73e68c11478b | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Generalized DNS Notifications | Generalized DNS Notifications | monolingualtext | ||||
STD:IETF:RFC9859$76f5e8e692ad | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9859$76f5e8e692ad | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9859$7e3cffc7e9f3 | IETF | STD:IETF:RFC9859 | Generalized DNS Notifications | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Stenstam | J. Stenstam | string | ||||
STD:IETF:RFC9860$00f3a77bb699 | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9860$00f3a77bb699 | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9860$03b5cc9396e2 | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9860$23929873663f | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9860$35f2752e6dbb | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9860 | https://www.rfc-editor.org/rfc/rfc9860 | url | ||||
STD:IETF:RFC9860$3d12f003bf6e | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. McBride | M. McBride | string | ||||
STD:IETF:RFC9860$5d0cd902a75e | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. Lin | C. Lin | string | ||||
STD:IETF:RFC9860$7198acd64f15 | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Xie | J. Xie | string | ||||
STD:IETF:RFC9860$8cba7661e763 | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9860$9a8d76295101 | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | monolingualtext | ||||
STD:IETF:RFC9860$a1dc1ea9151a | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Y. Liu | Y. Liu | string | ||||
STD:IETF:RFC9860$b0dca99a2335 | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies the use of Topology Independent Loop-Free Alternate (TI-LFA) mechanisms with Multicast-only Fast Reroute (MoFRR) for Protocol Independent Multicast (PIM). The TI-LFA provides Fast Reroute (FRR) protection for unicast traffic in IP networks by precomputing backup paths that avoid potential failu... | This document specifies the use of Topology Independent Loop-Free Alternate (TI-LFA) mechanisms with Multicast-only Fast Reroute (MoFRR) for Protocol Independent Multicast (PIM). The TI-LFA provides Fast Reroute (FRR) protection for unicast traffic in IP networks by precomputing backup paths that avoid potential failu... | monolingualtext | ||||
STD:IETF:RFC9860$bb9ebc321619 | IETF | STD:IETF:RFC9860 | Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9861$228cf8bb650e | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Q. Dang | Q. Dang | string | ||||
STD:IETF:RFC9861$252fe8affb5e | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Wong | D. Wong | string | ||||
STD:IETF:RFC9861$3901f8293241 | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9861$3ca4b582a597 | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9861$5033713e7592 | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines four eXtendable-Output Functions (XOFs), hash functions with output of arbitrary length, named TurboSHAKE128, TurboSHAKE256, KT128, and KT256. All four functions provide efficient and secure hashing primitives, and the last two are able to exploit the parallelism of the implementation in a scalab... | This document defines four eXtendable-Output Functions (XOFs), hash functions with output of arbitrary length, named TurboSHAKE128, TurboSHAKE256, KT128, and KT256. All four functions provide efficient and secure hashing primitives, and the last two are able to exploit the parallelism of the implementation in a scalab... | monolingualtext | ||||
STD:IETF:RFC9861$735edad462b8 | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | B. Viguier | B. Viguier | string | ||||
STD:IETF:RFC9861$8cdbe5f472dd | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9861$a446d102626f | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | KangarooTwelve and TurboSHAKE | KangarooTwelve and TurboSHAKE | monolingualtext | ||||
STD:IETF:RFC9861$aa55131b628b | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. Van Assche | G. Van Assche | string | ||||
STD:IETF:RFC9861$cdd8c2a91d84 | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9861 | https://www.rfc-editor.org/rfc/rfc9861 | url | ||||
STD:IETF:RFC9861$d4034eb3b77d | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Daemen | J. Daemen | string | ||||
STD:IETF:RFC9861$e60c4afe148c | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9861$e60c4afe148c | IETF | STD:IETF:RFC9861 | KangarooTwelve and TurboSHAKE | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9862$181f484dc241 | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9862$4270db7699af | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Koldychev | M. Koldychev | string | ||||
STD:IETF:RFC9862$5781cd7e8a2a | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Bidgoli | H. Bidgoli | string | ||||
STD:IETF:RFC9862$7e77f7bbc5be | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9862$7e77f7bbc5be | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9862$84195d824854 | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9862$918489f0b0f8 | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9862 | https://www.rfc-editor.org/rfc/rfc9862 | url | ||||
STD:IETF:RFC9862$99c2de7e8ccb | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9862$e48313080c3d | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | A Segment Routing (SR) Policy is an ordered list of instructions called "segments" that represent a source-routed policy. Packet flows are steered into an SR Policy on a node where it is instantiated. An SR Policy is made of one or more Candidate Paths. This document specifies the Path Computation Element Communicatio... | A Segment Routing (SR) Policy is an ordered list of instructions called "segments" that represent a source-routed policy. Packet flows are steered into an SR Policy on a node where it is instantiated. An SR Policy is made of one or more Candidate Paths. This document specifies the Path Computation Element Communicatio... | monolingualtext | ||||
STD:IETF:RFC9862$e7d9e9ded149 | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sivabalan | S. Sivabalan | string | ||||
STD:IETF:RFC9862$eb85b8758e5f | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Barth | C. Barth | string | ||||
STD:IETF:RFC9862$ee8c73e14f06 | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sidor | S. Sidor | string | ||||
STD:IETF:RFC9862$ef136e9a58fe | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | monolingualtext | ||||
STD:IETF:RFC9862$fdc94771400a | IETF | STD:IETF:RFC9862 | Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Peng | S. Peng | string | ||||
STD:IETF:RFC9863$0279d2efe430 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9863$0411ae2bcf80 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Rajagopalan | B. Rajagopalan | string | ||||
STD:IETF:RFC9863$13d8f0f4dc71 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9863$13d8f0f4dc71 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9863$2aa3f67e271e | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Path Computation Element Protocol (PCEP) Extension for Color | Path Computation Element Protocol (PCEP) Extension for Color | monolingualtext | ||||
STD:IETF:RFC9863$63647584a0d9 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Koldychev | M. Koldychev | string | ||||
STD:IETF:RFC9863$671438bd3f06 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9863 | https://www.rfc-editor.org/rfc/rfc9863 | url | ||||
STD:IETF:RFC9863$72be242b3c0f | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9863$a2dad0f0bde2 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | V. Beeram | V. Beeram | string | ||||
STD:IETF:RFC9863$ba8716a6ef33 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mishra | G. Mishra | string | ||||
STD:IETF:RFC9863$bf96c3ac8694 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Color is a 32-bit numerical (unsigned integer) attribute used to associate a Traffic Engineering (TE) tunnel or policy with an intent or objective. For example, a TE Tunnel constructed to deliver low latency services and whose path is optimized for delay can be tagged with a color that represents "low latency." This d... | Color is a 32-bit numerical (unsigned integer) attribute used to associate a Traffic Engineering (TE) tunnel or policy with an intent or objective. For example, a TE Tunnel constructed to deliver low latency services and whose path is optimized for delay can be tagged with a color that represents "low latency." This d... | monolingualtext | ||||
STD:IETF:RFC9863$df1065ee2295 | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9863$f77dfaeeea2f | IETF | STD:IETF:RFC9863 | Path Computation Element Protocol (PCEP) Extension for Color | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Peng | S. Peng | string | ||||
STD:IETF:RFC9864$14cb4f6dcb74 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9864$1ade28816dbb | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M.B. Jones | M.B. Jones | string | ||||
STD:IETF:RFC9864$2a39866fb056 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.