Re: [STDS-802-16] Bandwidth request/grant for Management connections
Hi,
This is one thing that has puzzled me all along - the QoS parameters
for the basic, primary and secondary connections are left up to the
vendor implementing the BS or SS.
This means that vendor A's SS can implement secondary management
connection as a minimum reserved traffic rate connection of 64 Kbps
where as another vendor B's BS can implement the same connection as a
best effort connection only.
All this can lead to interoperability issues - the only products that
will work seamlessly as expected will be the ones from the same vendor
(SS and BS). It would have been much better to mandate the basic,
primary and secondary management connection parameters - or provide a
way for the BS to set up these parameters for the SS.
Thanks
Kalash
On 4/21/05, Al Dabagh, Baraa <baraa.al.dabagh@intel.com> wrote:
>
>
>
> Sanesh,
>
>
>
> The mechanism for requesting bandwidth is the same for al CIDs. You can use
> contention based or piggybacked requests. QoS parameters will apply, and you
> will have to define something that make sense to your scheduler
> implementation.
>
>
>
> BA
>
>
>
>
> ________________________________
>
>
> From: owner-stds-802-16@LISTSERV.IEEE.ORG
> [mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of
> Sanesh Kariyadan
> Sent: Thursday, April 21, 2005 7:37 AM
> To: STDS-802-16@LISTSERV.IEEE.ORG
> Subject: [STDS-802-16] Bandwidth request/grant for Management connections
>
>
>
>
>
> Hi,
>
>
>
> For SNMP sort of Secondary Management message connections, how the bandwidth
> request- grant mechanism works ? Is there a activated QoS parameters for
> this ?
>
>
>
> How much or how to allocate bandwidth for management messages, after network
> entry and registration ?
>
> -Regards,
>
> Sanesh Kumar K
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com