Guidelines for Specifying the Use of IPsec Version 2

Metadata

Publisher: IETF
Doc Type: Best Practice
Pages: 13
Abstract: The Security Considerations sections of many Internet Drafts say, in effect, "just use IPsec". While this is sometimes correct, more often it will leave users without real, interoperable security mechanisms. This memo offers some guidance on when IPsec Version 2 should and should not be specified. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Publication Date: 2009-02-01
Status Note: Best Current Practice
DOI: 10.17487/RFC5406
Link: https://doi.org/10.17487/RFC5406
Author(s): Steven Bellovin
Keyword(s): Security Considerations

Latest version of IETF RFC 5406

Document Versions — IETF RFC 5406

▶ IETF RFC 5406 (2009-02-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2401 [Superseded*]
IETF RFC 2402 [Superseded*]
IETF RFC 2406 [Superseded*]
IETF RFC 2409 [Superseded*]
RFC3554 — RFC3554 EXTERNAL
IETF RFC 3948 [Active*]
IETF RFC 4107 [Active*]
IETF RFC 5280 [Active, Amended*]
RFC5374 — RFC5374 EXTERNAL

Bibliographic Reference(s)

Kent, S., Lynn, C., Mikkelson, J., and K. Seo, "Secure Border Gateway Protocol (Secure-BGP) -- Real World Performance and Deployment Issues", Proc. Network and Distributed System Security Symposium (NDSS), 2000. EXTERNAL
Kent, S., Lynn, C., and K. Seo, "Secure Border Gateway Protocol (Secure-BGP)", IEEE Journal on Selected Areas in Communications, 18:4, pp. 582-592, 2000. EXTERNAL
Bellovin, S., "Problem Areas for the IP Security Protocols", Proc. Sixth Usenix Security Symposium, pp. 205-214, 1996. EXTERNAL
IETF RFC 2385 [Superseded*]
IETF RFC 2461 [Superseded*]
IETF RFC 2661 [Active*]
IETF RFC 3547 [Superseded*]
IETF RFC 3552 [Active*]
IETF RFC 3715 [Active*]
IETF RFC 3830 [Active*]
IETF RFC 4271 [Active*]
IETF RFC 4301 [Active, Amended*]
IETF RFC 4302 [Active*]
IETF RFC 4303 [Active*]
IETF RFC 4306 [Superseded*]
RFC4430 — kink EXTERNAL
IETF RFC 4535 [Active*]
IETF RFC 4960 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5406.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 5406, Guidelines for Specifying the Use of IPsec Version 2. Available at https://doi.org/10.17487/RFC5406

Snippet:

IETF RFC 5406, Guidelines for Specifying the Use of IPsec Version 2. Available at https://doi.org/10.17487/RFC5406

HTML (ISO 690 compliant)

Preview:

IETF RFC 5406, Guidelines for Specifying the Use of IPsec Version 2. Available at https://doi.org/10.17487/RFC5406

Snippet:

<span class="citation"><cite>IETF RFC 5406</cite>, Guidelines for Specifying the Use of IPsec Version 2. Available at <a href="https://doi.org/10.17487/RFC5406" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5406</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5406, Guidelines for Specifying the Use of IPsec Version 2
doi: 10.17487/RFC5406
url: https://doi.org/10.17487/RFC5406

Snippet:

<li>
<cite id="bib-rfc5406">IETF RFC 5406</cite>, Guidelines for Specifying the Use of IPsec Version 2
<span class="doi">10.17487/RFC5406</span>
</li>

Referenced By

IETF RFC 6347 [Superseded*]