References from rfc3049
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 References Referenced by |
Best Current Practice | Reference | |
| RFC 1576 |
TN3270 Current Practices References Referenced by |
Informational | Possible Reference | Possible Downref |
| RFC 1646 |
TN3270 Extensions for LUname and Printer Selection References Referenced by |
Informational | Possible Reference | Possible Downref |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 2165 |
Service Location Protocol References Referenced by |
Proposed Standard | Reference | |
| RFC 2246 |
The TLS Protocol Version 1.0 References Referenced by |
Historic | Reference | Possible Downref |
| RFC 2355 |
TN3270 Enhancements References Referenced by |
Draft Standard | Possible Reference | |
| RFC 2608 |
Service Location Protocol, Version 2 References Referenced by |
Proposed Standard | Reference | |
| RFC 2609 |
Service Templates and Service: Schemes References Referenced by |
Proposed Standard | Reference | |
| RFC 2614 |
An API for Service Location References Referenced by |
Informational | Reference | Possible Downref |
| STD 1 |
Internet Official Protocol Standards References Referenced by |
Historic | Possible Reference | Possible Downref |