Channel Bindings for TLS
RFC 5929
Document | Type |
RFC - Proposed Standard
(July 2010; No errata)
Was draft-altman-tls-channel-bindings (individual in sec area)
|
|
---|---|---|---|
Authors | Jeffrey Altman , Larry Zhu , Nicolás Williams | ||
Last updated | 2018-12-20 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5929 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Alexey Melnikov | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) J. Altman Request for Comments: 5929 Secure Endpoints Category: Standards Track N. Williams ISSN: 2070-1721 Oracle L. Zhu Microsoft Corporation July 2010 Channel Bindings for TLS Abstract This document defines three channel binding types for Transport Layer Security (TLS), tls-unique, tls-server-end-point, and tls-unique-for- telnet, in accordance with RFC 5056 (On Channel Binding). Note that based on implementation experience, this document changes the original definition of 'tls-unique' channel binding type in the channel binding type IANA registry. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5929. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Altman, et al. Standards Track [Page 1] RFC 5929 TLS Channel Bindings July 2010 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction ....................................................3 2. Conventions Used in This Document ...............................3 3. The 'tls-unique' Channel Binding Type ...........................3 3.1. Description ................................................3 3.2. Registration ...............................................4 4. The 'tls-server-end-point' Channel Binding Type .................5 4.1. Description ................................................5 4.2. Registration ...............................................6 5. The 'tls-unique-for-telnet' Channel Binding Type ................6 5.1. Description ................................................7 5.2. Registration ...............................................7 6. Applicability of TLS Channel Binding Types ......................7 7. Required Application Programming Interfaces ....................10 8. Description of Backwards-Incompatible Changes Made Herein to 'tls-unique' .........................................10 9. IANA Considerations ............................................11 10. Security Considerations .......................................11 10.1. Cryptographic Algorithm Agility ..........................12 10.2. On Disclosure of Channel Bindings Data by Authentication Mechanisms ................................12 11. References ....................................................13 11.1. Normative References .....................................13 11.2. Informative References ...................................14 Altman, et al. Standards Track [Page 2] RFC 5929 TLS Channel Bindings July 2010 1. Introduction Subsequent to the publication of "On Channel Bindings" [RFC5056],Show full document text