References from RFC 8353
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 | ||
RFC 2025 |
The Simple Public-Key GSS-API Mechanism (SPKM)
References Referenced by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2743 |
Generic Security Service Application Program Interface Version 2, Update 1
References Referenced by |
Proposed Standard | normatively references | |
RFC 2744 |
Generic Security Service API Version 2 : C-bindings
References Referenced by |
Proposed Standard | normatively references | |
RFC 2853 |
Generic Security Service API Version 2 : Java Bindings
References Referenced by |
Proposed Standard | normatively references | |
RFC 4121 |
The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2
References Referenced by |
Proposed Standard | normatively references | |
RFC 4178 |
The Simple and Protected Generic Security Service Application Program Interface (GSS-API) Negotiation Mechanism
References Referenced by |
Proposed Standard | normatively references | |
RFC 5653 |
Generic Security Service API Version 2: Java Bindings Update
References Referenced by |
Proposed Standard | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references |