RE: [802.21] Update on SAPs
> -----Original Message-----
> From: Qiaobing Xie [mailto:Qiaobing.Xie@motorola.com]
> Sent: Wednesday, December 14, 2005 3:38 PM
> To: Gupta, Vivek G
> Cc: STDS-802-21@LISTSERV.IEEE.ORG
> Subject: Re: [802.21] Update on SAPs
>
> Hi, Vivek,
>
> To echo what has been said by Ulises, it is clearly a neat idea to
> define everything link related around a generic SAP MIH_LINK_SAP in
> 802.21 spec, but we need to do it in such a way that we won't
compromise
> our initial objective of achieving max reusability of the existing
> primitives that has already been defined by the various link layers
> (both 802 and non-802).
[Vivek G Gupta]
Oh absolutely. We shall try to define as part of MIH_LINK_SAP,
functionality not commonly (already) present across different link
layers. The main goal here has been is to identify new functionality
that may needed to be amended/added to different link layer technologies
for better handover performance and optimization.
>
> best regards,
> -Qiaobing
>
> Gupta, Vivek G wrote:
>
> > Ulises,
> >
> > Agree with you comment and that is why I had included a (to be
updated)
> > placeholder below. As per your comment for 3GPP/3GPP2 we shall look
> > forward to updated contributions and mapping tables to have a clear
idea
> > of any recommended link layer enhancements for these specific media
> > types.
> >
> > Best Regards,
> > -Vivek
> >
> >
> >>-----Original Message-----
> >>From: Olvera-Hernandez, Ulises [mailto:Ulises.Olvera-
> >>Hernandez@InterDigital.com]
> >>Sent: Wednesday, December 14, 2005 7:34 AM
> >>To: Gupta, Vivek G; STDS-802-21@listserv.ieee.org
> >>Cc: Peretz Feder
> >>Subject: RE: [802.21] Update on SAPs
> >>
> >>Vivek,
> >>
> >>I just have a minor comment.
> >>
> >>I agree with the suggestion to adopt MIH_LINK_SAP as a generic SAP.
> >>Currently it is defined only for 802.11. For points 1) and 2) below
it
> >>is clear that new changes will need to be identified for the
> >>corresponding technologies. For point 3) however we have defined a
> >>mapping table as a means to minimize changes in 3GPP/3GPP2 and take
> >>advantage of the primitives defined for MIH_LINK_SAP. The action
from
> >>Vancouver was to refined this table and incorporate 3GPP2 mapping as
> >>well.
> >>
> >>Regards,
> >>Ulises
> >>-----Original Message-----
> >>From: Gupta, Vivek G [mailto:vivek.g.gupta@INTEL.COM]
> >>Sent: Wednesday, December 14, 2005 9:20 AM
> >>To: STDS-802-21@listserv.ieee.org
> >>Subject: [802.21] Update on SAPs
> >>
> >>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
> >>
> >>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)
> >>
> >>There were some ideas presented along these lines in last meeting at
> >>Vancouver as well. The above organization makes things clearer and
> >>consistent.
> >>
> >>Best Regards,
> >>-Vivek
> >
> >