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

Jari Arkko <jari.arkko@piuha.net> Tue, 29 January 2008 11:38 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 1JJonj-0004x5-Gv; Tue, 29 Jan 2008 06:38:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJoni-0004x0-Lk for mobopts@irtf.org; Tue, 29 Jan 2008 06:38:50 -0500
Received: from p130.piuha.net ([2001:14b8:400::130] helo=smtp.piuha.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJoni-0002Ik-1l for mobopts@irtf.org; Tue, 29 Jan 2008 06:38:50 -0500
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 2775D198C8E; Tue, 29 Jan 2008 13:38:49 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id ADEE7198957; Tue, 29 Jan 2008 13:38:48 +0200 (EET)
Message-ID: <479F1049.6050108@piuha.net>
Date: Tue, 29 Jan 2008 13:38:49 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.14pre (X11/20071022)
MIME-Version: 1.0
To: Rajeev Koodli <rajeev.koodli@gmail.com>
Subject: Re: [Mobopts] Re: draft-irtf-mobopts-l2-abstractions-04.txt comments
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>
In-Reply-To: <3d57679a0801281008k21537bb8u7b273ce5d184b4cb@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -0.6 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: Fumio Teraoka <tera@ics.keio.ac.jp>, "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

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