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:RFC9662$8a560faa5117 | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Lonvick | C. Lonvick | string | ||||
STD:IETF:RFC9662$a4df4f1badbe | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9662$ad1640806e5c | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9662$ad1640806e5c | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9662$d568219934f8 | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9662$ffa6451879f0 | IETF | STD:IETF:RFC9662 | Updates to the Cipher Suites in Secure Syslog | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Turner | S. Turner | string | ||||
STD:IETF:RFC9663$125b29ffeda1 | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document discusses an IPv6 deployment scenario when individual nodes connected to large broadcast networks (such as enterprise networks or public Wi-Fi networks) are allocated unique prefixes via DHCPv6 Prefix Delegation (DHCPv6-PD), as specified in RFC 8415. | This document discusses an IPv6 deployment scenario when individual nodes connected to large broadcast networks (such as enterprise networks or public Wi-Fi networks) are allocated unique prefixes via DHCPv6 Prefix Delegation (DHCPv6-PD), as specified in RFC 8415. | monolingualtext | ||||
STD:IETF:RFC9663$2a2576d4dcf7 | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9663$2a2576d4dcf7 | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9663$483c72ed3b44 | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9663$7b76d12b8747 | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | X. Ma | X. Ma | string | ||||
STD:IETF:RFC9663$9ecb9aab03ec | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | L. Colitti | L. Colitti | string | ||||
STD:IETF:RFC9663$9eeac02e6b66 | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | monolingualtext | ||||
STD:IETF:RFC9663$a905536191c7 | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9663$c307cba34d4d | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9663$cd31729b998d | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Linkova | J. Linkova | string | ||||
STD:IETF:RFC9663$edff291015df | IETF | STD:IETF:RFC9663 | Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9663 | https://www.rfc-editor.org/rfc/rfc9663 | url | ||||
STD:IETF:RFC9664$037f8551a44e | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9664 | https://www.rfc-editor.org/rfc/rfc9664 | url | ||||
STD:IETF:RFC9664$3eb39c32b861 | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Cheshire | S. Cheshire | string | ||||
STD:IETF:RFC9664$5c0e66ef7e13 | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9664$6a46844c5023 | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes an EDNS(0) option that can be used between DNS Update Requesters and authoritative DNS servers to include a lifetime (lease duration) in a DNS Update or DNS Update Response, allowing a server to garbage collect stale Resource Records that have been added by DNS Updates if they are not renewed. | This document describes an EDNS(0) option that can be used between DNS Update Requesters and authoritative DNS servers to include a lifetime (lease duration) in a DNS Update or DNS Update Response, allowing a server to garbage collect stale Resource Records that have been added by DNS Updates if they are not renewed. | monolingualtext | ||||
STD:IETF:RFC9664$735961aad907 | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9664$753b8ef4f2bb | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Lemon | T. Lemon | string | ||||
STD:IETF:RFC9664$7ac9a48eb22b | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9664$9d88277ec852 | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | An EDNS(0) Option to Negotiate Leases on DNS Updates | An EDNS(0) Option to Negotiate Leases on DNS Updates | monolingualtext | ||||
STD:IETF:RFC9664$d68848032384 | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9664$d68848032384 | IETF | STD:IETF:RFC9664 | An EDNS(0) Option to Negotiate Leases on DNS Updates | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9665$05254f398401 | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Service Registration Protocol (SRP) for DNS-based Service Discovery (DNS-SD) uses the standard DNS Update mechanism to enable DNS-SD using only unicast packets. This makes it possible to deploy DNS-SD without multicast, which greatly improves scalability and improves performance on networks where multicast service... | The Service Registration Protocol (SRP) for DNS-based Service Discovery (DNS-SD) uses the standard DNS Update mechanism to enable DNS-SD using only unicast packets. This makes it possible to deploy DNS-SD without multicast, which greatly improves scalability and improves performance on networks where multicast service... | monolingualtext | ||||
STD:IETF:RFC9665$3e9b8bf2c1f5 | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9665$3e9b8bf2c1f5 | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9665$5b862af9bb14 | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9665$7879defc371d | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Cheshire | S. Cheshire | string | ||||
STD:IETF:RFC9665$7b6b723072c0 | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9665$7f912eb309ba | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Service Registration Protocol for DNS-Based Service Discovery | Service Registration Protocol for DNS-Based Service Discovery | monolingualtext | ||||
STD:IETF:RFC9665$846138019088 | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9665 | https://www.rfc-editor.org/rfc/rfc9665 | url | ||||
STD:IETF:RFC9665$dbc4536a97de | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9665$f8972129e9dc | IETF | STD:IETF:RFC9665 | Service Registration Protocol for DNS-Based Service Discovery | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Lemon | T. Lemon | string | ||||
STD:IETF:RFC9666$0cf530653351 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | Area Proxy for IS-IS | Area Proxy for IS-IS | monolingualtext | ||||
STD:IETF:RFC9666$0f133635d1f9 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9666$1609dd5a039e | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | G. Mishra | G. Mishra | string | ||||
STD:IETF:RFC9666$365711a07cf5 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9666$39e17ac9a040 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9666 | https://www.rfc-editor.org/rfc/rfc9666 | url | ||||
STD:IETF:RFC9666$6f116cf0dce2 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Link-state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies to each other, thereby leading to scaling issues. To avoid such issues, this document discusses extensions to the IS-IS routing protocol that a... | Link-state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies to each other, thereby leading to scaling issues. To avoid such issues, this document discusses extensions to the IS-IS routing protocol that a... | monolingualtext | ||||
STD:IETF:RFC9666$7358cc9845ea | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | S. Chen | S. Chen | string | ||||
STD:IETF:RFC9666$73e650959065 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | V. Ilangovan | V. Ilangovan | string | ||||
STD:IETF:RFC9666$9afc8202da04 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9666$9afc8202da04 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9666$a38f86ec16ee | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | T. Li | T. Li | string | ||||
STD:IETF:RFC9666$bfe24e98f719 | IETF | STD:IETF:RFC9666 | Area Proxy for IS-IS | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9667$0d9b2fd17894 | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | T. Li | T. Li | string | ||||
STD:IETF:RFC9667$0ed7de8c75b2 | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9667$4ecf68c21405 | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9667$5761241810ce | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | S. Dontula | S. Dontula | string | ||||
STD:IETF:RFC9667$64805b1616d4 | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Routing with link-state protocols in dense network topologies can result in suboptimal convergence times due to the overhead associated with flooding. This can be addressed by decreasing the flooding topology so that it is less dense. This document discusses the problem in some depth and an architectural solution. Spe... | Routing with link-state protocols in dense network topologies can result in suboptimal convergence times due to the overhead associated with flooding. This can be addressed by decreasing the flooding topology so that it is less dense. This document discusses the problem in some depth and an architectural solution. Spe... | monolingualtext | ||||
STD:IETF:RFC9667$72a9f3f2145d | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9667 | https://www.rfc-editor.org/rfc/rfc9667 | url | ||||
STD:IETF:RFC9667$b2ad40194d8d | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | Dynamic Flooding on Dense Graphs | Dynamic Flooding on Dense Graphs | monolingualtext | ||||
STD:IETF:RFC9667$bf637fc390a4 | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | L. Jalil | L. Jalil | string | ||||
STD:IETF:RFC9667$da0daf94969a | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9667$da0daf94969a | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9667$de401ba51676 | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | H. Chen | H. Chen | string | ||||
STD:IETF:RFC9667$ea6ab37a7b5e | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | P. Psenak | P. Psenak | string | ||||
STD:IETF:RFC9667$fff5440e2770 | IETF | STD:IETF:RFC9667 | Dynamic Flooding on Dense Graphs | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9668$0591674f0596 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Tiloca | M. Tiloca | string | ||||
STD:IETF:RFC9668$415583b597a1 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Palombini | F. Palombini | string | ||||
STD:IETF:RFC9668$45a7e63ac35e | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Hristozov | S. Hristozov | string | ||||
STD:IETF:RFC9668$49901dc60d64 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The lightweight authenticated key exchange protocol Ephemeral Diffie-Hellman Over COSE (EDHOC) can be run over the Constrained Application Protocol (CoAP) and used by two peers to establish a Security Context for the security protocol Object Security for Constrained RESTful Environments (OSCORE). This document details... | The lightweight authenticated key exchange protocol Ephemeral Diffie-Hellman Over COSE (EDHOC) can be run over the Constrained Application Protocol (CoAP) and used by two peers to establish a Security Context for the security protocol Object Security for Constrained RESTful Environments (OSCORE). This document details... | monolingualtext | ||||
STD:IETF:RFC9668$549b9518f6e9 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9668$59f2c8c998af | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Selander | G. Selander | string | ||||
STD:IETF:RFC9668$70e7a99c6eb9 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | monolingualtext | ||||
STD:IETF:RFC9668$a2f48030fa68 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9668$a92bd856131f | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9668 | https://www.rfc-editor.org/rfc/rfc9668 | url | ||||
STD:IETF:RFC9668$c83768556023 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9668$c83768556023 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9668$d604ae868bdd | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9668$e8da29bd9806 | IETF | STD:IETF:RFC9668 | Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Höglund | R. Höglund | string | ||||
STD:IETF:RFC9669$0c0d00b6f88b | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | BPF Instruction Set Architecture (ISA) | BPF Instruction Set Architecture (ISA) | monolingualtext | ||||
STD:IETF:RFC9669$10417ed5f1b4 | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9669$231688fc6716 | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9669 | https://www.rfc-editor.org/rfc/rfc9669 | url | ||||
STD:IETF:RFC9669$2d75ce74e396 | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9669$2d75ce74e396 | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9669$4109fb3670b6 | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9669$5dd1dc4d15d9 | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | eBPF (which is no longer an acronym for anything), also commonly referred to as BPF, is a technology with origins in the Linux kernel that can run untrusted programs in a privileged context such as an operating system kernel. This document specifies the BPF instruction set architecture (ISA). | eBPF (which is no longer an acronym for anything), also commonly referred to as BPF, is a technology with origins in the Linux kernel that can run untrusted programs in a privileged context such as an operating system kernel. This document specifies the BPF instruction set architecture (ISA). | monolingualtext | ||||
STD:IETF:RFC9669$7126f478359b | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9669$91b7dd648b61 | IETF | STD:IETF:RFC9669 | BPF Instruction Set Architecture (ISA) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Thaler | D. Thaler | string | ||||
STD:IETF:RFC9670$0e7d4c718b25 | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies a data model for sharing data between users using the JSON Meta Application Protocol (JMAP). Future documents can reference this document when defining data types to support a consistent model of sharing. | This document specifies a data model for sharing data between users using the JSON Meta Application Protocol (JMAP). Future documents can reference this document when defining data types to support a consistent model of sharing. | monolingualtext | ||||
STD:IETF:RFC9670$396f314325b3 | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9670 | https://www.rfc-editor.org/rfc/rfc9670 | url | ||||
STD:IETF:RFC9670$51dd7f467b4c | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Jenkins | N. Jenkins | string | ||||
STD:IETF:RFC9670$789592c36768 | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9670$84668ec137f8 | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9670$84668ec137f8 | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9670$93d7efaf0f02 | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9670$a2c26cf2a955 | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | JSON Meta Application Protocol (JMAP) Sharing | JSON Meta Application Protocol (JMAP) Sharing | monolingualtext | ||||
STD:IETF:RFC9670$a768234bb904 | IETF | STD:IETF:RFC9670 | JSON Meta Application Protocol (JMAP) Sharing | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9671$043b0b2c6d2b | IETF | STD:IETF:RFC9671 | Sieve Email Filtering: Extension for Processing Calendar Attachments | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the "processcalendar" extension to the Sieve email filtering language. The "processcalendar" extension gives Sieve the ability to process machine-readable calendar data that is encapsulated in an email message using Multipurpose Internet Mail Extensions (MIME). | This document describes the "processcalendar" extension to the Sieve email filtering language. The "processcalendar" extension gives Sieve the ability to process machine-readable calendar data that is encapsulated in an email message using Multipurpose Internet Mail Extensions (MIME). | monolingualtext | ||||
STD:IETF:RFC9671$28ff06438903 | IETF | STD:IETF:RFC9671 | Sieve Email Filtering: Extension for Processing Calendar Attachments | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9671$28ff06438903 | IETF | STD:IETF:RFC9671 | Sieve Email Filtering: Extension for Processing Calendar Attachments | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9671$343e710d3456 | IETF | STD:IETF:RFC9671 | Sieve Email Filtering: Extension for Processing Calendar Attachments | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Sieve Email Filtering: Extension for Processing Calendar Attachments | Sieve Email Filtering: Extension for Processing Calendar Attachments | monolingualtext | ||||
STD:IETF:RFC9671$90705de00aad | IETF | STD:IETF:RFC9671 | Sieve Email Filtering: Extension for Processing Calendar Attachments | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9671$9ac58abcbe20 | IETF | STD:IETF:RFC9671 | Sieve Email Filtering: Extension for Processing Calendar Attachments | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Murchison | K. Murchison | string | ||||
STD:IETF:RFC9671$b465b24d6a4f | IETF | STD:IETF:RFC9671 | Sieve Email Filtering: Extension for Processing Calendar Attachments | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9671 | https://www.rfc-editor.org/rfc/rfc9671 | url |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.