References from RFC 3195
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 |
Reference | ||
BCP 47 |
References Referenced by |
Reference | ||
RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | Possible Reference | |
RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | Reference | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2782 |
A DNS RR for specifying the location of services (DNS SRV)
References Referenced by |
Proposed Standard | Reference | |
RFC 2831 |
Using Digest Authentication as a SASL Mechanism
References Referenced by |
Historic | Reference | |
RFC 3066 |
Tags for the Identification of Languages
References Referenced by |
Best Current Practice | Reference | |
RFC 3080 |
The Blocks Extensible Exchange Protocol Core
References Referenced by |
Proposed Standard | Reference | |
RFC 3081 |
Mapping the BEEP Core onto TCP
References Referenced by |
Proposed Standard | Reference | |
RFC 3164 |
The BSD Syslog Protocol
References Referenced by |
Informational | Reference |