Re: [Mobopts] FW: Mobopts review
Rajeev Koodli <rajeev.koodli@nokia.com> Tue, 07 August 2007 17:49 UTC
Return-path: <mobopts-bounces@irtf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IITBZ-0005ZT-US; Tue, 07 Aug 2007 13:49:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IITBY-0005ZM-Ml for mobopts@irtf.org; Tue, 07 Aug 2007 13:49:36 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IITBX-0005EN-0X for mobopts@irtf.org; Tue, 07 Aug 2007 13:49:36 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l77HgSbQ028263; Tue, 7 Aug 2007 20:42:54 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Aug 2007 20:42:42 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Aug 2007 12:42:40 -0500
Received: from 10.241.59.91 ([10.241.59.91]) by daebe103.NOE.Nokia.com ([10.241.35.24]) with Microsoft Exchange Server HTTP-DAV ; Tue, 7 Aug 2007 17:42:40 +0000
User-Agent: Microsoft-Entourage/11.2.4.060510
Date: Tue, 07 Aug 2007 10:42:42 -0700
Subject: Re: [Mobopts] FW: Mobopts review
From: Rajeev Koodli <rajeev.koodli@nokia.com>
To: Rajeev Koodli <rajeev.koodli@nokia.com>, tera@ics.keio.ac.jp
Message-ID: <C2DDFD22.14A9D%rajeev.koodli@nokia.com>
Thread-Topic: [Mobopts] FW: Mobopts review
Thread-Index: AcfQiawc6nxDKjx8EdyNZwAWy5YJpwIkK69D
In-Reply-To: <C2CF9E6C.1483F%rajeev.koodli@nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 07 Aug 2007 17:42:40.0747 (UTC) FILETIME=[5A1B63B0:01C7D91A]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: ext John L <johnl@iecc.com>, "mobopts@irtf.org" <mobopts@irtf.org>
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=subscribe>
Errors-To: mobopts-bounces@irtf.org
Hello, I have few more suggestions (editorial) to revise the document. Regards, -Rajeev Abstract: "To solve the problem, this draft defines nine kinds of L2 abstractions in the form of "primitive" to achieve fast handovers in the network.." ^^^^ primitives 1. Introduction In recent years, the execution environment around computers is not static and changes dynamically. Especially, when a mobile node moves to a different network, its communication environment considerably changes. For example, in the case of wireless communication, parameters such as radio strength largely changes depending on time or site. Replace above paragraph with the following: RK> Recent years have witnessed rapid proliferation of wireless networks as well as mobile devices accessing them. Unlike wired network environments, wireless networks are characterized by dynamically changing radio conditions, connectivity, and available bandwidth. RK> You may combine the following paragraph with the above to make it a single paragraph. For efficient network communication, it is vital for a protocol layer to know or utilize other layer's control information. Mobile IPv4 [1] and Mobile IPv6 [2] have been standerdized to support communication with mobile nodes. There are several proposals for seamless handovers in IPv6 network such as Fast Handovers for Mobile IPv6 (FMIPv6) [3] and Hierarchical Mobile IPv6 (HMIPv6) [4]. In FMIPv6, the network layer must know the indication of a handover from the link layer in advance to achieve seamless handovers. However, control information exchange between protocol layers is not allowed ^^ => typically not available because each protocol layer is designed independently. To solve the problem, this draft defines nine kinds of L2 abstractions in the form of "primitive" to achieve fast handovers ^^ primitives in the network layer. This mechanism is called "L3-driven fast handovers" because the network layer initiates L2 and L3 handovers by using the "primitives". 4.1. L2-LinkStatus (Type 1) The L2-LinkStatus.request primitive is sent to the link layer when an upper layer needs the current information of a link. The L2- LinkStatus.request primitive contains the "Network Interface ID" parameter (See Section 5.1). ^^^^^^^^^^ 6.1. PoA ^^^^ Expand PoA On 7/27/07 1:06 PM, "ext Rajeev Koodli" <rajeev.koodli@nokia.com> wrote: > > > Hello, > > Here is the IRSG review of L2 abstractions ID. I think the comments are > mostly editorial and very useful in improving the overall quality of the > document. > > Thanks John for your review. > > Authors: please take a look and respond. > > Regards, > > -Rajeev > -- > http://people.nokia.net/~rajeev > > > ------ Forwarded Message > From: ext John L <johnl@iecc.com> > Date: Fri, 27 Jul 2007 16:00:06 -0400 (EDT) > To: Rajeev Koodli <rajeev.koodli@nokia.com> > Cc: Aaron Falk <falk@bbn.com> > Subject: Mobopts review > > I've read through draft-irtf-mobopts-l2-abstractions-03, and I find it > almost but not quite ready for publication. > > Keeping in mind that I am not particularly expert in mobile computing, > the content seems fine. It needs a careful copy-edit to fix some > language problems that are distracting and occasionally ambiguous. For > example, page 6 defines PoA as "the attachment point of a mobile node". > PoA presumably stands for Point of Attachment, and it just seems odd to > have the abbreviation and definition not match. More seriously, there are > places where the complexity of English syntax leads to confusion. For > example, on page 3 the last sentence of the first paragraph reads "a > layer can evenly communicate with each other", which I think is trying to > say that the communication between layers is symmetrical, but I'm not > sure. A careful copy edit, in consultation with the authors to be sure > the ambiguities are resolved correctly, should solve this. > > Appendix B appears to contain two paper examples and one report of an > experiment. They're all fine, but it would be helpful to explain either > why they tested the third example or why they didn't test the first two. > > None of these problems are major, and I expect all could be fixed in one > more editing pass. > > Regards, > John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for > Dummies", > Information Superhighwayman wanna-be, http://www.johnlevine.com, ex-Mayor > "More Wiener schnitzel, please", said Tom, revealingly. > > ------ End of Forwarded Message > > > _______________________________________________ > Mobopts mailing list > Mobopts@irtf.org > https://www1.ietf.org/mailman/listinfo/mobopts -- http://people.nokia.net/~rajeev _______________________________________________ Mobopts mailing list Mobopts@irtf.org https://www1.ietf.org/mailman/listinfo/mobopts
- [Mobopts] FW: Mobopts review Rajeev Koodli
- Re: [Mobopts] FW: Mobopts review Rajeev Koodli
- [Mobopts] Draft-irtf-mobopts-l2-abstractions Rajeev Koodli
- [Mobopts] Re: Draft-irtf-mobopts-l2-abstractions John L
- [Mobopts] FW: Draft-irtf-mobopts-l2-abstractions Rajeev Koodli