draft-ietf-netlmm-grekey-option-08.txt   draft-ietf-netlmm-grekey-option-09.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: November 1, 2009 S. Gundavelli Expires: November 7, 2009 S. Gundavelli
K. Leung K. Leung
Cisco Systems Cisco Systems
April 30, 2009 May 6, 2009
GRE Key Option for Proxy Mobile IPv6 GRE Key Option for Proxy Mobile IPv6
draft-ietf-netlmm-grekey-option-08.txt draft-ietf-netlmm-grekey-option-09.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 November 1, 2009. This Internet-Draft will expire on November 7, 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
skipping to change at page 2, line 39 skipping to change at page 2, line 39
4.2. Operational Summary . . . . . . . . . . . . . . . . . . . 9 4.2. Operational Summary . . . . . . . . . . . . . . . . . . . 9
5. Local Mobility Anchor Considerations . . . . . . . . . . . . . 10 5. Local Mobility Anchor Considerations . . . . . . . . . . . . . 10
5.1. Extensions to the Binding Cache Entry . . . . . . . . . . 10 5.1. Extensions to the Binding Cache Entry . . . . . . . . . . 10
5.2. Operational Summary . . . . . . . . . . . . . . . . . . . 11 5.2. Operational Summary . . . . . . . . . . . . . . . . . . . 11
6. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 12 6. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. GRE Key Option . . . . . . . . . . . . . . . . . . . . . . 12 6.1. GRE Key Option . . . . . . . . . . . . . . . . . . . . . . 12
6.2. Proxy Binding Update Message Extension . . . . . . . . . . 13 6.2. Proxy Binding Update Message Extension . . . . . . . . . . 13
6.3. Proxy Binding Acknowledgement Message Extension . . . . . 14 6.3. Proxy Binding Acknowledgement Message Extension . . . . . 14
6.4. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 15 6.4. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 15
7. Data Packets Processing Considerations . . . . . . . . . . . . 15 7. Data Packets Processing Considerations . . . . . . . . . . . . 15
7.1. Tunneling Format . . . . . . . . . . . . . . . . . . . . . 15 7.1. Tunneling Format . . . . . . . . . . . . . . . . . . . . . 16
7.2. TLV-header Tunneling Negotiation . . . . . . . . . . . . . 17 7.2. TLV-header Tunneling Negotiation . . . . . . . . . . . . . 17
7.3. Mobile Access Gateway Operation . . . . . . . . . . . . . 18 7.3. Mobile Access Gateway Operation . . . . . . . . . . . . . 18
7.3.1. Sending and Receiving Data Packets . . . . . . . . . . 19 7.3.1. Sending and Receiving Data Packets . . . . . . . . . . 19
7.4. Local Mobility Anchor Operation . . . . . . . . . . . . . 20 7.4. Local Mobility Anchor Operation . . . . . . . . . . . . . 20
7.4.1. Sending and Receiving Data Packets . . . . . . . . . . 21 7.4.1. Sending and Receiving Data Packets . . . . . . . . . . 21
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
9. Security Considerations . . . . . . . . . . . . . . . . . . . 22 9. Security Considerations . . . . . . . . . . . . . . . . . . . 22
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
11.1. Normative References . . . . . . . . . . . . . . . . . . . 23 11.1. Normative References . . . . . . . . . . . . . . . . . . . 23
skipping to change at page 7, line 20 skipping to change at page 7, line 20
After the local mobility anchor successfully processes the initial After the local mobility anchor successfully processes the initial
Proxy Binding Update and accepts the GRE encapsulation request and Proxy Binding Update and accepts the GRE encapsulation request and
the downlink GRE key based on a policy check, the local mobility the downlink GRE key based on a policy check, the local mobility
anchor MUST include the GRE Key option with the uplink GRE key in the anchor MUST include the GRE Key option with the uplink GRE key in the
GRE Key Identifier field in a successful Proxy Binding GRE Key Identifier field in a successful Proxy Binding
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 local mobility anchor has successfully negotiated and
exchanged the initial GRE keys with the mobile access gateway for a
specific mobile node binding, the local mobility anchor MUST maintain
the same negotiated uplink GRE key for the lifetime of the mobility
session. However, for administrative reasons, e.g., local mobility
anchor reboot, the local mobility anchor MAY change the uplink GRE
key for the mobility session. In that case, some packet loss may be
experienced.
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 SHOULD return Proxy Binding Update message, the local mobility anchor MUST 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 in the last successful Proxy Binding Update for the same gateway in the last successful Proxy Binding Update for the same
mobility session in the GRE key option in a successful Proxy Binding mobility session in the GRE key option in a successful Proxy Binding
Acknowledgement message. 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
 End of changes. 7 change blocks. 
6 lines changed or deleted 15 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/