Local Mobility Agents in IPv6
draft-dommety-mobileip-lma-ipv6-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2001-07-18 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-dommety-mobileip-lma-ipv6-03.txt
Abstract
Mobile IPv6 is better integrated into IPv6, thereby obviating the need for Foreign Agents (FA) in IPv6 [5]. In IPv6 most, if not all, ofthe functions of the Mobile IPv4 FA [1] are assumed by other parts of the Mobile IPv6 architecture. Specifically, all routers send Router Advertisements and the Mobile Node (MN) does its own detunneling and Routing Header processing.
Authors
Gopal Dommety
(gdommety@cisco.com)
Madhavi Subbarao
(msubbara@cisco.com)
Kent Leung
(kleung@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)