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:RFC9573$0ad6d2dce27d | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9573$44fbb4a69fd3 | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | MVPN/EVPN Tunnel Aggregation with Common Labels | MVPN/EVPN Tunnel Aggregation with Common Labels | monolingualtext | ||||
STD:IETF:RFC9573$4bdd7ea64969 | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9573$4bdd7ea64969 | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9573$4c6acb4b1fef | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9573$b9a751aaf76f | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Multicast VPN (MVPN) specifications allow a single Point-to-Multipoint (P2MP) tunnel to carry traffic of multiple IP VPNs (referred to as VPNs in this document). The EVPN specifications allow a single P2MP tunnel to carry traffic of multiple Broadcast Domains (BDs). These features require the ingress router of th... | The Multicast VPN (MVPN) specifications allow a single Point-to-Multipoint (P2MP) tunnel to carry traffic of multiple IP VPNs (referred to as VPNs in this document). The EVPN specifications allow a single P2MP tunnel to carry traffic of multiple Broadcast Domains (BDs). These features require the ingress router of th... | monolingualtext | ||||
STD:IETF:RFC9573$bb73c363762e | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9573$be69389515a3 | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Li | Z. Li | string | ||||
STD:IETF:RFC9573$c003481dab89 | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Rosen | E. Rosen | string | ||||
STD:IETF:RFC9573$cab3cb92c820 | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Lin | W. Lin | string | ||||
STD:IETF:RFC9573$e2d8ed3394df | IETF | STD:IETF:RFC9573 | MVPN/EVPN Tunnel Aggregation with Common Labels | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9574$069a50101d75 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9574 | https://www.rfc-editor.org/rfc/rfc9574 | url | ||||
STD:IETF:RFC9574$1a7992e31772 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9574$1ff423bd5c5c | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | monolingualtext | ||||
STD:IETF:RFC9574$25ec04385cf2 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9574$46b090caf244 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sathappan | S. Sathappan | string | ||||
STD:IETF:RFC9574$4eb7b008a129 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9574$6876fb96a115 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9574$6a05c5a84a8a | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Lin | W. Lin | string | ||||
STD:IETF:RFC9574$6c2378eb4600 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Katiyar | M. Katiyar | string | ||||
STD:IETF:RFC9574$974d3adeaa94 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Network Virtualization Overlay (NVO) networks using Ethernet VPNs (EVPNs) as their control plane may use trees based on ingress replication or Protocol Independent Multicast (PIM) to convey the overlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIM provides an efficient solution that prevents sending mult... | Network Virtualization Overlay (NVO) networks using Ethernet VPNs (EVPNs) as their control plane may use trees based on ingress replication or Protocol Independent Multicast (PIM) to convey the overlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIM provides an efficient solution that prevents sending mult... | monolingualtext | ||||
STD:IETF:RFC9574$ad0987626936 | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sajassi | A. Sajassi | string | ||||
STD:IETF:RFC9574$f952902bfb5a | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9574$f952902bfb5a | IETF | STD:IETF:RFC9574 | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9575$3725677c787e | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Moskowitz | R. Moskowitz | string | ||||
STD:IETF:RFC9575$653f0a151b47 | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Card | S. Card | string | ||||
STD:IETF:RFC9575$74ef85b3cc4a | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9575 | https://www.rfc-editor.org/rfc/rfc9575 | url | ||||
STD:IETF:RFC9575$8001faf9b75c | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9575$97582b8ffd95 | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9575$a78e02cbc9ea | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9575$a78e02cbc9ea | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9575$b03d1402a021 | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | monolingualtext | ||||
STD:IETF:RFC9575$da0e5c901053 | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Wiethuechter | A. Wiethuechter | string | ||||
STD:IETF:RFC9575$dc310c6fab93 | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Drone Remote Identification Protocol (DRIP), plus trust policies and periodic access to registries, augments Unmanned Aircraft System (UAS) Remote Identification (RID), enabling local real-time assessment of trustworthiness of received RID messages and observed UAS, even by Observers lacking Internet access. This ... | The Drone Remote Identification Protocol (DRIP), plus trust policies and periodic access to registries, augments Unmanned Aircraft System (UAS) Remote Identification (RID), enabling local real-time assessment of trustworthiness of received RID messages and observed UAS, even by Observers lacking Internet access. This ... | monolingualtext | ||||
STD:IETF:RFC9575$ecd0c71e51e0 | IETF | STD:IETF:RFC9575 | DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9576$13efb50adfb6 | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9576$13efb50adfb6 | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9576$422d028e00aa | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9576$42a1a977f9fe | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Davidson | A. Davidson | string | ||||
STD:IETF:RFC9576$4719237c439f | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9576 | https://www.rfc-editor.org/rfc/rfc9576 | url | ||||
STD:IETF:RFC9576$47aecacddf52 | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9576$5e45f1e51c61 | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. A. Wood | C. A. Wood | string | ||||
STD:IETF:RFC9576$a3575c331d0c | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | The Privacy Pass Architecture | The Privacy Pass Architecture | monolingualtext | ||||
STD:IETF:RFC9576$c6a90bc6c415 | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies the Privacy Pass architecture and requirements for its constituent protocols used for authorization based on privacy-preserving authentication mechanisms. It describes the conceptual model of Privacy Pass and its protocols, its security and privacy goals, practical deployment models, and recomm... | This document specifies the Privacy Pass architecture and requirements for its constituent protocols used for authorization based on privacy-preserving authentication mechanisms. It describes the conceptual model of Privacy Pass and its protocols, its security and privacy goals, practical deployment models, and recomm... | monolingualtext | ||||
STD:IETF:RFC9576$ca6c2121e884 | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Iyengar | J. Iyengar | string | ||||
STD:IETF:RFC9576$d3374f83c2a2 | IETF | STD:IETF:RFC9576 | The Privacy Pass Architecture | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9577$117718ec38c8 | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9577$266620735ad9 | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. A. Wood | C. A. Wood | string | ||||
STD:IETF:RFC9577$38e123daba78 | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The Privacy Pass HTTP Authentication Scheme | The Privacy Pass HTTP Authentication Scheme | monolingualtext | ||||
STD:IETF:RFC9577$653707f4821c | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9577$653707f4821c | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9577$7e34af3446dc | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9577$b2bd4a0e0666 | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9577$bca7dc50025f | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Valdez | S. Valdez | string | ||||
STD:IETF:RFC9577$f158ad220c0b | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines an HTTP authentication scheme for Privacy Pass, a privacy-preserving authentication mechanism used for authorization. The authentication scheme specified in this document can be used by Clients to redeem Privacy Pass tokens with an Origin. It can also be used by Origins to challenge Clients to p... | This document defines an HTTP authentication scheme for Privacy Pass, a privacy-preserving authentication mechanism used for authorization. The authentication scheme specified in this document can be used by Clients to redeem Privacy Pass tokens with an Origin. It can also be used by Origins to challenge Clients to p... | monolingualtext | ||||
STD:IETF:RFC9577$fcf0c9b6f62d | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9577 | https://www.rfc-editor.org/rfc/rfc9577 | url | ||||
STD:IETF:RFC9577$ffb56e879023 | IETF | STD:IETF:RFC9577 | The Privacy Pass HTTP Authentication Scheme | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9578$0b1c439f19af | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Davidson | A. Davidson | string | ||||
STD:IETF:RFC9578$0ebd3401627f | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9578 | https://www.rfc-editor.org/rfc/rfc9578 | url | ||||
STD:IETF:RFC9578$1f937f433fbf | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9578$69c517058630 | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Celi | S. Celi | string | ||||
STD:IETF:RFC9578$70384c3932aa | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9578$70384c3932aa | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9578$7362aaf49927 | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Privacy Pass Issuance Protocols | Privacy Pass Issuance Protocols | monolingualtext | ||||
STD:IETF:RFC9578$8fb60fc3f68f | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. A. Wood | C. A. Wood | string | ||||
STD:IETF:RFC9578$9a1771507e9b | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9578$9a6a5d387903 | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Valdez | S. Valdez | string | ||||
STD:IETF:RFC9578$cb883902c9b7 | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies two variants of the two-message issuance protocol for Privacy Pass tokens: one that produces tokens that are privately verifiable using the Issuer Private Key and one that produces tokens that are publicly verifiable using the Issuer Public Key. Instances of "issuance protocol" and "issuance pr... | This document specifies two variants of the two-message issuance protocol for Privacy Pass tokens: one that produces tokens that are privately verifiable using the Issuer Private Key and one that produces tokens that are publicly verifiable using the Issuer Public Key. Instances of "issuance protocol" and "issuance pr... | monolingualtext | ||||
STD:IETF:RFC9578$cdb34ac81b7f | IETF | STD:IETF:RFC9578 | Privacy Pass Issuance Protocols | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9579$1da3fd562410 | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | monolingualtext | ||||
STD:IETF:RFC9579$4eb6df10dc5c | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies additions and amendments to RFCs 7292 and 8018. It defines a way to use the Password-Based Message Authentication Code 1 (PBMAC1), defined in RFC 8018, inside the PKCS #12 syntax. The purpose of this specification is to permit the use of more modern Password-Based Key Derivation Functions (PBK... | This document specifies additions and amendments to RFCs 7292 and 8018. It defines a way to use the Password-Based Message Authentication Code 1 (PBMAC1), defined in RFC 8018, inside the PKCS #12 syntax. The purpose of this specification is to permit the use of more modern Password-Based Key Derivation Functions (PBK... | monolingualtext | ||||
STD:IETF:RFC9579$674c2d15f239 | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9579$674c2d15f239 | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9579$9903adcea375 | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9579 | https://www.rfc-editor.org/rfc/rfc9579 | url | ||||
STD:IETF:RFC9579$9d74e3615164 | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9579$bca817d6d19d | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | H. Kario | H. Kario | string | ||||
STD:IETF:RFC9579$e7b9fe612180 | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9579$e895328faf3a | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P156 | followed by | STD:IETF:RFC9879 | RFC9879 | wikibase-item | ||||
STD:IETF:RFC9579$f19e37b2768d | IETF | STD:IETF:RFC9579 | Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9580$022d926bde99 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. Niibe | Y. Niibe | string | ||||
STD:IETF:RFC9580$0749b402ec89 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9580$075dbc07644e | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC4880 | RFC4880 | wikibase-item | ||||
STD:IETF:RFC9580$0dbf4bff2723 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC6637 | RFC6637 | wikibase-item | ||||
STD:IETF:RFC9580$20eb88ca0bcd | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9580$20eb88ca0bcd | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9580$404cc50159e1 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9580$4f65931d5c07 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC5581 | RFC5581 | wikibase-item | ||||
STD:IETF:RFC9580$5bb80f078700 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Winter | J. Winter | string | ||||
STD:IETF:RFC9580$83c792859d9b | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Wouters | P. Wouters | string | ||||
STD:IETF:RFC9580$9c418ea7a0ad | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies the message formats used in OpenPGP. OpenPGP provides encryption with public key or symmetric cryptographic algorithms, digital signatures, compression, and key management. This document is maintained in order to publish all necessary information needed to develop interoperable applications bas... | This document specifies the message formats used in OpenPGP. OpenPGP provides encryption with public key or symmetric cryptographic algorithms, digital signatures, compression, and key management. This document is maintained in order to publish all necessary information needed to develop interoperable applications bas... | monolingualtext | ||||
STD:IETF:RFC9580$b16309e00a87 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | OpenPGP | OpenPGP | monolingualtext | ||||
STD:IETF:RFC9580$cc7b0c754ec3 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9580$f360fcd27087 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Huigens | D. Huigens | string | ||||
STD:IETF:RFC9580$f88038a40122 | IETF | STD:IETF:RFC9580 | OpenPGP | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9580 | https://www.rfc-editor.org/rfc/rfc9580 | url | ||||
STD:IETF:RFC9581$1ec313f5afa5 | IETF | STD:IETF:RFC9581 | Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period | Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period | monolingualtext | ||||
STD:IETF:RFC9581$2621b1654022 | IETF | STD:IETF:RFC9581 | Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Bormann | C. Bormann | string | ||||
STD:IETF:RFC9581$52bf38dd0823 | IETF | STD:IETF:RFC9581 | Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9581$6c0f9d137569 | IETF | STD:IETF:RFC9581 | Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9581$76485aa5568d | IETF | STD:IETF:RFC9581 | Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9581 | https://www.rfc-editor.org/rfc/rfc9581 | url | ||||
STD:IETF:RFC9581$8d49a01ca5b8 | IETF | STD:IETF:RFC9581 | Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.