draft-ietf-ipsecme-ikev2-redirect-12.txt | draft-ietf-ipsecme-ikev2-redirect-13.txt | |||
---|---|---|---|---|
Network Working Group V. Devarapalli | Network Working Group V. Devarapalli | |||
Internet-Draft WiChorus | Internet-Draft WiChorus | |||
Intended status: Standards Track K. Weniger | Intended status: Standards Track K. Weniger | |||
Expires: January 31, 2010 July 30, 2009 | Expires: February 5, 2010 August 4, 2009 | |||
Redirect Mechanism for IKEv2 | Redirect Mechanism for IKEv2 | |||
draft-ietf-ipsecme-ikev2-redirect-12.txt | draft-ietf-ipsecme-ikev2-redirect-13.txt | |||
Status of this Memo | Status of this Memo | |||
This Internet-Draft is submitted to IETF in full conformance with the | This Internet-Draft is submitted to IETF in full conformance with the | |||
provisions of BCP 78 and BCP 79. This document may contain material | provisions of BCP 78 and BCP 79. This document may contain material | |||
from IETF Documents or IETF Contributions published or made publicly | from IETF Documents or IETF Contributions published or made publicly | |||
available before November 10, 2008. The person(s) controlling the | available before November 10, 2008. The person(s) controlling the | |||
copyright in some of this material may not have granted the IETF | copyright in some of this material may not have granted the IETF | |||
Trust the right to allow modifications of such material outside the | Trust the right to allow modifications of such material outside the | |||
IETF Standards Process. Without obtaining an adequate license from | IETF Standards Process. Without obtaining an adequate license from | |||
skipping to change at page 1, line 42 | skipping to change at page 1, line 42 | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on January 31, 2010. | This Internet-Draft will expire on February 5, 2010. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2009 IETF Trust and the persons identified as the | Copyright (c) 2009 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents in effect on the date of | Provisions Relating to IETF Documents in effect on the date of | |||
publication of this document (http://trustee.ietf.org/license-info). | publication of this document (http://trustee.ietf.org/license-info). | |||
Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
and restrictions with respect to this document. | and restrictions with respect to this document. | |||
Abstract | Abstract | |||
IKEv2 is a protocol for setting up Virtual Private Network (VPN) | IKEv2 is a protocol for setting up Virtual Private Network (VPN) | |||
tunnels from a remote location to a gateway so that the VPN client | tunnels from a remote location to a gateway so that the VPN client | |||
can access services in the network behind the gateway. This document | can access services in the network behind the gateway. This document | |||
defines an IKEv2 extension that allows an overloaded VPN gateway or a | defines an IKEv2 extension that allows an overloaded VPN gateway or a | |||
VPN gateway that is being shot down for maintenance to redirect the | VPN gateway that is being shut down for maintenance to redirect the | |||
VPN client to attach to another gateway. The proposed mechanism can | VPN client to attach to another gateway. The proposed mechanism can | |||
also be used in Mobile IPv6 to enable the home agent to redirect the | also be used in Mobile IPv6 to enable the home agent to redirect the | |||
mobile node to another home agent. | mobile node to another home agent. | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
3. IKEv2 Initial Exchange with Redirect . . . . . . . . . . . . . 3 | 3. IKEv2 Initial Exchange with Redirect . . . . . . . . . . . . . 3 | |||
4. Use of Anycast Addresses with the Redirect Mechanism . . . . . 5 | 4. Use of Anycast Addresses with the Redirect Mechanism . . . . . 5 | |||
End of changes. 4 change blocks. | ||||
4 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |