draft-ietf-netlmm-grekey-option-01.txt   draft-ietf-netlmm-grekey-option-02.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: April 10, 2009 S. Gundavelli Expires: May 25, 2009 S. Gundavelli
K. Leung K. Leung
Cisco Systems Cisco Systems
October 07, 2008 November 21, 2008
GRE Key Option for Proxy Mobile IPv6 GRE Key Option for Proxy Mobile IPv6
draft-ietf-netlmm-grekey-option-01.txt draft-ietf-netlmm-grekey-option-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 April 10, 2009. This Internet-Draft will expire on May 25, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines a new Mobility Option for allowing the mobile This document defines a new Mobility Option for allowing the mobile
access gateway and the local mobility anchor to negotiate GRE access gateway and the local mobility anchor to negotiate GRE
encapsulation mode and exchange the downlink and uplink GRE keys encapsulation mode and exchange the downlink and uplink GRE keys
skipping to change at page 8, line 37 skipping to change at page 8, line 37
with the GRE Key option which includes the uplink GRE key, the with the GRE Key option which includes the uplink GRE key, the
mobile access gateway MUST update the related three fields in the mobile access gateway MUST update the related three fields in the
mobile node Binding Update List entry described in Section 4.1. mobile node Binding Update List entry described in Section 4.1.
Additionally, the MAG MUST use the assigned uplink GRE Key for Additionally, the MAG MUST use the assigned uplink GRE Key for
tunneling all the traffic originating from the mobile node before tunneling all the traffic originating from the mobile node before
forwarding the tunneled traffic to the LMA. forwarding the tunneled traffic to the LMA.
o If the mobile access gateway included the GRE Key option in the o If the mobile access gateway included the GRE Key option in the
Proxy Binding Update for a specific mobile node and the local Proxy Binding Update for a specific mobile node and the local
mobility anchor accepts the Proxy Binding Update by sending a mobility anchor accepts the Proxy Binding Update by sending a
Proxy Binding Acknowledgement with a status code <SUCCESS> or any Proxy Binding Acknowledgement with a success status code (less
status code that is less than 128 other than <GRE KEY OPTION NOT than 128) other than <GRE KEY OPTION NOT REQUIRED>, but without
REQUIRED>, the mobile access gateway MUST consider that the local the GRE Key option, then the mobile access gateway MUST consider
mobility anchor does not support GRE Key option as per this that the local mobility anchor does not support GRE Key option as
specification. The mobile access gateway SHOULD NOT include the per this specification. The mobile access gateway SHOULD NOT
GRE Key option in any subsequent Proxy Binding Update message that include the GRE Key option in any subsequent Proxy Binding Update
is sent to that LMA. message that is sent to that LMA.
o If the mobile access gateway sent a Proxy Binding Update message o If the mobile access gateway sent a Proxy Binding Update message
without the GRE Key option, but the received Proxy Binding without the GRE Key option, but the received Proxy Binding
Acknowledgement has the Status Code <GRE KEY OPTION REQUIRED>, Acknowledgement has the Status Code <GRE KEY OPTION REQUIRED>,
indicating that the GRE encapsulation and GRE key is required, the indicating that the GRE encapsulation and GRE key is required, the
mobile access gateway SHOULD resend the Proxy Binding Update mobile access gateway SHOULD resend the Proxy Binding Update
message with the GRE Key option. If the MAG does not support the message with the GRE Key option. If the MAG does not support the
GRE Key option, the MAG MAY log the event and possibly raise an GRE Key option, the MAG MAY log the event and possibly raise an
alarm to indicate a possible misconfiguration. alarm to indicate a possible misconfiguration.
skipping to change at page 11, line 18 skipping to change at page 11, line 18
header, the local mobility anchor MUST use the GRE Key present in header, the local mobility anchor MUST use the GRE Key present in
the GRE extension header to determine the necessary special the GRE extension header to determine the necessary special
processing for the data packet, e.g., lookup the mobile node's processing for the data packet, e.g., lookup the mobile node's
home gateway address, determine any special processing or home gateway address, determine any special processing or
treatment for the data packet flow, then remove the encapsulation treatment for the data packet flow, then remove the encapsulation
header before forwarding the packet. header before forwarding the packet.
6. Message Formats 6. Message Formats
This section defines an extension to the Mobile IPv6 [RFC3775] This section defines an extension to the Mobile IPv6 [RFC3775]
protocol messages for supporting the GRE tunneling and GRE Key protocol messages. The use of GRE Key option for supporting GRE
exchange for Proxy Mobile IPv6. tunneling and GRE Key exchange for Proxy Mobile IPv6 is defined in
this document.
6.1. GRE Key Option 6.1. GRE Key Option
A new mobility option, the GRE Key option, is defined for use in the A new mobility option, the GRE Key option, is defined for use in the
Proxy Binding Update and Proxy Binding Acknowledgment messages Proxy Binding Update and Proxy Binding Acknowledgment messages
exchanged between the mobile access gateway and the local mobility exchanged between the mobile access gateway and the local mobility
anchor. This option can be used for negotiating GRE encapsulation anchor. This option can be used for negotiating GRE encapsulation
mode and exchanging the downlink and uplink GRE keys that can be used mode and exchanging the downlink and uplink GRE keys that can be used
by the peers in all GRE encapsulated packets for marking that by the peers in all GRE encapsulated packets for marking that
specific mobile node's data flow. specific mobile node's data flow.
 End of changes. 6 change blocks. 
13 lines changed or deleted 14 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/