RE: [802.21] Update on SAPs
Sure. The idea is to map the functionality and get the essence of it
reflected in best possible way that we can. Also since 802.21 does not
control the specifications of different media specific groups, from
802.21 perspective we can only make appropriate recommendations.
BR,
-Vivek
> -----Original Message-----
> From: Junghoon Jee [mailto:jhjee@etri.re.kr]
> Sent: Thursday, December 15, 2005 8:08 PM
> To: Gupta, Vivek G; STDS-802-21@listserv.ieee.org
> Subject: RE: [802.21] Update on SAPs
>
> Vivek,
> Comments below,
>
> > > Thanks for clarification.
> > > If so, I think major key work needs to be done is how to map media
> > > independent primitives of MIH_LINK_SAP to media dependant
> > primitives
> > > of media dependant SAPs(for an example, MLME_SAP of .11).
> > > I guess that it is not possible for all the primitives of
> > MIH_LINK_SAP
> > can
> > > have their corresponding media dependent primitives.
> > > Any good idea or hints for this? Should the generic link
> > layer perform
> > > some magic(mapping, converting, adaptation)?
> > >
> > [Vivek G Gupta]
> > I am not sure this is "major key work that needs to be done"
> > at this point, at least for 802 technologies. Most of this
> > has already been done for 802.16 and if you follow the
> > requirements doc for 802.11 most of this is already there as
> > well. This change is more of a reorganization at this point
> > to better represent the SAPs and primitives in our draft and
> > their relationship to media specific technologies.
> > We shall discuss the changes for 802.11 in our Jan telecon.
>
> Hmm,
> If a primitive that is defined in MIH_LINK_SAP can not be mapped to
any
> primitives of media dependant SAPs then,,,?
> I guess not all the network can provide the exact functions which are
> defined from MIH_LINK_SAP.
>
> Thanks,
> Junghoon