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:RFC9325$d7eed3f372cd | 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 | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9325$e975bcb83b1c | 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 | P. Saint-Andre | P. Saint-Andre | string | ||||
STD:IETF:RFC9325$fa90a984f2ba | 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 | Y. Sheffer | Y. Sheffer | string | ||||
STD:IETF:RFC9326$038afa7fbc4b | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9326 | https://www.rfc-editor.org/rfc/rfc9326 | url | ||||
STD:IETF:RFC9326$330fa1fbac2d | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9326$36c555c46e2e | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Mizrahi | T. Mizrahi | string | ||||
STD:IETF:RFC9326$6bb27bc1189e | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9326$6bb27bc1189e | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9326$7660a5a6d5d8 | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9326$8a9959e018ce | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9326$a0b735317275 | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Gafni | B. Gafni | string | ||||
STD:IETF:RFC9326$ae87b5c2e2b9 | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Bhandari | S. Bhandari | string | ||||
STD:IETF:RFC9326$becd893694d9 | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In situ Operations, Administration, and Maintenance (IOAM) is used for recording and collecting operational and telemetry information. Specifically, IOAM allows telemetry data to be pushed into data packets while they traverse the network. This document introduces a new IOAM option type (denoted IOAM-Option-Type) cal... | In situ Operations, Administration, and Maintenance (IOAM) is used for recording and collecting operational and telemetry information. Specifically, IOAM allows telemetry data to be pushed into data packets while they traverse the network. This document introduces a new IOAM option type (denoted IOAM-Option-Type) cal... | monolingualtext | ||||
STD:IETF:RFC9326$cb73c556e311 | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Song | H. Song | string | ||||
STD:IETF:RFC9326$ea7fd0dfc841 | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Brockners | F. Brockners | string | ||||
STD:IETF:RFC9326$ed2cf84ba25b | IETF | STD:IETF:RFC9326 | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | monolingualtext | ||||
STD:IETF:RFC9327$09989226937e | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9327 | https://www.rfc-editor.org/rfc/rfc9327 | url | ||||
STD:IETF:RFC9327$3cf5d21eda5d | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9327$5566f4d87627 | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P50 | author | B. Haberman | B. Haberman | string | ||||
STD:IETF:RFC9327$6b4612d063a0 | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the structure of the control messages that were historically used with the Network Time Protocol (NTP) before the advent of more modern control and management approaches. These control messages have been used to monitor and control the NTP application running on any IP network attached computer.... | This document describes the structure of the control messages that were historically used with the Network Time Protocol (NTP) before the advent of more modern control and management approaches. These control messages have been used to monitor and control the NTP application running on any IP network attached computer.... | monolingualtext | ||||
STD:IETF:RFC9327$772512089248 | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P1476 | title | Control Messages Protocol for Use with Network Time Protocol Version 4 | Control Messages Protocol for Use with Network Time Protocol Version 4 | monolingualtext | ||||
STD:IETF:RFC9327$b55e4f4ac089 | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9327$c9fbea063402 | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | HISTORIC | HISTORIC | string | ||||
STD:IETF:RFC9327$c9fbea063402 | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | HISTORIC | HISTORIC | string | ||||
STD:IETF:RFC9327$eb4f0a883068 | IETF | STD:IETF:RFC9327 | Control Messages Protocol for Use with Network Time Protocol Version 4 | HISTORIC | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9328$09627bcf0691 | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This memo describes an RTP payload format for the Versatile Video Coding (VVC) specification, which was published as both ITU-T Recommendation H.266 and ISO/IEC International Standard 23090-3. VVC was developed by the Joint Video Experts Team (JVET). The RTP payload format allows for packetization of one or more Netw... | This memo describes an RTP payload format for the Versatile Video Coding (VVC) specification, which was published as both ITU-T Recommendation H.266 and ISO/IEC International Standard 23090-3. VVC was developed by the Joint Video Experts Team (JVET). The RTP payload format allows for packetization of one or more Netw... | monolingualtext | ||||
STD:IETF:RFC9328$359304e57785 | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. M Hannuksela | M. M Hannuksela | string | ||||
STD:IETF:RFC9328$40d6534faaae | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9328 | https://www.rfc-editor.org/rfc/rfc9328 | url | ||||
STD:IETF:RFC9328$60b38ce70b0c | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9328$6ba742c599e5 | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Zhao | S. Zhao | string | ||||
STD:IETF:RFC9328$6ff7a0362af2 | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9328$8b167cbbd2ab | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. Sanchez | Y. Sanchez | string | ||||
STD:IETF:RFC9328$97094c0be340 | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9328$97094c0be340 | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9328$abc879d1d883 | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Wenger | S. Wenger | string | ||||
STD:IETF:RFC9328$c6072185bf74 | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9328$e78c8dd440ad | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y.-K. Wang | Y.-K. Wang | string | ||||
STD:IETF:RFC9328$ee8a17c4b77a | IETF | STD:IETF:RFC9328 | RTP Payload Format for Versatile Video Coding (VVC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | RTP Payload Format for Versatile Video Coding (VVC) | RTP Payload Format for Versatile Video Coding (VVC) | monolingualtext | ||||
STD:IETF:RFC9329$22095263f127 | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | V. Smyslov | V. Smyslov | string | ||||
STD:IETF:RFC9329$276bf00a2d65 | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9329 | https://www.rfc-editor.org/rfc/rfc9329 | url | ||||
STD:IETF:RFC9329$578ccd55eb6b | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9329$5e70dafe0a29 | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9329$6bc5151bd659 | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9329$6bc5151bd659 | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9329$a8864f30838f | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | monolingualtext | ||||
STD:IETF:RFC9329$c20e5c35540c | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9329$ca73177e9831 | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC8229 | RFC8229 | wikibase-item | ||||
STD:IETF:RFC9329$d61106fc7154 | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9329$d6e1199bad0e | IETF | STD:IETF:RFC9329 | TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a method to transport Internet Key Exchange Protocol (IKE) and IPsec packets over a TCP connection for traversing network middleboxes that may block IKE negotiation over UDP. This method, referred to as "TCP encapsulation", involves sending both IKE packets for Security Association (SA) establis... | This document describes a method to transport Internet Key Exchange Protocol (IKE) and IPsec packets over a TCP connection for traversing network middleboxes that may block IKE negotiation over UDP. This method, referred to as "TCP encapsulation", involves sending both IKE packets for Security Association (SA) establis... | monolingualtext | ||||
STD:IETF:RFC9330$02c8e7c2140e | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | B. Briscoe | B. Briscoe | string | ||||
STD:IETF:RFC9330$04cdffcc5337 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Bagnulo | M. Bagnulo | string | ||||
STD:IETF:RFC9330$11326f1c8802 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9330$15cf6dba9f34 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. White | G. White | string | ||||
STD:IETF:RFC9330$4f561c92b29d | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | K. De Schepper | K. De Schepper | string | ||||
STD:IETF:RFC9330$5467de28517f | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9330$65014c7d5211 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9330$65014c7d5211 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9330$7b0ab0c56a09 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9330$94af83604e06 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9330 | https://www.rfc-editor.org/rfc/rfc9330 | url | ||||
STD:IETF:RFC9330$c11728cb2400 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the L4S architecture, which enables Internet applications to achieve low queuing latency, low congestion loss, and scalable throughput control. L4S is based on the insight that the root cause of queuing delay is in the capacity-seeking congestion controllers of senders, not in the queue itself. ... | This document describes the L4S architecture, which enables Internet applications to achieve low queuing latency, low congestion loss, and scalable throughput control. L4S is based on the insight that the root cause of queuing delay is in the capacity-seeking congestion controllers of senders, not in the queue itself. ... | monolingualtext | ||||
STD:IETF:RFC9330$f4d21e20a2b1 | IETF | STD:IETF:RFC9330 | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture | monolingualtext | ||||
STD:IETF:RFC9331$3e92557dd407 | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9331$4a20f68edf95 | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9331$5ce6e6869cd4 | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9331$617565021850 | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | B. Briscoe | B. Briscoe | string | ||||
STD:IETF:RFC9331$68a89af87b28 | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | monolingualtext | ||||
STD:IETF:RFC9331$699406a03630 | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | K. De Schepper | K. De Schepper | string | ||||
STD:IETF:RFC9331$803aa314731e | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This specification defines the protocol to be used for a new network service called Low Latency, Low Loss, and Scalable throughput (L4S). L4S uses an Explicit Congestion Notification (ECN) scheme at the IP layer that is similar to the original (or 'Classic') ECN approach, except as specified within. L4S uses 'Scalable'... | This specification defines the protocol to be used for a new network service called Low Latency, Low Loss, and Scalable throughput (L4S). L4S uses an Explicit Congestion Notification (ECN) scheme at the IP layer that is similar to the original (or 'Classic') ECN approach, except as specified within. L4S uses 'Scalable'... | monolingualtext | ||||
STD:IETF:RFC9331$83b4b66ca7cb | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9331$83b4b66ca7cb | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9331$c3503b7c26ad | IETF | STD:IETF:RFC9331 | The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9331 | https://www.rfc-editor.org/rfc/rfc9331 | url | ||||
STD:IETF:RFC9332$251416c6e136 | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9332 | https://www.rfc-editor.org/rfc/rfc9332 | url | ||||
STD:IETF:RFC9332$3a4bc9678575 | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9332$3c33e81541d1 | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | monolingualtext | ||||
STD:IETF:RFC9332$4c1090eb61f2 | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | G. White | G. White | string | ||||
STD:IETF:RFC9332$53ccef0989a6 | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9332$a4443ea13050 | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This specification defines a framework for coupling the Active Queue Management (AQM) algorithms in two queues intended for flows with different responses to congestion. This provides a way for the Internet to transition from the scaling problems of standard TCP-Reno-friendly ('Classic') congestion controls to the fami... | This specification defines a framework for coupling the Active Queue Management (AQM) algorithms in two queues intended for flows with different responses to congestion. This provides a way for the Internet to transition from the scaling problems of standard TCP-Reno-friendly ('Classic') congestion controls to the fami... | monolingualtext | ||||
STD:IETF:RFC9332$a7e738386a4e | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | B. Briscoe | B. Briscoe | string | ||||
STD:IETF:RFC9332$ab089fc2649e | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | K. De Schepper | K. De Schepper | string | ||||
STD:IETF:RFC9332$b5e49b273c1a | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9332$f7d0f462a3a6 | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9332$f7d0f462a3a6 | IETF | STD:IETF:RFC9332 | Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9333$0f1ec0359616 | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9333$3c81ff70a6d5 | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9333 | https://www.rfc-editor.org/rfc/rfc9333 | url | ||||
STD:IETF:RFC9333$4e723852a8cc | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9333$4e723852a8cc | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9333$5929bf4fd0f9 | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9333$71ff32d2c937 | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Guggemos | T. Guggemos | string | ||||
STD:IETF:RFC9333$75a6d8a6be9c | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Migault | D. Migault | string | ||||
STD:IETF:RFC9333$a619485c935c | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9333$d53f9a875d2a | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the minimal properties that an IP Encapsulating Security Payload (ESP) implementation needs to meet to remain interoperable with the standard ESP as defined in RFC 4303. Such a minimal version of ESP is not intended to become a replacement of ESP in RFC 4303. Instead, a minimal implementation is... | This document describes the minimal properties that an IP Encapsulating Security Payload (ESP) implementation needs to meet to remain interoperable with the standard ESP as defined in RFC 4303. Such a minimal version of ESP is not intended to become a replacement of ESP in RFC 4303. Instead, a minimal implementation is... | monolingualtext | ||||
STD:IETF:RFC9333$ddc98e612a92 | IETF | STD:IETF:RFC9333 | Minimal IP Encapsulating Security Payload (ESP) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Minimal IP Encapsulating Security Payload (ESP) | Minimal IP Encapsulating Security Payload (ESP) | monolingualtext | ||||
STD:IETF:RFC9334$101ce7251214 | IETF | STD:IETF:RFC9334 | Remote ATtestation procedureS (RATS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | In network protocol exchanges, it is often useful for one end of a communication to know whether the other end is in an intended operating state. This document provides an architectural overview of the entities involved that make such tests possible through the process of generating, conveying, and evaluating evidenti... | In network protocol exchanges, it is often useful for one end of a communication to know whether the other end is in an intended operating state. This document provides an architectural overview of the entities involved that make such tests possible through the process of generating, conveying, and evaluating evidenti... | monolingualtext | ||||
STD:IETF:RFC9334$1d296a3b4bda | IETF | STD:IETF:RFC9334 | Remote ATtestation procedureS (RATS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9334 | https://www.rfc-editor.org/rfc/rfc9334 | url | ||||
STD:IETF:RFC9334$48b233437e20 | IETF | STD:IETF:RFC9334 | Remote ATtestation procedureS (RATS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Remote ATtestation procedureS (RATS) Architecture | Remote ATtestation procedureS (RATS) Architecture | monolingualtext | ||||
STD:IETF:RFC9334$6e1c09643030 | IETF | STD:IETF:RFC9334 | Remote ATtestation procedureS (RATS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Thaler | D. Thaler | string | ||||
STD:IETF:RFC9334$6fed4ee8ef38 | IETF | STD:IETF:RFC9334 | Remote ATtestation procedureS (RATS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | N. Smith | N. Smith | string | ||||
STD:IETF:RFC9334$710b3ee5b8f6 | IETF | STD:IETF:RFC9334 | Remote ATtestation procedureS (RATS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9334$710b3ee5b8f6 | IETF | STD:IETF:RFC9334 | Remote ATtestation procedureS (RATS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9334$724d96081b87 | IETF | STD:IETF:RFC9334 | Remote ATtestation procedureS (RATS) Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | W. Pan | W. Pan | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.