API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 4107
[ACTIVE]

Guidelines for Cryptographic Key Management

Metadata

Publisher
IETF
Doc Type
Best Practice
Pages
7
Abstract
The question often arises of whether a given security system requires some form of automated key management, or whether manual keying is sufficient. This memo provides guidelines for making such decisions. When symmetric cryptographic mechanisms are used in a protocol, the presumption is that automated key management is generally but not always needed. If manual keying is proposed, the burden of proving that automated key management is not required falls to the proposer. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Publication Date
2005-06-01
Status Note
Best Current Practice
DOI
10.17487/RFC4107
Link
https://doi.org/10.17487/RFC4107
Author(s)
Steven Bellovin
Russ Housley
Keyword(s)
Key Management
Latest version of IETF RFC 4107

Document Versions — IETF RFC 4107

  • ▶ IETF RFC 4107 (2005-06-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • NIST SP 800-38A [Active, Amended]
  • G. Lowe. "An attack on the Needham-Schroeder public key authentication protocol", Information Processing Letters, 56(3):131--136, November 1995. EXTERNAL
  • R. Needham and M. Schroeder. "Using encryption for authentication in large networks of computers", Communications of the ACM, 21(12), December 1978. EXTERNAL
  • M. Abadi and R. Needham, "Prudent Engineering Practice for Cryptographic Protocols", Proc. IEEE Computer Society Symposium on Research in Security and Privacy, May 1994. EXTERNAL
  • D. Denning and G. Sacco. "Timestamps in key distributed protocols", Communication of the ACM, 24(8):533--535, 1981. EXTERNAL
  • Thayer, R. and K. Kaukonen. "A Stream Cipher Encryption Algorithm", Work in Progress. EXTERNAL
  • IETF RFC 2246 [Superseded*]
  • IETF RFC 2409 [Superseded*]
  • IETF RFC 3610 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4107.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 4107, Guidelines for Cryptographic Key Management. Available at https://doi.org/10.17487/RFC4107
Snippet:
IETF RFC 4107, Guidelines for Cryptographic Key Management. Available at https://doi.org/10.17487/RFC4107

HTML (ISO 690 compliant)

Preview:
IETF RFC 4107, Guidelines for Cryptographic Key Management. Available at https://doi.org/10.17487/RFC4107
Snippet:
<span class="citation"><cite>IETF RFC 4107</cite>, Guidelines for Cryptographic Key Management. Available at <a href="https://doi.org/10.17487/RFC4107" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4107</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 4107, Guidelines for Cryptographic Key Management
doi: 10.17487/RFC4107
url: https://doi.org/10.17487/RFC4107
Snippet:
<li>
<cite id="bib-rfc4107">IETF RFC 4107</cite>, Guidelines for Cryptographic Key Management
<span class="doi">10.17487/RFC4107</span>
</li>

Referenced By