draft-ietf-tokbind-negotiation-08.txt   draft-ietf-tokbind-negotiation-09.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: October 23, 2017 D. Balfanz Expires: January 21, 2018 D. Balfanz
A. Langley A. Langley
Google Inc. Google Inc.
April 21, 2017 July 20, 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-08 draft-ietf-tokbind-negotiation-09
Abstract Abstract
This document specifies a Transport Layer Security (TLS) [RFC5246] This document specifies a Transport Layer Security (TLS) extension
extension for the negotiation of Token Binding protocol for the negotiation of Token Binding protocol version and key
[I-D.ietf-tokbind-protocol] version and key parameters. 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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 October 23, 2017. This Internet-Draft will expire on January 21, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
skipping to change at page 2, line 31 skipping to change at page 2, line 31
8.1. Normative References . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
In order to use the Token Binding protocol In order to use the Token Binding protocol
[I-D.ietf-tokbind-protocol], the client and server need to agree on [I-D.ietf-tokbind-protocol], the client and server need to agree on
the Token Binding protocol version and the parameters (signature the Token Binding protocol version and the parameters (signature
algorithm, length) of the Token Binding key. This document specifies algorithm, length) of the Token Binding key. This document specifies
a new TLS extension to accomplish this negotiation without a new TLS [RFC5246] extension to accomplish this negotiation without
introducing additional network round-trips in TLS 1.2 and earlier introducing additional network round-trips in TLS 1.2 and earlier
versions. The negotiation of the Token Binding protocol and key versions. The negotiation of the Token Binding protocol and key
parameters in combination with TLS 1.3 and later versions is beyond parameters in combination with TLS 1.3 and later versions is beyond
the scope of this document. the scope of this document.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
skipping to change at page 5, line 31 skipping to change at page 5, line 31
Please note that the Token Binding protocol version and key Please note that the Token Binding protocol version and key
parameters are negotiated for each TLS connection, which means that parameters are negotiated for each TLS connection, which means that
the client and server include their "token_binding" extensions both the client and server include their "token_binding" extensions both
in the full TLS handshake that establishes a new TLS session and in in the full TLS handshake that establishes a new TLS session and in
the subsequent abbreviated TLS handshakes that resume the TLS the subsequent abbreviated TLS handshakes that resume the TLS
session. session.
5. IANA Considerations 5. IANA Considerations
This document updates the TLS "ExtensionType Values" registry This document updates the TLS "ExtensionType Values" registry. IANA
originally created in [RFC4366]. IANA has provided the following has provided the following temporary registration for the
temporary registration for the "token_binding" TLS extension: "token_binding" TLS extension:
Value: 24 Value: 24
Extension name: token_binding Extension name: token_binding
Reference: this document Reference: this document
IANA is requested to make this registration permanent, keeping the IANA is requested to make this registration permanent, keeping the
value of 24, which has been used by the prototype implementations of value of 24, which has been used by the prototype implementations of
the Token Binding protocol. the Token Binding protocol.
skipping to change at page 6, line 43 skipping to change at page 6, line 43
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-13 (work in progress), February ietf-tokbind-protocol-14 (work in progress), April 2017.
2017.
[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.,
and T. Wright, "Transport Layer Security (TLS)
Extensions", RFC 4366, DOI 10.17487/RFC4366, April 2006,
<http://www.rfc-editor.org/info/rfc4366>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, DOI 10.17487/RFC5246, August 2008,
<http://www.rfc-editor.org/info/rfc5246>. <http://www.rfc-editor.org/info/rfc5246>.
[RFC5705] Rescorla, E., "Keying Material Exporters for Transport [RFC5705] Rescorla, E., "Keying Material Exporters for Transport
Layer Security (TLS)", RFC 5705, DOI 10.17487/RFC5705, Layer Security (TLS)", RFC 5705, DOI 10.17487/RFC5705,
March 2010, <http://www.rfc-editor.org/info/rfc5705>. March 2010, <http://www.rfc-editor.org/info/rfc5705>.
[RFC5746] Rescorla, E., Ray, M., Dispensa, S., and N. Oskov, [RFC5746] Rescorla, E., Ray, M., Dispensa, S., and N. Oskov,
 End of changes. 9 change blocks. 
23 lines changed or deleted 12 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/