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:RFC9815$4ce85fdd847f | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Zandi | S. Zandi | string | ||||
STD:IETF:RFC9815$4dce263ea39a | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9815$62ad1870fec1 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Many Massively Scaled Data Centers (MSDCs) have converged on simplified Layer 3 (L3) routing. Furthermore, requirements for operational simplicity have led many of these MSDCs to converge on BGP as their single routing protocol for both fabric routing and Data Center Interconnect (DCI) routing. This document describe... | Many Massively Scaled Data Centers (MSDCs) have converged on simplified Layer 3 (L3) routing. Furthermore, requirements for operational simplicity have led many of these MSDCs to converge on BGP as their single routing protocol for both fabric routing and Data Center Interconnect (DCI) routing. This document describe... | monolingualtext | ||||
STD:IETF:RFC9815$7a844589a3d4 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Henderickx | W. Henderickx | string | ||||
STD:IETF:RFC9815$822328ddcee6 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9815$822328ddcee6 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9815$b0e6e93f1577 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9815$b38b4e000311 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9815 | https://www.rfc-editor.org/rfc/rfc9815 | url | ||||
STD:IETF:RFC9815$c1aa12c1cfb2 | IETF | STD:IETF:RFC9815 | BGP Link State (BGP-LS) Shortest Path First (SPF) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Lindem | A. Lindem | string | ||||
STD:IETF:RFC9816$09bbdb9c43ad | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9816$09bbdb9c43ad | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9816$1d860f125db7 | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9816$3cd3b4153b5b | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | monolingualtext | ||||
STD:IETF:RFC9816$5133a7770b44 | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. Dawra | G. Dawra | string | ||||
STD:IETF:RFC9816$61a51b8a90b5 | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Zandi | S. Zandi | string | ||||
STD:IETF:RFC9816$6209837670cd | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document discusses the usage and applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) extensions in data center networks utilizing Clos or Fat Tree topologies. The document is intended to provide simplified guidance for the deployment of BGP-LS SPF extensions. | This document discusses the usage and applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) extensions in data center networks utilizing Clos or Fat Tree topologies. The document is intended to provide simplified guidance for the deployment of BGP-LS SPF extensions. | monolingualtext | ||||
STD:IETF:RFC9816$666bbe54d4ff | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9816$788ec13611c4 | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Dong | J. Dong | string | ||||
STD:IETF:RFC9816$7dbba5758bcb | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Lindem | A. Lindem | string | ||||
STD:IETF:RFC9816$c214dfc3488a | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9816$cc0853100f90 | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | K. Patel | K. Patel | string | ||||
STD:IETF:RFC9816$cd75eecdd0d3 | IETF | STD:IETF:RFC9816 | Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data Centers | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9816 | https://www.rfc-editor.org/rfc/rfc9816 | url | ||||
STD:IETF:RFC9817$0b8f41d2569f | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Rio | M. Rio | string | ||||
STD:IETF:RFC9817$2cc383c90707 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9817$391b40ecc6d7 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | K. Wehrle | K. Wehrle | string | ||||
STD:IETF:RFC9817$6762b7ea989d | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Computing in the Network (COIN) comes with the prospect of deploying processing functionality on networking devices such as switches and network interface cards. While such functionality can be beneficial, it has to be carefully placed into the context of the general Internet communication, and it needs to be clearly i... | Computing in the Network (COIN) comes with the prospect of deploying processing functionality on networking devices such as switches and network interface cards. While such functionality can be beneficial, it has to be carefully placed into the context of the general Internet communication, and it needs to be clearly i... | monolingualtext | ||||
STD:IETF:RFC9817$827b10dcdcac | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9817$9460461d4891 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M-J. Montpetit | M-J. Montpetit | string | ||||
STD:IETF:RFC9817$958447c245fc | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | I. Kunze | I. Kunze | string | ||||
STD:IETF:RFC9817$a2c3f4510065 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9817 | https://www.rfc-editor.org/rfc/rfc9817 | url | ||||
STD:IETF:RFC9817$ada2c8c63ba5 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Use Cases for In-Network Computing | Use Cases for In-Network Computing | monolingualtext | ||||
STD:IETF:RFC9817$c0dcca683d50 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | X. de Foy | X. de Foy | string | ||||
STD:IETF:RFC9817$d243935dce13 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9817$dbd0ea202292 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Trossen | D. Trossen | string | ||||
STD:IETF:RFC9817$f21dc47bd115 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Griffin | D. Griffin | string | ||||
STD:IETF:RFC9817$f955217ff7e5 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9817$f955217ff7e5 | IETF | STD:IETF:RFC9817 | Use Cases for In-Network Computing | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9818$3249c5b50c31 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9818$3249c5b50c31 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9818$592a4adb2802 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9818 | https://www.rfc-editor.org/rfc/rfc9818 | url | ||||
STD:IETF:RFC9818$928e0f3a85b1 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9818$b4a762307080 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9818$bb1510958d24 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines requirements for IPv6 Customer Edge (CE) routers to support DHCPv6 Prefix Delegation for distributing available prefixes to LAN devices that were delegated to an IPv6 CE router. This document updates RFC 7084. | This document defines requirements for IPv6 Customer Edge (CE) routers to support DHCPv6 Prefix Delegation for distributing available prefixes to LAN devices that were delegated to an IPv6 CE router. This document updates RFC 7084. | monolingualtext | ||||
STD:IETF:RFC9818$e56c3eca7320 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | monolingualtext | ||||
STD:IETF:RFC9818$f1f352b17213 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Winters | T. Winters | string | ||||
STD:IETF:RFC9818$fe9d89cada94 | IETF | STD:IETF:RFC9818 | DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9819$100cd1cf57ec | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9819$100cd1cf57ec | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9819$2843d34e4177 | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 9252 defines procedures and messages for BGP overlay services for Segment Routing over IPv6 (SRv6), including Layer 3 Virtual Private Network (L3VPN), Ethernet VPN (EVPN), and global Internet routing. This document updates RFC 9252 and provides more detailed specifications for the signaling and processing of SRv6 ... | RFC 9252 defines procedures and messages for BGP overlay services for Segment Routing over IPv6 (SRv6), including Layer 3 Virtual Private Network (L3VPN), Ethernet VPN (EVPN), and global Internet routing. This document updates RFC 9252 and provides more detailed specifications for the signaling and processing of SRv6 ... | monolingualtext | ||||
STD:IETF:RFC9819$3d4cb4111d8d | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9819$3fb37a851e5d | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9819$4c4fa62403e7 | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Raza | K. Raza | string | ||||
STD:IETF:RFC9819$5f68cfb2c7ad | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9819 | https://www.rfc-editor.org/rfc/rfc9819 | url | ||||
STD:IETF:RFC9819$69da7c9ec7cc | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9819$c22863d854c1 | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Lin | W. Lin | string | ||||
STD:IETF:RFC9819$d182e0113e66 | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9819$d3498eab1310 | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9819$fb8998e10805 | IETF | STD:IETF:RFC9819 | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6) | monolingualtext | ||||
STD:IETF:RFC9820$12d84f596cdc | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Garcia-Carrillo | D. Garcia-Carrillo | string | ||||
STD:IETF:RFC9820$4138a0c38707 | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies an authentication service that uses the Constrained Application Protocol (CoAP) as a transport method to carry the Extensible Authentication Protocol (EAP). As such, it defines an EAP lower layer based on CoAP called "CoAP-EAP". One of the main goals is to authenticate a CoAP-enabled Internet ... | This document specifies an authentication service that uses the Constrained Application Protocol (CoAP) as a transport method to carry the Extensible Authentication Protocol (EAP). As such, it defines an EAP lower layer based on CoAP called "CoAP-EAP". One of the main goals is to authenticate a CoAP-enabled Internet ... | monolingualtext | ||||
STD:IETF:RFC9820$45948b39fcca | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9820$45948b39fcca | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9820$45eeceb6e863 | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9820$4b0407e1f48f | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9820$71c5a2bae549 | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | monolingualtext | ||||
STD:IETF:RFC9820$9ea81ff6ff31 | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9820 | https://www.rfc-editor.org/rfc/rfc9820 | url | ||||
STD:IETF:RFC9820$ad82b6dfb122 | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Marin-Lopez | R. Marin-Lopez | string | ||||
STD:IETF:RFC9820$d78c41bcfaf8 | IETF | STD:IETF:RFC9820 | Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9824$102726338f86 | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Huque | S. Huque | string | ||||
STD:IETF:RFC9824$1ccc610f1989 | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9824$3b3cb27e72b6 | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Compact Denial of Existence in DNSSEC | Compact Denial of Existence in DNSSEC | monolingualtext | ||||
STD:IETF:RFC9824$75208f8293c7 | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9824 | https://www.rfc-editor.org/rfc/rfc9824 | url | ||||
STD:IETF:RFC9824$783018e9b72c | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9824$783018e9b72c | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9824$8a22e4f7d63d | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9824$8d3d45d7e981 | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Elmerot | C. Elmerot | string | ||||
STD:IETF:RFC9824$abf7268744ac | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | O. Gudmundsson | O. Gudmundsson | string | ||||
STD:IETF:RFC9824$b5f9158ba89a | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a technique to generate a signed DNS response on demand for a nonexistent name by claiming that the name exists but doesn't have any data for the queried record type. Such responses require only one minimally covering NSEC or NSEC3 record, allow online signing servers to minimize signing operati... | This document describes a technique to generate a signed DNS response on demand for a nonexistent name by claiming that the name exists but doesn't have any data for the queried record type. Such responses require only one minimally covering NSEC or NSEC3 record, allow online signing servers to minimize signing operati... | monolingualtext | ||||
STD:IETF:RFC9824$bacca8f3e672 | IETF | STD:IETF:RFC9824 | Compact Denial of Existence in DNSSEC | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9825$15be13c29271 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Extensions to OSPF for Advertising Prefix Administrative Tags | Extensions to OSPF for Advertising Prefix Administrative Tags | monolingualtext | ||||
STD:IETF:RFC9825$320004e403a1 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9825$32a5029b3423 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9825$5edb59001695 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9825$75782218b58e | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Lindem | A. Lindem | string | ||||
STD:IETF:RFC9825$8d2596f33ad0 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | It is useful for routers in OSPFv2 and OSPFv3 routing domains to be able to associate tags with prefixes. Previously, OSPFv2 and OSPFv3 were relegated to a single tag and only for Autonomous System (AS) External and Not-So-Stubby-Area (NSSA) prefixes. With the flexible encodings provided by OSPFv2 Prefix/Link Attribu... | It is useful for routers in OSPFv2 and OSPFv3 routing domains to be able to associate tags with prefixes. Previously, OSPFv2 and OSPFv3 were relegated to a single tag and only for Autonomous System (AS) External and Not-So-Stubby-Area (NSSA) prefixes. With the flexible encodings provided by OSPFv2 Prefix/Link Attribu... | monolingualtext | ||||
STD:IETF:RFC9825$a26f852395ff | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Psenak | P. Psenak | string | ||||
STD:IETF:RFC9825$a48c064446b5 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9825 | https://www.rfc-editor.org/rfc/rfc9825 | url | ||||
STD:IETF:RFC9825$a9328c962aa8 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9825$a9328c962aa8 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9825$d40b411e5c30 | IETF | STD:IETF:RFC9825 | Extensions to OSPF for Advertising Prefix Administrative Tags | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. Qu | Y. Qu | string | ||||
STD:IETF:RFC9826$3fb1b7357bb1 | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | V. Beeram | V. Beeram | string | ||||
STD:IETF:RFC9826$5b22e380d66b | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | monolingualtext | ||||
STD:IETF:RFC9826$86f4ee5cf6bf | IETF | STD:IETF:RFC9826 | A YANG Data Model for 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:RFC9826$89104aa00046 | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a YANG data model for the management of the Path Computation Element Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. | This document defines a YANG data model for the management of the Path Computation Element Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. | monolingualtext | ||||
STD:IETF:RFC9826$a36b3b9cb1d1 | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9826$a9959b1a15fc | IETF | STD:IETF:RFC9826 | A YANG Data Model for 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:RFC9826$a9959b1a15fc | IETF | STD:IETF:RFC9826 | A YANG Data Model for 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:RFC9826$bb8b17a27064 | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9826$c61b09da599a | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Dhody | D. Dhody | string | ||||
STD:IETF:RFC9826$d4b0159a5799 | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.