RFC 5739: IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)
In plain English — editorial summary, not part of the RFC
When Internet Key Exchange Protocol version 2 (IKEv2) is used for remote VPN access (client to VPN gateway), the gateway assigns the client an IP address from the internal network using IKEv2 configuration payloads. The configuration payloads specified in RFC 4306 work well for IPv4 but make it difficult to use certain features of IPv6. This document specifies new configuration attributes for IKEv2 that allows the VPN gateway to assign IPv6 prefixes to clients, enabling all features of IPv6 to be used with the client-gateway "virtual link". This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5739
- Published
- February 2010
- Authors
- P. Eronen; J. Laganier; C. Madson
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6467Secure Password Framework for Internet Key Exchange Version 2 (IKEv2)Current
December 2011
- RFC 7926Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered NetworksCurrent
July 2016
- RFC 5746Transport Layer Security (TLS) Renegotiation Indication ExtensionCurrent
February 2010
- RFC 5749Distribution of EAP-Based Keys for Handover and Re-AuthenticationCurrent
March 2010
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
- RFC 5751Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message SpecificationObsoleted
January 2010
- RFC 5752Multiple Signatures in Cryptographic Message Syntax (CMS)Current
January 2010
- RFC 5753Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)Current
January 2010
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?