References to RFC 1041
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.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 4450 |
Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents
References Referenced by |
Informational | normatively references | |
| RFC 6270 |
The 'tn3270' URI Scheme
References Referenced by |
Proposed Standard | normatively references | |
| RFC 1576 |
TN3270 Current Practices
References Referenced by |
Informational | informatively references | |
| RFC 1647 |
TN3270 Enhancements
References Referenced by |
Proposed Standard | informatively references | |
| RFC 1700 |
Assigned Numbers
References Referenced by |
Historic | informatively references | |
| RFC 2355 |
TN3270 Enhancements
References Referenced by |
Draft Standard | informatively references | |
| RFC 2561 |
Base Definitions of Managed Objects for TN3270E Using SMIv2
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2562 |
Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)
References Referenced by |
Proposed Standard | informatively references |