On the Use of Channel Bindings to Secure Channels
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 23
- Abstract
- The concept of channel binding allows applications to establish that the two end-points of a secure channel at one network layer are the same as at a higher layer by binding authentication at the higher layer to the channel at the lower layer. This allows applications to delegate session protection to lower layers, which has various performance benefits. This document discusses and formalizes the concept of channel binding to secure channels. [STANDARDS-TRACK]
- Publication Date
- 2007-11-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5056- Link
- https://doi.org/10.17487/RFC5056
- Author(s)
- Nicolás Williams
Latest version of IETF RFC 5056
Document Versions — IETF RFC 5056
-
▶ IETF RFC 5056 (2007-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
Bibliographic Reference(s)
- Touch, J., Black, D., and Y. Wang, "Problem and Applicability Statement for Better Than Nothing Security (BTNS)", Work in Progress, October 2007. EXTERNAL
- Richardson, M. and N. Williams, "Better-Than-Nothing- Security: An Unauthenticated Mode of IPsec", Work in Progress, September 2007. EXTERNAL
- Callaghan, B. and T. Talpey, "NFS Direct Data Placement", Work in Progress, July 2007. EXTERNAL
- Richardson, M. and B. Sommerfeld, "Requirements for an IPsec API", Work in Progress, April 2006. EXTERNAL
- Altman, J. and N. Williams, "Unique Channel Bindings for TLS", Work in Progress, November 2007. EXTERNAL
- Williams, N., "Channel Binding Identifiers for Secure Shell Channels", Work in Progress, November 2007. EXTERNAL
- Lampson, B., Abadi, M., Burrows, M., and E. Wobber, "Authentication in Distributed Systems: Theory and Practive", October 1991. EXTERNAL
- Williams, N., "Stackable Generic Security Service Pseudo-Mechanisms", Work in Progress, June 2006. EXTERNAL
- Josefsson, S., "Using GSS-API Mechanisms in SASL: The GS2 Mechanism Family", Work in Progress, October 2007. EXTERNAL
- Williams, N., "IPsec Channels: Connection Latching" , Work in Progress, September 2007. EXTERNAL
- IETF RFC 1964 [Active*]
- IETF RFC 2203 [Active*]
- IETF RFC 2401 [Superseded*]
- IETF RFC 2434 [Superseded*]
- IETF RFC 2743 [Active*]
- IETF RFC 2744 [Active*]
- IETF RFC 2817 [Active*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 3530 [Superseded*]
- IETF RFC 3720 [Superseded*]
- IETF RFC 3748 [Active*]
- IETF RFC 4120 [Active*]
- IETF RFC 4251 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4302 [Active*]
- IETF RFC 4303 [Active*]
- IETF RFC 4346 [Superseded*]
- IETF RFC 4422 [Active*]
- IETF RFC 4462 [Active*]
- IETF RFC 5046 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5056.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5056, On the Use of Channel Bindings to Secure Channels. Available at https://doi.org/10.17487/RFC5056
Snippet:
IETF RFC 5056, On the Use of Channel Bindings to Secure Channels. Available at https://doi.org/10.17487/RFC5056
HTML (ISO 690 compliant)
Preview:
IETF RFC 5056, On the Use of Channel Bindings to Secure Channels. Available at https://doi.org/10.17487/RFC5056
Snippet:
<span class="citation"><cite>IETF RFC 5056</cite>, On the Use of Channel Bindings to Secure Channels. Available at <a href="https://doi.org/10.17487/RFC5056" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5056</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5056, On the Use of Channel Bindings to Secure Channels
doi: 10.17487/RFC5056
url: https://doi.org/10.17487/RFC5056
doi: 10.17487/RFC5056
url: https://doi.org/10.17487/RFC5056
Snippet:
<li> <cite id="bib-rfc5056">IETF RFC 5056</cite>, On the Use of Channel Bindings to Secure Channels <span class="doi">10.17487/RFC5056</span> </li>
Referenced By
- IETF RFC 5386 [Active*]
- IETF RFC 5387 [Active*]
- IETF RFC 5403 [Active*]
- IETF RFC 5532 [Active*]
- IETF RFC 5554 [Active*]
- IETF RFC 5660 [Active*]
- IETF RFC 5666 [Superseded*]
- IETF RFC 5746 [Active*]
- IETF RFC 5801 [Active*]
- IETF RFC 5802 [Active*]
- IETF RFC 5929 [Active*]
- IETF RFC 6120 [Active*]
- IETF RFC 6331 [Active*]
- IETF RFC 6542 [Active*]
- IETF RFC 6677 [Active*]
- IETF RFC 6678 [Active*]
- IETF RFC 7055 [Active*]
- IETF RFC 7861 [Active*]
- IETF RFC 8062 [Active*]
- IETF RFC 9140 [Active*]
- IETF RFC 9266 [Active*]
- IETF RFC 9289 [Active*]