Re: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
Vijay Devarapalli <vijay.devarapalli@azairenet.com> Fri, 22 December 2006 19:21 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxpwz-00076k-Dl; Fri, 22 Dec 2006 14:21:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxpwx-00076c-U8 for mip4@ietf.org; Fri, 22 Dec 2006 14:20:59 -0500
Received: from mail2.azairenet.com ([66.92.223.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxpww-0006rg-Kr for mip4@ietf.org; Fri, 22 Dec 2006 14:20:59 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 22 Dec 2006 11:20:57 -0800
Message-ID: <458C301B.2030104@azairenet.com>
Date: Fri, 22 Dec 2006 11:20:59 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Hans Sjostrand <hans@ipunplugged.com>
Subject: Re: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com> <45895610.6040701@ipunplugged.com>
In-Reply-To: <45895610.6040701@ipunplugged.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Dec 2006 19:20:57.0913 (UTC) FILETIME=[4EE88290:01C725FE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: mip4@ietf.org, McCann Peter-A001034 <pete.mccann@motorola.com>
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
Hans Sjostrand wrote: > Pete and Vijay, > > Some thoughts > > 1. Access mode home seams to be forgotten. > The answer there seams to be "Yes". Is the intention to pass WGLC > without taking home mode in consideration? The home address has not been considered as an access mode in any of the MIP4 VPN documents so far. We can either continue not counting this as an access mode, or add a new access mode to the draft. 3.1.1. Access mode: 'h' This access mode is standard Mobile IPv4 [2] when the mobile node is attached to its home link. The mobile node must detect that it is connected to home link before using this mode. It seems unnecessary to me. Comments anyone else? > 3. Dual tunnel a normative reference > Vijay has proposed to make Dual tunnel a normative reference. I was sort > of hoping that the draft-ietf-mip4-mobike-connectivity could be made > self sufficient instead. But if it is the intention of the editors and > working group to push these as a bundle I'm not the person to question > that. Yes, this is an issue. For now, I am hoping both documents will advance as proposed standards. If ever we need to make draft-ietf-mip4-mobike-connectivity self contained, then we would have to add more text on crossing security boundaries to the draft. Vijay -- 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] Summing up: draft-ietf-mip4-mobike-connect… McCann Peter-A001034
- RE: [Mip4] Summing up: draft-ietf-mip4-mobike-con… Narayanan, Vidya
- Re: [Mip4] Summing up: draft-ietf-mip4-mobike-con… Henrik Levkowetz
- Re: [Mip4] Summing up: draft-ietf-mip4-mobike-con… Vijay Devarapalli
- Re: [Mip4] Summing up: draft-ietf-mip4-mobike-con… Hans Sjostrand
- Re: [Mip4] Summing up: draft-ietf-mip4-mobike-con… Vijay Devarapalli
- Re: [Mip4] Summing up: draft-ietf-mip4-mobike-con… Vijay Devarapalli