Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [RE] Stream identification at the MAC SAP



Richard,
 
IEEE 802.2 was due for reaffirmation last year. As there is no acting 802.2 chair, my recollection is that the hibernating chair of IEEE 802.5 handled the reaffirmation along with the IEEE 802.5 reaffirmation because 802.5 requires 802.2 so it didn't make sense to reaffirm one without the other. It may have been someone else on the exec who handled it.
 
I agree that 802.2 is not required to be the MAC client at end nodes. In the majority of IEEE 802.3 end nodes it is not used.
 
Regards,
Pat
-----Original Message-----
From: owner-stds-802-3-re@IEEE.ORG [mailto:owner-stds-802-3-re@IEEE.ORG]On Behalf Of Richard Brand
Sent: Wednesday, 10 November, 2004 4:11 PM
To: STDS-802-3-RE@LISTSERV.IEEE.ORG
Subject: Re: [RE] Stream identification at the MAC SAP

Hello William:
You can't mean 802.2 because that is not a requirement and as well that group is in hibernation so I'd be surprised if they took any action last year.
Do you mean 802.1?  If that is the case support for 802.1 is not a requirement but you have to specify that you specifically do not intend to meet the .1 requirements on the PAR.
Richard

Shvodian William-r63101 wrote:

 
I have a general question on the MAC-SAP interface for RE.  All 802 standards are required to support the 802.2 interface.  The 802.2 interface does not provide a way of identifying an isochronous stream to the MAC at the MAC SAP.  When 802.2 was up for reconfirmation last year I suggested that they add a stream identification parameter that could be used for protocols that provide isochronous services like 802.15.3 or now 802.3 RE.  802.2 rejected the comment. 
Has anyone given a thought to how streams would be identified at the MAC-SAP?  Would there be optional parameters added beyond those provided by the 802.2 interface?  The current parameters from 802.3 are listed here:

MA-UNITDATA request (

source_address,

destination_address,

routing_information,

data,

priority,

service_class

)

and from 802.3:

MA_DATA.request (

destination_address,

source_address,

m_sdu,

service_class

)

Thanks.
Bill