A new Request for Comments is now available in online RFC libraries.
RFC 8672
Title: TLS Server Identity Pinning with Tickets
Author: Y. Sheffer,
D. Migault
Status: Experimental
Stream: Independent
Date: October 2019
Mailbox: [email protected],
[email protected]
Pages: 22
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-sheffer-tls-pinning-ticket-12.txt
URL: https://www.rfc-editor.org/info/rfc8672
DOI: 10.17487/RFC8672
Misissued public-key certificates can prevent TLS clients from
appropriately authenticating the TLS server. Several alternatives
have been proposed to detect this situation and prevent a client from
establishing a TLS session with a TLS end point authenticated with an
illegitimate public-key certificate. These mechanisms are either not
widely deployed or limited to public web browsing.
This document proposes experimental extensions to TLS with opaque
pinning tickets as a way to pin the server's identity. During an
initial TLS session, the server provides an original encrypted
pinning ticket. In subsequent TLS session establishment, upon receipt
of the pinning ticket, the server proves its ability to decrypt the
pinning ticket and thus the ownership of the pinning protection key.
The client can now safely conclude that the TLS session is
established with the same TLS server as the original TLS session. One
of the important properties of this proposal is that no manual
management actions are required.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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/retrieve/bulk
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
Association Management Solutions, LLC
_______________________________________________
IETF-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-announce
