References from rfc3838
This is an experimental product. 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 Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 Refs Ref'd by |
Draft Standard | informatively references | |
| RFC 3060 |
Policy Core Information Model -- Version 1 Specification Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3198 |
Terminology for Policy-Based Management Refs Ref'd by |
Informational | informatively references | |
| RFC 3238 |
IAB Architectural and Policy Considerations for Open Pluggable Edge Services Refs Ref'd by |
Informational | normatively references | |
| RFC 3835 |
An Architecture for Open Pluggable Edge Services (OPES) Refs Ref'd by |
Informational | normatively references | |
| RFC 3837 |
Security Threats and Risks for Open Pluggable Edge Services (OPES) Refs Ref'd by |
Informational | normatively references |