RFC 9966: Bootstrapped TLS Authentication with Proof of Knowledge
In plain English — editorial summary, not part of the RFC
This document defines a mechanism that enables a bootstrapping device to establish trust and mutually authenticate against a TLS server. Bootstrapping devices have a public/private key pair; this mechanism enables a TLS server to prove to the device that it knows the public key and enables the device to prove to the TLS server that it knows the private key. The mechanism leverages existing Device Provisioning Profile (DPP) and TLS standards and can be used in an Extensible Authentication Protocol (EAP) exchange with an EAP server.
Document record
- Document ID
- RFC9966
- Published
- May 2026
- Authors
- O. Friel; D. Harkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9967System for Cross-Domain Identity Management (SCIM) Profile for Security Event Tokens (SETs)Current
May 2026
- RFC 9965The eap.arpa. Domain and Extensible Authentication Protocol (EAP) ProvisioningCurrent
May 2026
- RFC 9964ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)Current
May 2026
- RFC 9963Legacy RSASSA-PKCS1-v1_5 Code Points for TLS 1.3Current
April 2026
- RFC 9973TLS 1.3 Extension for Using Certificates with an External Pre-Shared KeyCurrent
July 2026
- RFC 9958Post-Quantum Cryptography for EngineersCurrent
June 2026
- RFC 9955Hybrid Signature SpectrumsCurrent
July 2026
- RFC 9954Hybrid Key Exchange in TLS 1.3Current
July 2026
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?