Skip to main content

Issues in candidate access router discovery for seamless IP-level handoffs

Document Type Expired Internet-Draft (seamoby WG)
Expired & archived
Authors Dirk Trossen , Hemant Chaskar , Govind Krishnamurthi , James Kempf , Hemant Chaskar
Last updated 2015-10-14 (Latest revision 2002-10-17)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired (IESG: Dead)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Handoff in IP mobility protocols involves moving a mobile node's Layer 3 routing reachability point from one access router to another, before or after the mobile node has established a Layer 2 connection with the radio access point that is covered by the new access router. In addition, other context information about the mobile node's IP service may be transferred from the old access router to the new one, in order to minimize the service disruption during the handoff process. While the exact details of how this is accomplished vary depending on the IP mobility and seamless handoff protocols, one common thread required for IP-level handoffs is discovering the candidate access routers for the mobile node's handoff. Discovering the candidate access router involves identifying its IP address as well as its capabilities that the mobile node might be interested in. At the time of IP-level handoff, if a collection of candidates is identified, an algorithm is run to determine the target access router for the mobile node's handoff. This document describes the problem of candidate access router discovery. The document does not discuss the algorithm by which the actual target access router is selected, nor how the handoff to the target is achieved.


Dirk Trossen
Hemant Chaskar
Govind Krishnamurthi
James Kempf
Hemant Chaskar

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)