Re: [Mipshop] RFC4140bis
Vijay Devarapalli <vijay.devarapalli@azairenet.com> Sun, 25 June 2006 17:46 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuYh1-00060u-70; Sun, 25 Jun 2006 13:46:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuYh0-0005yn-1J for mipshop@ietf.org; Sun, 25 Jun 2006 13:46:42 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuYgx-0004PA-NP for mipshop@ietf.org; Sun, 25 Jun 2006 13:46:42 -0400
Received: from [10.1.210.15] ([10.1.210.15]) by bart.corp.azairenet.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 25 Jun 2006 10:46:38 -0700
Message-ID: <449ECBFA.8060607@azairenet.com>
Date: Sun, 25 Jun 2006 10:46:34 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mipshop] RFC4140bis
References: <7EB20EA0938B4D42A2D82689365C9B7A07C74D@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A07C74D@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jun 2006 17:46:38.0671 (UTC) FILETIME=[4F61B5F0:01C6987F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: mipshop@ietf.org
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Errors-To: mipshop-bounces@ietf.org
hi Hesham, there is one issue I would like to raise. on the NETLMM mailing list, I was arguing for not tying HMIPv6 or FMIPv6 with the use of Mobile IPv6. FMIPv6 already does that. it can be used independent of MIPv6. for example, it can provide fast handoffs for a MOBIKE enabled IPsec tunnel. HMIPv6 OTOH has text thats says after sending a BU to the MAP, there MUST be a BU sent to the HA. basically it assumes MIPv6 is being used at the same time. I think it would be a good idea to clean up the text so that HMIPv6 can be used independent of any "global" mobility management protocol. Vijay Soliman, Hesham wrote: > Folks, > > I submitted an RFC 4140bis to start the work towards a PS RFC for > HMIPv6. > The draft can be found at: > > http://www.ietf.org/internet-drafts/draft-soliman-mipshop-4140bis-00.txt > > There are no changes from the RFC but I do have a list of TODOs that I > hope to get a slot for in Montreal. > > Hesham > > _______________________________________________ > Mipshop mailing list > Mipshop@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop
- AW: [Mipshop] Replay protection (was RE: Review o… Tschofenig, Hannes
- RE: [Mipshop] Replay protection (was RE: Review o… Narayanan, Vidya
- [Mipshop] RFC4140bis Soliman, Hesham
- Re: [Mipshop] RFC4140bis Vijay Devarapalli
- RE: [Mipshop] RFC4140bis Soliman, Hesham