Re: [netlmm] IPv4 Support

Vijay Devarapalli <vijay.devarapalli@azairenet.com> Wed, 14 March 2007 20:47 UTC

Return-path: <netlmm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRaNl-0006ob-Lg; Wed, 14 Mar 2007 16:47:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRaNk-0006oR-QM for netlmm@ietf.org; Wed, 14 Mar 2007 16:47:36 -0400
Received: from mail2.azairenet.com ([207.47.15.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRaNW-0001Sz-QH for netlmm@ietf.org; Wed, 14 Mar 2007 16:47:36 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Mar 2007 13:47:22 -0700
Message-ID: <45F85F5A.1050607@azairenet.com>
Date: Wed, 14 Mar 2007 13:47:22 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [netlmm] IPv4 Support
References: <73296.53968.qm@web84113.mail.mud.yahoo.com> <45F84C98.3080007@azairenet.com> <45F8529A.6030604@gmail.com> <45F859F2.3020205@azairenet.com> <45F85EA1.8030504@gmail.com>
In-Reply-To: <45F85EA1.8030504@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Mar 2007 20:47:22.0293 (UTC) FILETIME=[F6E99E50:01C76679]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: netlmm@ietf.org
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Errors-To: netlmm-bounces@ietf.org

Alexandru Petrescu wrote:

>>>>> draft-sgundave-mip6-proxymip6-02 also provides support for an
>>>>> IPv4-only mobile node. The mobile node need not have a dual
>>>>> stack. See section 5.6.
>>>>>
>>>>> [behcet] You mean, HA is going to cheat MN and act as if MN is dual 
>>>>> stack? while it is in reality not so? What?
>>>>
>>>> I don't understand your question. The mobile node that supports
>>>> IPv4 only will continue to use IPv4. It is not aware of the fact
>>>> that there is PMIPv6 being used in the network or the fact that
>>>> its IPv4 traffic might be tunneled over an IPv6 tunnel between
>>>> the MAG and the LMA.
>>>
>>> Double-encapsulation for IPv4 Host?
>>>
>>> Would make sense to tunnel an IPv4 packet from MN into an IPv6 tunnel 
>>> (between MAG and LMA) and into another IPv4 packet (the IPv6-in-IPv4 
>>> of DS-MIPv6)?
>>>
>>> If the Host is IPv4, and the network between MAG and LMA is IPv4, why 
>>> encapsulating with IPv6?  Sorry, I may miss something.
>>
>> There is no double encapsulation. It will either be IPv4-in-IPv4
>> or IPv4-in-IPv6.
> 
> For IPv4, this is not clear at all to me.  Which IPv4-in-IPv4 
> encapsulation method?  GRE?  "IP-in-IP" RFC2003?  "Minimal" rfc2004?
> 
> Neither DS-MIPv6 nor PMIPv6 seem to say, IMHO.
> 
> Or maybe any that is available?

See the discussion on Issue 93 on the MIP6 mailing list. This
will be done as part of the DS-MIPv6 spec. It would be a good
idea to just re-use it for PMIPv6.

Vijay

_______________________________________________
netlmm mailing list
netlmm@ietf.org
https://www1.ietf.org/mailman/listinfo/netlmm