References from draft-ietf-mops-network-overlay-impacts
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 3234 |
Middleboxes: Taxonomy and Issues
References Referenced by |
Informational | normatively references | |
| RFC 6891 |
Extension Mechanisms for DNS (EDNS(0))
References Referenced by |
Internet Standard | normatively references | |
| RFC 7258 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7264 |
An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer Routing
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7624 |
Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement
References Referenced by |
Informational | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 9000 |
QUIC: A UDP-Based Multiplexed and Secure Transport
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9317 |
Operational Considerations for Streaming Media
References Referenced by |
Informational | normatively references | |
| RFC 9484 |
Proxying IP in HTTP
References Referenced by |
Proposed Standard | normatively references |