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:RFC9910$bc241d9920fe | IETF | STD:IETF:RFC9910 | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9910 | https://www.rfc-editor.org/rfc/rfc9910 | url | ||||
STD:IETF:RFC9910$d2849433230e | IETF | STD:IETF:RFC9910 | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | monolingualtext | ||||
STD:IETF:RFC9910$dc7dd6b23edb | IETF | STD:IETF:RFC9910 | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Registration Data Access Protocol (RDAP) is used by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs) to provide access to their resource registration information. The core specifications for RDAP define basic search functionality, but there are various search options related to IP addresses, I... | The Registration Data Access Protocol (RDAP) is used by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs) to provide access to their resource registration information. The core specifications for RDAP define basic search functionality, but there are various search options related to IP addresses, I... | monolingualtext | ||||
STD:IETF:RFC9910$e2d9949bc1a4 | IETF | STD:IETF:RFC9910 | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9910$ecf6ed871a0b | IETF | STD:IETF:RFC9910 | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9910$ecf6ed871a0b | IETF | STD:IETF:RFC9910 | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9910$fa795562101b | IETF | STD:IETF:RFC9910 | Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9911$149aac0cd1ff | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9911$1a47ebb81263 | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9911 | https://www.rfc-editor.org/rfc/rfc9911 | url | ||||
STD:IETF:RFC9911$2f7c750bdbf9 | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9911$735746a01361 | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9911$85c0fe748c84 | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Common YANG Data Types | Common YANG Data Types | monolingualtext | ||||
STD:IETF:RFC9911$8fc417b385a1 | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a collection of common data types to be used with the YANG data modeling language. It includes several new type definitions and obsoletes RFC 6991. | This document defines a collection of common data types to be used with the YANG data modeling language. It includes several new type definitions and obsoletes RFC 6991. | monolingualtext | ||||
STD:IETF:RFC9911$b108cdbcfa69 | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Schönwälder | J. Schönwälder | string | ||||
STD:IETF:RFC9911$ccbeb0a90937 | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9911$ccbeb0a90937 | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9911$da97705d88ec | IETF | STD:IETF:RFC9911 | Common YANG Data Types | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC6991 | RFC6991 | wikibase-item | ||||
STD:IETF:RFC9912$1a5c0e3dc48e | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9912 | https://www.rfc-editor.org/rfc/rfc9912 | url | ||||
STD:IETF:RFC9912$2c99b7708e07 | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Reliable and Available Wireless (RAW) Architecture | Reliable and Available Wireless (RAW) Architecture | monolingualtext | ||||
STD:IETF:RFC9912$33ddf96a43d2 | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | P. Thubert | P. Thubert | string | ||||
STD:IETF:RFC9912$6bd6bdf4bdad | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9912$6bd6bdf4bdad | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9912$d1e80c8acfa9 | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9912$d273b43eff4b | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9912$e1d941b290da | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Reliable and Available Wireless (RAW) extends the reliability and availability of Deterministic Networking (DetNet) to networks composed of any combination of wired and wireless segments. The RAW architecture leverages and extends RFC 8655 ("Deterministic Networking Architecture") to adapt to challenges that prominent... | Reliable and Available Wireless (RAW) extends the reliability and availability of Deterministic Networking (DetNet) to networks composed of any combination of wired and wireless segments. The RAW architecture leverages and extends RFC 8655 ("Deterministic Networking Architecture") to adapt to challenges that prominent... | monolingualtext | ||||
STD:IETF:RFC9912$f098de82dd20 | IETF | STD:IETF:RFC9912 | Reliable and Available Wireless (RAW) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9913$640e98617ec2 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Farkas | J. Farkas | string | ||||
STD:IETF:RFC9913$6716b54dfd10 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Cavalcanti | D. Cavalcanti | string | ||||
STD:IETF:RFC9913$735c6c2c51c5 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9913$735c6c2c51c5 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9913$8bba02c368aa | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9913$91912b2e3e54 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | P. Thubert | P. Thubert | string | ||||
STD:IETF:RFC9913$932f05a28073 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | X. Vilajosana | X. Vilajosana | string | ||||
STD:IETF:RFC9913$b05da3a8de49 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. Schmitt | C. Schmitt | string | ||||
STD:IETF:RFC9913$b084ac9ecdd4 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9913$cab0b0019383 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document surveys the short- and middle-range radio technologies over which providing Deterministic Networking (DetNet), and more specifically, Reliable and Available Wireless (RAW) service is suitable. It also presents the characteristics that RAW may leverage and explores the applicability of the technologies to... | This document surveys the short- and middle-range radio technologies over which providing Deterministic Networking (DetNet), and more specifically, Reliable and Available Wireless (RAW) service is suitable. It also presents the characteristics that RAW may leverage and explores the applicability of the technologies to... | monolingualtext | ||||
STD:IETF:RFC9913$ce2d5a0932ad | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9913$e9fdd62f71f9 | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Reliable and Available Wireless (RAW) Technologies | Reliable and Available Wireless (RAW) Technologies | monolingualtext | ||||
STD:IETF:RFC9913$fa613468319b | IETF | STD:IETF:RFC9913 | Reliable and Available Wireless (RAW) Technologies | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9913 | https://www.rfc-editor.org/rfc/rfc9913 | url | ||||
STD:IETF:RFC9914$0a0a0ef000c0 | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | monolingualtext | ||||
STD:IETF:RFC9914$24cf4e81e9f0 | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Thubert | P. Thubert | string | ||||
STD:IETF:RFC9914$68f26f93ff0e | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9914$6a21aa0bb135 | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Routing Protocol for Low-Power and Lossy Networks (RPL) (RFC 6550) enables data packet routing along a Destination-Oriented Directed Acyclic Graph (DODAG). However, the default route establishment mechanism relies on hop-by-hop forwarding along the DODAG, which may not always provide optimal routing efficiency. T... | The Routing Protocol for Low-Power and Lossy Networks (RPL) (RFC 6550) enables data packet routing along a Destination-Oriented Directed Acyclic Graph (DODAG). However, the default route establishment mechanism relies on hop-by-hop forwarding along the DODAG, which may not always provide optimal routing efficiency. T... | monolingualtext | ||||
STD:IETF:RFC9914$6e74b7450623 | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Richardson | M. Richardson | string | ||||
STD:IETF:RFC9914$7404b847be96 | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9914$74f4a1f38fe5 | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9914 | https://www.rfc-editor.org/rfc/rfc9914 | url | ||||
STD:IETF:RFC9914$777ce8163781 | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9914$7d02f5b3f02f | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9914$7d02f5b3f02f | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9914$a952a50cc1c5 | IETF | STD:IETF:RFC9914 | Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R.A. Jadhav | R.A. Jadhav | string | ||||
STD:IETF:RFC9915$1f6f3bacaeb8 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9915$36f19d5a5e9d | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P50 | author | B. Volz | B. Volz | string | ||||
STD:IETF:RFC9915$40596b6eedfe | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P50 | author | M. Richardson | M. Richardson | string | ||||
STD:IETF:RFC9915$4687909863f9 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INTERNET STANDARD | INTERNET STANDARD | string | ||||
STD:IETF:RFC9915$4687909863f9 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INTERNET STANDARD | INTERNET STANDARD | string | ||||
STD:IETF:RFC9915$50c2054968d8 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9915$7cea0677634e | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9915$7e2d92abfcd8 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P50 | author | T. Mrugalski | T. Mrugalski | string | ||||
STD:IETF:RFC9915$967d4f46cff8 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P1476 | title | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | monolingualtext | ||||
STD:IETF:RFC9915$ac0d0cc7b245 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies the Dynamic Host Configuration Protocol for IPv6 (DHCPv6), an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly or in combination with stateful assignment of one or more IPv6 addresses and/or IPv6 ... | This document specifies the Dynamic Host Configuration Protocol for IPv6 (DHCPv6), an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly or in combination with stateful assignment of one or more IPv6 addresses and/or IPv6 ... | monolingualtext | ||||
STD:IETF:RFC9915$c54330009b22 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P50 | author | T. Winters | T. Winters | string | ||||
STD:IETF:RFC9915$cd8ec21e948a | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P50 | author | S. Jiang | S. Jiang | string | ||||
STD:IETF:RFC9915$f7f4f3254dfb | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC8415 | RFC8415 | wikibase-item | ||||
STD:IETF:RFC9915$faa688459ae5 | IETF | STD:IETF:RFC9915 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | INTERNET STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9915 | https://www.rfc-editor.org/rfc/rfc9915 | url | ||||
STD:IETF:RFC9917$3fb6afe471fa | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9917$3fb6afe471fa | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9917$50b028dea44b | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9917 | https://www.rfc-editor.org/rfc/rfc9917 | url | ||||
STD:IETF:RFC9917$6adab904ad86 | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9917$86c0a350dd41 | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | IGP Flexible Algorithms Reverse Affinity Constraint | IGP Flexible Algorithms Reverse Affinity Constraint | monolingualtext | ||||
STD:IETF:RFC9917$89cd2fa1c3a8 | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Psenak | P. Psenak | string | ||||
STD:IETF:RFC9917$926e88c06fa4 | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Dhamija | A. Dhamija | string | ||||
STD:IETF:RFC9917$a7506d4eda67 | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | An IGP Flexible Algorithm (Flex-Algorithm) enables the computation of constraint-based paths within an IGP domain, allowing operators to influence path selection according to administrative policies. This document defines an extension to Flex-Algorithm that allows the inclusion or exclusion of links from path computati... | An IGP Flexible Algorithm (Flex-Algorithm) enables the computation of constraint-based paths within an IGP domain, allowing operators to influence path selection according to administrative policies. This document defines an extension to Flex-Algorithm that allows the inclusion or exclusion of links from path computati... | monolingualtext | ||||
STD:IETF:RFC9917$ab5c36bc1a20 | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Horn | J. Horn | string | ||||
STD:IETF:RFC9917$df49089f3c2f | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9917$f0dfea2d349a | IETF | STD:IETF:RFC9917 | IGP Flexible Algorithms Reverse Affinity Constraint | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9920$09dba0eb8e67 | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Rossi | A. Rossi | string | ||||
STD:IETF:RFC9920$0a0a8f6a67dc | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9920$192e138a6fec | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | P. Hoffman | P. Hoffman | string | ||||
STD:IETF:RFC9920$219c38ffc1a1 | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9920 | https://www.rfc-editor.org/rfc/rfc9920 | url | ||||
STD:IETF:RFC9920$2bcd6e3b16fb | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | RFC Editor Model (Version 3) | RFC Editor Model (Version 3) | monolingualtext | ||||
STD:IETF:RFC9920$3ebbf596b62e | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9920$548827959b4a | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies version 3 of the RFC Editor Model. The model defines two high-level tasks related to the RFC Series. First, policy definition is the joint responsibility of the RFC Series Working Group (RSWG), which produces policy proposals, and the RFC Series Approval Board (RSAB), which approves such proposa... | This document specifies version 3 of the RFC Editor Model. The model defines two high-level tasks related to the RFC Series. First, policy definition is the joint responsibility of the RFC Series Working Group (RSWG), which produces policy proposals, and the RFC Series Approval Board (RSAB), which approves such proposa... | monolingualtext | ||||
STD:IETF:RFC9920$ac6f7f1dfcd4 | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC9280 | RFC9280 | wikibase-item | ||||
STD:IETF:RFC9920$b281797c4700 | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9920$c509bf134f12 | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9920$c509bf134f12 | IETF | STD:IETF:RFC9920 | RFC Editor Model (Version 3) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9921$08dc672a8521 | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | monolingualtext | ||||
STD:IETF:RFC9921$0e111870dd3c | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9921 | https://www.rfc-editor.org/rfc/rfc9921 | url | ||||
STD:IETF:RFC9921$1ccacc190c86 | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines two CBOR Object Signing and Encryption (COSE) header parameters for incorporating timestamping based on RFC 3161 into COSE message structures (COSE_Sign and COSE_Sign1). This enables the use of established timestamping infrastructure per RFC 3161 in COSE-based protocols. | This document defines two CBOR Object Signing and Encryption (COSE) header parameters for incorporating timestamping based on RFC 3161 into COSE message structures (COSE_Sign and COSE_Sign1). This enables the use of established timestamping infrastructure per RFC 3161 in COSE-based protocols. | monolingualtext | ||||
STD:IETF:RFC9921$732a24bfd210 | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Birkholz | H. Birkholz | string | ||||
STD:IETF:RFC9921$8a4e667a534c | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9921$9773bdd53b7e | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Riechert | M. Riechert | string | ||||
STD:IETF:RFC9921$a7722d65da09 | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9921$a7722d65da09 | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9921$b04853e8b00d | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Fossati | T. Fossati | string | ||||
STD:IETF:RFC9921$d81d1309bbc9 | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2026-01 | 2026-01 | time | ||||
STD:IETF:RFC9921$fcf89bf15118 | IETF | STD:IETF:RFC9921 | CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161 | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9922$02b1d65590e6 | IETF | STD:IETF:RFC9922 | A Common YANG Data Model for Scheduling | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9922 | https://www.rfc-editor.org/rfc/rfc9922 | url | ||||
STD:IETF:RFC9922$1cbe751fc347 | IETF | STD:IETF:RFC9922 | A Common YANG Data Model for Scheduling | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A Common YANG Data Model for Scheduling | A Common YANG Data Model for Scheduling | monolingualtext | ||||
STD:IETF:RFC9922$1faad2e4df67 | IETF | STD:IETF:RFC9922 | A Common YANG Data Model for Scheduling | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Q. Ma | Q. Ma | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.