RFC 7210: Database of Long-Lived Symmetric Cryptographic Keys
In plain English — editorial summary, not part of the RFC
This document specifies the information contained in a conceptual database of long-lived cryptographic keys used by many different routing protocols for message security. The database is designed to support both manual and automated key management. In addition to describing the schema for the database, this document describes the operations that can be performed on the database as well as the requirements for the routing protocols that wish to use the database. In many typical scenarios, the protocols do not directly use the long-lived key, but rather a key derivation function is used to derive a short-lived key from a long-lived key.
Document record
- Document ID
- RFC7210
- Published
- April 2014
- Authors
- R. Housley; T. Polk; S. Hartman; D. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7209Requirements for Ethernet VPN (EVPN)Current
May 2014
- RFC 7211Operations Model for Router KeyingCurrent
June 2014
- RFC 7212MPLS Generic Associated Channel (G-ACh) Advertisement ProtocolCurrent
June 2014
- RFC 7213MPLS Transport Profile (MPLS-TP) Next-Hop Ethernet AddressingCurrent
June 2014
- RFC 7214Moving Generic Associated Channel (G-ACh) IANA Registries to a New RegistryCurrent
May 2014
- RFC 7215Locator/Identifier Separation Protocol (LISP) Network Element Deployment ConsiderationsCurrent
April 2014
- RFC 7196Making Route Flap Damping UsableCurrent
May 2014
- RFC 7226Requirements for Advanced Multipath in MPLS NetworksCurrent
May 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?