MIPv4 Registration Request

Description

The MIPv4 Registration Request (RRQ) is the initiating message in the Mobile IPv4 (MIPv4) registration procedure, sent by the Mobile Node (MN) to its Home Agent (HA). Its purpose is to inform the HA of the MN's current point of attachment to the internet, represented by a Care-of Address (CoA), and to request that the HA bind this CoA to the MN's permanent Home Address. This binding is essential for enabling IP mobility, as it instructs the HA to intercept packets destined for the Home Address and forward them via IP-in-IP encapsulation to the CoA.

The RRQ packet is constructed according to the MIPv4 specification (RFC 5944). It contains mandatory fields such as the MN's Home Address, the Home Agent's address, and the Care-of Address being registered. A critical field is the Identification, a 64-bit number generated by the MN, which is used to match this request with the subsequent Registration Response (RRP) and to protect against replay attacks. The RRQ also specifies a requested Lifetime for the binding, after which it will expire unless renewed. Extensions are often included, most importantly the Mobile-Home Authentication Extension, which contains a digital signature (using a shared secret) to prove the MN's identity and protect the message's integrity.

The RRQ can be sent directly to the HA if the MN has a co-located CoA, or it can be relayed via a Foreign Agent (FA) present in the visited network. When an FA is used, the MN sends the RRQ to the FA, which then forwards it to the HA. The FA may also add its own CoA to the message. Upon sending the RRQ, the MN starts a retransmission timer; if no RRP is received, it will retransmit the request. This process occurs whenever the MN acquires a new CoA (e.g., after moving to a new subnet) or when an existing binding is nearing expiration and needs renewal.

In the context of 3GPP standards, the RRQ is utilized as part of the MIPv4 FA mode procedures defined for interworking with non-3GPP access networks, such as WLAN. The UE (acting as the MN) would send an RRQ to register its CoA (provided by the WLAN access network) with a Home Agent function residing in the 3GPP Packet Data Network Gateway (PDN GW). This allows the UE to maintain IP connectivity through the 3GPP core network while physically connected via WLAN.

Purpose & Motivation

The MIPv4 Registration Request exists to initiate the mobility binding process, which is the core mechanism enabling a device to be reachable at a constant IP address while moving across different IP subnets. The fundamental problem it solves is the conflict between the Internet's routing architecture, which assumes an IP address denotes a fixed network location, and the need for mobile devices to change their physical point of attachment. Without the RRQ to signal a new location, a mobile node would become unreachable after moving.

The creation of the RRQ and the MIPv4 protocol was motivated by the desire for seamless, network-layer mobility for IP hosts. Prior solutions were application-specific or relied on link-layer mechanisms that didn't scale across heterogeneous networks. The RRQ provides a standardized, secure, and efficient way for a mobile node to proactively announce its new location to the entity (the Home Agent) responsible for managing its reachability. This allows all correspondent nodes to continue sending packets to the stable Home Address, unaware of the mobility.

3GPP adopted MIPv4 and the RRQ message to fulfill specific mobility requirements in early interworking scenarios, particularly with WLAN. It addressed the limitation of 3GPP's own GTP-based mobility, which was optimized within the 3GPP ecosystem but not for external IP networks. The RRQ provided a well-known, IETF-standardized method for a UE to register with the 3GPP core from an external access network, enabling operators to offer integrated services. It served as a bridge between non-3GPP IP access and the 3GPP packet core before the more comprehensive Proxy Mobile IPv6 (PMIPv6) became the preferred network-based solution.

Key Features

• Initiates the binding update procedure between a Mobile Node and its Home Agent
• Carries the Mobile Node's current Care-of Address and requested binding lifetime
• Includes a unique Identification field for message matching and replay protection
• Supports authentication extensions to securely prove the Mobile Node's identity
• Can be sent directly or via a Foreign Agent acting as a relay
• Triggers the Home Agent to establish a tunnel for forwarding IP packets

Evolution Across Releases

Defining Specifications