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:RFC9864$3be3f75cdd80 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9864 | https://www.rfc-editor.org/rfc/rfc9864 | url | ||||
STD:IETF:RFC9864$43674fd5be87 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9864$43674fd5be87 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9864$815c38e16c45 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This specification refers to cryptographic algorithm identifiers that fully specify the cryptographic operations to be performed, including any curve, key derivation function (KDF), and hash functions, as being "fully specified". It refers to cryptographic algorithm identifiers that require additional information beyon... | This specification refers to cryptographic algorithm identifiers that fully specify the cryptographic operations to be performed, including any curve, key derivation function (KDF), and hash functions, as being "fully specified". It refers to cryptographic algorithm identifiers that require additional information beyon... | monolingualtext | ||||
STD:IETF:RFC9864$8163bbbdd092 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | O. Steele | O. Steele | string | ||||
STD:IETF:RFC9864$9a3a8c20b016 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9864$a5c91fbe3d52 | IETF | STD:IETF:RFC9864 | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) | monolingualtext | ||||
STD:IETF:RFC9865$23cc93dba875 | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Peterson | M. Peterson | string | ||||
STD:IETF:RFC9865$2e30bc799d05 | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9865$2e30bc799d05 | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9865$3af86b5d87b3 | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9865$3bcfd62fc15d | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9865 | https://www.rfc-editor.org/rfc/rfc9865 | url | ||||
STD:IETF:RFC9865$3db066ab8960 | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | monolingualtext | ||||
STD:IETF:RFC9865$483027cd8d6b | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9865$8b771952c4fa | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sehgal | A. Sehgal | string | ||||
STD:IETF:RFC9865$bbe00598182a | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates RFCs 7643 and 7644 by defining additional System for Cross-Domain Identity Management (SCIM) query parameters and result attributes to allow use of cursor-based pagination in SCIM service providers that are implemented with existing codebases, databases, or APIs where cursor-based pagination is al... | This document updates RFCs 7643 and 7644 by defining additional System for Cross-Domain Identity Management (SCIM) query parameters and result attributes to allow use of cursor-based pagination in SCIM service providers that are implemented with existing codebases, databases, or APIs where cursor-based pagination is al... | monolingualtext | ||||
STD:IETF:RFC9865$e2b5dec4b046 | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9865$e98cd121188d | IETF | STD:IETF:RFC9865 | Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Zollner | D. Zollner | string | ||||
STD:IETF:RFC9866$070974f03cf0 | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | By and large, correct operation of a network running the Routing Protocol for Low-Power and Lossy Networks (RPL) requires border routers to be up. In many applications, it is beneficial for the nodes to detect a failure of a border router as soon as possible to trigger fallback actions. This document specifies the Ro... | By and large, correct operation of a network running the Routing Protocol for Low-Power and Lossy Networks (RPL) requires border routers to be up. In many applications, it is beneficial for the nodes to detect a failure of a border router as soon as possible to trigger fallback actions. This document specifies the Ro... | monolingualtext | ||||
STD:IETF:RFC9866$0e5abc7e3289 | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes 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:RFC9866$0e5abc7e3289 | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes 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:RFC9866$55eef727bbc6 | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes in the Routing Protocol for Low-Power and Lossy Networks (RPL) | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes in the Routing Protocol for Low-Power and Lossy Networks (RPL) | monolingualtext | ||||
STD:IETF:RFC9866$6079047a7c32 | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Iwanicki | K. Iwanicki | string | ||||
STD:IETF:RFC9866$6b5d1d201a60 | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes 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:RFC9866$7591e517a6d2 | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes 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/rfc9866 | https://www.rfc-editor.org/rfc/rfc9866 | url | ||||
STD:IETF:RFC9866$83f0c5a1d6a3 | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes 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:RFC9866$c72071d3bc2d | IETF | STD:IETF:RFC9866 | Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes in the Routing Protocol for Low-Power and Lossy Networks (RPL) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9867$21691bcadf32 | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | monolingualtext | ||||
STD:IETF:RFC9867$472ddba5ffe7 | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9867 | https://www.rfc-editor.org/rfc/rfc9867 | url | ||||
STD:IETF:RFC9867$488dc4ec9437 | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9867$6c8cef581049 | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9867$72759d7e75cf | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | An Internet Key Exchange Protocol Version 2 (IKEv2) extension defined in RFC 8784 allows IPsec traffic to be protected against someone storing VPN communications and decrypting them later, when (and if) a Cryptographically Relevant Quantum Computer (CRQC) is available. The protection is achieved by means of a Post-quan... | An Internet Key Exchange Protocol Version 2 (IKEv2) extension defined in RFC 8784 allows IPsec traffic to be protected against someone storing VPN communications and decrypting them later, when (and if) a Cryptographically Relevant Quantum Computer (CRQC) is available. The protection is achieved by means of a Post-quan... | monolingualtext | ||||
STD:IETF:RFC9867$80dfa568eeb4 | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | V. Smyslov | V. Smyslov | string | ||||
STD:IETF:RFC9867$9ac16df656a1 | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9867$9ac16df656a1 | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9867$a6eb4320765b | IETF | STD:IETF:RFC9867 | Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum Security | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9868$0292b5b45687 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Transport protocols are extended through the use of transport header options. This document updates RFC 768 (UDP) by indicating the location, syntax, and semantics for UDP transport layer options within the surplus area after the end of the UDP user data but before the end of the IP datagram. | Transport protocols are extended through the use of transport header options. This document updates RFC 768 (UDP) by indicating the location, syntax, and semantics for UDP transport layer options within the surplus area after the end of the UDP user data but before the end of the IP datagram. | monolingualtext | ||||
STD:IETF:RFC9868$1caa152d10d1 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Touch | J. Touch | string | ||||
STD:IETF:RFC9868$310ff11cce75 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9868$310ff11cce75 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9868$550704cee236 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9868$5593a82689f8 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9868$78f2704ee288 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9868 | https://www.rfc-editor.org/rfc/rfc9868 | url | ||||
STD:IETF:RFC9868$acb842311942 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Heard | C. Heard | string | ||||
STD:IETF:RFC9868$b48cca7d9630 | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9868$d425c851557f | IETF | STD:IETF:RFC9868 | Transport Options for UDP | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Transport Options for UDP | Transport Options for UDP | monolingualtext | ||||
STD:IETF:RFC9869$413eff682c3c | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9869 | https://www.rfc-editor.org/rfc/rfc9869 | url | ||||
STD:IETF:RFC9869$609117d570d9 | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | monolingualtext | ||||
STD:IETF:RFC9869$7bdf8c9d7b8a | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Fairhurst | G. Fairhurst | string | ||||
STD:IETF:RFC9869$a6472050de92 | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9869$a933920a2570 | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies how a UDP Options sender implements Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) as a robust method for Path MTU Discovery (PMTUD). This method uses the UDP Options packetization layer. It allows an application to discover the largest size of datagram that can be sent across a ne... | This document specifies how a UDP Options sender implements Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) as a robust method for Path MTU Discovery (PMTUD). This method uses the UDP Options packetization layer. It allows an application to discover the largest size of datagram that can be sent across a ne... | monolingualtext | ||||
STD:IETF:RFC9869$e213a581146d | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9869$e213a581146d | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9869$f05b3d7d9e0b | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9869$f2712c412aca | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9869$f45e1e3e84a2 | IETF | STD:IETF:RFC9869 | Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Jones | T. Jones | string | ||||
STD:IETF:RFC9870$2c81768f563e | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9870$3d141759d3e6 | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9870$5dfc2ac79d8a | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9870$5dfc2ac79d8a | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9870$7d925b12d29c | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Boucadair | M. Boucadair | string | ||||
STD:IETF:RFC9870$b13ece418fa6 | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies new IP Flow Information Export (IPFIX) Information Elements for UDP Options. | This document specifies new IP Flow Information Export (IPFIX) Information Elements for UDP Options. | monolingualtext | ||||
STD:IETF:RFC9870$beeca03b4ddd | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Export of UDP Options Information in IP Flow Information Export (IPFIX) | Export of UDP Options Information in IP Flow Information Export (IPFIX) | monolingualtext | ||||
STD:IETF:RFC9870$c30514b5d882 | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9870 | https://www.rfc-editor.org/rfc/rfc9870 | url | ||||
STD:IETF:RFC9870$d3a315a169b1 | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Reddy.K | T. Reddy.K | string | ||||
STD:IETF:RFC9870$eed90f768852 | IETF | STD:IETF:RFC9870 | Export of UDP Options Information in IP Flow Information Export (IPFIX) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9871$057e3bca7688 | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9871 | https://www.rfc-editor.org/rfc/rfc9871 | url | ||||
STD:IETF:RFC9871$1b2771f378ee | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | S. Agrawal | S. Agrawal | string | ||||
STD:IETF:RFC9871$4a0f5fd99dd2 | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a BGP-based routing solution to establish end-to-end intent-aware paths across a multi-domain transport network. The transport network can span multiple service provider and customer network domains. The BGP intent-aware paths can be used to steer traffic flows for service routes that need a spe... | This document describes a BGP-based routing solution to establish end-to-end intent-aware paths across a multi-domain transport network. The transport network can span multiple service provider and customer network domains. The BGP intent-aware paths can be used to steer traffic flows for service routes that need a spe... | monolingualtext | ||||
STD:IETF:RFC9871$513230e1903d | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9871$73541613f867 | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | BGP Color-Aware Routing (CAR) | BGP Color-Aware Routing (CAR) | monolingualtext | ||||
STD:IETF:RFC9871$905608f76970 | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9871$d5539bad30dc | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9871$d5539bad30dc | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9871$ecc3072c49a0 | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | D. Rao | D. Rao | string | ||||
STD:IETF:RFC9871$ed4b5bf2b654 | IETF | STD:IETF:RFC9871 | BGP Color-Aware Routing (CAR) | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9872$12d55da51d19 | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9872$40be43ea1f57 | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | N. Buraglio | N. Buraglio | string | ||||
STD:IETF:RFC9872$41e564df905c | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9872$4d9d2b7d0746 | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Linkova | J. Linkova | string | ||||
STD:IETF:RFC9872$778037ec04bf | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | On networks providing IPv4-IPv6 translation (RFC 7915), hosts and other endpoints need to know the IPv6 prefix(es) used for translation (the NAT64 prefix (RFC 6052)). This document provides guidelines for NAT64 prefix discovery, specifically recommending obtaining the NAT64 prefix from the Router Advertisement option ... | On networks providing IPv4-IPv6 translation (RFC 7915), hosts and other endpoints need to know the IPv6 prefix(es) used for translation (the NAT64 prefix (RFC 6052)). This document provides guidelines for NAT64 prefix discovery, specifically recommending obtaining the NAT64 prefix from the Router Advertisement option ... | monolingualtext | ||||
STD:IETF:RFC9872$87487bd7d4b9 | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Jensen | T. Jensen | string | ||||
STD:IETF:RFC9872$8e2b3b84f45b | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9872$9377728e55a0 | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9872 | https://www.rfc-editor.org/rfc/rfc9872 | url | ||||
STD:IETF:RFC9872$976ef62ee697 | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9872$976ef62ee697 | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9872$d1c799a4546c | IETF | STD:IETF:RFC9872 | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis | monolingualtext | ||||
STD:IETF:RFC9873$2651a7bb0942 | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Extensible Provisioning Protocol (EPP) does not inherently support internationalized email addresses because the specifications for these addresses did not exist when EPP was developed. This document describes a command-response extension that adds support for associating an additional email address with an EPP co... | The Extensible Provisioning Protocol (EPP) does not inherently support internationalized email addresses because the specifications for these addresses did not exist when EPP was developed. This document describes a command-response extension that adds support for associating an additional email address with an EPP co... | monolingualtext | ||||
STD:IETF:RFC9873$3385b9cffaad | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | monolingualtext | ||||
STD:IETF:RFC9873$4014bb8a7945 | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9873 | https://www.rfc-editor.org/rfc/rfc9873 | url | ||||
STD:IETF:RFC9873$42923cb708ab | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Hollenbeck | S. Hollenbeck | string | ||||
STD:IETF:RFC9873$5ff85ab03440 | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9873$5ff85ab03440 | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9873$641d5da3752b | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Gould | J. Gould | string | ||||
STD:IETF:RFC9873$84a13021291c | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9873$aaac3283c806 | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Belyavsky | D. Belyavsky | string | ||||
STD:IETF:RFC9873$b082152cecf0 | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9873$b57cc0b3c402 | IETF | STD:IETF:RFC9873 | Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9874$10afe7fa871e | IETF | STD:IETF:RFC9874 | Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9874$10afe7fa871e | IETF | STD:IETF:RFC9874 | Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.