References from RFC 4496
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 |
References Referenced by |
normatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
RFC 2033 |
Local Mail Transfer Protocol
References Referenced by |
Informational | informatively references | |
RFC 2476 |
Message Submission
References Referenced by |
Proposed Standard | informatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | informatively references | |
RFC 2821 |
Simple Mail Transfer Protocol
References Referenced by |
Proposed Standard | informatively references | |
RFC 3752 |
Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios
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 | |
RFC 4037 |
Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
References Referenced by |
Proposed Standard | normatively references | |
RFC 4236 |
HTTP Adaptation with Open Pluggable Edge Services (OPES)
References Referenced by |
Proposed Standard | normatively references |