RFC 4595: Use of IKEv2 in the Fibre Channel Security Association Management Protocol
In plain English — editorial summary, not part of the RFC
This document describes the use of IKEv2 to negotiate security protocols and transforms for Fibre Channel as part of the Fibre Channel Security Association Management Protocol. This usage requires that IKEv2 be extended with Fibre-Channel-specific security protocols, transforms, and name types. This document specifies these IKEv2 extensions and allocates identifiers for them. Using new IKEv2 identifiers for Fibre Channel security protocols avoids any possible confusion between IKEv2 negotiation for IP networks and IKEv2 negotiation for Fibre Channel. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4595
- Published
- July 2006
- Authors
- F. Maino; D. Black
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4621Design of the IKEv2 Mobility and Multihoming (MOBIKE) ProtocolCurrent
August 2006
- RFC 4555IKEv2 Mobility and Multihoming Protocol (MOBIKE)Current
June 2006
- RFC 4718IKEv2 Clarifications and Implementation GuidelinesObsoleted
October 2006
- RFC 4430Kerberized Internet Negotiation of Keys (KINK)Current
March 2006
- RFC 4308Cryptographic Suites for IPsecCurrent
December 2005
- RFC 4307Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)Obsoleted
December 2005
- RFC 4304Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP)Current
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?