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:RFC9843$d9c152e5144b | IETF | STD:IETF:RFC9843 | IGP Flexible Algorithms: Bandwidth, Delay, Metrics, and Constraints | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9843 | https://www.rfc-editor.org/rfc/rfc9843 | url | ||||
STD:IETF:RFC9843$f1d3187ecc33 | IETF | STD:IETF:RFC9843 | IGP Flexible Algorithms: Bandwidth, Delay, Metrics, and Constraints | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Many networks configure the IGP link metric relative to the link capacity, and high bandwidth traffic gets routed per the link capacity. Flexible Algorithms provide mechanisms to create constraint-based paths in an IGP. This specification documents a generic metric-type and a set of bandwidth-related constraints to be ... | Many networks configure the IGP link metric relative to the link capacity, and high bandwidth traffic gets routed per the link capacity. Flexible Algorithms provide mechanisms to create constraint-based paths in an IGP. This specification documents a generic metric-type and a set of bandwidth-related constraints to be ... | monolingualtext | ||||
STD:IETF:RFC9844$2c38a69b366b | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9844$2c38a69b366b | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9844$4cc68182080f | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9844$500d8e6b530a | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Carpenter | B. Carpenter | string | ||||
STD:IETF:RFC9844$7dede0dd9fc7 | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Hinden | R. Hinden | string | ||||
STD:IETF:RFC9844$8bd36ec40863 | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Entering IPv6 Zone Identifiers in User Interfaces | Entering IPv6 Zone Identifiers in User Interfaces | monolingualtext | ||||
STD:IETF:RFC9844$b2a68c87c688 | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC6874 | RFC6874 | wikibase-item | ||||
STD:IETF:RFC9844$bcae1dd0c34d | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes how the zone identifier of an IPv6 scoped address, defined in the IPv6 Scoped Address Architecture specification (RFC 4007), should be entered into a user interface. This document obsoletes RFC 6874 and updates RFCs 4007, 7622, and 8089. | This document describes how the zone identifier of an IPv6 scoped address, defined in the IPv6 Scoped Address Architecture specification (RFC 4007), should be entered into a user interface. This document obsoletes RFC 6874 and updates RFCs 4007, 7622, and 8089. | monolingualtext | ||||
STD:IETF:RFC9844$d200482ec538 | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9844$d90889f8c0c1 | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9844$ea9ce130900c | IETF | STD:IETF:RFC9844 | Entering IPv6 Zone Identifiers in User Interfaces | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9844 | https://www.rfc-editor.org/rfc/rfc9844 | url | ||||
STD:IETF:RFC9845$37a1ae43d3ab | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M-P. Odini | M-P. Odini | string | ||||
STD:IETF:RFC9845$453f65bfe91a | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. Westphal | C. Westphal | string | ||||
STD:IETF:RFC9845$5769d1112e52 | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9845 | https://www.rfc-editor.org/rfc/rfc9845 | url | ||||
STD:IETF:RFC9845$595fc98c9e9c | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | L. Ciavaglia | L. Ciavaglia | string | ||||
STD:IETF:RFC9845$5b5014f0c6bc | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Clemm | A. Clemm | string | ||||
STD:IETF:RFC9845$758aed9a0a6e | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9845$8a56d520739d | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9845$a644637dc957 | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9845$a644637dc957 | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9845$a73fdf729c4e | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9845$ac604728d843 | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9845$af4bf9819d1f | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Reducing humankind's environmental footprint and making technology more environmentally sustainable are among the biggest challenges of our age. Networks play an important part in this challenge. On one hand, they enable applications that help to reduce this footprint. On the other hand, they significantly contribute t... | Reducing humankind's environmental footprint and making technology more environmentally sustainable are among the biggest challenges of our age. Networks play an important part in this challenge. On one hand, they enable applications that help to reduce this footprint. On the other hand, they significantly contribute t... | monolingualtext | ||||
STD:IETF:RFC9845$c8d8357c9f5c | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. Pignataro | C. Pignataro | string | ||||
STD:IETF:RFC9845$cd6ccb77112f | IETF | STD:IETF:RFC9845 | Challenges and Opportunities in Management for Green Networking | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Challenges and Opportunities in Management for Green Networking | Challenges and Opportunities in Management for Green Networking | monolingualtext | ||||
STD:IETF:RFC9847$46126476dc93 | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates the changes to the TLS and DTLS IANA registries made in RFC 8447. It adds a new value, "D" for discouraged, to the "Recommended" column of the selected TLS registries and adds a "Comment" column to all active registries that do not already have a "Comment" column. Finally, it updates the registrat... | This document updates the changes to the TLS and DTLS IANA registries made in RFC 8447. It adds a new value, "D" for discouraged, to the "Recommended" column of the selected TLS registries and adds a "Comment" column to all active registries that do not already have a "Comment" column. Finally, it updates the registrat... | monolingualtext | ||||
STD:IETF:RFC9847$6246dd994b76 | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9847$680165505b0a | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Turner | S. Turner | string | ||||
STD:IETF:RFC9847$84a8c0399e80 | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | IANA Registry Updates for TLS and DTLS | IANA Registry Updates for TLS and DTLS | monolingualtext | ||||
STD:IETF:RFC9847$98184ed1bd53 | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9847$98184ed1bd53 | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9847$9a477cbe4489 | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Salowey | J. Salowey | string | ||||
STD:IETF:RFC9847$b093e07b6e16 | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9847$cf6ae53c5149 | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9847$dd78509553ed | IETF | STD:IETF:RFC9847 | IANA Registry Updates for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9847 | https://www.rfc-editor.org/rfc/rfc9847 | url | ||||
STD:IETF:RFC9848$0118bcbc4853 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9848 | https://www.rfc-editor.org/rfc/rfc9848 | url | ||||
STD:IETF:RFC9848$0860623ff339 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9848$5a0db8ac5745 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9848$5b5c5b9b95a0 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | monolingualtext | ||||
STD:IETF:RFC9848$713c40187585 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Schwartz | B. Schwartz | string | ||||
STD:IETF:RFC9848$792db25d33b1 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9848$880d619637ac | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Nygren | E. Nygren | string | ||||
STD:IETF:RFC9848$c185ee42a367 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Bishop | M. Bishop | string | ||||
STD:IETF:RFC9848$e297e7968288 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9848$e297e7968288 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9848$fe65b3b34533 | IETF | STD:IETF:RFC9848 | Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | To use TLS Encrypted ClientHello (ECH), the client needs to learn the ECH configuration for a server before it attempts a connection to the server. This specification provides a mechanism for conveying the ECH configuration information via DNS, using a SVCB or HTTPS resource record (RR). | To use TLS Encrypted ClientHello (ECH), the client needs to learn the ECH configuration for a server before it attempts a connection to the server. This specification provides a mechanism for conveying the ECH configuration information via DNS, using a SVCB or HTTPS resource record (RR). | monolingualtext | ||||
STD:IETF:RFC9849$178f8a2d3378 | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Oku | K. Oku | string | ||||
STD:IETF:RFC9849$49fd679b2f93 | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | TLS Encrypted Client Hello | TLS Encrypted Client Hello | monolingualtext | ||||
STD:IETF:RFC9849$55b22ff5091c | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9849$6413b1e3e94d | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a mechanism in Transport Layer Security (TLS) for encrypting a message under a server public key. | This document describes a mechanism in Transport Layer Security (TLS) for encrypting a message under a server public key. | monolingualtext | ||||
STD:IETF:RFC9849$706f36dbd091 | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. A. Wood | C. A. Wood | string | ||||
STD:IETF:RFC9849$96106eef7c75 | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Rescorla | E. Rescorla | string | ||||
STD:IETF:RFC9849$9bfa3a950f85 | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Sullivan | N. Sullivan | string | ||||
STD:IETF:RFC9849$9ca1869b5867 | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9849$cb6dd48d82f3 | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9849 | https://www.rfc-editor.org/rfc/rfc9849 | url | ||||
STD:IETF:RFC9849$d451009083dd | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9849$d451009083dd | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9849$ebfc96cdfc4c | IETF | STD:IETF:RFC9849 | TLS Encrypted Client Hello | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9853$26d89388a9d8 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Tschofenig | H. Tschofenig | string | ||||
STD:IETF:RFC9853$2b979c51b2c8 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Return Routability Check for DTLS 1.2 and 1.3 | Return Routability Check for DTLS 1.2 and 1.3 | monolingualtext | ||||
STD:IETF:RFC9853$55019b2ac6ae | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9853$668ad917fc81 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Kraus | A. Kraus | string | ||||
STD:IETF:RFC9853$6c10348e82c9 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Fossati | T. Fossati | string | ||||
STD:IETF:RFC9853$8acf698be044 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9853$99f2c55dea00 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies a Return Routability Check (RRC) subprotocol for use in the context of the Connection ID (CID) construct for the Datagram Transport Layer Security (DTLS) protocol versions 1.2 and 1.3. Implementations offering the CID functionality described in RFCs 9146 and 9147 are encouraged to also provide ... | This document specifies a Return Routability Check (RRC) subprotocol for use in the context of the Connection ID (CID) construct for the Datagram Transport Layer Security (DTLS) protocol versions 1.2 and 1.3. Implementations offering the CID functionality described in RFCs 9146 and 9147 are encouraged to also provide ... | monolingualtext | ||||
STD:IETF:RFC9853$9efcf7553d85 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9853$9efcf7553d85 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9853$a914402c9813 | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9853 | https://www.rfc-editor.org/rfc/rfc9853 | url | ||||
STD:IETF:RFC9853$c17becaff2dd | IETF | STD:IETF:RFC9853 | Return Routability Check for DTLS 1.2 and 1.3 | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9854$22bab0393e16 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S.V.R. Anand | S.V.R. Anand | string | ||||
STD:IETF:RFC9854$260873714672 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9854$260873714672 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9854$4c97fe3f326f | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C.E. Perkins | C.E. Perkins | string | ||||
STD:IETF:RFC9854$87eb88947d81 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9854$b48ff8f9d6d4 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Route discovery for symmetric and asymmetric Peer-to-Peer (P2P) traffic flows is a desirable feature in Low-Power and Lossy Networks (LLNs). For that purpose, this document specifies AODV-RPL -- the Routing Protocol for Low-Power and Lossy Networks (RPL) based on Ad hoc On-demand Distance Vector (AODV) routing. AODV-... | Route discovery for symmetric and asymmetric Peer-to-Peer (P2P) traffic flows is a desirable feature in Low-Power and Lossy Networks (LLNs). For that purpose, this document specifies AODV-RPL -- the Routing Protocol for Low-Power and Lossy Networks (RPL) based on Ad hoc On-demand Distance Vector (AODV) routing. AODV-... | monolingualtext | ||||
STD:IETF:RFC9854$c183b5d8575e | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9854$c2edecc42347 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9854$d987ca20d060 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Liu | B. Liu | string | ||||
STD:IETF:RFC9854$dd309c3262b7 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | monolingualtext | ||||
STD:IETF:RFC9854$df6f01d5cebb | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9854 | https://www.rfc-editor.org/rfc/rfc9854 | url | ||||
STD:IETF:RFC9854$fd367cf5aad0 | IETF | STD:IETF:RFC9854 | AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Anamalamudi | S. Anamalamudi | string | ||||
STD:IETF:RFC9855$086d619d7f28 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Francois | P. Francois | string | ||||
STD:IETF:RFC9855$0898d74babad | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Filsfils | C. Filsfils | string | ||||
STD:IETF:RFC9855$0d48e2bec4b4 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9855$0d48e2bec4b4 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9855$15836055e223 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9855 | https://www.rfc-editor.org/rfc/rfc9855 | url | ||||
STD:IETF:RFC9855$1c81d26f5df0 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9855$1f0370c0e8fb | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Decraene | B. Decraene | string | ||||
STD:IETF:RFC9855$4dcdae161068 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document presents Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute (FRR), which is aimed at providing protection of node and Adjacency segments within the Segment Routing (SR) framework. This FRR behavior builds on proven IP FRR concepts being LFAs, Remote LFAs (RLFAs), and Directed Loop-Free Altern... | This document presents Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute (FRR), which is aimed at providing protection of node and Adjacency segments within the Segment Routing (SR) framework. This FRR behavior builds on proven IP FRR concepts being LFAs, Remote LFAs (RLFAs), and Directed Loop-Free Altern... | monolingualtext | ||||
STD:IETF:RFC9855$6f8dc2e18a83 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9855$7254e6bd5569 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9855$75cddbd6516f | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Bashandy | A. Bashandy | string | ||||
STD:IETF:RFC9855$76c01fa7c547 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Litkowski | S. Litkowski | string | ||||
STD:IETF:RFC9855$8bc8c0e60bf4 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Voyer | D. Voyer | string | ||||
STD:IETF:RFC9855$ff966e9c3361 | IETF | STD:IETF:RFC9855 | Topology Independent Fast Reroute Using Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Topology Independent Fast Reroute Using Segment Routing | Topology Independent Fast Reroute Using Segment Routing | monolingualtext | ||||
STD:IETF:RFC9856$0c4a0765560f | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Lin | W. Lin | string | ||||
STD:IETF:RFC9856$17d309954c0b | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9856$215c796d945f | IETF | STD:IETF:RFC9856 | Multicast Source Redundancy in EVPNs | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.