Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt
Christophe Janneteau <Christophe.Janneteau@motorola.com> Thu, 17 January 2008 11:42 UTC
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFT8t-0008Hm-R4; Thu, 17 Jan 2008 06:42:43 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1JFT8s-0008Hh-OH for mip4-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 06:42:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFT8s-0008HZ-BE for mip4@ietf.org; Thu, 17 Jan 2008 06:42:42 -0500
Received: from mail128.messagelabs.com ([216.82.250.131]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JFT8r-0002uI-PD for mip4@ietf.org; Thu, 17 Jan 2008 06:42:42 -0500
X-VirusChecked: Checked
X-Env-Sender: Christophe.Janneteau@motorola.com
X-Msg-Ref: server-2.tower-128.messagelabs.com!1200570160!1334323!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 26800 invoked from network); 17 Jan 2008 11:42:40 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-2.tower-128.messagelabs.com with SMTP; 17 Jan 2008 11:42:40 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m0HBgdrX028279; Thu, 17 Jan 2008 04:42:39 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id m0HBgdPd009382; Thu, 17 Jan 2008 05:42:39 -0600 (CST)
Received: from [10.161.201.129] (zfr01-2129.crm.mot.com [10.161.201.129]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id m0HBgbdR009363; Thu, 17 Jan 2008 05:42:38 -0600 (CST)
Message-ID: <478F3F2D.2050201@motorola.com>
Date: Thu, 17 Jan 2008 12:42:37 +0100
From: Christophe Janneteau <Christophe.Janneteau@motorola.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt
References: <00bd01c858eb$9fc6bda0$a864a8c0@china.huawei.com> <478F2C05.3030901@gmail.com>
In-Reply-To: <478F2C05.3030901@gmail.com>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CFilter-Loop: Reflected
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: john.zhao@huawei.com, mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org
John, Alex, My understanding is that the base NEMOv4 specification (draft-ietf-mip4-nemo-v4-base-07.txt) requires double encapsulation to be used for the Foreign Agent CoA mode, but makes it optional for the Collocated CoA mode. In other words, in Collocated CoA mode, the spec allows (and actually encourages = SHOULD) the simple (bi-directional) encapsulation between MR and HA to be used. The double encapsulation is required in the FA CoA mode, to ensure transparency with respect to legacy (RFC3344) Foreign Agent. If simple encapsulation only would be used, the FA would need to be able to forward a packet addressed to an LFN address while only the MR's HoA is present in the FA's visitor list...and the packet would be dropped. The draft "FA extensions to NEMOv4 Base" (draft-ietf-mip4-nemov4-fa-01.txt) aims at addressing this specific issue by defining extension to FA to make it NEMOv4 aware and thus allow the use of simple encapsulation (i.e. of the sole FA<->HA tunnel and nor more the additional inner MR_HOA<-->HA tunnel). Can authors confirm this was the intention of the two different specs (i.e. the NEMOv4 base spec allowing simple encapsulation for the Collocated CoA mode, while a separate doc specifying it for the FA CoA mode)? I have not checked the last version of the base NEMOv4 spec to determine if the current text is explicit enough about these aspects. John what do you think? Thanks Christophe. Alexandru Petrescu wrote: > John.zhao wrote: >> Hi,all In the section 7, to co-located mode MR, it seems that it can >> also send traffics based on the optimization and only tunnel once with >> the CoA as its source address. Right? > > Hi John, thanks for pointing this. The intention is indeed to have the > simple encapsulation (optimization of double encapsulation) described in > a separate document and not here. > > I would like to know which paragraph in section 7 read made you think > optimization is used? I would like to identify it and keep track. > > I could think of the following in section 7: >> For optimization, the Home Agent SHOULD only encapsulate the packet >> with the tunnel header (source IP address set to Home Agent and >> destination IP address set to CoA) for Collocated CoA mode. > > Also know that I'm not sure who/how/when can make modifications to the > document, since it's advanced a bit past the WG discussion. > > Alex > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > -- Mip4 mailing list: Mip4@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] I-D Action:draft-ietf-mip4-nemo-v4-base-07… Internet-Drafts
- Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-bas… Alexandru Petrescu
- RE: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-bas… John.zhao
- Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-bas… Alexandru Petrescu
- Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-bas… Christophe Janneteau
- Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-bas… George Tsirtsis
- RE: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-bas… John.zhao