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:RFC9555$65cf19340204 | IETF | STD:IETF:RFC9555 | JSContact: Converting from and to vCard | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines how to convert contact information between the JSContact and vCard data formats. It defines conversion rules for every JSContact and vCard element registered at IANA at the time of publication. It also defines new JSContact properties as well as vCard properties and parameters, to support conver... | This document defines how to convert contact information between the JSContact and vCard data formats. It defines conversion rules for every JSContact and vCard element registered at IANA at the time of publication. It also defines new JSContact properties as well as vCard properties and parameters, to support conver... | monolingualtext | ||||
STD:IETF:RFC9555$7695a50fae6f | IETF | STD:IETF:RFC9555 | JSContact: Converting from and to vCard | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Stepanek | R. Stepanek | string | ||||
STD:IETF:RFC9555$7f4d254708ae | IETF | STD:IETF:RFC9555 | JSContact: Converting from and to vCard | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Loffredo | M. Loffredo | string | ||||
STD:IETF:RFC9555$a09f927df4d5 | IETF | STD:IETF:RFC9555 | JSContact: Converting from and to vCard | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9555$e24d3f6e29fe | IETF | STD:IETF:RFC9555 | JSContact: Converting from and to vCard | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | JSContact: Converting from and to vCard | JSContact: Converting from and to vCard | monolingualtext | ||||
STD:IETF:RFC9555$e3165a485456 | IETF | STD:IETF:RFC9555 | JSContact: Converting from and to vCard | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9555 | https://www.rfc-editor.org/rfc/rfc9555 | url | ||||
STD:IETF:RFC9556$175b26b06df6 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Schooler | E. Schooler | string | ||||
STD:IETF:RFC9556$2b7f4d51e800 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9556$3a5fc3d7c5e8 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Kovatsch | M. Kovatsch | string | ||||
STD:IETF:RFC9556$558574bf1128 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Y-G. Hong | Y-G. Hong | string | ||||
STD:IETF:RFC9556$95eb5f191d2f | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9556$a0d30c4a967c | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Many Internet of Things (IoT) applications have requirements that cannot be satisfied by centralized cloud-based systems (i.e., cloud computing). These include time sensitivity, data volume, connectivity cost, operation in the face of intermittent services, privacy, and security. As a result, IoT is driving the Inter... | Many Internet of Things (IoT) applications have requirements that cannot be satisfied by centralized cloud-based systems (i.e., cloud computing). These include time sensitivity, data volume, connectivity cost, operation in the face of intermittent services, privacy, and security. As a result, IoT is driving the Inter... | monolingualtext | ||||
STD:IETF:RFC9556$a2db14a05130 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Kutscher | D. Kutscher | string | ||||
STD:IETF:RFC9556$a6995c505ebd | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Internet of Things (IoT) Edge Challenges and Functions | Internet of Things (IoT) Edge Challenges and Functions | monolingualtext | ||||
STD:IETF:RFC9556$af37ad214103 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9556 | https://www.rfc-editor.org/rfc/rfc9556 | url | ||||
STD:IETF:RFC9556$bedb5ea80dd7 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9556$c6439767204c | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Hong | J. Hong | string | ||||
STD:IETF:RFC9556$ce49d82df32a | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | X. de Foy | X. de Foy | string | ||||
STD:IETF:RFC9556$e200a941cd63 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9556$e200a941cd63 | IETF | STD:IETF:RFC9556 | Internet of Things (IoT) Edge Challenges and Functions | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9557$0103fcc45af5 | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9557$15b796cfdd80 | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Date and Time on the Internet: Timestamps with Additional Information | Date and Time on the Internet: Timestamps with Additional Information | monolingualtext | ||||
STD:IETF:RFC9557$31d9777c72e9 | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9557$31d9777c72e9 | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9557$556a22f54da0 | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9557 | https://www.rfc-editor.org/rfc/rfc9557 | url | ||||
STD:IETF:RFC9557$587c8dd11efa | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | U. Sharma | U. Sharma | string | ||||
STD:IETF:RFC9557$58a15a7d1a5a | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Bormann | C. Bormann | string | ||||
STD:IETF:RFC9557$9b75c56314ed | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9557$d0721e5af28c | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9557$d21721045dce | IETF | STD:IETF:RFC9557 | Date and Time on the Internet: Timestamps with Additional Information | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines an extension to the timestamp format defined in RFC 3339 for representing additional information, including a time zone. It updates RFC 3339 in the specific interpretation of the local offset Z, which is no longer understood to "imply that UTC is the preferred reference point for the specified ti... | This document defines an extension to the timestamp format defined in RFC 3339 for representing additional information, including a time zone. It updates RFC 3339 in the specific interpretation of the local offset Z, which is no longer understood to "imply that UTC is the preferred reference point for the specified ti... | monolingualtext | ||||
STD:IETF:RFC9558$159f163f9e1b | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9558$159f163f9e1b | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9558$2b89aa93688b | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | V. Dolmatov | V. Dolmatov | string | ||||
STD:IETF:RFC9558$35bccddf5770 | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9558$3ae26b0faba9 | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9558 | https://www.rfc-editor.org/rfc/rfc9558 | url | ||||
STD:IETF:RFC9558$5807929cb608 | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9558$ada8376d9b35 | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9558$c426f8573a98 | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes how to produce digital signatures and hash functions using the GOST R 34.10-2012 and GOST R 34.11-2012 algorithms for DNSKEY, RRSIG, and DS resource records, for use in the Domain Name System Security Extensions (DNSSEC). | This document describes how to produce digital signatures and hash functions using the GOST R 34.10-2012 and GOST R 34.11-2012 algorithms for DNSKEY, RRSIG, and DS resource records, for use in the Domain Name System Security Extensions (DNSSEC). | monolingualtext | ||||
STD:IETF:RFC9558$d4dcafe6327b | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | monolingualtext | ||||
STD:IETF:RFC9558$d841ac365ade | IETF | STD:IETF:RFC9558 | Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | B. Makarenko | B. Makarenko | string | ||||
STD:IETF:RFC9559$40aa9c5273a1 | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9559$5bfcbd567c26 | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Matroska Media Container Format Specification | Matroska Media Container Format Specification | monolingualtext | ||||
STD:IETF:RFC9559$5d9b7634f99a | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9559 | https://www.rfc-editor.org/rfc/rfc9559 | url | ||||
STD:IETF:RFC9559$6dc909ac4ae8 | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines the Matroska audiovisual data container structure, including definitions of its structural elements, terminology, vocabulary, and application. This document updates RFC 8794 to permit the use of a previously reserved Extensible Binary Meta Language (EBML) Element ID. | This document defines the Matroska audiovisual data container structure, including definitions of its structural elements, terminology, vocabulary, and application. This document updates RFC 8794 to permit the use of a previously reserved Extensible Binary Meta Language (EBML) Element ID. | monolingualtext | ||||
STD:IETF:RFC9559$73345eb74e45 | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9559$73345eb74e45 | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9559$7c5a8eddda40 | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Bunkus | M. Bunkus | string | ||||
STD:IETF:RFC9559$c801131bb21c | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9559$cccc81daf50f | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Lhomme | S. Lhomme | string | ||||
STD:IETF:RFC9559$df159d37c841 | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Rice | D. Rice | string | ||||
STD:IETF:RFC9559$ec41b6f76a55 | IETF | STD:IETF:RFC9559 | Matroska Media Container Format Specification | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9560$0d88f3c6770b | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | monolingualtext | ||||
STD:IETF:RFC9560$57a69bee56c7 | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9560$59a50c15b726 | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9560$76442aa41148 | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Hollenbeck | S. Hollenbeck | string | ||||
STD:IETF:RFC9560$9fd8242d0639 | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9560$d1376485bd99 | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9560$d1376485bd99 | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9560$f93c4c2d9375 | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Registration Data Access Protocol (RDAP) provides Representational State Transfer (RESTful) web services to retrieve registration metadata from domain name and regional internet registries. RDAP allows a server to make access control decisions based on client identity, and as such, it includes support for client i... | The Registration Data Access Protocol (RDAP) provides Representational State Transfer (RESTful) web services to retrieve registration metadata from domain name and regional internet registries. RDAP allows a server to make access control decisions based on client identity, and as such, it includes support for client i... | monolingualtext | ||||
STD:IETF:RFC9560$f994b79e9e1e | IETF | STD:IETF:RFC9560 | Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9560 | https://www.rfc-editor.org/rfc/rfc9560 | url | ||||
STD:IETF:RFC9561$1940e4ea6ec4 | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9561$4b567db3dfaa | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9561$5dd98a9d2673 | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9561$5dd98a9d2673 | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9561$6a1f0c1172f9 | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Lever | C. Lever | string | ||||
STD:IETF:RFC9561$7e1d8a49f46d | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies how to use the Parallel Network File System (pNFS) Small Computer System Interface (SCSI) Layout Type to access storage devices using the Non-Volatile Memory Express (NVMe) protocol family. | This document specifies how to use the Parallel Network File System (pNFS) Small Computer System Interface (SCSI) Layout Type to access storage devices using the Non-Volatile Memory Express (NVMe) protocol family. | monolingualtext | ||||
STD:IETF:RFC9561$9e7cb7f79397 | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | monolingualtext | ||||
STD:IETF:RFC9561$a9ee2265cdd3 | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Hellwig | C. Hellwig | string | ||||
STD:IETF:RFC9561$b6d76c89443f | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Black | D. Black | string | ||||
STD:IETF:RFC9561$c1db75bb5915 | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Faibish | S. Faibish | string | ||||
STD:IETF:RFC9561$e104bf1e367f | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9561 | https://www.rfc-editor.org/rfc/rfc9561 | url | ||||
STD:IETF:RFC9561$fc6749b1f9f0 | IETF | STD:IETF:RFC9561 | Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9562$0f28c2707af3 | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9562$107e312c36bb | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Peabody | B. Peabody | string | ||||
STD:IETF:RFC9562$31d18e095d48 | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC4122 | RFC4122 | wikibase-item | ||||
STD:IETF:RFC9562$52fef82764c5 | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9562$58742edaed31 | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Leach | P. Leach | string | ||||
STD:IETF:RFC9562$68432b6cf0f4 | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9562 | https://www.rfc-editor.org/rfc/rfc9562 | url | ||||
STD:IETF:RFC9562$815d9bf88c93 | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Universally Unique IDentifiers (UUIDs) | Universally Unique IDentifiers (UUIDs) | monolingualtext | ||||
STD:IETF:RFC9562$a9b7852e6abb | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This specification defines UUIDs (Universally Unique IDentifiers) --
also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform
Resource Name namespace for UUIDs. A UUID is 128 bits long and is
intended to guarantee uniqueness across space and time. UUIDs were
originally used in the Apollo Network Computing Sys... | This specification defines UUIDs (Universally Unique IDentifiers) --
also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform
Resource Name namespace for UUIDs. A UUID is 128 bits long and is
intended to guarantee uniqueness across space and time. UUIDs were
originally used in the Apollo Network Computing Sys... | monolingualtext | ||||
STD:IETF:RFC9562$e5ba2cc187cf | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9562$e5ba2cc187cf | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9562$f516745d7e63 | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9562$fca492932ecd | IETF | STD:IETF:RFC9562 | Universally Unique IDentifiers (UUIDs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Davis | K. Davis | string | ||||
STD:IETF:RFC9563$047e242bfdef | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | SM2 Digital Signature Algorithm for DNSSEC | SM2 Digital Signature Algorithm for DNSSEC | monolingualtext | ||||
STD:IETF:RFC9563$05742a8691c7 | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9563$1e9cccb62a61 | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | F. Leng | F. Leng | string | ||||
STD:IETF:RFC9563$2904fd88e48e | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Y. Liu | Y. Liu | string | ||||
STD:IETF:RFC9563$3359c5661a72 | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. Zhang | C. Zhang | string | ||||
STD:IETF:RFC9563$5813a8aebeee | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9563 | https://www.rfc-editor.org/rfc/rfc9563 | url | ||||
STD:IETF:RFC9563$6a81e9e4aebf | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Z. He | Z. He | string | ||||
STD:IETF:RFC9563$894056ff229b | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9563$894056ff229b | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9563$96f9450a0d7b | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Q. Zhao | Q. Zhao | string | ||||
STD:IETF:RFC9563$a96ad942a814 | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9563$e5ab41832385 | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9563$ee97aae038a7 | IETF | STD:IETF:RFC9563 | SM2 Digital Signature Algorithm for DNSSEC | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies the use of the SM2 digital signature algorithm and SM3 hash algorithm for DNS Security (DNSSEC). This document is an Independent Submission to the RFC series and does not have consensus of the IETF community. | This document specifies the use of the SM2 digital signature algorithm and SM3 hash algorithm for DNS Security (DNSSEC). This document is an Independent Submission to the RFC series and does not have consensus of the IETF community. | monolingualtext | ||||
STD:IETF:RFC9564$0460553c85f4 | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9564$23e1f2b9a27e | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9564$43a6be57a991 | IETF | STD:IETF:RFC9564 | Faster Than Light Speed Protocol (FLIP) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The recent advances in artificial intelligence (AI) such as large language models enable the design of the Faster than LIght speed Protocol (FLIP) for Internet. FLIP provides a way to avoid congestion, enhance security, and deliver faster packets on the Internet by using AI to predict future packets at the receiving p... | The recent advances in artificial intelligence (AI) such as large language models enable the design of the Faster than LIght speed Protocol (FLIP) for Internet. FLIP provides a way to avoid congestion, enhance security, and deliver faster packets on the Internet by using AI to predict future packets at the receiving p... | monolingualtext |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.