References from RFC 5248
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 26 |
References Referenced by |
informatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
RFC 1893 |
Enhanced Mail System Status Codes
References Referenced by |
Proposed Standard | informatively references | |
RFC 2821 |
Simple Mail Transfer Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 3463 |
Enhanced Mail System Status Codes
References Referenced by |
Draft Standard | normatively references | |
RFC 3886 |
An Extensible Message Format for Message Tracking Responses
References Referenced by |
Proposed Standard | normatively references | |
RFC 4468 |
Message Submission BURL Extension
References Referenced by |
Proposed Standard | normatively references | |
RFC 4954 |
SMTP Service Extension for Authentication
References Referenced by |
Proposed Standard | normatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references |