Bill is correct. The reason that the context block is not defined is that the varieties of context information were not defined at the time 802.11F was written. The context block is an envelope that can carry any information needed to be transferred between APs when a client roams. It is left up to other task groups to include in their standards what will go into the context block.
-Bob O'Hara (technical editor of 802.11F) BTW, Happy New Year, Bill! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Arbaugh Sent: Thursday, January 01, 2004 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; RAKESH AIRODI Subject: Re: [BAWUG] IAPP (Roaming) Support for 802.1x The task group opted not to define specifically what context is and left it as opaque much like SEAMBY (IETF WG). SEAMBY did, however, define the format of the context blob in a draft. The advantage of this is that you can share any context you like. The down side is that it won't work with anyone else's equipment until the specific context is standardized. Best, Bill On Jan 1, 2004, at 6:19 PM, Bobby Sardana wrote: > (Re-posting query from Rakesh on hostap list to BAWUG) > > >The 802.11f Draft mentions about the MOVE packets. It does'nt say > >anything about the contents of the "context block".. Is there anything > >else I am missing. > > > >Regards > >Rakesh > > The context block encapsulates security and accounting information but > am unable to find any references to it in other 802.11 specs. Can > someone provide guidance on "Context Block" and its structure? > > regards, > > Bobby Sardana. > [EMAIL PROTECTED] > > -- > general wireless list, a bawug thing <http://www.bawug.org/> > [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless -- general wireless list, a bawug thing <http://www.bawug.org/> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless -- general wireless list, a bawug thing <http://www.bawug.org/> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
