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:RFC9626$217128879ae6 | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | S. Nandakumar | S. Nandakumar | string | ||||
STD:IETF:RFC9626$54a0577ecb14 | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | Video Frame Marking RTP Header Extension | Video Frame Marking RTP Header Extension | monolingualtext | ||||
STD:IETF:RFC9626$5a97bbf35a71 | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9626$818e2a38dcb0 | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9626$87fea46d6f7a | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9626$898dd8a4d260 | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | M. Zanaty | M. Zanaty | string | ||||
STD:IETF:RFC9626$a6ebd99e25c6 | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a Video Frame Marking RTP header extension used to convey information about video frames that is critical for error recovery and packet forwarding in RTP middleboxes or network nodes. It is most useful when media is encrypted and essential when the middlebox or node has no access to the media d... | This document describes a Video Frame Marking RTP header extension used to convey information about video frames that is critical for error recovery and packet forwarding in RTP middleboxes or network nodes. It is most useful when media is encrypted and essential when the middlebox or node has no access to the media d... | monolingualtext | ||||
STD:IETF:RFC9626$be832e87c2e5 | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9626$be832e87c2e5 | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9626$c70b498c67fb | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9626 | https://www.rfc-editor.org/rfc/rfc9626 | url | ||||
STD:IETF:RFC9626$da63fdaf162a | IETF | STD:IETF:RFC9626 | Video Frame Marking RTP Header Extension | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | E. Berger | E. Berger | string | ||||
STD:IETF:RFC9627$162d50d3dec5 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9627$1864511b4417 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Flodman | M. Flodman | string | ||||
STD:IETF:RFC9627$3a3cefd004f2 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The Layer Refresh Request (LRR) RTCP Feedback Message | The Layer Refresh Request (LRR) RTCP Feedback Message | monolingualtext | ||||
STD:IETF:RFC9627$43dd14325772 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Holmer | S. Holmer | string | ||||
STD:IETF:RFC9627$52587d8ad489 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9627 | https://www.rfc-editor.org/rfc/rfc9627 | url | ||||
STD:IETF:RFC9627$6ac4630ed1b0 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9627$8b64dc00801c | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This memo describes the RTCP Payload-Specific Feedback Message Layer Refresh Request (LRR), which can be used to request a state refresh of one or more substreams of a layered media stream. This document also defines its use with several RTP payloads for scalable media formats. | This memo describes the RTCP Payload-Specific Feedback Message Layer Refresh Request (LRR), which can be used to request a state refresh of one or more substreams of a layered media stream. This document also defines its use with several RTP payloads for scalable media formats. | monolingualtext | ||||
STD:IETF:RFC9627$980fed47fea8 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Uberti | J. Uberti | string | ||||
STD:IETF:RFC9627$afed6f35ab51 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9627$afed6f35ab51 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9627$e60eaaa53b81 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Lennox | J. Lennox | string | ||||
STD:IETF:RFC9627$e6ed38f290d2 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Hong | D. Hong | string | ||||
STD:IETF:RFC9627$edeede9cff26 | IETF | STD:IETF:RFC9627 | The Layer Refresh Request (LRR) RTCP Feedback Message | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9628$0d1564d3a704 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9628$0ddc23375eb9 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This specification describes an RTP payload format for the VP9 video codec. The payload format has wide applicability as it supports applications from low bitrate peer-to-peer usage to high bitrate video conferences. It includes provisions for temporal and spatial scalability. | This specification describes an RTP payload format for the VP9 video codec. The payload format has wide applicability as it supports applications from low bitrate peer-to-peer usage to high bitrate video conferences. It includes provisions for temporal and spatial scalability. | monolingualtext | ||||
STD:IETF:RFC9628$2754ce896df5 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9628$2754ce896df5 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9628$3933bf9af9b1 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Hong | D. Hong | string | ||||
STD:IETF:RFC9628$3cac94f668b8 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9628$6061efe3a6f4 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Flodman | M. Flodman | string | ||||
STD:IETF:RFC9628$68774ec793dc | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Uberti | J. Uberti | string | ||||
STD:IETF:RFC9628$c05abc2b28ac | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | RTP Payload Format for VP9 Video | RTP Payload Format for VP9 Video | monolingualtext | ||||
STD:IETF:RFC9628$cec8fd249a3c | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Holmer | S. Holmer | string | ||||
STD:IETF:RFC9628$d18eb23e74c9 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9628 | https://www.rfc-editor.org/rfc/rfc9628 | url | ||||
STD:IETF:RFC9628$f2accbdaaeb4 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9628$f5ed21522e89 | IETF | STD:IETF:RFC9628 | RTP Payload Format for VP9 Video | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Lennox | J. Lennox | string | ||||
STD:IETF:RFC9629$36c21c4f797b | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9629$37b889bf91db | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | monolingualtext | ||||
STD:IETF:RFC9629$4aa0f75586cc | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9629$63e15304a724 | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9629$746e0f918137 | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Gray | J. Gray | string | ||||
STD:IETF:RFC9629$8f2d85e6e4fe | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9629 | https://www.rfc-editor.org/rfc/rfc9629 | url | ||||
STD:IETF:RFC9629$9144eefb8ca2 | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9629$9144eefb8ca2 | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9629$a01056d84a19 | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Housley | R. Housley | string | ||||
STD:IETF:RFC9629$cb7886f46739 | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Cryptographic Message Syntax (CMS) supports key transport and key agreement algorithms. In recent years, cryptographers have been specifying Key Encapsulation Mechanism (KEM) algorithms, including quantum-secure KEM algorithms. This document defines conventions for the use of KEM algorithms by the originator and ... | The Cryptographic Message Syntax (CMS) supports key transport and key agreement algorithms. In recent years, cryptographers have been specifying Key Encapsulation Mechanism (KEM) algorithms, including quantum-secure KEM algorithms. This document defines conventions for the use of KEM algorithms by the originator and ... | monolingualtext | ||||
STD:IETF:RFC9629$cd3b22b4fa47 | IETF | STD:IETF:RFC9629 | Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Okubo | T. Okubo | string | ||||
STD:IETF:RFC9630$39ba13cce924 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9630$39ba13cce924 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9630$529ca7159fc9 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9630$53e14b333b5a | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9630$7c883b6256fd | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | monolingualtext | ||||
STD:IETF:RFC9630$8bd649849519 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Song | H. Song | string | ||||
STD:IETF:RFC9630$8d34d76a0b52 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mishra | G. Mishra | string | ||||
STD:IETF:RFC9630$9335f64f7ef8 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9630$a83df87b8f17 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Zhou | T. Zhou | string | ||||
STD:IETF:RFC9630$a90e57d4ab30 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Asaeda | H. Asaeda | string | ||||
STD:IETF:RFC9630$d27cee28de79 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies two solutions to meet the requirements of on-path telemetry for multicast traffic using IOAM. While IOAM is advantageous for multicast traffic telemetry, some unique challenges are present. This document provides the solutions based on the IOAM trace option and direct export option to support ... | This document specifies two solutions to meet the requirements of on-path telemetry for multicast traffic using IOAM. While IOAM is advantageous for multicast traffic telemetry, some unique challenges are present. This document provides the solutions based on the IOAM trace option and direct export option to support ... | monolingualtext | ||||
STD:IETF:RFC9630$dfe2baefde91 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9630$e3442ac66487 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9630 | https://www.rfc-editor.org/rfc/rfc9630 | url | ||||
STD:IETF:RFC9630$f39471057533 | IETF | STD:IETF:RFC9630 | Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. McBride | M. McBride | string | ||||
STD:IETF:RFC9631$0b139b51ee3d | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes an experiment in which two new IPv6 Routing headers are implemented and deployed. Collectively, they are called the Compact Routing Header (CRH). Individually, they are called CRH-16 and CRH-32. One purpose of this experiment is to demonstrate that the CRH can be implemented and deployed in a p... | This document describes an experiment in which two new IPv6 Routing headers are implemented and deployed. Collectively, they are called the Compact Routing Header (CRH). Individually, they are called CRH-16 and CRH-32. One purpose of this experiment is to demonstrate that the CRH can be implemented and deployed in a p... | monolingualtext | ||||
STD:IETF:RFC9631$1c55b6ac239a | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9631$1c55b6ac239a | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9631$4d26c42f3984 | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9631 | https://www.rfc-editor.org/rfc/rfc9631 | url | ||||
STD:IETF:RFC9631$523e53a68e7c | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | A. Alston | A. Alston | string | ||||
STD:IETF:RFC9631$56ec62fc8e43 | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | D. Henriques | D. Henriques | string | ||||
STD:IETF:RFC9631$577eb6062a55 | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | L. Jalil | L. Jalil | string | ||||
STD:IETF:RFC9631$70d24c74cffa | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | Y. Kamite | Y. Kamite | string | ||||
STD:IETF:RFC9631$8d46ab9b5c5a | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9631$bcb682aa0eef | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | The IPv6 Compact Routing Header (CRH) | The IPv6 Compact Routing Header (CRH) | monolingualtext | ||||
STD:IETF:RFC9631$d19401e06c4f | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | R. Bonica | R. Bonica | string | ||||
STD:IETF:RFC9631$d88651d46aef | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9631$dfa4494958f3 | IETF | STD:IETF:RFC9631 | The IPv6 Compact Routing Header (CRH) | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9632$0d082eee75d8 | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Kumari | W. Kumari | string | ||||
STD:IETF:RFC9632$21cd72e84de6 | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Bush | R. Bush | string | ||||
STD:IETF:RFC9632$26ee1b47ff2a | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies how to augment the Routing Policy Specification Language (RPSL) inetnum: class to refer specifically to geofeed comma-separated values (CSV) data files and describes an optional scheme that uses the Resource Public Key Infrastructure (RPKI) to authenticate the geofeed data files. This document ... | This document specifies how to augment the Routing Policy Specification Language (RPSL) inetnum: class to refer specifically to geofeed comma-separated values (CSV) data files and describes an optional scheme that uses the Resource Public Key Infrastructure (RPKI) to authenticate the geofeed data files. This document ... | monolingualtext | ||||
STD:IETF:RFC9632$2f52da6cfefe | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9632$849b161f9843 | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC9092 | RFC9092 | wikibase-item | ||||
STD:IETF:RFC9632$98c358b40c3f | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9632$98c358b40c3f | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9632$cc9830e7d277 | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Candela | M. Candela | string | ||||
STD:IETF:RFC9632$e252c5925fa3 | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9632 | https://www.rfc-editor.org/rfc/rfc9632 | url | ||||
STD:IETF:RFC9632$e94815ebf031 | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9632$ed9daa5e90c8 | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Housley | R. Housley | string | ||||
STD:IETF:RFC9632$f9c5041b8d17 | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Finding and Using Geofeed Data | Finding and Using Geofeed Data | monolingualtext | ||||
STD:IETF:RFC9632$fb9530909f7a | IETF | STD:IETF:RFC9632 | Finding and Using Geofeed Data | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9633$0e302a7c8509 | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9633$3eb549aea38c | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Deterministic Networking (DetNet) YANG Data Model | Deterministic Networking (DetNet) YANG Data Model | monolingualtext | ||||
STD:IETF:RFC9633$47a9420296da | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9633 | https://www.rfc-editor.org/rfc/rfc9633 | url | ||||
STD:IETF:RFC9633$872ee4e6deb9 | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9633$b1f9f29e4856 | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Fedyk | D. Fedyk | string | ||||
STD:IETF:RFC9633$cf1c7baf24e2 | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | X. Geng | X. Geng | string | ||||
STD:IETF:RFC9633$d90684bcdd4d | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document contains the specification for the Deterministic Networking (DetNet) YANG data model for configuration and operational data for DetNet flows. The model allows the provisioning of an end-to-end DetNet service on devices along the path without depending on any signaling protocol. It also specifies operation... | This document contains the specification for the Deterministic Networking (DetNet) YANG data model for configuration and operational data for DetNet flows. The model allows the provisioning of an end-to-end DetNet service on devices along the path without depending on any signaling protocol. It also specifies operation... | monolingualtext | ||||
STD:IETF:RFC9633$e6bfb885d2e7 | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. Ryoo | Y. Ryoo | string | ||||
STD:IETF:RFC9633$e8b6bbf40f08 | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Li | Z. Li | string | ||||
STD:IETF:RFC9633$ea345f25daae | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9633$ea345f25daae | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9633$face9aad9a66 | IETF | STD:IETF:RFC9633 | Deterministic Networking (DetNet) YANG Data Model | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Rahman | R. Rahman | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.