References from rfc2148
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 |
|---|---|---|---|---|
| RFC 1006 |
ISO Transport Service on top of the TCP Version: 3 Refs Ref'd by |
Internet Standard | Reference | |
| RFC 1255 |
A Naming Scheme for c=US Refs Ref'd by |
Informational | Reference | Possible Downref |
| RFC 1274 |
The COSINE and Internet X.500 Schema Refs Ref'd by |
Proposed Standard | Reference | Possible Downref |
| RFC 1276 |
Replication and Distributed Operations extensions to provide an Internet Directory using X.500 Refs Ref'd by |
Historic | Reference | Possible Downref |
| RFC 1562 |
Naming Guidelines for the AARNet X.500 Directory Service Refs Ref'd by |
Informational | Reference | Possible Downref |
| RFC 1617 |
Naming and Structuring Guidelines for X.500 Directory Pilots Refs Ref'd by |
Informational | Reference | Possible Downref |
| RFC 1632 |
A Revised Catalog of Available X.500 Implementations Refs Ref'd by |
Informational | Reference | Possible Downref |
| RFC 1777 |
Lightweight Directory Access Protocol Refs Ref'd by |
Historic | Reference | Possible Downref |
| RFC 1803 |
Recommendations for an X.500 Production Directory Service Refs Ref'd by |
Informational | Reference | Possible Downref |
| RFC 1943 |
Building an X.500 Directory Service in the US Refs Ref'd by |
Informational | Reference | Possible Downref |
| RFC 1983 |
Internet Users' Glossary Refs Ref'd by |
Informational | Possible Reference | Possible Downref |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | Reference | |
| RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES Refs Ref'd by |
Internet Standard | Possible Reference |