References from draft-tomar-scone-ecn
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
draft-joras-sconepro-video-opt-requirements |
SCONEPRO Video Optimization Requirements
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3168 |
The Addition of Explicit Congestion Notification (ECN) to IP
References Referenced by |
Proposed Standard | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8803 |
0-RTT TCP Convert Protocol
References Referenced by |
Experimental | informatively references | |
RFC 8804 |
Content Delivery Network Interconnection (CDNI) Request Routing Extensions
References Referenced by |
Proposed Standard | informatively references | |
RFC 9330 |
Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
References Referenced by |
Informational | informatively references | |
RFC 9331 |
The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
References Referenced by |
Experimental | informatively references | |
RFC 9332 |
Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)
References Referenced by |
Experimental | informatively references |