IETF Logo Mail Archive

Re: [MEXT] FW: DISCUSS and COMMENT: draft-ietf-mext-nemo-v4traversal

Hesham Soliman <hesham@elevatemobile.com> Mon, 23 February 2009 11:42 UTC

Return-Path: <hesham@elevatemobile.com>
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A54A73A67A1 for <mext@core3.amsl.com>; Mon, 23 Feb 2009 03:42:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sNpW4HWS89pW for <mext@core3.amsl.com>; Mon, 23 Feb 2009 03:42:50 -0800 (PST)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id CCA9F3A67D4 for <mext@ietf.org>; Mon, 23 Feb 2009 03:42:49 -0800 (PST)
Received: from [60.224.64.52] (helo=[192.168.0.187]) by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1 (Debian)) id 1LbZDA-00043i-Tj; Mon, 23 Feb 2009 22:43:01 +1100
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Mon, 23 Feb 2009 22:42:56 +1100
From: Hesham Soliman <hesham@elevatemobile.com>
To: Christian.Kaas-Petersen@tieto.com, Basavaraj.Patil@nokia.com, mext@ietf.org
Message-ID: <C5C8D6F0.BA93%hesham@elevatemobile.com>
Thread-Topic: [MEXT] FW: DISCUSS and COMMENT: draft-ietf-mext-nemo-v4traversal
Thread-Index: AcmRYrn9Oi5m4+57iEyWrCYRX2CktwA36z8rAFfqHiUAgAC04AABiywqAAB7TZAAAGyQ9g==
In-Reply-To: <D3CFEF84287B46408A7F0405EE7C545701C81F2A@corvette.eu.tieto.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [MEXT] FW: DISCUSS and COMMENT: draft-ietf-mext-nemo-v4traversal
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 11:42:50 -0000

On 23/02/09 10:39 PM, "Christian.Kaas-Petersen@tieto.com"
<Christian.Kaas-Petersen@tieto.com> wrote:

> So there will be a Destination Option / Home Address Option in an MPS
> when the MN is attached to an IPv4-only foreign network?

=> Yes, we have to do that according to 3775. I assume we have to leave the
HoA in the src address as well. Looks silly but there doesn't seem to be
another option apart from tunnelling or using a mapped address and we can't
do the latter. The former is even sillier.

Hesham

> 
> Christian 
> 
>> -----Original Message-----
>> From: Hesham Soliman [mailto:hesham@elevatemobile.com]
>> Sent: 23. februar 2009 12:17
>> To: Kaas-Petersen Christian; Basavaraj.Patil@nokia.com; mext@ietf.org
>> Subject: Re: [MEXT] FW: DISCUSS and COMMENT:
>> draft-ietf-mext-nemo-v4traversal
>> 
>>> 
>>> In my view, this does not change with DSMIP, except that the home
>>> address is no longer stored in a destination option but in the
>>> (inner) IPv6 source address.  Because the mobile node already knows
>>> its IPv6 home address, I should think it a valid
>> functionality to ask
>>> the home agent of any updates in the IPv6 home prefixes.
>> 
>> => DSMIP will not change the use of the HAO for MPS and MPA.
>> The HAO will still be used.
>> 
>> Hesham
>>

v2.23.0 | Report a Bug | By Email