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:RFC9450$77471f3f76dd | IETF | STD:IETF:RFC9450 | Reliable and Available Wireless (RAW) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9450$77471f3f76dd | IETF | STD:IETF:RFC9450 | Reliable and Available Wireless (RAW) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9450$a954b4950e86 | IETF | STD:IETF:RFC9450 | Reliable and Available Wireless (RAW) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. Papadopoulos | G. Papadopoulos | string | ||||
STD:IETF:RFC9450$c32d4c33637d | IETF | STD:IETF:RFC9450 | Reliable and Available Wireless (RAW) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9450$d0de6d36e190 | IETF | STD:IETF:RFC9450 | Reliable and Available Wireless (RAW) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9450$ec35e78c6d7c | IETF | STD:IETF:RFC9450 | Reliable and Available Wireless (RAW) Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | P. Thubert | P. Thubert | string | ||||
STD:IETF:RFC9451$05de7f4f1fe5 | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9451$5ce51ef5217a | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | monolingualtext | ||||
STD:IETF:RFC9451$5f142f0b85f2 | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9451$7bed81f3e7eb | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9451$82843b33d2e9 | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9451$82843b33d2e9 | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9451$b67fc069a039 | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9451 | https://www.rfc-editor.org/rfc/rfc9451 | url | ||||
STD:IETF:RFC9451$e22a0232e009 | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Boucadair | M. Boucadair | string | ||||
STD:IETF:RFC9451$ebd135dbae82 | IETF | STD:IETF:RFC9451 | Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document clarifies an ambiguity in the Network Service Header (NSH) specification related to the handling of O bit. In particular, this document clarifies the meaning of "OAM packet". This document updates RFC 8300. | This document clarifies an ambiguity in the Network Service Header (NSH) specification related to the handling of O bit. In particular, this document clarifies the meaning of "OAM packet". This document updates RFC 8300. | monolingualtext | ||||
STD:IETF:RFC9452$12abd3dcc408 | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9452$4bcbe3f7a0d1 | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Brockners | F. Brockners | string | ||||
STD:IETF:RFC9452$563b10237c24 | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9452$655cd89c91f9 | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Bhandari | S. Bhandari | string | ||||
STD:IETF:RFC9452$65fcf80812ae | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9452 | https://www.rfc-editor.org/rfc/rfc9452 | url | ||||
STD:IETF:RFC9452$892fed4b824d | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9452$9c8a934c5c4e | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | monolingualtext | ||||
STD:IETF:RFC9452$df6b8234b768 | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In situ Operations, Administration, and Maintenance (IOAM) is used for recording and collecting operational and telemetry information while the packet traverses a path between two points in the network. This document outlines how IOAM-Data-Fields are encapsulated with the Network Service Header (NSH). | In situ Operations, Administration, and Maintenance (IOAM) is used for recording and collecting operational and telemetry information while the packet traverses a path between two points in the network. This document outlines how IOAM-Data-Fields are encapsulated with the Network Service Header (NSH). | monolingualtext | ||||
STD:IETF:RFC9452$ef99852f86b2 | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9452$ef99852f86b2 | IETF | STD:IETF:RFC9452 | Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9453$3ef00ca26759 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9453$41d6b9fb9d75 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. Gomez | C. Gomez | string | ||||
STD:IETF:RFC9453$57c0d4e56661 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9453$5e2efe867506 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Y. Choi | Y. Choi | string | ||||
STD:IETF:RFC9453$65cffa31e1a2 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9453$65cffa31e1a2 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9453$68bd8173e813 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the applicability of IPv6 over constrained-node networks (6lo) and provides practical deployment examples. In addition to IEEE Std 802.15.4, various link-layer technologies are used as examples, such as ITU-T G.9959 (Z-Wave), Bluetooth Low Energy (Bluetooth LE), Digital Enhanced Cordless Teleco... | This document describes the applicability of IPv6 over constrained-node networks (6lo) and provides practical deployment examples. In addition to IEEE Std 802.15.4, various link-layer technologies are used as examples, such as ITU-T G.9959 (Z-Wave), Bluetooth Low Energy (Bluetooth LE), Digital Enhanced Cordless Teleco... | monolingualtext | ||||
STD:IETF:RFC9453$7b973d12ba88 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9453 | https://www.rfc-editor.org/rfc/rfc9453 | url | ||||
STD:IETF:RFC9453$7c255d0a25ee | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | monolingualtext | ||||
STD:IETF:RFC9453$8187841de41f | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9453$96ad277062a2 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Sangi | A. Sangi | string | ||||
STD:IETF:RFC9453$9de398372066 | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Chakrabarti | S. Chakrabarti | string | ||||
STD:IETF:RFC9453$da4ac167d34b | IETF | STD:IETF:RFC9453 | Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | Y. Hong | Y. Hong | string | ||||
STD:IETF:RFC9454$0918bdf73511 | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates some OSPF terminology to be in line with inclusive language used in the industry. The IETF has designated "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards" by the US National Institute of Standards and Technology (NIST) for its inclusive language guidelines. It is inte... | This document updates some OSPF terminology to be in line with inclusive language used in the industry. The IETF has designated "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards" by the US National Institute of Standards and Technology (NIST) for its inclusive language guidelines. It is inte... | monolingualtext | ||||
STD:IETF:RFC9454$1cc60e4a6a29 | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Fox | M. Fox | string | ||||
STD:IETF:RFC9454$2cba478e5e7a | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Update to OSPF Terminology | Update to OSPF Terminology | monolingualtext | ||||
STD:IETF:RFC9454$5725f0418b17 | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Lindem | A. Lindem | string | ||||
STD:IETF:RFC9454$6c5fe08b56ac | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Retana | A. Retana | string | ||||
STD:IETF:RFC9454$6f58c6829991 | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9454$ba6343bfd2df | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9454$c0317adc87a2 | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9454$e22eecc53aa4 | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9454$e22eecc53aa4 | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9454$edbb2545f3ec | IETF | STD:IETF:RFC9454 | Update to OSPF Terminology | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9454 | https://www.rfc-editor.org/rfc/rfc9454 | url | ||||
STD:IETF:RFC9455$05a7956171a8 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | Z. Yan | Z. Yan | string | ||||
STD:IETF:RFC9455$0f4a0f412831 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | G. Geng | G. Geng | string | ||||
STD:IETF:RFC9455$2373fb80aa75 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | T. de Kock | T. de Kock | string | ||||
STD:IETF:RFC9455$2ad6012b21b7 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9455$2ad6012b21b7 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9455$4bb2b466f2eb | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9455 | https://www.rfc-editor.org/rfc/rfc9455 | url | ||||
STD:IETF:RFC9455$4f4085a21bb3 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | monolingualtext | ||||
STD:IETF:RFC9455$6404d7e0ee29 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | When using the Resource Public Key Infrastructure (RPKI), address space holders need to issue Route Origin Authorization (ROA) object(s) to authorize one or more Autonomous Systems (ASes) to originate BGP routes to IP address prefix(es). This memo discusses operational problems that may arise from ROAs containing mult... | When using the Resource Public Key Infrastructure (RPKI), address space holders need to issue Route Origin Authorization (ROA) object(s) to authorize one or more Autonomous Systems (ASes) to originate BGP routes to IP address prefix(es). This memo discusses operational problems that may arise from ROAs containing mult... | monolingualtext | ||||
STD:IETF:RFC9455$6426f73dad7a | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | R. Bush | R. Bush | string | ||||
STD:IETF:RFC9455$82f7d565e490 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | J. Yao | J. Yao | string | ||||
STD:IETF:RFC9455$8ffa0e0bd04c | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9455$c77d32e71be6 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9455$f0ba3826c7a0 | IETF | STD:IETF:RFC9455 | Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9456$0b5056ddf435 | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9456$0b5056ddf435 | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9456$270417e6e05b | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9456$358bd62fe6df | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9456 | https://www.rfc-editor.org/rfc/rfc9456 | url | ||||
STD:IETF:RFC9456$57ef0867cf3a | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9456$74e167301253 | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9456$94fd13988e9d | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates RFC 6353 ("Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)") to reflect changes necessary to support Transport Layer Security version 1.3 (TLS 1.3) and Datagram Transport Layer Security version 1.3 (DTLS 1.3), which are jointly known as "(D)TLS 1.3"... | This document updates RFC 6353 ("Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)") to reflect changes necessary to support Transport Layer Security version 1.3 (TLS 1.3) and Datagram Transport Layer Security version 1.3 (DTLS 1.3), which are jointly known as "(D)TLS 1.3"... | monolingualtext | ||||
STD:IETF:RFC9456$9fe936429380 | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Vaughn | K. Vaughn | string | ||||
STD:IETF:RFC9456$c67e14feca15 | IETF | STD:IETF:RFC9456 | Updates to the TLS Transport Model for SNMP | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Updates to the TLS Transport Model for SNMP | Updates to the TLS Transport Model for SNMP | monolingualtext | ||||
STD:IETF:RFC9457$1b07d2ae1ce0 | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC7807 | RFC7807 | wikibase-item | ||||
STD:IETF:RFC9457$4b8ce0c39ce6 | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Nottingham | M. Nottingham | string | ||||
STD:IETF:RFC9457$6ffc5031db96 | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9457 | https://www.rfc-editor.org/rfc/rfc9457 | url | ||||
STD:IETF:RFC9457$99348fb5445a | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Dalal | S. Dalal | string | ||||
STD:IETF:RFC9457$a2f61286d81a | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9457$b3a78308263d | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Problem Details for HTTP APIs | Problem Details for HTTP APIs | monolingualtext | ||||
STD:IETF:RFC9457$b7c68219757f | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a "problem detail" to carry machine-readable details of errors in HTTP response content to avoid the need to define new error response formats for HTTP APIs. This document obsoletes RFC 7807. | This document defines a "problem detail" to carry machine-readable details of errors in HTTP response content to avoid the need to define new error response formats for HTTP APIs. This document obsoletes RFC 7807. | monolingualtext | ||||
STD:IETF:RFC9457$bb2e427164c7 | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9457$c77e686d18c2 | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9457$caed6805eb35 | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9457$caed6805eb35 | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9457$d070ca39bcd9 | IETF | STD:IETF:RFC9457 | Problem Details for HTTP APIs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Wilde | E. Wilde | string | ||||
STD:IETF:RFC9458$503bf4bb705c | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes Oblivious HTTP, a protocol for forwarding encrypted HTTP messages. Oblivious HTTP allows a client to make multiple requests to an origin server without that server being able to link those requests to the client or to identify the requests as having come from the same client, while placing only... | This document describes Oblivious HTTP, a protocol for forwarding encrypted HTTP messages. Oblivious HTTP allows a client to make multiple requests to an origin server without that server being able to link those requests to the client or to identify the requests as having come from the same client, while placing only... | monolingualtext | ||||
STD:IETF:RFC9458$66e39ee32bb9 | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. A. Wood | C. A. Wood | string | ||||
STD:IETF:RFC9458$69dedc45c961 | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9458 | https://www.rfc-editor.org/rfc/rfc9458 | url | ||||
STD:IETF:RFC9458$a008d1979eb2 | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Thomson | M. Thomson | string | ||||
STD:IETF:RFC9458$a5e5a9db261d | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9458$bb00e2eb2cbb | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9458$bb00e2eb2cbb | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9458$bc072ea9b691 | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Oblivious HTTP | Oblivious HTTP | monolingualtext | ||||
STD:IETF:RFC9458$dcd25336b3a0 | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9458$f1b87fa1de44 | IETF | STD:IETF:RFC9458 | Oblivious HTTP | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9459$5b70e3d25feb | IETF | STD:IETF:RFC9459 | CBOR Object Signing and Encryption (COSE): AES-CTR and AES-CBC | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9459$5d83c5db11eb | IETF | STD:IETF:RFC9459 | CBOR Object Signing and Encryption (COSE): AES-CTR and AES-CBC | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Housley | R. Housley | string | ||||
STD:IETF:RFC9459$6bbef827a184 | IETF | STD:IETF:RFC9459 | CBOR Object Signing and Encryption (COSE): AES-CTR and AES-CBC | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9459$6c3b0464a7cb | IETF | STD:IETF:RFC9459 | CBOR Object Signing and Encryption (COSE): AES-CTR and AES-CBC | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9459 | https://www.rfc-editor.org/rfc/rfc9459 | url | ||||
STD:IETF:RFC9459$8e148499d9d3 | IETF | STD:IETF:RFC9459 | CBOR Object Signing and Encryption (COSE): AES-CTR and AES-CBC | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Concise Binary Object Representation (CBOR) data format is designed for small code size and small message size. CBOR Object Signing and Encryption (COSE) is specified in RFC 9052 to provide basic security services using the CBOR data format. This document specifies the conventions for using AES-CTR and AES-CBC as... | The Concise Binary Object Representation (CBOR) data format is designed for small code size and small message size. CBOR Object Signing and Encryption (COSE) is specified in RFC 9052 to provide basic security services using the CBOR data format. This document specifies the conventions for using AES-CTR and AES-CBC as... | monolingualtext | ||||
STD:IETF:RFC9459$a7aaa76addb5 | IETF | STD:IETF:RFC9459 | CBOR Object Signing and Encryption (COSE): AES-CTR and AES-CBC | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9459$e1dfa3b1692c | IETF | STD:IETF:RFC9459 | CBOR Object Signing and Encryption (COSE): AES-CTR and AES-CBC | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.