RFC 6063: Dynamic Symmetric Key Provisioning Protocol (DSKPP)
In plain English — editorial summary, not part of the RFC
The Dynamic Symmetric Key Provisioning Protocol (DSKPP) is a client-server protocol for initialization (and configuration) of symmetric keys to locally and remotely accessible cryptographic modules. The protocol can be run with or without private key capabilities in the cryptographic modules and with or without an established public key infrastructure. Two variations of the protocol support multiple usage scenarios. With the four-pass variant, keys are mutually generated by the provisioning server and cryptographic module; provisioned keys are not transferred over-the-wire or over-the-air. The two-pass variant enables secure and efficient download and installation of pre-generated symmetric keys to a cryptographic module. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6063
- Published
- December 2010
- Authors
- A. Doherty; M. Pei; S. Machani; M. Nystrom
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 105
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5998An Extension for EAP-Only Authentication in IKEv2Current
September 2010
- RFC 5723Internet Key Exchange Protocol Version 2 (IKEv2) Session ResumptionCurrent
January 2010
- RFC 9593Announcing Supported Authentication Methods in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
July 2024
- RFC 6467Secure Password Framework for Internet Key Exchange Version 2 (IKEv2)Current
December 2011
- RFC 6066Transport Layer Security (TLS) Extensions: Extension DefinitionsUpdated
January 2011
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
- RFC 6054Using Counter Modes with Encapsulating Security Payload (ESP) and Authentication Header (AH) to Protect Group TrafficCurrent
November 2010
- RFC 6031Cryptographic Message Syntax (CMS) Symmetric Key Package Content TypeCurrent
December 2010
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?