A new Request for Comments is now available in online RFC libraries.

        RFC 9966

        Title:      Bootstrapped TLS Authentication with Proof of Knowledge
        Author:     O. Friel,
                    D. Harkins
        Status:     Proposed Standard
        Stream:     IETF
        Date:       May 2026
        Mailbox:    [email protected],
                    [email protected]
        Pages:      16
        Updates:    None
        Obsoletes:  None

        I-D Tag:    draft-ietf-emu-bootstrapped-tls-11.txt

        URL:        https://www.rfc-editor.org/info/rfc9966

        DOI:        10.17487/RFC9966

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.

This document is a product of the EAP Method Update Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards/) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe 
or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to