RFC 9642: A YANG Data Model for a Keystore
In plain English — editorial summary, not part of the RFC
This document presents a YANG module called "ietf-keystore" that enables centralized configuration of both symmetric and asymmetric keys. The secret value for both key types may be encrypted or hidden. Asymmetric keys may be associated with certificates. Notifications are sent when certificates are about to expire.
Document record
- Document ID
- RFC9642
- Published
- October 2024
- Authors
- K. Watsen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9643YANG Groupings for TCP Clients and TCP ServersCurrent
October 2024
- RFC 9641A YANG Data Model for a TruststoreCurrent
October 2024
- RFC 9645YANG Groupings for TLS Clients and TLS ServersCurrent
October 2024
- RFC 7221Handling of Internet-Drafts by IETF Working GroupsCurrent
April 2014
- RFC 3844IETF Problem Resolution ProcessCurrent
August 2004
- RFC 3797Publicly Verifiable Nominations Committee (NomCom) Random SelectionCurrent
June 2004
- RFC 3774IETF Problem StatementCurrent
May 2004
- RFC 2777Publicly Verifiable Nomcom Random SelectionObsoleted
February 2000
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?