![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
On Wed, 2007-03-07 at 08:07 +0200, Pekka Savola wrote: > Hi, > > On Tue, 6 Mar 2007, Geoff Mulligan wrote: > > You question about switches does point to an overloaded term. In that > > particular paragraph the "switches" we are talking about are electrical > > switches, as in light switches, not network switches. We'll fix the > > wording. > > I guessed as much, which is what triggered me to wonder about the use > of the term 'personal' as I don't think an electrical switch is > typically carried in your PAN :-) > > > The reason we use the term personal area network is that it is the > > industry term used for 802.15.4 networks. I agree that these devices > > are not "personal", but it is a nomenclature that we are stuck with by > > the IEEE. > > If you don't want to drop 'Personal' from the used terminology, I > would suggest considering adding a sentence or two in Introduction of > all relevant documents to make it clearer that the IETF has designed a > generic solution which also applies outside of PANs. The IETF > specifications as far as I can see are not ress complete(!) and "Transient Session Keys = (TSKs)", where the EAP peers negotiate a ciphersuite for this = purpose. Although I don't think it's prohibited for EAP methods to = negotiate ciphersuites for subsequent use _by other protocols_ (such as = 802.11i, etc.), I don't know of any that do & I don't think that = that is what is meant in this definition: it is only the rather IMHO = sloppy use of the terms "authenticator" and "peer" = to mean, basically, "whatever is hanging off the ends of the = wire" that allows this usage.</FONT></P> </BODY> </HTML> ------_=_NextPart_001_01C75E3E.929A9595-- --===============0938587276== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf --===============0938587276==--
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.