[MEXT] I-D ACTION:draft-ietf-mext-rfc3775bis-00.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MEXT] I-D ACTION:draft-ietf-mext-rfc3775bis-00.txt



A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Mobility EXTensions for IPv6 Working Group of the IETF.

	Title		:  Mobility Support in IPv6
	Author(s)	: D. Johnson, C. Perkins, J. Arkko
	Filename	: draft-ietf-mext-rfc3775bis-00.txt
	Pages		: 172
	Date		: 2008-6-3
	
 This document specifies a protocol which allows nodes to remain
   reachable while moving around in the IPv6 Internet.  Each mobile node
   is always identified by its home address, regardless of its current
   point of attachment to the Internet.  While situated away from its
   home, a mobile node is also associated with a care-of address, which
   provides information about the mobile node's current location.  IPv6
   packets addressed to a mobile node's home address are transparently
   routed to its care-of address.  The protocol enables IPv6 nodes to
   cache the binding of a mobile node's home address with its care-of
   address, and to then send any packets destined for the mobile node
   directly to it at this care-of address.  To support this operation,
   Mobile IPv6 defines a new IPv6 protocol and a new destination option.
   All IPv6 nodes, whether mobile or stationary, can communicate with
   mobile nodes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mext-rfc3775bis-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-mext-rfc3775bis-00.txt>
_______________________________________________
MEXT mailing list
MEXT at ietf.org
https://www.ietf.org/mailman/listinfo/mext

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.