[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]

- Ray

------------------------------------------------------------------------
Raymond J. Jayabal                 | I2R, A-STAR
jraymond@icr.a-star.edu.sg         | 20 Science Park Rd #02-34/37
Tel: +65 6870 9330                 | Singapore 117674
------------------------------------------------------------------------


----- Original Message -----

Subject: RE: [Seamoby] LWAPP


> Are you all aware that IEEE 802.11k is working to make the
measurements in the 802.11 PHYs and MACs available for upper layers?
This includes per AP tables and per STA tables.  I think your  triggers
could be determined from the signal strength and other measurements
available through 802.11k.
>
> Richard H. Paine
> Success is getting what you want, happiness is liking what you get!
> Work: 425-865-4921
> Pager: 206-797-4580
> Cell:  206-854-8199
> IPPhone:  425-373-8964
> Email:  richard.h.paine@boeing.com
>
>
> -----Original Message-----
&amp;amp;gt; From: Alper Yegin [&amp;lt;a  href=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:alper@docomolabs-usa.com&amp;quot&quot";>mailto:alper@docomolabs-usa.com&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="mailto:alper@docomolabs-usa.com&amp;quot";>mailto:alper@docomolabs-usa.com&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:alper@docomolabs-usa.com&quot";>mailto:alper@docomolabs-usa.com&quot</a>;&gt;<a  rel="nofollow" href="mailto:alper@docomolabs-usa.com";>mailto:alper@docomolabs-usa.com</a>&lt;/a&gt;&amp;lt;/a&amp;gt;]
&amp;amp;gt; Sent: Tuesday, April 08, 2003 3:59 PM
&amp;amp;gt; To: Pat Calhoun
&amp;amp;gt; Cc: seamoby@ietf.org; skelly@airespace.com; rsuri@airespace.com;
bob@airespace.com; Glen Zorn; funato@docomolabs-usa.com
&amp;amp;gt; Subject: Re: [Seamoby] LWAPP
&amp;amp;gt;
&amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt; No, it's does alot more than just configure APs. The information
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt; provided in the protocol can provide many additional features,
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt; include fast handoffs, creating a secure interface between the AP
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt; and the AR, etc.
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt; I don't see any fast handoffs information carried in the draft.
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;
&amp;amp;gt; &amp;amp;gt; A foobar on my part. There is a message between the AP and the AR
that
&amp;amp;gt; &amp;amp;gt; is used to communicate a trigger. Used with the signal strength in
the
&amp;amp;gt; &amp;amp;gt; message (which is already in the draft), it can be used by the AR to
&amp;amp;gt; &amp;amp;gt; determine a mobile's current point of attachment.
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt; I put out the document rather hastily, but will follow up with
another
&amp;amp;gt; &amp;amp;gt; version that includes this (and the formatting problems).
&amp;amp;gt;
&amp;amp;gt; If you are talking about carrying L2 event notifications around,
please see:
&amp;amp;gt;
&amp;amp;gt; &amp;lt;a  href=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="http://ietf.org/internet-drafts/draft-yegin-l2-triggers-00.txt&amp;quot&quot";>http://ietf.org/internet-drafts/draft-yegin-l2-triggers-00.txt&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="http://ietf.org/internet-drafts/draft-yegin-l2-triggers-00.txt&amp;quot";>http://ietf.org/internet-drafts/draft-yegin-l2-triggers-00.txt&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="http://ietf.org/internet-drafts/draft-yegin-l2-triggers-00.txt&quot";>http://ietf.org/internet-drafts/draft-yegin-l2-triggers-00.txt&quot</a>;&gt;<a  rel="nofollow" href="http://ietf.org/internet-drafts/draft-yegin-l2-triggers-00.txt";>http://ietf.org/internet-drafts/draft-yegin-l2-triggers-00.txt</a>&lt;/a&gt;&amp;lt;/a&amp;gt;
&amp;amp;gt;
&amp;amp;gt; How does what you have in mind compare/relate to the above draft?
&amp;amp;gt;
&amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt; I'm not sure
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt; what exactly you mean by &amp;amp;quot;secure interface&amp;amp;quot;, but based on my
reading
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt; of the draft the only security is for protecting this protocol's
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt; packets between the AP and the AR. And this is not an additional
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt; feature but a requirement on the protocol.
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt; Correct - that is the secure interface I mentioned. It is assumed
that
&amp;amp;gt; &amp;amp;gt; the user will protect his/her own traffic... and that the AR will
&amp;amp;gt; &amp;amp;gt; enforce whatever policy it has defined. LWAPP was not intended to
&amp;amp;gt; &amp;amp;gt; replace end-to-end security, but securing that interface *is* a
&amp;amp;gt; &amp;amp;gt; requirement, not an additional feature. A malicious AP can do very
&amp;amp;gt; &amp;amp;gt; nasty things to an AR.
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt; Further, the market has made it pretty clear that they no longer
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt; want smart APs that have to be managed individually. They want a
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt; central point of control, with remote interfaces. But this is a
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;&amp;amp;gt; market issue, not a standards one.
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt; This makes sense. But is there any difference between your proposed
&amp;amp;gt; &amp;amp;gt;&amp;amp;gt; protocol and SNMP in this context?
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt; Sure, let me explain.
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt; What we've heard from our customers is that they are tired to
managing
&amp;amp;gt; &amp;amp;gt; APs scattered throughout their networks (oh, and it's clear the
&amp;amp;gt; &amp;amp;gt; industry is moving in this direction, these are not just my own
&amp;amp;gt; &amp;amp;gt; ramblings). The issue SNMP in the AP is that it does require the
&amp;amp;gt; &amp;amp;gt; administrator to touch the device. People want a secure plug and
play
&amp;amp;gt; &amp;amp;gt; solution. If SNMP is on the box, you must configure the community
&amp;amp;gt; &amp;amp;gt; string (and user in the case of v3), and this security relationship
is
&amp;amp;gt; &amp;amp;gt; one that must be administered over the course of the device's
&amp;amp;gt; &amp;amp;gt; lifetime. The market is pretty clear in the fact that it wants an AP
&amp;amp;gt; &amp;amp;gt; that can auto-discover ARs and establish a security relationship w/o
&amp;amp;gt; &amp;amp;gt; any administrator involvement. The draft's use of certificates
&amp;amp;gt; &amp;amp;gt; provides this feature, but I agree that a shared secret mechanism
&amp;amp;gt; &amp;amp;gt; should probably  be defined as well.
&amp;amp;gt;
&amp;amp;gt; If I'm understanding this right, the problem is that SNMP does not
know how to use certificates for authentication.... I don't know how
hard it is to solve this if it is needed as you described....
&amp;amp;gt;
&amp;amp;gt; alper
&amp;amp;gt;
&amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt; PatC
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt; _______________________________________________
&amp;amp;gt; &amp;amp;gt; Seamoby mailing list
&amp;amp;gt; &amp;amp;gt; Seamoby@ietf.org &amp;lt;a  href=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>&lt;/a&gt;&amp;lt;/a&amp;gt;
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt;
&amp;amp;gt; _______________________________________________
&amp;amp;gt; Seamoby mailing list
&amp;amp;gt; Seamoby@ietf.org
&amp;amp;gt; &amp;lt;a  href=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>&lt;/a&gt;&amp;lt;/a&amp;gt;
&amp;amp;gt; _______________________________________________
&amp;amp;gt; Seamoby mailing list
&amp;amp;gt; Seamoby@ietf.org
&amp;amp;gt; &amp;lt;a  href=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>&lt;/a&gt;&amp;lt;/a&amp;gt;
&amp;amp;gt;


_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
&amp;lt;a  href=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>&lt;/a&gt;&amp;lt;/a&amp;gt;



&amp;lt;/pre&amp;gt;

&amp;lt;!--X-Body-of-Message-End--&amp;gt;
&amp;lt;!--X-MsgBody-End--&amp;gt;
&amp;lt;!--X-Follow-Ups--&amp;gt;
&amp;lt;hr&amp;gt;
&amp;lt;!--X-Follow-Ups-End--&amp;gt;
&amp;lt;!--X-References--&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;References&amp;lt;/strong&amp;gt;:
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;&amp;lt;a name=&amp;quot;01934&amp;quot; href=&amp;quot;msg01934.html&amp;quot;&amp;gt;RE: [Seamoby] LWAPP&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;&amp;lt;em&amp;gt;From:&amp;lt;/em&amp;gt; &amp;amp;quot;Paine, Richard H&amp;amp;quot; &amp;amp;lt;richard.h.paine@boeing.com&amp;amp;gt;&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;
&amp;lt;!--X-References-End--&amp;gt;
&amp;lt;!--X-BotPNI--&amp;gt;
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;Prev by Date:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg01935.html&amp;quot;&amp;gt;[Seamoby] CFP IEEE/IFIP Intern. Conference on Management of Multimedia Networks &amp;amp;amp; Services 2003&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Next by Date:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg01937.html&amp;quot;&amp;gt;Re: [Seamoby] LWAPP&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Previous by thread:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg01934.html&amp;quot;&amp;gt;RE: [Seamoby] LWAPP&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Next by thread:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg01938.html&amp;quot;&amp;gt;RE: [Seamoby] LWAPP&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Index(es):
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;a href=&amp;quot;maillist.html#01936&amp;quot;&amp;gt;&amp;lt;strong&amp;gt;Date&amp;lt;/strong&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;a href=&amp;quot;thrd2.html#01936&amp;quot;&amp;gt;&amp;lt;strong&amp;gt;Thread&amp;lt;/strong&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;

&amp;lt;!--X-BotPNI-End--&amp;gt;
&amp;lt;!--X-User-Footer--&amp;gt;
&amp;lt;!--X-User-Footer-End--&amp;gt;
&amp;lt;/body&amp;gt;
&amp;lt;/html&amp;gt;
&lt;/pre&gt;
&lt;!--X-Body-of-Message-End--&gt;
&lt;!--X-MsgBody-End--&gt;
&lt;!--X-Follow-Ups--&gt;
&lt;hr&gt;
&lt;!--X-Follow-Ups-End--&gt;
&lt;!--X-References--&gt;
&lt;!--X-References-End--&gt;
&lt;!--X-BotPNI--&gt;
&lt;ul&gt;
&lt;li&gt;Prev by Date:
&lt;strong&gt;&lt;a href=&quot;msg01933.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Next by Date:
&lt;strong&gt;&lt;a href=&quot;msg01935.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Previous by thread:
&lt;strong&gt;&lt;a href=&quot;msg01933.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Next by thread:
&lt;strong&gt;&lt;a href=&quot;msg01935.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Index(es):
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;maillist.html#01934&quot;&gt;&lt;strong&gt;Date&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;threads.html#01934&quot;&gt;&lt;strong&gt;Thread&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;!--X-BotPNI-End--&gt;
&lt;!--X-User-Footer--&gt;
&lt;!--X-User-Footer-End--&gt;
&lt;/body&gt;
&lt;/html&gt;
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg01933.html">[no subject]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg01935.html">[no subject]</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg01933.html">[no subject]</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg01935.html">[no subject]</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#01934"><strong>Date</strong></a></li>
<li><a href="threads.html#01934"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>