References from rfc2609
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 | Reference | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by |
Best Current Practice | Reference | |
| RFC 1766 |
Tags for the Identification of Languages Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | Possible Reference | |
| RFC 2165 |
Service Location Protocol Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2222 |
Simple Authentication and Security Layer (SASL) Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2244 |
ACAP -- Application Configuration Access Protocol Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2279 |
UTF-8, a transformation format of ISO 10646 Refs Ref'd by |
Draft Standard | Reference | |
| RFC 2396 |
Uniform Resource Identifiers (URI): Generic Syntax Refs Ref'd by |
Draft Standard | Reference | |
| RFC 2608 |
Service Location Protocol, Version 2 Refs Ref'd by |
Proposed Standard | Reference |