draft-ietf-netlmm-grekey-option-07.txt   draft-ietf-netlmm-grekey-option-08.txt 
Network Working Group A. Muhanna Network Working Group A. Muhanna
Internet-Draft M. Khalil Internet-Draft M. Khalil
Intended status: Standards Track Nortel Intended status: Standards Track Nortel
Expires: October 28, 2009 S. Gundavelli Expires: November 1, 2009 S. Gundavelli
K. Leung K. Leung
Cisco Systems Cisco Systems
April 26, 2009 April 30, 2009
GRE Key Option for Proxy Mobile IPv6 GRE Key Option for Proxy Mobile IPv6
draft-ietf-netlmm-grekey-option-07.txt draft-ietf-netlmm-grekey-option-08.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. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 October 28, 2009. This Internet-Draft will expire on November 1, 2009.
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
This specification defines a new Mobility Option for allowing the This specification defines a new Mobility Option for allowing the
Mobile Access Gateway and the Local Mobility Anchor to negotiate GRE mobile access gateway and the local mobility anchor to negotiate GRE
(Generic Routing Encapsulation) encapsulation mode and exchange the (Generic Routing Encapsulation) encapsulation mode and exchange the
downlink and uplink GRE keys which are used for marking the downlink downlink and uplink GRE keys which are used for marking the downlink
and uplink traffic that belong to a specific mobility session. In and uplink traffic that belong to a specific mobility session. In
addition, the same mobility option can be used to negotiate the GRE addition, the same mobility option can be used to negotiate the GRE
encapsulation mode without exchanging the GRE keys. encapsulation mode without exchanging the GRE keys.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 3 2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 3
skipping to change at page 3, line 10 skipping to change at page 3, line 10
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
11.1. Normative References . . . . . . . . . . . . . . . . . . . 23 11.1. Normative References . . . . . . . . . . . . . . . . . . . 23
11.2. Informative References . . . . . . . . . . . . . . . . . . 23 11.2. Informative References . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
Proxy Mobile IPv6 specification [RFC5213] and Proxy Mobile IPv6 Proxy Mobile IPv6 specification [RFC5213] and Proxy Mobile IPv6
support for IPv4 [ID-PMIP6-IPv4] allow the use of IPv6 and IPv4 support for IPv4 [ID-PMIP6-IPv4] allow the use of IPv6 and IPv4
encapsulation modes as specified in [RFC2473] and [RFC2003] for the encapsulation modes as specified in [RFC2473] and [RFC2003] for the
tunneled traffic between the local mobility anchor and the mobile tunneled traffic between the local mobility anchor (LMA) and the
access gateway. There are scenarios where these encapsulation modes mobile access gateway (MAG). There are scenarios where these
are not sufficient to uniquely identify the destination of packets of encapsulation modes are not sufficient to uniquely identify the
a specific mobility session. Thus, there is a need for an destination of packets of a specific mobility session. Thus, there
encapsulation mode with richer semantics. The Generic Routing is a need for an encapsulation mode with richer semantics. The
Encapsulation (GRE) [RFC2784] and the Key extension as defined in Generic Routing Encapsulation (GRE) [RFC2784] and the Key extension
[RFC2890], has the required semantics to allow such distinction for as defined in [RFC2890], has the required semantics to allow such
use in Proxy Mobile IPv6. distinction for use in Proxy Mobile IPv6.
This specification defines the GRE Key option to be used for the This specification defines the GRE Key option to be used for the
negotiation of GRE encapsulation mode and exchange of the uplink and negotiation of GRE encapsulation mode and exchange of the uplink and
downlink GRE keys. The negotiated downlink and uplink GRE keys can downlink GRE keys. The negotiated downlink and uplink GRE keys can
be used for marking the downlink and uplink traffic for a specific be used for marking the downlink and uplink traffic for a specific
mobility session. In addition, this specification enables the Mobile mobility session. In addition, this specification enables the mobile
Access Gateway (MAG) and the Local Mobility Anchor (LMA) to negotiate access gateway and the local mobility anchor to negotiate the use of
the use of GRE encapsulation mode without exchanging the GRE keys. GRE encapsulation mode without exchanging the GRE keys.
This specification has no impact on IPv4 or IPv6 mobile nodes. This specification has no impact on IPv4 or IPv6 mobile nodes.
2. Conventions & Terminology 2. Conventions & Terminology
2.1. Conventions 2.1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
specification are to be interpreted as described in RFC 2119 specification are to be interpreted as described in RFC 2119
skipping to change at page 7, line 26 skipping to change at page 7, line 26
Acknowledgement and send it to the mobile access gateway. Acknowledgement and send it to the mobile access gateway.
3.3.2. GRE Key Exchange During Binding Re-registration 3.3.2. GRE Key Exchange During Binding Re-registration
If the mobile access gateway has successfully negotiated and If the mobile access gateway has successfully negotiated and
exchanged the initial GRE keys with the local mobility anchor for a exchanged the initial GRE keys with the local mobility anchor for a
specific mobile node binding, the mobile access gateway MUST include specific mobile node binding, the mobile access gateway MUST include
the GRE Key option with the downlink GRE key in the Proxy Binding the GRE Key option with the downlink GRE key in the Proxy Binding
Update which is used for requesting a Binding Lifetime Extension. In Update which is used for requesting a Binding Lifetime Extension. In
this case, if the local mobility anchor successfully processes the this case, if the local mobility anchor successfully processes the
Proxy Binding Update message, the local mobility anchor MUST return Proxy Binding Update message, the local mobility anchor SHOULD return
the same uplink GRE key that was exchanged with the mobile access the same uplink GRE key that was exchanged with the mobile access
gateway for the same mobility session in the GRE key option in a gateway in the last successful Proxy Binding Update for the same
successful Proxy Binding Acknowledgement message. mobility session in the GRE key option in a successful Proxy Binding
Acknowledgement message.
However, during inter-MAG handoff and if the new mobile access However, during inter-MAG handoff and if the new mobile access
gateway determines, based on, e.g., private IPv4 address support, the gateway determines, based on, e.g., private IPv4 address support, the
mobile access gateway local policy, the MAG-LMA peer agreement, or an mobile access gateway local policy, the MAG-LMA peer agreement, or an
indication during the handoff process, that GRE encapsulation and GRE indication during the handoff process, that GRE encapsulation and GRE
keys exchange are required, the new mobile access gateway MUST keys exchange are required, the new mobile access gateway MUST
include the GRE key option with the downlink GRE key in the Proxy include the GRE key option with the downlink GRE key in the Proxy
Binding Update which is used for requesting an after handoff Binding Binding Update which is used for requesting an after handoff Binding
Lifetime extension. In this case, the new mobile access gateway may Lifetime extension. In this case, the new mobile access gateway may
either pick a new downlink GRE key or use the downlink GRE key that either pick a new downlink GRE key or use the downlink GRE key that
 End of changes. 9 change blocks. 
19 lines changed or deleted 20 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/