References from draft-knodel-e2ee-definition
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 1958 |
Architectural Principles of the Internet
References Referenced by |
Informational | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | informatively references | |
| RFC 3238 |
IAB Architectural and Policy Considerations for Open Pluggable Edge Services
References Referenced by |
Informational | informatively references | |
| RFC 3552 |
Guidelines for Writing RFC Text on Security Considerations
References Referenced by |
Best Current Practice | informatively references | |
| RFC 3724 |
The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture
References Referenced by |
Informational | informatively references | |
| RFC 3935 |
A Mission Statement for the IETF
References Referenced by |
Best Current Practice | informatively references | |
| RFC 4949 |
Internet Security Glossary, Version 2
References Referenced by |
Informational | informatively references | |
| RFC 7258 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7624 |
Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement
References Referenced by |
Informational | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | informatively references |