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:RFC9689$757f5cfce958 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Z. Li | Z. Li | string | ||||
STD:IETF:RFC9689$7bd5b9571fec | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Q. Zhao | Q. Zhao | string | ||||
STD:IETF:RFC9689$9ba51ce23eae | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9689$9e805f03c1b0 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9689$9ef1e4c05e35 | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Use Cases for a PCE as a Central Controller (PCECC) | Use Cases for a PCE as a Central Controller (PCECC) | monolingualtext | ||||
STD:IETF:RFC9689$f4715b6274bd | IETF | STD:IETF:RFC9689 | Use Cases for a PCE as a Central Controller (PCECC) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Z. Ke | Z. Ke | string | ||||
STD:IETF:RFC9690$09a496c55400 | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9690$17479964df16 | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9690 | https://www.rfc-editor.org/rfc/rfc9690 | url | ||||
STD:IETF:RFC9690$255deea3ca20 | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Turner | S. Turner | string | ||||
STD:IETF:RFC9690$32b1378a56ca | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | monolingualtext | ||||
STD:IETF:RFC9690$7966d35b9252 | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Housley | R. Housley | string | ||||
STD:IETF:RFC9690$8aa0fe2936ef | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9690$c1a5a0f65f1c | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9690$cd95adabcf2b | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The RSA Key Encapsulation Mechanism (RSA-KEM) algorithm is a one-pass (store-and-forward) cryptographic mechanism for an originator to securely send keying material to a recipient using the recipient's RSA public key. The RSA-KEM algorithm is specified in Clause 11.5 of ISO/IEC: 18033-2:2006. This document specifies ... | The RSA Key Encapsulation Mechanism (RSA-KEM) algorithm is a one-pass (store-and-forward) cryptographic mechanism for an originator to securely send keying material to a recipient using the recipient's RSA public key. The RSA-KEM algorithm is specified in Clause 11.5 of ISO/IEC: 18033-2:2006. This document specifies ... | monolingualtext | ||||
STD:IETF:RFC9690$f651318e1c05 | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm 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:RFC9690$f651318e1c05 | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm 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:RFC9690$fe116bcfdcd4 | IETF | STD:IETF:RFC9690 | Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC5990 | RFC5990 | wikibase-item | ||||
STD:IETF:RFC9691$505c07347e27 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | A Trust Anchor Locator (TAL) is used by Relying Parties (RPs) in the Resource Public Key Infrastructure (RPKI) to locate and validate a Trust Anchor (TA) Certification Authority (CA) certificate used in RPKI validation. This document defines an RPKI signed object for a Trust Anchor Key (TAK). A TAK object can be used... | A Trust Anchor Locator (TAL) is used by Relying Parties (RPs) in the Resource Public Key Infrastructure (RPKI) to locate and validate a Trust Anchor (TA) Certification Authority (CA) certificate used in RPKI validation. This document defines an RPKI signed object for a Trust Anchor Key (TAK). A TAK object can be used... | monolingualtext | ||||
STD:IETF:RFC9691$5d09a7ab042f | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9691 | https://www.rfc-editor.org/rfc/rfc9691 | url | ||||
STD:IETF:RFC9691$672011901623 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9691$6756cc86f952 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Michaelson | G. Michaelson | string | ||||
STD:IETF:RFC9691$6d6ff668d32f | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Austein | R. Austein | string | ||||
STD:IETF:RFC9691$78b5e3396247 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9691$78dc7b52ef6a | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Harrison | T. Harrison | string | ||||
STD:IETF:RFC9691$8cdd8b6a03e6 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9691$8cdd8b6a03e6 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9691$8ed13ac71e5c | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Bruijnzeels | T. Bruijnzeels | string | ||||
STD:IETF:RFC9691$a1d090f9d965 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | monolingualtext | ||||
STD:IETF:RFC9691$aaba6ede71e6 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9691$ac6a3e28bab9 | IETF | STD:IETF:RFC9691 | A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Martinez | C. Martinez | string | ||||
STD:IETF:RFC9692$11e90d33be62 | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | RIFT: Routing in Fat Trees | RIFT: Routing in Fat Trees | monolingualtext | ||||
STD:IETF:RFC9692$2426a2219a6a | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Head | J. Head | string | ||||
STD:IETF:RFC9692$342026f4c30f | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9692$3b5c2b5195e4 | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Afanasiev | D. Afanasiev | string | ||||
STD:IETF:RFC9692$6bd0fdd59ccd | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Przygienda | T. Przygienda | string | ||||
STD:IETF:RFC9692$8acb3a713baf | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Thubert | P. Thubert | string | ||||
STD:IETF:RFC9692$918327f280ba | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9692 | https://www.rfc-editor.org/rfc/rfc9692 | url | ||||
STD:IETF:RFC9692$a1f0ef7425be | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9692$a36aec85d28c | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Rijsman | B. Rijsman | string | ||||
STD:IETF:RFC9692$b3d63e755ae0 | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a specialized, dynamic routing protocol for Clos, fat tree, and variants thereof. These topologies were initially used within crossbar interconnects and consequently router and switch backplanes, but their characteristics make them ideal for constructing IP fabrics as well. The protocol specifie... | This document defines a specialized, dynamic routing protocol for Clos, fat tree, and variants thereof. These topologies were initially used within crossbar interconnects and consequently router and switch backplanes, but their characteristics make them ideal for constructing IP fabrics as well. The protocol specifie... | monolingualtext | ||||
STD:IETF:RFC9692$cd1d4e386aad | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9692$cd1d4e386aad | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9692$ee4fac570a94 | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9692$fd550c94fa61 | IETF | STD:IETF:RFC9692 | RIFT: Routing in Fat Trees | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sharma | A. Sharma | string | ||||
STD:IETF:RFC9693$2321551768c3 | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9693$2bb39943c9e0 | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9693 | https://www.rfc-editor.org/rfc/rfc9693 | url | ||||
STD:IETF:RFC9693$33e6bde64881 | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. Lencse | G. Lencse | string | ||||
STD:IETF:RFC9693$381681feb9d6 | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 2544 defines a benchmarking methodology for network interconnect devices. RFC 5180 addresses IPv6 specificities, and it also provides a technology update but excludes IPv6 transition technologies. RFC 8219 addresses IPv6 transition technologies, including stateful NAT64. However, none of them discuss how to appl... | RFC 2544 defines a benchmarking methodology for network interconnect devices. RFC 5180 addresses IPv6 specificities, and it also provides a technology update but excludes IPv6 transition technologies. RFC 8219 addresses IPv6 transition technologies, including stateful NAT64. However, none of them discuss how to appl... | monolingualtext | ||||
STD:IETF:RFC9693$44601dc2aac8 | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9693$4cd19b692607 | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Benchmarking Methodology for Stateful NATxy Gateways | Benchmarking Methodology for Stateful NATxy Gateways | monolingualtext | ||||
STD:IETF:RFC9693$52ada7454b83 | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9693$52ada7454b83 | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9693$5ab0a6acca3a | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9693$9a5666c053ab | IETF | STD:IETF:RFC9693 | Benchmarking Methodology for Stateful NATxy Gateways | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | K. Shima | K. Shima | string | ||||
STD:IETF:RFC9694$1a94f9b2e33a | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines best practices for defining new top-level media types. It also introduces a registry for top-level media types, and contains a short history of top-level media types. It updates RFC 6838. | This document defines best practices for defining new top-level media types. It also introduces a registry for top-level media types, and contains a short history of top-level media types. It updates RFC 6838. | monolingualtext | ||||
STD:IETF:RFC9694$21d065298f53 | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | Guidelines for the Definition of New Top-Level Media Types | Guidelines for the Definition of New Top-Level Media Types | monolingualtext | ||||
STD:IETF:RFC9694$2509a64f9c0f | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9694$4652c2c3c235 | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9694$4652c2c3c235 | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9694$72192cf33756 | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9694 | https://www.rfc-editor.org/rfc/rfc9694 | url | ||||
STD:IETF:RFC9694$ad6a42ca6305 | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9694$afe0ee850696 | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9694$c7f94403506e | IETF | STD:IETF:RFC9694 | Guidelines for the Definition of New Top-Level Media Types | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | M.J. Dürst | M.J. Dürst | string | ||||
STD:IETF:RFC9695$0a18c12d2eb2 | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9695$451f7de21b29 | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9695 | https://www.rfc-editor.org/rfc/rfc9695 | url | ||||
STD:IETF:RFC9695$742b8414b630 | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This memo registers and documents the 'haptics' top-level media type, under which subtypes for representation formats for haptics may be registered. This document also serves as a registration for a set of subtypes, which are representative of some existing subtypes already in use. | This memo registers and documents the 'haptics' top-level media type, under which subtypes for representation formats for haptics may be registered. This document also serves as a registration for a set of subtypes, which are representative of some existing subtypes already in use. | monolingualtext | ||||
STD:IETF:RFC9695$84e0ba69e865 | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9695$d06a4d95eeaf | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Ullrich | C. Ullrich | string | ||||
STD:IETF:RFC9695$d969b777159c | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. K. Muthusamy | Y. K. Muthusamy | string | ||||
STD:IETF:RFC9695$da11d56ad851 | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9695$f161451d1e79 | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9695$f161451d1e79 | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9695$f3f3c7e7a503 | IETF | STD:IETF:RFC9695 | The 'haptics' Top-Level Media Type | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The 'haptics' Top-Level Media Type | The 'haptics' Top-Level Media Type | monolingualtext | ||||
STD:IETF:RFC9696$0e8f3a375f04 | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9696$33183a503159 | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | monolingualtext | ||||
STD:IETF:RFC9696$400b243d2dcc | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Afanasiev | D. Afanasiev | string | ||||
STD:IETF:RFC9696$4fe53e161d57 | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9696$60f0b0195895 | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9696$62fee27a7f1f | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Y. Wei | Y. Wei | string | ||||
STD:IETF:RFC9696$7f806509c413 | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9696$7f806509c413 | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9696$9b908cc54084 | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Przygienda | T. Przygienda | string | ||||
STD:IETF:RFC9696$b20fc013549a | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9696 | https://www.rfc-editor.org/rfc/rfc9696 | url | ||||
STD:IETF:RFC9696$b44e0f28cdaa | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | P. Thubert | P. Thubert | string | ||||
STD:IETF:RFC9696$dc4b524d6798 | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document discusses the properties, applicability, and operational considerations of Routing in Fat Trees (RIFT) in different network scenarios with the intention of providing a rough guide on how RIFT can be deployed to simplify routing operations in Clos topologies and their variations. | This document discusses the properties, applicability, and operational considerations of Routing in Fat Trees (RIFT) in different network scenarios with the intention of providing a rough guide on how RIFT can be deployed to simplify routing operations in Clos topologies and their variations. | monolingualtext | ||||
STD:IETF:RFC9696$e84bdcf40b9a | IETF | STD:IETF:RFC9696 | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9697$046e4ab237fa | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. de Kock | T. de Kock | string | ||||
STD:IETF:RFC9697$1ede5ee0e432 | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9697$1ede5ee0e432 | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9697$1faa6d9ef9cf | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9697$332ba2db5965 | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9697 | https://www.rfc-editor.org/rfc/rfc9697 | url | ||||
STD:IETF:RFC9697$481815c7e9a9 | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Snijders | J. Snijders | string | ||||
STD:IETF:RFC9697$7cd45385a117 | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9697$a755974a62ec | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes an approach for Resource Public Key Infrastructure (RPKI) Relying Parties to detect a particular form of RPKI Repository Delta Protocol (RRDP) session desynchronization and how to recover. This document updates RFC 8182. | This document describes an approach for Resource Public Key Infrastructure (RPKI) Relying Parties to detect a particular form of RPKI Repository Delta Protocol (RRDP) session desynchronization and how to recover. This document updates RFC 8182. | monolingualtext | ||||
STD:IETF:RFC9697$dc3bc6db6a70 | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9697$dc8eb57a7a67 | IETF | STD:IETF:RFC9697 | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | Detecting RPKI Repository Delta Protocol (RRDP) Session Desynchronization | monolingualtext | ||||
STD:IETF:RFC9698$001faa27a732 | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9698$118a3e3aa177 | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9698 | https://www.rfc-editor.org/rfc/rfc9698 | url | ||||
STD:IETF:RFC9698$2abcceca276b | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9698$59cf15b67c89 | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The JMAPACCESS Extension for IMAP | The JMAPACCESS Extension for IMAP | monolingualtext |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.