Re: FW: I-D ACTION:draft-tsirtsis-dsmip-problem-00.txt

Hi George,

Thank you for writing this draft, this is an interesting perspective.
There is one point you do not mention: what if the IPv6 node is using
directly or indirectly IPv6 in IPv4 tunnels for its IPv6 connectivity?
For example, it may derive a 6to4 prefix from its home address
and then uses MIPv4....
There are extra complexities here that I'm not sure I fully understand.
Is it a problem space that you intend to cover?

	- Alain.

On Tuesday, July 29, 2003, at 12:17  PM, Tsirtsis George wrote:

> Hi all,
>
> During the Mobile IP WG meeting in Austria, Hesham and myself brought 
> up the
> issue of mobility management for dual stack nodes.
>
> Thomas N. requested that we put together a problem statement so that 
> we can
> discuss the issue; the draft below was published today - it is short 
> and I
> hope to the point - so do read it :)
>
> I have copied v6ops since I think this is a v4 - v6 migration issue as 
> well
> as Mobile IPv4 and Mobile IPv6 issue.
>
> Let us know what you think.
>
> George
>
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Tuesday, July 29, 2003 5:15 PM
> Subject: I-D ACTION:draft-tsirtsis-dsmip-problem-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: Mobility management for Dual stack mobile nodes  A
>
>                           Problem Statement
> 	Author(s)	: G. Tsirtsis, H. Soliman
> 	Filename	: draft-tsirtsis-dsmip-problem-00.txt
> 	Pages		: 4
> 	Date		: 2003-7-29
> 	
> This draft discusses the issues associated with mobility management
> for dual stack mobile nodes. Currently, two mobility management
> protocols are defined for IPv4 and IPv6. Deploying both in a dual
> stack mobile node introduces a number of inefficiencies. Deployment
> and operational issues motivate the use of a single mobility
> management protocol. This draft discusses such motivations. The draft
> also hints on how current MIPv4 and MIPv6 could be extended so that
> they can support mobility management for a dual stack node.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-tsirtsis-dsmip-problem-00.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the 
> message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the 
> username
> "anonymous" and a password of your e-mail address. After logging in, 
> type
> "cd internet-drafts" and then
> 	"get draft-tsirtsis-dsmip-problem-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	[email protected]
> In the body type:
> 	"FILE /internet-drafts/draft-tsirtsis-dsmip-problem-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> Date: Tue Jul 29, 2003  9:40:01  AM US/Pacific
> To:
> Subject:
>
>
>
> <ATT19898.txt>
>