RFC 6602: Bulk Binding Update Support for Proxy Mobile IPv6
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6602
- Published
- May 2012
- Authors
- F. Abinader; S. Gundavelli; K. Leung; S. Krishnan; D. Premec
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6496Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)Current
February 2012
- RFC 7148Prefix Delegation Support for Proxy Mobile IPv6Current
March 2014
- RFC 7161Proxy Mobile IPv6 (PMIPv6) Multicast Handover Optimization by the Subscription Information Acquisition through the LMA (SIAL)Current
March 2014
- RFC 6636Tuning the Behavior of the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) for Routers in Mobile and Wireless NetworksCurrent
May 2012
- RFC 6705Localized Routing for Proxy Mobile IPv6Current
September 2012
- RFC 7028Multicast Mobility Routing Optimizations for Proxy Mobile IPv6Current
September 2013
- RFC 6097Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6Current
February 2011
- RFC 5949Fast Handovers for Proxy Mobile IPv6Current
September 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?