Re: [Mobopts] Re: draft-irtf-mobopts-l2-abstractions-04.txt comments

Fumio Teraoka <tera@ics.keio.ac.jp> Tue, 29 January 2008 12:41 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 1JJpmU-0000r7-8x; Tue, 29 Jan 2008 07:41:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJpmT-0000pH-4E for mobopts@irtf.org; Tue, 29 Jan 2008 07:41:37 -0500
Received: from maro.tera.ics.keio.ac.jp ([131.113.71.3] helo=smtp.tera.ics.keio.ac.jp) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JJpmQ-0006Eg-Jt for mobopts@irtf.org; Tue, 29 Jan 2008 07:41:37 -0500
Received: (qmail 44862 invoked from network); 29 Jan 2008 21:41:29 +0900
X-Authentication: tera was authenticated by 0 at 29 Jan 2008 21:41:29 +0900
Received: from unknown (HELO hotaka.ics.keio.ac.jp) (2001:200::6800::3) by 0 with SMTP; 29 Jan 2008 21:41:29 +0900
Message-Id: <6.2.3.4.2.20080129213835.0b497c10@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2J rev4.2
Date: Tue, 29 Jan 2008 21:41:32 +0900
To: Jari Arkko <jari.arkko@piuha.net>, Rajeev Koodli <rajeev.koodli@gmail.com>
From: Fumio Teraoka <tera@ics.keio.ac.jp>
Subject: Re: [Mobopts] Re: draft-irtf-mobopts-l2-abstractions-04.txt comments
In-Reply-To: <479F1049.6050108@piuha.net>
References: <C368CFA5.1D589%rajeev.koodli@nokia.com> <4761A5BE.8050509@piuha.net> <6.2.3.4.2.20080106232845.079864c0@localhost> <4784CDE1.5050105@piuha.net> <6.2.3.4.2.20080115000659.085e8240@localhost> <3d57679a0801281008k21537bb8u7b273ce5d184b4cb@mail.gmail.com> <479F1049.6050108@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Rajeev Koodli <rajeev.koodli@nokia.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

Jari, Rajeev,

I will submit a new version (-06) by the end of this week.

Regards,
Fumio Teraoka

At 08/01/29 13:38 +0200, Jari Arkko wrote:
>Rajeev Koodli kirjoitti:
>>
>> Hi Jari,
>>
>> could we close this one? We could then send the revised ID for
>> publication.
>>
>> Thanks,
>>
>> -Rajeev
>>
>>
>>
>> On Jan 14, 2008 7:32 AM, Fumio Teraoka <tera@ics.keio.ac.jp
>> <mailto:tera@ics.keio.ac.jp>> wrote:
>>
>>     Jari,
>>
>>     Thanks for comments. Replies are inline:
>>
>>     At 08/01/09 15:36 +0200, Jari Arkko wrote:
>>     (snip)
>>
>>     >> We modified the document as follows:
>>     >>
>>     >> - Sec. 4.5 L2-LinkUp (Type 2):
>>     >>   - old: The L2-LinkUp.indication primitive is asynchronously
>>     provided to
>>     >>          an upper layer when a new link is connected.
>>     >>
>>     >>   - new: The L2-LinkUp.indication primitive is asynchronously
>>     provided to
>>     >>          an upper layer when a new link is connected and IP
>>     packets can be
>>     >>          transmitted through the new link. As described in RFC
>>     4957[7],
>>     >>          what "link is connected" means depends on link types.
>>     >
>>     >Good.
>>     >
>>     >>  For example,
>>     >>          in case of the infrastructure mode in IEEE802.11
>>     (WiFi), this
>>     >>          primitive is provided when an association to an access
>>     point is
>>     >>          established.
>>     >>
>>     >
>>     >Really? I was under the impression that association was an early
>>     phase
>>     >and you would need to wait for something else if security was
>>     applied. I
>>     >could be mistaken, but this discussion is an example of the sort of
>>     >detail level that a fully defined interface would have to go to.
>>
>>     In my understanding of the IEEE802.11 infrastructure mode, at first,
>>     a mobile node is in Unauthenticated & Unassociated State. Next,
>>     the mobile node is authenticated and then the state changes to
>>     Authenticated & Unassociated State. Finally, an association is
>>     established with the AP and then the state changes to Authenticated
>>     and Associated state. Thus, we defined that L2-LinkUp is provided
>>     when an association is established in WiFi.
>>
>
>OK
>
>>
>>     (snip)
>>
>>     >> The quality levels of a device are independent of those of
>>     other devices.
>>     >> We added sentences at the last of "Sec. 6.2 Condition" as follows:
>>     >>
>>     >>   The quality levels of a L2 device are independent of those of
>>     other
>>     >>   devices.  An example of the thresholds among the five levels
>>     are described
>>     >>   in Appendix E.
>>     >>
>>     >> We also added the description about the example thresholds in
>>     Appendix E.
>>     >>
>>     >
>>     >The added text is good, but I'm still not convinced that you have a
>>     >generic solution capable of operating in different conditions. It
>>     might
>>     >be more useful to simply acknowledge that making decisions based on
>>     >these metrics is error prone and not guaranteed to result in optimal
>>     >choice of links.
>>
>>     I agree that "decisions based on these metrics is error prone and
>>     not guaranteed to result in optimal choice of links."
>>     I'll attend this sentence at the last of "6.2 Condition".
>>
>
>OK
>
>
>jari
>>
>>
>>     (snip)
>>
>>     Best Regards,
>>
>>     Fumio Teraoka
>>
>>
>>     _______________________________________________
>>     Mobopts mailing list
>>     Mobopts@irtf.org <mailto:Mobopts@irtf.org>
>>     https://www1.ietf.org/mailman/listinfo/mobopts
>>
>>


_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts