API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5660
[ACTIVE]

IPsec Channels: Connection Latching

Metadata

Publisher
IETF
Doc Type
Standard
Pages
31
Abstract
This document specifies, abstractly, how to interface applications and transport protocols with IPsec so as to create "channels" by latching "connections" (packet flows) to certain IPsec Security Association (SA) parameters for the lifetime of the connections. Connection latching is layered on top of IPsec and does not modify the underlying IPsec architecture. Connection latching can be used to protect applications against accidentally exposing live packet flows to unintended peers, whether as the result of a reconfiguration of IPsec or as the result of using weak peer identity to peer address associations. Weak association of peer ID and peer addresses is at the core of Better Than Nothing Security (BTNS); thus, connection latching can add a significant measure of protection to BTNS IPsec nodes. Finally, the availability of IPsec channels will make it possible to use channel binding to IPsec channels. [STANDARDS-TRACK]
Publication Date
2009-10-01
Status Note
Proposed Standard
DOI
10.17487/RFC5660
Link
https://doi.org/10.17487/RFC5660
Author(s)
Nicolás Williams
Keyword(s)
IPSEC, Connection Latching
Latest version of IETF RFC 5660

Document Versions — IETF RFC 5660

  • ▶ IETF RFC 5660 (2009-10-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Sun Microsystems, Inc., "ipsec(7P) man page, Solaris 10 Reference Manual Collection". EXTERNAL
  • Williams, N., "End-Point Channel Bindings for IPsec Using IKEv2 and Public Keys", Work in Progress, April 2008. EXTERNAL
  • Dondeti, L. and V. Narayanan, "Guidelines for using IPsec and IKEv2", Work in Progress, October 2006. EXTERNAL
  • Richardson, M., "An abstract interface between applications and IPsec", Work in Progress, November 2008. EXTERNAL
  • IETF RFC 1034 [Active*]
  • IETF RFC 2367 [Active*]
  • IETF RFC 5056 [Active*]
  • IETF RFC 5387 [Active*]
  • IETF RFC 5406 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5660.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5660, IPsec Channels: Connection Latching. Available at https://doi.org/10.17487/RFC5660
Snippet:
IETF RFC 5660, IPsec Channels: Connection Latching. Available at https://doi.org/10.17487/RFC5660

HTML (ISO 690 compliant)

Preview:
IETF RFC 5660, IPsec Channels: Connection Latching. Available at https://doi.org/10.17487/RFC5660
Snippet:
<span class="citation"><cite>IETF RFC 5660</cite>, IPsec Channels: Connection Latching. Available at <a href="https://doi.org/10.17487/RFC5660" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5660</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5660, IPsec Channels: Connection Latching
doi: 10.17487/RFC5660
url: https://doi.org/10.17487/RFC5660
Snippet:
<li>
<cite id="bib-rfc5660">IETF RFC 5660</cite>, IPsec Channels: Connection Latching
<span class="doi">10.17487/RFC5660</span>
</li>

Referenced By