| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
The
general solution to this class of issues seems fairly clear. Provide/define a
protocol entity that attaches to the/an Uncontrolled Port that is providing the
attachment point for the roving station.
Apart
from the fact that that entity appears to need to be able to read the current
status of the Authorized/Controlled Port (really as an optimization so that it
doesn't have to conduct its own further checks to guide its behavior - another
and possibly better solution might be to partition the overall functionality
between such an entity and a companion one that ataches to the Authorized Port,
or to define an entity which attaches to both), its definition ought to be
orthogonal to LinkSec.
Clearly with a roving type technology where ports come
and go an association (also quite properly known as a Port) needs to be in place
for such an entity to communicate with the roving station. That association
doesn't have to be secure however.
Wired
world:
Uncontrolled
Authorized
Port \ / Port
(secured association)
\ /
SecY
|
Port
(lower MSAP)
|
Unwired world:
Uncontrolled
Authorized
Port \ /
Port
\ /
SecY
|
Association
| Mick
[I'm
not saying that one can retrofit such a clean architecture to 802.11 as
currently defined.]
-----Original Message-----
From: owner-stds-802-linksec@majordomo.ieee.org [mailto:owner-stds-802-linksec@majordomo.ieee.org]On Behalf Of Dolors Sala Sent: Tuesday, August 19, 2003 11:08 AM To: LinkSec Cc: Johnston, Dj Subject: [LinkSec] updated handoff presentation On Behalv of Dave Johnston:
|