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:RFC9317$4198cc9ccd77 | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9317$6ce676629e39 | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9317$79baffb203b8 | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Operational Considerations for Streaming Media | Operational Considerations for Streaming Media | monolingualtext | ||||
STD:IETF:RFC9317$7dbe273a31fe | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9317$8bac566c0d58 | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Holland | J. Holland | string | ||||
STD:IETF:RFC9317$90902d5fb5bd | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document provides an overview of operational networking and transport protocol issues that pertain to the quality of experience (QoE) when streaming video and other high-bitrate media over the Internet. This document explains the characteristics of streaming media delivery that have surprised network designers or... | This document provides an overview of operational networking and transport protocol issues that pertain to the quality of experience (QoE) when streaming video and other high-bitrate media over the Internet. This document explains the characteristics of streaming media delivery that have surprised network designers or... | monolingualtext | ||||
STD:IETF:RFC9317$ac3a0c53a606 | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9317 | https://www.rfc-editor.org/rfc/rfc9317 | url | ||||
STD:IETF:RFC9317$f2c3f664fb30 | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9317$f2c3f664fb30 | IETF | STD:IETF:RFC9317 | Operational Considerations for Streaming Media | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9318$15369792a42a | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9318$15369792a42a | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9318$176d385d9a26 | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | IAB Workshop Report: Measuring Network Quality for End-Users | IAB Workshop Report: Measuring Network Quality for End-Users | monolingualtext | ||||
STD:IETF:RFC9318$4e05cae52c72 | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Measuring Network Quality for End-Users workshop was held virtually by the Internet Architecture Board (IAB) on September 14-16, 2021. This report summarizes the workshop, the topics discussed, and some preliminary conclusions drawn at the end of the workshop. Note that this document is a report on the proceedings... | The Measuring Network Quality for End-Users workshop was held virtually by the Internet Architecture Board (IAB) on September 14-16, 2021. This report summarizes the workshop, the topics discussed, and some preliminary conclusions drawn at the end of the workshop. Note that this document is a report on the proceedings... | monolingualtext | ||||
STD:IETF:RFC9318$533bc45c7c2a | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9318$6c656e0289ff | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | O. Shapira | O. Shapira | string | ||||
STD:IETF:RFC9318$8172fc0a4f4e | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9318$dc1e511ca26a | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | W. Hardaker | W. Hardaker | string | ||||
STD:IETF:RFC9318$efacdaabcea8 | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9318$f300bbd38c36 | IETF | STD:IETF:RFC9318 | IAB Workshop Report: Measuring Network Quality for End-Users | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9318 | https://www.rfc-editor.org/rfc/rfc9318 | url | ||||
STD:IETF:RFC9319$30ef900db164 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | S. Goldberg | S. Goldberg | string | ||||
STD:IETF:RFC9319$363aaebf41c2 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document recommends ways to reduce the forged-origin hijack attack surface by prudently limiting the set of IP prefixes that are included in a Route Origin Authorization (ROA). One recommendation is to avoid using the maxLength attribute in ROAs except in some specific cases. The recommendations complement and e... | This document recommends ways to reduce the forged-origin hijack attack surface by prudently limiting the set of IP prefixes that are included in a Route Origin Authorization (ROA). One recommendation is to avoid using the maxLength attribute in ROAs except in some specific cases. The recommendations complement and e... | monolingualtext | ||||
STD:IETF:RFC9319$4d0161672f38 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | K. Sriram | K. Sriram | string | ||||
STD:IETF:RFC9319$4fd86f4fa3d0 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | Y. Gilad | Y. Gilad | string | ||||
STD:IETF:RFC9319$68ea7046f30e | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9319$7a2962bae884 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9319$8e1b3ec31255 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9319$a31d7fd585f2 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | monolingualtext | ||||
STD:IETF:RFC9319$a6438fd92464 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | B. Maddison | B. Maddison | string | ||||
STD:IETF:RFC9319$ba055f45f4ce | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9319 | https://www.rfc-editor.org/rfc/rfc9319 | url | ||||
STD:IETF:RFC9319$bf8af2a86c60 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | J. Snijders | J. Snijders | string | ||||
STD:IETF:RFC9319$d633fb0351e3 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9319$d633fb0351e3 | IETF | STD:IETF:RFC9319 | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9320$31a23661d380 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9320$35fdbb93383e | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J.-Y. Le Boudec | J.-Y. Le Boudec | string | ||||
STD:IETF:RFC9320$3a0a99c7b309 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9320$3a0a99c7b309 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9320$3b0ca007b044 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document presents a timing model for sources, destinations, and Deterministic Networking (DetNet) transit nodes. Using the model, it provides a methodology to compute end-to-end latency and backlog bounds for various queuing methods. The methodology can be used by the management and control planes and by resourc... | This document presents a timing model for sources, destinations, and Deterministic Networking (DetNet) transit nodes. Using the model, it provides a methodology to compute end-to-end latency and backlog bounds for various queuing methods. The methodology can be used by the management and control planes and by resourc... | monolingualtext | ||||
STD:IETF:RFC9320$564641ff05d0 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9320 | https://www.rfc-editor.org/rfc/rfc9320 | url | ||||
STD:IETF:RFC9320$75f7396f80bf | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | N. Finn | N. Finn | string | ||||
STD:IETF:RFC9320$8274a01be7df | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Mohammadpour | E. Mohammadpour | string | ||||
STD:IETF:RFC9320$92a1ce8eba3e | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9320$93a738075ec7 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Deterministic Networking (DetNet) Bounded Latency | Deterministic Networking (DetNet) Bounded Latency | monolingualtext | ||||
STD:IETF:RFC9320$c1eae06cff54 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Zhang | J. Zhang | string | ||||
STD:IETF:RFC9320$eff26f904060 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9320$f5f37f61b166 | IETF | STD:IETF:RFC9320 | Deterministic Networking (DetNet) Bounded Latency | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | B. Varga | B. Varga | string | ||||
STD:IETF:RFC9321$11f4ad3cd2e9 | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9321$1c18c5518ffa | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Electronic signatures have a limited lifespan with respect to the time period that they can be validated and determined to be authentic. The Signature Validation Token (SVT) defined in this specification provides evidence that asserts the validity of an electronic signature. The SVT is provided by a trusted authority... | Electronic signatures have a limited lifespan with respect to the time period that they can be validated and determined to be authentic. The Signature Validation Token (SVT) defined in this specification provides evidence that asserts the validity of an electronic signature. The SVT is provided by a trusted authority... | monolingualtext | ||||
STD:IETF:RFC9321$23d6c8b9e9a9 | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9321 | https://www.rfc-editor.org/rfc/rfc9321 | url | ||||
STD:IETF:RFC9321$35bc7b9ce5af | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | R. Housley | R. Housley | string | ||||
STD:IETF:RFC9321$49b67d01127b | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Signature Validation Token | Signature Validation Token | monolingualtext | ||||
STD:IETF:RFC9321$80b2226482b9 | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9321$80b2226482b9 | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9321$9f220551449b | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9321$abee21a927a2 | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9321$c33e41779807 | IETF | STD:IETF:RFC9321 | Signature Validation Token | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Santesson | S. Santesson | string | ||||
STD:IETF:RFC9322$786fc7edec62 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9322$7b4d486d3398 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9322$8ce8b312e487 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Gafni | B. Gafni | string | ||||
STD:IETF:RFC9322$9db1e43d62e9 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9322 | https://www.rfc-editor.org/rfc/rfc9322 | url | ||||
STD:IETF:RFC9322$a14111abae99 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | monolingualtext | ||||
STD:IETF:RFC9322$a4c8e4b7a73d | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9322$a55ee9b7c502 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Spiegel | M. Spiegel | string | ||||
STD:IETF:RFC9322$ab16aa3b6f1b | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In situ Operations, Administration, and Maintenance (IOAM) collects operational and telemetry information in packets while they traverse a path between two points in the network. This document defines two new flags in the IOAM Trace Option headers, specifically the Loopback and Active flags. | In situ Operations, Administration, and Maintenance (IOAM) collects operational and telemetry information in packets while they traverse a path between two points in the network. This document defines two new flags in the IOAM Trace Option headers, specifically the Loopback and Active flags. | monolingualtext | ||||
STD:IETF:RFC9322$afe9048a91a8 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9322$afe9048a91a8 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9322$b1b38cd5253d | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Mizrahi | T. Mizrahi | string | ||||
STD:IETF:RFC9322$d54c330a64a9 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Bhandari | S. Bhandari | string | ||||
STD:IETF:RFC9322$f06e2084d495 | IETF | STD:IETF:RFC9322 | In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Brockners | F. Brockners | string | ||||
STD:IETF:RFC9323$00beda80c55e | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a Cryptographic Message Syntax (CMS) protected content type for use with the Resource Public Key Infrastructure (RPKI) to carry a general-purpose listing of checksums (a 'checklist'). The objective is to allow for the creation of an attestation, termed an "RPKI Signed Checklist (RSC)", which cont... | This document defines a Cryptographic Message Syntax (CMS) protected content type for use with the Resource Public Key Infrastructure (RPKI) to carry a general-purpose listing of checksums (a 'checklist'). The objective is to allow for the creation of an attestation, termed an "RPKI Signed Checklist (RSC)", which cont... | monolingualtext | ||||
STD:IETF:RFC9323$08d85cfc8d43 | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A Profile for RPKI Signed Checklists (RSCs) | A Profile for RPKI Signed Checklists (RSCs) | monolingualtext | ||||
STD:IETF:RFC9323$5cc35c097f0c | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9323$5cc35c097f0c | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9323$5f095b6f60b9 | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Harrison | T. Harrison | string | ||||
STD:IETF:RFC9323$6b1dd80e4137 | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9323$6bd0202fb8f5 | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9323$90c31fe6ec9d | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9323 | https://www.rfc-editor.org/rfc/rfc9323 | url | ||||
STD:IETF:RFC9323$9b4c6d40a2ab | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9323$be9c07bb748b | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Maddison | B. Maddison | string | ||||
STD:IETF:RFC9323$d5d315289dd7 | IETF | STD:IETF:RFC9323 | A Profile for RPKI Signed Checklists (RSCs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Snijders | J. Snijders | string | ||||
STD:IETF:RFC9324$22ddde359b1a | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9324 | https://www.rfc-editor.org/rfc/rfc9324 | url | ||||
STD:IETF:RFC9324$6f6d49f7e7a8 | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Bush | R. Bush | string | ||||
STD:IETF:RFC9324$7cc167b48de0 | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Smith | P. Smith | string | ||||
STD:IETF:RFC9324$7fed25c76276 | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9324$b0ab9d08759e | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Patel | K. Patel | string | ||||
STD:IETF:RFC9324$b221322e9b69 | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9324$c42a50121baa | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Tinka | M. Tinka | string | ||||
STD:IETF:RFC9324$c5bc3a585b37 | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | monolingualtext | ||||
STD:IETF:RFC9324$cd88fbe4c55f | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | A BGP speaker performing policy based on the Resource Public Key Infrastructure (RPKI) should not issue route refresh to its neighbors because it has received new RPKI data. This document updates RFC 8481 by describing how to avoid doing so by either keeping a full Adj-RIB-In or saving paths dropped due to ROV (Route ... | A BGP speaker performing policy based on the Resource Public Key Infrastructure (RPKI) should not issue route refresh to its neighbors because it has received new RPKI data. This document updates RFC 8481 by describing how to avoid doing so by either keeping a full Adj-RIB-In or saving paths dropped due to ROV (Route ... | monolingualtext | ||||
STD:IETF:RFC9324$d7c2008b7b12 | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9324$f6d0436a6557 | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9324$f6d0436a6557 | IETF | STD:IETF:RFC9324 | Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9325$0b2a6b4cddd4 | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used to protect data exchanged over a wide range of application protocols and can also form the basis for secure transport protocols. Over the years, the industry has witnessed several serious attacks on TLS and DTLS, including attacks on t... | Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used to protect data exchanged over a wide range of application protocols and can also form the basis for secure transport protocols. Over the years, the industry has witnessed several serious attacks on TLS and DTLS, including attacks on t... | monolingualtext | ||||
STD:IETF:RFC9325$1173a2be3090 | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | T. Fossati | T. Fossati | string | ||||
STD:IETF:RFC9325$1906543293d9 | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9325$35c68d04f5e6 | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9325$35c68d04f5e6 | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9325$518256236622 | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC7525 | RFC7525 | wikibase-item | ||||
STD:IETF:RFC9325$73924aa2df4e | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9325 | https://www.rfc-editor.org/rfc/rfc9325 | url | ||||
STD:IETF:RFC9325$83304394be19 | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9325$cdb1a45e9fcb | IETF | STD:IETF:RFC9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) | monolingualtext |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.