References from rfc3838
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 14 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
BCP 78 |
Rights Contributors Provide to the IETF Trust References Referenced by |
Best Current Practice | informatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by |
Draft Standard | informatively references | |
RFC 3060 |
Policy Core Information Model -- Version 1 Specification References Referenced by |
Proposed Standard | normatively references | |
RFC 3198 |
Terminology for Policy-Based Management References Referenced by |
Informational | informatively references | |
RFC 3238 |
IAB Architectural and Policy Considerations for Open Pluggable Edge Services References Referenced by |
Informational | normatively references | |
RFC 3835 |
An Architecture for Open Pluggable Edge Services (OPES) References Referenced by |
Informational | normatively references | |
RFC 3837 |
Security Threats and Risks for Open Pluggable Edge Services (OPES) References Referenced by |
Informational | normatively references |