References from draft-zeilenga-ldap-user-schema
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 |
normatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | normatively references | |
RFC 1274 |
The COSINE and Internet X.500 Schema
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2247 |
Using Domains in LDAP/X.500 Distinguished Names
References Referenced by |
Proposed Standard | normatively references | |
RFC 2798 |
Definition of the inetOrgPerson LDAP Object Class
References Referenced by |
Informational | informatively references | |
RFC 2821 |
Simple Mail Transfer Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 2822 |
Internet Message Format
References Referenced by |
Proposed Standard | normatively references | |
RFC 3383 |
Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3490 |
Internationalizing Domain Names in Applications (IDNA)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3667 |
IETF Rights in Contributions
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3668 |
Intellectual Property Rights in IETF Technology
References Referenced by |
Best Current Practice | Possible Reference | |
STD 13 |
References Referenced by |
normatively references |