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:RFC9797$03fd721e02a7 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9797$0d7d56823545 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | To limit the privacy issues created by the association between a device, its traffic, its location, and its user in IEEE 802 networks, client vendors and client OS vendors have started implementing Media Access Control (MAC) address randomization. This technology is particularly important in Wi-Fi networks (defined in ... | To limit the privacy issues created by the association between a device, its traffic, its location, and its user in IEEE 802 networks, client vendors and client OS vendors have started implementing Media Access Control (MAC) address randomization. This technology is particularly important in Wi-Fi networks (defined in ... | monolingualtext | ||||
STD:IETF:RFC9797$38894b704af4 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9797$468cb1c4dee1 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Henry | J. Henry | string | ||||
STD:IETF:RFC9797$562c877ed92e | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9797$5f43e9621e29 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9797$9e46f08ea206 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | monolingualtext | ||||
STD:IETF:RFC9797$d895b7d530c1 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Y. Lee | Y. Lee | string | ||||
STD:IETF:RFC9797$e1f14627ce18 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9797 | https://www.rfc-editor.org/rfc/rfc9797 | url | ||||
STD:IETF:RFC9798$12a4c6ba8caf | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | S. Venaas | S. Venaas | string | ||||
STD:IETF:RFC9798$26891b145a3e | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9798$3f3d02947b81 | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9798$3f3d02947b81 | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9798$42aa520299fe | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | monolingualtext | ||||
STD:IETF:RFC9798$60edfd3e7260 | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | V. Govindan | V. Govindan | string | ||||
STD:IETF:RFC9798$67458e09e162 | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9798 | https://www.rfc-editor.org/rfc/rfc9798 | url | ||||
STD:IETF:RFC9798$84210ff078b6 | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9798$b36982d45129 | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies an update to the Receiver RLOC (Routing Locator) field of the PIM Join/Prune attribute that supports the construction of multicast distribution trees where the source and receivers are located in different Locator/ID Separation Protocol (LISP) sites and are connected using underlay IP multicast.... | This document specifies an update to the Receiver RLOC (Routing Locator) field of the PIM Join/Prune attribute that supports the construction of multicast distribution trees where the source and receivers are located in different Locator/ID Separation Protocol (LISP) sites and are connected using underlay IP multicast.... | monolingualtext | ||||
STD:IETF:RFC9798$bbdf96adb27f | IETF | STD:IETF:RFC9798 | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9799$0491722099ec | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9799$0d579df25221 | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines extensions to the Automated Certificate Management Environment (ACME) to allow for the automatic issuance of certificates to Tor Hidden Services (".onion" Special-Use Domain Names). | This document defines extensions to the Automated Certificate Management Environment (ACME) to allow for the automatic issuance of certificates to Tor Hidden Services (".onion" Special-Use Domain Names). | monolingualtext | ||||
STD:IETF:RFC9799$26b458e1cdc0 | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | monolingualtext | ||||
STD:IETF:RFC9799$2b3f5cdcfc6c | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9799$67d84d04a977 | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9799$67d84d04a977 | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9799$77c3f6d956dd | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9799$92f1cff67499 | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Q Misell | Q Misell | string | ||||
STD:IETF:RFC9799$b881db93e4a8 | IETF | STD:IETF:RFC9799 | Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain Names | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9799 | https://www.rfc-editor.org/rfc/rfc9799 | url | ||||
STD:IETF:RFC9800$0cf0ae015855 | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Compressed SRv6 Segment List Encoding | Compressed SRv6 Segment List Encoding | monolingualtext | ||||
STD:IETF:RFC9800$5523aa849960 | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Clad | F. Clad | string | ||||
STD:IETF:RFC9800$58df93a833ac | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Filsfils | C. Filsfils | string | ||||
STD:IETF:RFC9800$628619c7e469 | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Decraene | B. Decraene | string | ||||
STD:IETF:RFC9800$6a88e3825674 | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9800$6a88e3825674 | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9800$874c4b8143fc | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9800$9445b07ffaa9 | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Cheng | W. Cheng | string | ||||
STD:IETF:RFC9800$9f30b3e401f4 | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Segment Routing over IPv6 (SRv6) is the instantiation of Segment Routing (SR) on the IPv6 data plane. This document specifies new flavors for the SRv6 endpoint behaviors defined in RFC 8986, which enable the compression of an SRv6 segment list. Such compression significantly reduces the size of the SRv6 encapsulation n... | Segment Routing over IPv6 (SRv6) is the instantiation of Segment Routing (SR) on the IPv6 data plane. This document specifies new flavors for the SRv6 endpoint behaviors defined in RFC 8986, which enable the compression of an SRv6 segment list. Such compression significantly reduces the size of the SRv6 encapsulation n... | monolingualtext | ||||
STD:IETF:RFC9800$a180b2a823fb | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9800 | https://www.rfc-editor.org/rfc/rfc9800 | url | ||||
STD:IETF:RFC9800$b4cf48b0f22a | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9800$e0a4ea69c41d | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9800$ff3c9ed2a07c | IETF | STD:IETF:RFC9800 | Compressed SRv6 Segment List Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Li | Z. Li | string | ||||
STD:IETF:RFC9801$307c3f148e75 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Whittaker | J. Whittaker | string | ||||
STD:IETF:RFC9801$4e430a104624 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9801 | https://www.rfc-editor.org/rfc/rfc9801 | url | ||||
STD:IETF:RFC9801$584bb2f16117 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9801$5d62b4ae1633 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Brown | C. Brown | string | ||||
STD:IETF:RFC9801$67ebb88081ff | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Leymann | N. Leymann | string | ||||
STD:IETF:RFC9801$69984e24a6b3 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Gringeri | S. Gringeri | string | ||||
STD:IETF:RFC9801$7a8309e4aaf6 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Private Line Emulation over Packet Switched Networks | Private Line Emulation over Packet Switched Networks | monolingualtext | ||||
STD:IETF:RFC9801$897c6744e54f | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9801$897c6744e54f | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9801$8d4ea87791d0 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9801$a1a08a792252 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9801$bbf7c893f302 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Schmutzer | C. Schmutzer | string | ||||
STD:IETF:RFC9801$ead4c0a50790 | IETF | STD:IETF:RFC9801 | Private Line Emulation over Packet Switched Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document expands the applicability of Virtual Private Wire Service (VPWS) bit-stream payloads beyond Time Division Multiplexing (TDM) signals and provides pseudowire transport with complete signal transparency over Packet Switched Networks (PSNs). | This document expands the applicability of Virtual Private Wire Service (VPWS) bit-stream payloads beyond Time Division Multiplexing (TDM) signals and provides pseudowire transport with complete signal transparency over Packet Switched Networks (PSNs). | monolingualtext | ||||
STD:IETF:RFC9802$24ccedb3e887 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Bashiri | K. Bashiri | string | ||||
STD:IETF:RFC9802$2cfa08b7a265 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Kousidis | S. Kousidis | string | ||||
STD:IETF:RFC9802$3984cb21460e | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9802 | https://www.rfc-editor.org/rfc/rfc9802 | url | ||||
STD:IETF:RFC9802$531cbd57dd61 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies algorithm identifiers and ASN.1 encoding formats for the following stateful Hash-Based Signature (HBS) schemes: Hierarchical Signature System (HSS), eXtended Merkle Signature Scheme (XMSS), and XMSS^MT (a multi-tree variant of XMSS). This specification applies to the Internet X.509 Public Key I... | This document specifies algorithm identifiers and ASN.1 encoding formats for the following stateful Hash-Based Signature (HBS) schemes: Hierarchical Signature System (HSS), eXtended Merkle Signature Scheme (XMSS), and XMSS^MT (a multi-tree variant of XMSS). This specification applies to the Internet X.509 Public Key I... | monolingualtext | ||||
STD:IETF:RFC9802$8fc2f41a05f3 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Fluhrer | S. Fluhrer | string | ||||
STD:IETF:RFC9802$a161ab5f06b5 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | monolingualtext | ||||
STD:IETF:RFC9802$b4b338467fe9 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9802$b4b338467fe9 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9802$b587c4748f4e | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Van Geest | D. Van Geest | string | ||||
STD:IETF:RFC9802$cfada24eb009 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9802$d0f81c9dc87a | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9802$d69e5d11740f | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Gazdag | S. Gazdag | string | ||||
STD:IETF:RFC9802$e04fb411bc82 | IETF | STD:IETF:RFC9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9803$452559c3118b | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9803$46388307e194 | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9803$8323cbf921a2 | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | monolingualtext | ||||
STD:IETF:RFC9803$a7d18fd03ffd | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9803$b21af4c8eb3c | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Brown | G. Brown | string | ||||
STD:IETF:RFC9803$ba3d27177eee | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9803$ba3d27177eee | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9803$caee527a2a8e | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9803 | https://www.rfc-editor.org/rfc/rfc9803 | url | ||||
STD:IETF:RFC9803$cf228fb53fe5 | IETF | STD:IETF:RFC9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes an extension to the Extensible Provisioning
Protocol (EPP) that allows EPP clients to manage the Time-to-Live
(TTL) value for domain name delegation records. | This document describes an extension to the Extensible Provisioning
Protocol (EPP) that allows EPP clients to manage the Time-to-Live
(TTL) value for domain name delegation records. | monolingualtext | ||||
STD:IETF:RFC9804$1631a8f89d4d | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9804$25eed4c15c21 | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9804$7d6560812f4b | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | R. Rivest | R. Rivest | string | ||||
STD:IETF:RFC9804$ab99321a60f2 | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9804$ab99321a60f2 | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9804$ce4f752c8771 | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9804 | https://www.rfc-editor.org/rfc/rfc9804 | url | ||||
STD:IETF:RFC9804$d5f044742dbb | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Eastlake 3rd | D. Eastlake 3rd | string | ||||
STD:IETF:RFC9804$d92f44f401bf | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9804$dfeb172595a2 | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This memo specifies the data structure representation that was devised to support Simple Public Key Infrastructure (SPKI) certificates, as detailed in RFC 2692, with the intent that it be more widely applicable. It has been and is being used elsewhere. There are multiple implementations in a variety of programming la... | This memo specifies the data structure representation that was devised to support Simple Public Key Infrastructure (SPKI) certificates, as detailed in RFC 2692, with the intent that it be more widely applicable. It has been and is being used elsewhere. There are multiple implementations in a variety of programming la... | monolingualtext | ||||
STD:IETF:RFC9804$ebe1faa9d52b | IETF | STD:IETF:RFC9804 | Simple Public Key Infrastructure (SPKI) S-Expressions | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Simple Public Key Infrastructure (SPKI) S-Expressions | Simple Public Key Infrastructure (SPKI) S-Expressions | monolingualtext | ||||
STD:IETF:RFC9805$3166ed6ce50e | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9805 | https://www.rfc-editor.org/rfc/rfc9805 | url | ||||
STD:IETF:RFC9805$3f2a0112c8eb | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Deprecation of the IPv6 Router Alert Option for New Protocols | Deprecation of the IPv6 Router Alert Option for New Protocols | monolingualtext | ||||
STD:IETF:RFC9805$462b3edc9a37 | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document deprecates the IPv6 Router Alert option. Protocols that use the IPv6 Router Alert option may continue to do so, even in future versions. However, new protocols that are standardized in the future must not use the IPv6 Router Alert option. This document updates RFC 2711. | This document deprecates the IPv6 Router Alert option. Protocols that use the IPv6 Router Alert option may continue to do so, even in future versions. However, new protocols that are standardized in the future must not use the IPv6 Router Alert option. This document updates RFC 2711. | monolingualtext | ||||
STD:IETF:RFC9805$78d924e82460 | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9805$85bd6346f097 | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9805$85bd6346f097 | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9805$9fdb9ab3739f | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9805$e1fc09a87a06 | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Bonica | R. Bonica | string | ||||
STD:IETF:RFC9805$f061b41c6f42 | IETF | STD:IETF:RFC9805 | Deprecation of the IPv6 Router Alert Option for New Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9806$26eb589062f8 | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9806 | https://www.rfc-editor.org/rfc/rfc9806 | url | ||||
STD:IETF:RFC9806$2da8b1d0cf02 | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The SIP-based Media Recording (SIPREC) protocol is defined by both "Session Initiation Protocol (SIP) Recording Metadata" (RFC 7865) and "Session Recording Protocol" (RFC 7866). Unfortunately, both RFCs contradict each other regarding how recording metadata is to be labeled. In addition, neither RFC registered the ne... | The SIP-based Media Recording (SIPREC) protocol is defined by both "Session Initiation Protocol (SIP) Recording Metadata" (RFC 7865) and "Session Recording Protocol" (RFC 7866). Unfortunately, both RFCs contradict each other regarding how recording metadata is to be labeled. In addition, neither RFC registered the ne... | monolingualtext | ||||
STD:IETF:RFC9806$341fa2fe1cd5 | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9806$52f34373208c | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9806$52f34373208c | IETF | STD:IETF:RFC9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.