RFC 4066: Candidate Access Router Discovery (CARD)
In plain English — editorial summary, not part of the RFC
To enable seamless IP-layer handover of a mobile node (MN) from one access router (AR) to another, the MN is required to discover the identities and capabilities of candidate ARs (CARs) for handover prior to the initiation of the handover. The act of discovery of CARs has two aspects: identifying the IP addresses of the CARs and finding their capabilities. This process is called "candidate access router discovery" (CARD). At the time of IP-layer handover, the CAR, whose capabilities are a good match to the preferences of the MN, is chosen as the target AR for handover. The protocol described in this document allows a mobile node to perform CARD. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4066
- Published
- July 2005
- Authors
- M. Liebsch; A. Singh; H. Chaskar; D. Funato; E. Shim
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 46
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4067Context Transfer Protocol (CXTP)Current
July 2005
- RFC 4068Fast Handovers for Mobile IPv6Obsoleted
July 2005
- RFC 4280Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control ServersCurrent
December 2005
- RFC 4285Authentication Protocol for Mobile IPv6Current
January 2006
- RFC 4449Securing Mobile IPv6 Route Optimization Using a Static Shared KeyCurrent
June 2006
- RFC 4640Problem Statement for bootstrapping Mobile IPv6 (MIPv6)Current
September 2006
- RFC 5419Why the Authentication Data Suboption is Needed for Mobile IPv6 (MIPv6)Current
January 2009
- RFC 4065Instructions for Seamoby and Experimental Mobility Protocol IANA AllocationsCurrent
July 2005
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?