RE: [802.21] Update on SAPs
Vivek,
Please see my inline comments.
> -----Original Message-----
> From: Gupta, Vivek G [mailto:vivek.g.gupta@intel.com]
> Sent: Thursday, December 15, 2005 10:54 PM
> To: Junghoon Jee; STDS-802-21@listserv.ieee.org
> Subject: RE: [802.21] Update on SAPs
>
>
> Junghoon,
>
> Some comments below.
>
> Best Regards
> -Vivek
>
> > -----Original Message-----
> > From: Junghoon Jee [mailto:jhjee@etri.re.kr]
> > Sent: Thursday, December 15, 2005 3:27 AM
> > To: Gupta, Vivek G; STDS-802-21@listserv.ieee.org
> > Subject: RE: [802.21] Update on SAPs
> >
> > Hello Vivek,
> >
> > >
> > > There is a minor update on SAPs that can help clarify the various
> > > diagrams/sections in 802.21 draft even better.
> > > From 802.21 perspective we can define the following SAPs
> in section
> > 7.
> > > 1] MIH_SAP: Specifies Interface of MIH with MIH Users.
> > > 2] MIH_SME_SAP: Specifies interface of MIH with
> System/Network Mgmt
> > > entity 3] MIH_LINK_SAP: Specifies interface of MIH with a generic
> > > link layer
> >
> > Could you elaborate the above mentioned generic link layer?
> > In my first understanding only with above description, it
> seems like
> > an **abstract** link layer which hides the different features of
> > underlying link layers.
> > Therefore, this MIH_LINK_SAP is changed to a kind of media
> independent
> > SAP, not a media dependent SAP.
> > BTW, current D4 defines this MIH_LINK_SAP as a media
> dependent SAP for
> > 802.11.
> > Let me make one more question to clearly understand the exact
> > definition.
> > What's the relationship between the generic link layer and media
> > specific *real* link layer?
> [Vivek G Gupta]
> As was said in a previous mail, the idea is to identify
> interface of MIH with a generic link layer that can be used
> as a reference. We then use this reference SAP interface to
> figure out differences with other media specific technologies
> and what we need to add/amend in these different link layer
> technologies (events/commands/etc.). Yes MIH_LINK_SAP has
> been shown as media specific SAP only for 802.11 in draft version D4.
> Instead of MIH_LINK_SAP it should be the MLME_SAP for 802.11
> and MIH_LINK_SAP can be the generic interface. In most cases
> (at least for
> 802 technologies) we shall be modifying existing media
> specific SAPs as opposed to adding nay new ones.
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)?
Thanks,
Junghoon
> >
> > > There can be media specific changes/enhancements because of
> > > definition of MIH_LINK_SAP. These would be identified as new
> > > events/commands etc.
> > > that need to be defined for different link layer
> technologies. These
> > > would be reflected as changes to:
> > > 1] MLME_SAP: for 802.11
> > > 2] C_SAP/M_SAP: for 802.16
> > > 3] MIH_3GLINK_SAP: for 3GPP/3GPP2 (to be updated)
> >
> > Thus, you're suggesting the amendment of the section 7 of
> the current
> > draft/D4?
> [Vivek G Gupta]
> Few changes in section 5 and section 7.
>
> > >
> > > Best Regards,
> > > -Vivek
>