Re: [Mip4] FW: I-D ACTION:draft-tsirtsis-v4v6-mipv4-01.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mip4] FW: I-D ACTION:draft-tsirtsis-v4v6-mipv4-01.txt

Hi George,

Tsirtsis, George wrote: 
Raj,

The purpose of DS-MIPv4 is slightly different than what you present
below. Keep in mind that Mobile IPv4 (unlike Mobile IPv6) is deployed
today in multiple networks, corporate and operator owned.

What we are trying to do is to allow these operators to provide IPv6 to
their customers with an incremental approach that fits their deployment
scenario (mobility) and without having to replace their entire
infrastructure.


I already disputed this argument. whats incremental
about deploying IPv6? compared to deploying IPv6
services, upgrading your home agent and mobile node
from MIPv4 to MIPv6 would be trivial. I don't buy
this argument.

Vijay


Think of it this way:

- DS-MIPv4 extensions will ease transition to IPv6 for networks that are
currently Mobile IPv4 based.

- DS-MIPv6 will allow green field IPv6 deployments to happen while
providing access to the IPv4 Internet.

George 

-----Original Message-----
From: Basavaraj Patil [mailto:basavaraj.patil at nokia.com]
Sent: Thursday, April 20, 2006 6:18 PM
To: Tsirtsis, George; mip4 at ietf.org
Subject: Re: [Mip4] FW: I-D ACTION:draft-tsirtsis-v4v6-mipv4-01.txt



George,

So we have many transition mechanisms for supporting IPv6 when a host
is attached to an IPv4 access today. Obviously none of them are able
to deal with mobility (i.e the host moving to different v4
subnets). Your I-D basically is provding yet another transition
mechanism for IPv6 with the added benefit of mobility. We are talking
about dual-stack mobile hosts here, right... And you would agree that
most IPv4 hosts do not have Mobile IPv4 client capability today. Given
that the host is a dual-stack node, it should support MIP6 as part of
its IPv6 stack. Hence it would be better to handle mobility using MIP6
and also provide IPv4 connectivity using such an approach.
In your I-D you state:

"
   On the other hand, and more importantly, it allows dual stack
mobile 
   nodes and networks to utilize a single protocol for the movement of
   both IPv4 and IPv6 stacks in the network topology.
"
The design team in MIP6/NEMO WG is essentially working on addressing
the same issue for DS nodes. Why not use IPv6 mobility as the baseline
mobility protocol?

The other point that I had was if connectivity to IPv6 islands is the
need of the hour with mobility, could you not address this by using a
Mobike solution that also provides transition GW capability on the GW
side?

-Raj 
-----Original Message-----
From: Henrik Levkowetz [mailto:henrik at levkowetz.com]
Sent: Monday, April 17, 2006 10:44 AM
To: Tsirtsis, George
Cc: Pete McCann; mip4 at ietf.org
Subject: Re: [Mip4] FW: I-D
ACTION:draft-tsirtsis-v4v6-mipv4-01.txt 
Hi George,

on 2006-04-17 16:34 Tsirtsis, George said the following: 
Pete/Henrik,

This draft was just updated and it is now available on the I-D
directory.

Good, good.

Based on the discussion during the WG meeting we are requesting
for
this
proposal to be adopted as a working group draft. 
Right.  Well, we didn't have time for any proper discussion during
the meeting, and there were voices which called for that,
explicitly,
so let's start by hearing what people have to say about this
proposal. 
Speak up, people!


Regards,

Henrik


Comments and suggestions are always welcome.

Regards
George

-----Original Message-----
From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org]
Sent: Friday, April 14, 2006 6:50 PM
To: i-d-announce at ietf.org
Subject: I-D ACTION:draft-tsirtsis-v4v6-mipv4-01.txt

A New Internet-Draft is available from the on-line
Internet-Drafts 
directories.


Title  : Dual Stack Mobile IPv4
Author(s) : G. Tsirtsis, et al.
Filename : draft-tsirtsis-v4v6-mipv4-01.txt
Pages  : 17
Date  : 2006-4-14

This specification provides IPv6 extensions to the Mobile IPv4
[MIPv4] protocol. The extensions allow a dual stack node to use
IPv4
and IPv6 home addresses as well as move between IPv4 and dual
stack 
network infrastructures.

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-tsirtsis-v4v6-mipv4-01.txt
To remove yourself from the I-D Announcement list, send a message
to
i-d-announce-request at ietf.org with the word unsubscribe in the
body
of 
the message.
You can also visit
https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-v4v6-mipv4-01.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:
mailserv at ietf.org.
In the body type:
"FILE /internet-drafts/draft-tsirtsis-v4v6-mipv4-01.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.

--
Mip4 mailing list: Mip4 at ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


"This email message and any attachments are confidential
information
of
Starent Networks, Corp. The information transmitted may not be used
to
create or change any contractual obligations of Starent Networks,
Corp.
Any review, retransmission, dissemination or other use of, or
taking
of
any action in reliance upon this e-mail and its attachments by
persons
or
entities other than the intended recipient is prohibited. If you
are
not 
the intended recipient, please notify the sender immediately -- by
replying to this message or by sending an email to
postmaster at starentnetworks.com -- and destroy all copies of this
message
and any attachments without reading or disclosing their contents.
Thank
you." 
--
Mip4 mailing list: Mip4 at ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/ 




--
Mip4 mailing list: Mip4 at ietf.org
   Web interface: https://www1.ietf.org/mailman/listinfo/mip4
    Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



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