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:RFC9788$df715ae793ee | IETF | STD:IETF:RFC9788 | Header Protection for Cryptographically Protected Email | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Header Protection for Cryptographically Protected Email | Header Protection for Cryptographically Protected Email | monolingualtext | ||||
STD:IETF:RFC9788$dfdc6577b0d8 | IETF | STD:IETF:RFC9788 | Header Protection for Cryptographically Protected Email | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9788$f0b001f48210 | IETF | STD:IETF:RFC9788 | Header Protection for Cryptographically Protected Email | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9788 | https://www.rfc-editor.org/rfc/rfc9788 | url | ||||
STD:IETF:RFC9789$065f5329c0b5 | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9789 | https://www.rfc-editor.org/rfc/rfc9789 | url | ||||
STD:IETF:RFC9789$14baa694e4b9 | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9789$20551d00c616 | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Li | T. Li | string | ||||
STD:IETF:RFC9789$38a4093f53a1 | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Bryant | S. Bryant | string | ||||
STD:IETF:RFC9789$5faedecda6d7 | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | MPLS Network Actions (MNAs) Framework | MPLS Network Actions (MNAs) Framework | monolingualtext | ||||
STD:IETF:RFC9789$75f7fcf28fcc | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Bocci | M. Bocci | string | ||||
STD:IETF:RFC9789$781f45fd438c | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | L. Andersson | L. Andersson | string | ||||
STD:IETF:RFC9789$7f6c8673093e | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes an architectural framework for MPLS Network Action (MNA) technologies. MNA technologies are used to indicate actions that impact the forwarding or other processing (such as monitoring) of the packet along the Label Switched Path (LSP) of the packet and to transfer any additional data needed for ... | This document describes an architectural framework for MPLS Network Action (MNA) technologies. MNA technologies are used to indicate actions that impact the forwarding or other processing (such as monitoring) of the packet along the Label Switched Path (LSP) of the packet and to transfer any additional data needed for ... | monolingualtext | ||||
STD:IETF:RFC9789$83661046aa00 | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9789$c7b82775cf9d | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9789$c7b82775cf9d | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9789$d25e26926752 | IETF | STD:IETF:RFC9789 | MPLS Network Actions (MNAs) Framework | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9790$166f6aa2d0bc | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Andersson | L. Andersson | string | ||||
STD:IETF:RFC9790$208bdbecd847 | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9790$2895d2fed4f1 | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9790$2f18e6d5e812 | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Bryant | S. Bryant | string | ||||
STD:IETF:RFC9790$696c4fc826a0 | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9790 | https://www.rfc-editor.org/rfc/rfc9790 | url | ||||
STD:IETF:RFC9790$7a0c3aea53fe | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9790$856285779ee2 | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document creates a new IANA registry (called the "Post-Stack First Nibble" registry) for the first nibble (4-bit field) immediately following an MPLS label stack. Furthermore, this document presents some requirements for registering new values and making the processing of MPLS packets easier and more robust. The ... | This document creates a new IANA registry (called the "Post-Stack First Nibble" registry) for the first nibble (4-bit field) immediately following an MPLS label stack. Furthermore, this document presents some requirements for registering new values and making the processing of MPLS packets easier and more robust. The ... | monolingualtext | ||||
STD:IETF:RFC9790$87f1ef83d63b | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Kompella | K. Kompella | string | ||||
STD:IETF:RFC9790$935027ccac7b | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Dong | J. Dong | string | ||||
STD:IETF:RFC9790$ab8d3e5b92aa | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9790$ab8d3e5b92aa | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9790$dd205cf4253a | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | monolingualtext | ||||
STD:IETF:RFC9790$f5a512a2cb84 | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9790$f9d3894b08c8 | IETF | STD:IETF:RFC9790 | IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Bocci | M. Bocci | string | ||||
STD:IETF:RFC9791$129c14c8aa9e | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9791$131efd42fd0f | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9791 | https://www.rfc-editor.org/rfc/rfc9791 | url | ||||
STD:IETF:RFC9791$1ca5770a0c37 | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9791$1ca5770a0c37 | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9791$1f9bfd9d221c | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Saad | T. Saad | string | ||||
STD:IETF:RFC9791$2ed2b87fe4a8 | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document presents use cases that have a common feature that may be addressed by encoding network action indicators and associated ancillary data within MPLS packets. There is community interest in extending the MPLS data plane to carry such indicators and ancillary data to address these use cases. The use cases d... | This document presents use cases that have a common feature that may be addressed by encoding network action indicators and associated ancillary data within MPLS packets. There is community interest in extending the MPLS data plane to carry such indicators and ancillary data to address these use cases. The use cases d... | monolingualtext | ||||
STD:IETF:RFC9791$46c794facd0b | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9791$51667c01cefa | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9791$61b73296d0d9 | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | K. Makhijani | K. Makhijani | string | ||||
STD:IETF:RFC9791$c9e1b2e3849b | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Use Cases for MPLS Network Action Indicators and Ancillary Data | Use Cases for MPLS Network Action Indicators and Ancillary Data | monolingualtext | ||||
STD:IETF:RFC9791$d773d84c332e | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | H. Song | H. Song | string | ||||
STD:IETF:RFC9791$ef8334eb36a4 | IETF | STD:IETF:RFC9791 | Use Cases for MPLS Network Action Indicators and Ancillary Data | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9792$159e5fe2eb44 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9792$159e5fe2eb44 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9792$45278a439daf | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9792$4564e54fdc96 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Psenak | P. Psenak | string | ||||
STD:IETF:RFC9792$4674ab3e1547 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9792$476851baae80 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9792$9c0dab5b7b0c | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Chen | R. Chen | string | ||||
STD:IETF:RFC9792$9d64af9e19bd | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9792$a803447f9168 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9792 | https://www.rfc-editor.org/rfc/rfc9792 | url | ||||
STD:IETF:RFC9792$e7f3bd6a1603 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Gong | L. Gong | string | ||||
STD:IETF:RFC9792$eb04f35fc898 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Each OSPF prefix can be advertised with an 8-bit field to indicate specific properties of that prefix. However, all the OSPFv3 Prefix Options bits have already been assigned, and only a few bits remain unassigned in the Flags field of the OSPFv2 Extended Prefix TLV. This document solves this problem by defining a vari... | Each OSPF prefix can be advertised with an 8-bit field to indicate specific properties of that prefix. However, all the OSPFv3 Prefix Options bits have already been assigned, and only a few bits remain unassigned in the Flags field of the OSPFv2 Extended Prefix TLV. This document solves this problem by defining a vari... | monolingualtext | ||||
STD:IETF:RFC9792$ecf611f3f1c9 | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Prefix Flag Extension for OSPFv2 and OSPFv3 | Prefix Flag Extension for OSPFv2 and OSPFv3 | monolingualtext | ||||
STD:IETF:RFC9792$f998a750c0bf | IETF | STD:IETF:RFC9792 | Prefix Flag Extension for OSPFv2 and OSPFv3 | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Zhao | D. Zhao | string | ||||
STD:IETF:RFC9793$04ee9300993d | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9793$04ee9300993d | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9793$1186b76057a6 | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Patel | K. Patel | string | ||||
STD:IETF:RFC9793$504b85d3986d | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Przygienda | T. Przygienda | string | ||||
STD:IETF:RFC9793$54ec1a40c353 | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9793$5b74d20e1109 | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Bit Index Explicit Replication (BIER) is a multicast forwarding architecture that doesn't require an explicit tree-building protocol and doesn't require intermediate routers to maintain per-tree multicast states. Some BIER-specific information and states, which are only in proportion to the number of BIER routers but ... | Bit Index Explicit Replication (BIER) is a multicast forwarding architecture that doesn't require an explicit tree-building protocol and doesn't require intermediate routers to maintain per-tree multicast states. Some BIER-specific information and states, which are only in proportion to the number of BIER routers but ... | monolingualtext | ||||
STD:IETF:RFC9793$9835988383d5 | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Chen | M. Chen | string | ||||
STD:IETF:RFC9793$a14fecd2e88e | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | X. Xu | X. Xu | string | ||||
STD:IETF:RFC9793$a447471c1d44 | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9793$b294a56e44b9 | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | BGP Extensions for Bit Index Explicit Replication (BIER) | BGP Extensions for Bit Index Explicit Replication (BIER) | monolingualtext | ||||
STD:IETF:RFC9793$cde318c9503c | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | IJ. Wijnands | IJ. Wijnands | string | ||||
STD:IETF:RFC9793$e8e01d25878e | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9793$ef911556510e | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9793 | https://www.rfc-editor.org/rfc/rfc9793 | url | ||||
STD:IETF:RFC9793$f69266d48022 | IETF | STD:IETF:RFC9793 | BGP Extensions for Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9794$0b2f91600294 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Terminology for Post-Quantum Traditional Hybrid Schemes | Terminology for Post-Quantum Traditional Hybrid Schemes | monolingualtext | ||||
STD:IETF:RFC9794$18664f090382 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | B. Hale | B. Hale | string | ||||
STD:IETF:RFC9794$74feedb2b2c4 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9794$88ac549f78d9 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | One aspect of the transition to post-quantum algorithms in cryptographic protocols is the development of hybrid schemes that incorporate both post-quantum and traditional asymmetric algorithms. This document defines terminology for such schemes. It is intended to be used as a reference and, hopefully, to ensure consi... | One aspect of the transition to post-quantum algorithms in cryptographic protocols is the development of hybrid schemes that incorporate both post-quantum and traditional asymmetric algorithms. This document defines terminology for such schemes. It is intended to be used as a reference and, hopefully, to ensure consi... | monolingualtext | ||||
STD:IETF:RFC9794$930b288ee589 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9794$99b0938ea52e | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9794$b12cd54f6f60 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9794 | https://www.rfc-editor.org/rfc/rfc9794 | url | ||||
STD:IETF:RFC9794$b4bb4892b0ce | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Parsons | M. Parsons | string | ||||
STD:IETF:RFC9794$c88d90a14b93 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9794$c88d90a14b93 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9794$d1f33514dac8 | IETF | STD:IETF:RFC9794 | Terminology for Post-Quantum Traditional Hybrid Schemes | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | F. Driscoll | F. Driscoll | string | ||||
STD:IETF:RFC9795$0d0f6bdf678f | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9795$0d0f6bdf678f | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9795$1ac6f5b4589b | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9795$1bad3cd74a86 | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9795$bcb94f69bc91 | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Wendt | C. Wendt | string | ||||
STD:IETF:RFC9795$c6172e8818d6 | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9795$d265135f413b | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document extends Personal Assertion Token (PASSporT), a token for conveying cryptographically signed call information about personal communications, to include rich metadata about a call and caller that can be signed and integrity protected, transmitted, and subsequently rendered to the called party. This framewo... | This document extends Personal Assertion Token (PASSporT), a token for conveying cryptographically signed call information about personal communications, to include rich metadata about a call and caller that can be signed and integrity protected, transmitted, and subsequently rendered to the called party. This framewo... | monolingualtext | ||||
STD:IETF:RFC9795$d97965db6bfe | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Peterson | J. Peterson | string | ||||
STD:IETF:RFC9795$e6f7ae292298 | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9795 | https://www.rfc-editor.org/rfc/rfc9795 | url | ||||
STD:IETF:RFC9795$f5f342cdbfa9 | IETF | STD:IETF:RFC9795 | Personal Assertion Token (PASSporT) Extension for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Personal Assertion Token (PASSporT) Extension for Rich Call Data | Personal Assertion Token (PASSporT) Extension for Rich Call Data | monolingualtext | ||||
STD:IETF:RFC9796$27c6298fa439 | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Peterson | J. Peterson | string | ||||
STD:IETF:RFC9796$350e50436ca5 | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9796$350e50436ca5 | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9796$4e86a5fa5b05 | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Wendt | C. Wendt | string | ||||
STD:IETF:RFC9796$6c28903f3c6b | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies a usage of the SIP Call-Info header field that incorporates Rich Call Data (RCD) associated with the identity of the originating party in order to provide to the terminating party a description of the caller (including details about the reason for the session). RCD includes information about the... | This document specifies a usage of the SIP Call-Info header field that incorporates Rich Call Data (RCD) associated with the identity of the originating party in order to provide to the terminating party a description of the caller (including details about the reason for the session). RCD includes information about the... | monolingualtext | ||||
STD:IETF:RFC9796$737aff5784f6 | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9796 | https://www.rfc-editor.org/rfc/rfc9796 | url | ||||
STD:IETF:RFC9796$8142296c2658 | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9796$8bb255560402 | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9796$98d4fbec160a | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9796$a4c2adbc3bb0 | IETF | STD:IETF:RFC9796 | SIP Call-Info Parameters for Rich Call Data | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | SIP Call-Info Parameters for Rich Call Data | SIP Call-Info Parameters for Rich Call Data | monolingualtext | ||||
STD:IETF:RFC9797$03fd721e02a7 | IETF | STD:IETF:RFC9797 | Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.