References from draft-nottingham-transport-metadata-impact
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 |
|---|---|---|---|---|
| BCP 188 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | informatively references | |
| BCP 90 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | informatively references | |
| draft-hardie-spud-use-cases |
Use Cases for SPUD
References Referenced by |
informatively references | ||
| draft-hildebrand-spud-prototype |
Substrate Protocol for User Datagrams (SPUD) Prototype
References Referenced by |
informatively references | ||
| draft-nottingham-gin |
Granular Information about Networks
References Referenced by |
informatively references | ||
| draft-sprecher-mobile-tg-exposure-req-arch |
Requirements and reference architecture for Mobile Throughput Guidance Exposure
References Referenced by |
informatively references | ||
| draft-trammell-stackevo-newtea |
Thoughts a New Transport Encapsulation Architecture
References Referenced by |
informatively references | ||
| RFC 1984 |
IAB and IESG Statement on Cryptographic Technology and the Internet
References Referenced by |
Best Current Practice | informatively references | |
| RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7258 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | informatively references |