References from draft-quan-l4s-ioam
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 |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7665 |
Service Function Chaining (SFC) Architecture
References Referenced by |
Informational | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 9197 |
Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9326 |
In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9330 |
Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
References Referenced by |
Informational | normatively references | |
| RFC 9331 |
The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
References Referenced by |
Experimental | normatively references | |
| RFC 9332 |
Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)
References Referenced by |
Experimental | normatively references |