Re: [802.21] FW: Requirements on 802 groups
With regard to fast authentication, I believe the following documents
contain some useful information in terms of performing authentication
proactively.
http://www.ietf.org/internet-drafts/draft-ietf-pana-preauth-00.txt
http://www.ietf.org/internet-drafts/draft-ohba-mobopts-mpa-framework-01.txt
http://www.ietf.org/internet-drafts/draft-ohba-mobopts-mpa-implementation-01.txt
http://www.ietf.org/internet-drafts/draft-ohba-mobopts-heterogeneous-requirement-00.txt
Best regards,
Yoshihiro Ohba
On Thu, Nov 10, 2005 at 06:20:26AM -0800, Michael G. Williams wrote:
> > Colleagues,
> >
> > During the conference call on joint 802.11 and 802.21 requirements,
> > the topic of fast authentication was mentioned. It was determined that
> > a thread on the mailing list should be brought up to see if additional
> > requirements should be added in this topic. It was also mentioned that
> > this might not be limited to joint .21 and .11 requirements, but apply
> > to other 802 as well.
> >
> > Although .21's scope precludes certain aspects of security, it can
> > make the requirements for other groups to fulfill. As such, there were
> > (at least) three issues that need to be considered. During the
> > conference call, two of them were agreed:
> >
> > 1) Information Service to be available pre-association
> > (pre-authenticated state)
> > 2) Information Service to be available post-association (authenticated
> > state)
> >
> > The third issue was:
> > 3) Enable "fast authentication" transition between supported network
> > types, not limited to:
> > - between 802.11 ESSs
> > - between 802.11 and 802.16
> >
> > The notion here is that authentication has to be fast enough, or
> > enough in advance, that it doesn't get in the way of seamless
> > handover. This is an area discussed quite thoroughly by 802.11r so
> > within the 802 we can leverage that knowledge, and cut off a process
> > of re-educating a whole new set of people not familiar with what has
> > been done there.
> >
> > This is a request for active proposals on the third item. Please frame
> > your input on this topic to the list only as proposed requirement(s),
> > or later, modifications to previously posted proposed requirement(s).
> > Along with the proposed requirements, additional explanatory text is
> > acceptable. Please do not post comments or questions that are not
> > accompanied by proposed requirements.
> >
> > Best Regards,
> > Michael
>