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:RFC9681$0ceabf006e1f | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | M. Karasek | M. Karasek | string | ||||
STD:IETF:RFC9681$1cd3412991e4 | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | G. Van de Velde | G. Van de Velde | string | ||||
STD:IETF:RFC9681$2e8806e5ca32 | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9681$31581b938abd | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | T. Li | T. Li | string | ||||
STD:IETF:RFC9681$32da006aae5f | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | IS-IS Fast Flooding | IS-IS Fast Flooding | monolingualtext | ||||
STD:IETF:RFC9681$343eaf43e54e | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9681$3506efc6adc1 | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9681$3506efc6adc1 | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9681$6fe46bc8224d | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Current Link State PDU flooding rates are much slower than what modern networks can support. The use of IS-IS at larger scale requires faster flooding rates to achieve desired convergence goals. This document discusses the need for faster flooding, the issues around faster flooding, and some example approaches to ach... | Current Link State PDU flooding rates are much slower than what modern networks can support. The use of IS-IS at larger scale requires faster flooding rates to achieve desired convergence goals. This document discusses the need for faster flooding, the issues around faster flooding, and some example approaches to ach... | monolingualtext | ||||
STD:IETF:RFC9681$8f30767b1e4d | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | L. Ginsberg | L. Ginsberg | string | ||||
STD:IETF:RFC9681$a13b3ab0a590 | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9681 | https://www.rfc-editor.org/rfc/rfc9681 | url | ||||
STD:IETF:RFC9681$ac9712f11fa1 | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | G. Solignac | G. Solignac | string | ||||
STD:IETF:RFC9681$d28022b711e5 | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | T. Przygienda | T. Przygienda | string | ||||
STD:IETF:RFC9681$da18a4475a02 | IETF | STD:IETF:RFC9681 | IS-IS Fast Flooding | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9682$4df81b196899 | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9682$659f1b275c6f | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Bormann | C. Bormann | string | ||||
STD:IETF:RFC9682$65d9455226cc | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9682$879317ee327f | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Updates to the Concise Data Definition Language (CDDL) Grammar | Updates to the Concise Data Definition Language (CDDL) Grammar | monolingualtext | ||||
STD:IETF:RFC9682$8e554ccd20f2 | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9682 | https://www.rfc-editor.org/rfc/rfc9682 | url | ||||
STD:IETF:RFC9682$b400f3cb600a | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Concise Data Definition Language (CDDL), as defined in RFCs 8610 and 9165, provides an easy and unambiguous way to express structures for protocol messages and data formats that are represented in Concise Binary Object Representation (CBOR) or JSON. This document updates RFC 8610 by addressing related errata repor... | The Concise Data Definition Language (CDDL), as defined in RFCs 8610 and 9165, provides an easy and unambiguous way to express structures for protocol messages and data formats that are represented in Concise Binary Object Representation (CBOR) or JSON. This document updates RFC 8610 by addressing related errata repor... | monolingualtext | ||||
STD:IETF:RFC9682$c86645028d32 | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9682$e8cd5ad7ae29 | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9682$e8cd5ad7ae29 | IETF | STD:IETF:RFC9682 | Updates to the Concise Data Definition Language (CDDL) Grammar | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9683$31596bed1d04 | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Voit | E. Voit | string | ||||
STD:IETF:RFC9683$458fda07f039 | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9683$4689a18aa109 | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9683 | https://www.rfc-editor.org/rfc/rfc9683 | url | ||||
STD:IETF:RFC9683$77ade87f4cdf | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9683$859edb631076 | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | monolingualtext | ||||
STD:IETF:RFC9683$98fc6ed787bf | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9683$bf11952b0a6b | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9683$bf11952b0a6b | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9683$dc3ef53953fa | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. C. Fedorkow | G. C. Fedorkow | string | ||||
STD:IETF:RFC9683$e1e6dd9e30e5 | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a workflow for remote attestation of the integrity of firmware and software installed on network devices that contain Trusted Platform Modules (TPMs), as defined by the Trusted Computing Group (TCG), or equivalent hardware implementations that include the protected capabilities, as provided by T... | This document describes a workflow for remote attestation of the integrity of firmware and software installed on network devices that contain Trusted Platform Modules (TPMs), as defined by the Trusted Computing Group (TCG), or equivalent hardware implementations that include the protected capabilities, as provided by T... | monolingualtext | ||||
STD:IETF:RFC9683$f8fa5c9da8cf | IETF | STD:IETF:RFC9683 | Remote Integrity Verification of Network Devices Containing Trusted Platform Modules | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Fitzgerald-McKay | J. Fitzgerald-McKay | string | ||||
STD:IETF:RFC9684$2351e2095895 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9684 | https://www.rfc-editor.org/rfc/rfc9684 | url | ||||
STD:IETF:RFC9684$23a3ffb0e54c | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9684$272c86e65b83 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Bhandari | S. Bhandari | string | ||||
STD:IETF:RFC9684$48b21445bf94 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | monolingualtext | ||||
STD:IETF:RFC9684$62c73c88944c | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9684$63b8b81f3264 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9684$6b175e83d0f9 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Laffey | T. Laffey | string | ||||
STD:IETF:RFC9684$8b444da5d9f2 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9684$8b444da5d9f2 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9684$b32aa8fccbd4 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines the YANG Remote Procedure Calls (RPCs) and configuration nodes that are required to retrieve attestation evidence about integrity measurements from a device, following the operational context defined in RFC 9683 "TPM-based Network Device Remote Integrity Verification". Complementary measurement l... | This document defines the YANG Remote Procedure Calls (RPCs) and configuration nodes that are required to retrieve attestation evidence about integrity measurements from a device, following the operational context defined in RFC 9683 "TPM-based Network Device Remote Integrity Verification". Complementary measurement l... | monolingualtext | ||||
STD:IETF:RFC9684$b973924bcd71 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Sulzen | B. Sulzen | string | ||||
STD:IETF:RFC9684$c65d99bfc6ef | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. C. Fedorkow | G. C. Fedorkow | string | ||||
STD:IETF:RFC9684$d48593454a2b | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Voit | E. Voit | string | ||||
STD:IETF:RFC9684$dc1d3c6d8f57 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Eckel | M. Eckel | string | ||||
STD:IETF:RFC9684$fa846bd9caa2 | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Xia | L. Xia | string | ||||
STD:IETF:RFC9684$fae6af6f5ceb | IETF | STD:IETF:RFC9684 | A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Birkholz | H. Birkholz | string | ||||
STD:IETF:RFC9685$0cda056dba18 | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9685$132e17e1fa6b | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9685$31768d3b6760 | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Thubert | P. Thubert | string | ||||
STD:IETF:RFC9685$3473640bbd44 | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9685$36892b4ec4bb | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9685 | https://www.rfc-editor.org/rfc/rfc9685 | url | ||||
STD:IETF:RFC9685$3ed3aa0db1c4 | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | monolingualtext | ||||
STD:IETF:RFC9685$92d9d5a37968 | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9685$92d9d5a37968 | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9685$c5063b9f940b | IETF | STD:IETF:RFC9685 | Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates the 6LoWPAN extensions to IPv6 Neighbor Discovery (specified in RFCs 4861 and 8505) to enable a listener to subscribe to an IPv6 anycast or multicast address. This document also updates the Routing Protocol for Low-Power and Lossy Networks (RPL) (specified in RFCs 6550 and 6553) to add a new Non-... | This document updates the 6LoWPAN extensions to IPv6 Neighbor Discovery (specified in RFCs 4861 and 8505) to enable a listener to subscribe to an IPv6 anycast or multicast address. This document also updates the Routing Protocol for Low-Power and Lossy Networks (RPL) (specified in RFCs 6550 and 6553) to add a new Non-... | monolingualtext | ||||
STD:IETF:RFC9686$50ac2ca7a7cb | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Krishnan | S. Krishnan | string | ||||
STD:IETF:RFC9686$570f99e6f2ed | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9686$6109a3817a20 | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9686 | https://www.rfc-editor.org/rfc/rfc9686 | url | ||||
STD:IETF:RFC9686$6143f8c31fdf | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Registering Self-Generated IPv6 Addresses Using DHCPv6 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | monolingualtext | ||||
STD:IETF:RFC9686$691f673bcbdb | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Asati | R. Asati | string | ||||
STD:IETF:RFC9686$7e507f90bead | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Linkova | J. Linkova | string | ||||
STD:IETF:RFC9686$8630cc841f88 | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Colitti | L. Colitti | string | ||||
STD:IETF:RFC9686$8d8ffc6b40a5 | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Jiang | S. Jiang | string | ||||
STD:IETF:RFC9686$8e6852712cae | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9686$8e6852712cae | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9686$abd74a1c06aa | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Kumari | W. Kumari | string | ||||
STD:IETF:RFC9686$bf53fd98f485 | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a method to inform a DHCPv6 server that a device has one or more self-generated or statically configured addresses. | This document defines a method to inform a DHCPv6 server that a device has one or more self-generated or statically configured addresses. | monolingualtext | ||||
STD:IETF:RFC9686$ca08e196285b | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9686$db837ff860b3 | IETF | STD:IETF:RFC9686 | Registering Self-Generated IPv6 Addresses Using DHCPv6 | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9687$0893fbb28fbf | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9687$1fc529ba7763 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Snijders | J. Snijders | string | ||||
STD:IETF:RFC9687$23d3fc0df632 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9687 | https://www.rfc-editor.org/rfc/rfc9687 | url | ||||
STD:IETF:RFC9687$5c4867b7c77b | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Cartwright-Cox | B. Cartwright-Cox | string | ||||
STD:IETF:RFC9687$cafc9bb7b077 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. Qu | Y. Qu | string | ||||
STD:IETF:RFC9687$d257b0215fd4 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9687$d2eedeb01b93 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9687$d2eedeb01b93 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9687$dee8ba75d0b6 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9687$e0ad12731c62 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | monolingualtext | ||||
STD:IETF:RFC9687$eab429e3dc30 | IETF | STD:IETF:RFC9687 | Border Gateway Protocol 4 (BGP-4) Send Hold Timer | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines the SendHoldTimer, along with the SendHoldTimer_Expires event, for the Border Gateway Protocol (BGP) Finite State Machine (FSM). Implementation of the SendHoldTimer helps overcome situations where a BGP connection is not terminated after the local system detects that the remote system is not proc... | This document defines the SendHoldTimer, along with the SendHoldTimer_Expires event, for the Border Gateway Protocol (BGP) Finite State Machine (FSM). Implementation of the SendHoldTimer helps overcome situations where a BGP connection is not terminated after the local system detects that the remote system is not proc... | monolingualtext | ||||
STD:IETF:RFC9688$03cc875e570f | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9688$03cc875e570f | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9688$22e197035c16 | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Housley | R. Housley | string | ||||
STD:IETF:RFC9688$63f4712d9e6e | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | monolingualtext | ||||
STD:IETF:RFC9688$76ea8b83f8b3 | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9688 | https://www.rfc-editor.org/rfc/rfc9688 | url | ||||
STD:IETF:RFC9688$7ea1ab7eb89f | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9688$df0b830b1184 | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9688$dffdabcfe6d6 | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the conventions for using the one-way hash functions in the SHA3 family with the Cryptographic Message Syntax (CMS). The SHA3 family can be used as a message digest algorithm, as part of a signature algorithm, as part of a message authentication code, or as part of a Key Derivation Function (KD... | This document describes the conventions for using the one-way hash functions in the SHA3 family with the Cryptographic Message Syntax (CMS). The SHA3 family can be used as a message digest algorithm, as part of a signature algorithm, as part of a message authentication code, or as part of a Key Derivation Function (KD... | monolingualtext | ||||
STD:IETF:RFC9688$e7c38a16e32a | IETF | STD:IETF:RFC9688 | Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9689$2416596a53c7 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9689$310625e62e79 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | B. Khasanov | B. Khasanov | string | ||||
STD:IETF:RFC9689$3b1702b3fcd5 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9689 | https://www.rfc-editor.org/rfc/rfc9689 | url | ||||
STD:IETF:RFC9689$42545393ad83 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The PCE is a core component of a Software-Defined Networking (SDN) system. It can be used to compute optimal paths for network traffic and update existing paths to reflect changes in the network or traffic demands. The PCE was developed to derive Traffic Engineering (TE) paths in MPLS networks, which are supplied to th... | The PCE is a core component of a Software-Defined Networking (SDN) system. It can be used to compute optimal paths for network traffic and update existing paths to reflect changes in the network or traffic demands. The PCE was developed to derive Traffic Engineering (TE) paths in MPLS networks, which are supplied to th... | monolingualtext | ||||
STD:IETF:RFC9689$4e41b933781e | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Dhody | D. Dhody | string | ||||
STD:IETF:RFC9689$64d4ff89bbf9 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9689$64d4ff89bbf9 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.