References from draft-ietf-kitten-kerberos-iana-registries
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 26 |
References Referenced by |
normatively references | ||
| draft-lha-krb-wg-some-numbers-to-iana |
Kerberos number registry to IANA
References Referenced by |
Possible Reference | ||
| RFC 1510 |
The Kerberos Network Authentication Service (V5)
References Referenced by |
Historic | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2253 |
Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 3961 |
Encryption and Checksum Specifications for Kerberos 5
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4120 |
The Kerberos Network Authentication Service (V5)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5179 |
Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6111 |
Additional Kerberos Naming Constraints
References Referenced by |
Proposed Standard | Possible Reference |