Bulk Binding Update Support for Proxy Mobile IPv6
RFC 6602
Internet Engineering Task Force (IETF) F. Abinader, Ed.
Request for Comments: 6602 Instituto Nokia de Tecnologia
Category: Standards Track S. Gundavelli, Ed.
ISSN: 2070-1721 K. Leung
Cisco
S. Krishnan
Ericsson
D. Premec
Unaffiliated
May 2012
Bulk Binding Update Support for Proxy Mobile IPv6
Abstract
For extending the lifetime of a mobility session, the Proxy Mobile
IPv6 specification requires the mobile access gateway to send a Proxy
Binding Update message to the local mobility anchor on a per-session
basis. In the absence of signaling semantics for performing
operations with group-specific scope, this results in a significant
amount of signaling traffic on a periodic basis between a given
mobile access gateway and a local mobility anchor. This document
defines optimizations to the binding update and revocation operations
in Proxy Mobile IPv6 for performing operations with group-specific
scope with the use of a group identifier.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6602.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
Abinader, et al. Standards Track [Page 1]
RFC 6602 Bulk Binding Update Support May 2012
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
2. Conventions and Terminology .....................................4
2.1. Conventions ................................................4
2.2. Terminology ................................................4
3. Bulk Binding Update Overview ....................................4
3.1. Motivation .................................................4
3.2. General Operation ..........................................5
4. Message Formats .................................................8
4.1. Extensions to Proxy Binding Update Message .................9
4.2. Extensions to Proxy Binding Acknowledgement Message .......10
4.3. Mobile Node Group Identifier Option .......................10
4.4. Status Codes ..............................................11
5. Protocol Considerations ........................................12
5.1. MAG Considerations ........................................12
5.1.1. Extensions to Binding Update List Entry
Data Structure .....................................12
5.1.2. Requesting Bulk Binding Update Support for
a Mobility Session .................................12
5.1.3. Supporting Bulk Binding Updates ....................14
5.2. LMA Considerations ........................................15
5.2.1. Extensions to Binding Cache Entry Data Structure ...15
5.2.2. Enabling Bulk Binding Update Support for a
Mobility Session ...................................16
5.2.3. Supporting Bulk Binding Updates ....................18
6. Protocol Configuration Variables ...............................20
6.1. Local Mobility Anchor - Configuration Variables ...........20
6.2. Mobile Access Gateway - Configuration Variables ...........20
7. IANA Considerations ............................................20
8. Security Considerations ........................................21
Show full document text