draft-ietf-tokbind-negotiation-06.txt   draft-ietf-tokbind-negotiation-07.txt 
Internet Engineering Task Force A. Popov, Ed. Internet Engineering Task Force A. Popov, Ed.
Internet-Draft M. Nystroem Internet-Draft M. Nystroem
Intended status: Standards Track Microsoft Corp. Intended status: Standards Track Microsoft Corp.
Expires: May 27, 2017 D. Balfanz Expires: August 20, 2017 D. Balfanz
A. Langley A. Langley
Google Inc. Google Inc.
November 23, 2016 February 16, 2017
Transport Layer Security (TLS) Extension for Token Binding Protocol Transport Layer Security (TLS) Extension for Token Binding Protocol
Negotiation Negotiation
draft-ietf-tokbind-negotiation-06 draft-ietf-tokbind-negotiation-07
Abstract Abstract
This document specifies a Transport Layer Security (TLS) [RFC5246] This document specifies a Transport Layer Security (TLS) [RFC5246]
extension for the negotiation of Token Binding protocol extension for the negotiation of Token Binding protocol
[I-D.ietf-tokbind-protocol] version and key parameters. [I-D.ietf-tokbind-protocol] version and key parameters.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 27, 2017. This Internet-Draft will expire on August 20, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 6, line 11 skipping to change at page 6, line 11
active attackers from modifying the messages of the TLS handshake, active attackers from modifying the messages of the TLS handshake,
therefore it is not possible for the attacker to remove or modify the therefore it is not possible for the attacker to remove or modify the
"token_binding" extension. The signature algorithm and key length "token_binding" extension. The signature algorithm and key length
used in the TokenBinding of type "provided_token_binding" MUST match used in the TokenBinding of type "provided_token_binding" MUST match
the parameters negotiated via "token_binding" extension. the parameters negotiated via "token_binding" extension.
6.2. Triple Handshake Vulnerability in TLS 1.2 and Older TLS Versions 6.2. Triple Handshake Vulnerability in TLS 1.2 and Older TLS Versions
The Token Binding protocol relies on the TLS Exporters [RFC5705] to The Token Binding protocol relies on the TLS Exporters [RFC5705] to
associate a TLS connection with a Token Binding. The triple associate a TLS connection with a Token Binding. The triple
handshake attack [TRIPLE-HS] is a known TLS protocol vulnerability handshake attack [TRIPLE-HS] is a known vulnerability in TLS 1.2 and
allowing the attacker to synchronize exported keying material between older TLS versions, allowing the attacker to synchronize keying
TLS connections. The attacker can then successfully replay bound material between TLS connections. The attacker can then successfully
tokens. For this reason, the Token Binding protocol MUST NOT be replay bound tokens. For this reason, the Token Binding protocol
negotiated with these TLS versions, unless the Extended Master Secret MUST NOT be negotiated with these TLS versions, unless the Extended
[RFC7627] and Renegotiation Indication [RFC5746] TLS extensions have Master Secret [RFC7627] and Renegotiation Indication [RFC5746] TLS
also been negotiated. extensions have also been negotiated.
7. Acknowledgements 7. Acknowledgements
This document incorporates comments and suggestions offered by Eric This document incorporates comments and suggestions offered by Eric
Rescorla, Gabriel Montenegro, Martin Thomson, Vinod Anupam, Anthony Rescorla, Gabriel Montenegro, Martin Thomson, Vinod Anupam, Anthony
Nadalin, Michael B. Jones, Bill Cox, Nick Harper, Brian Campbell and Nadalin, Michael B. Jones, Bill Cox, Nick Harper, Brian Campbell and
others. others.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-tokbind-protocol] [I-D.ietf-tokbind-protocol]
Popov, A., Nystrom, M., Balfanz, D., Langley, A., and J. Popov, A., Nystrom, M., Balfanz, D., Langley, A., and J.
Hodges, "The Token Binding Protocol Version 1.0", draft- Hodges, "The Token Binding Protocol Version 1.0", draft-
ietf-tokbind-protocol-10 (work in progress), September ietf-tokbind-protocol-11 (work in progress), November
2016. 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC4366] Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen, J., [RFC4366] Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen, J.,
and T. Wright, "Transport Layer Security (TLS) and T. Wright, "Transport Layer Security (TLS)
Extensions", RFC 4366, DOI 10.17487/RFC4366, April 2006, Extensions", RFC 4366, DOI 10.17487/RFC4366, April 2006,
 End of changes. 7 change blocks. 
13 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/