1 / 5

MA-UNITDATA-STATUSdication Interpretation

MA-UNITDATA-STATUS.indication Interpretation. There are two possible interpretations of when this is sent. (1) Synchronously, immediately after receipt and decoding of the MA-UNITDATA.request.

belk
Download Presentation

MA-UNITDATA-STATUSdication Interpretation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MA-UNITDATA-STATUS.indication Interpretation • There are two possible interpretations of when this is sent. • (1) Synchronously, immediately after receipt and decoding of the MA-UNITDATA.request. • (2) Asynchronously after the transmission attempt(s) associated with an MA-UNITDATA.request have completed. Mike Moreton, Synad Technologies

  2. Arguments for Synchronous Interpretation • Apparently someone argued very strongly for it, but no-one seems to know who, or why. Mike Moreton, Synad Technologies

  3. Arguments For Asynchronous Interpretation • Some of the values of the “Transmission Status” field only make sense for asynchronous behaviour. • If it was a synchronous response it should have been called “MA-UNITDATA.confirm”. • SDL says it is sent “if request is invalid, or when status is available” which suggests that the behaviour may be asynchronous. • 802.2 indicates that a status primitive should in general be returned after the associated indication at the remote party. • Means that no changes are required to the current issued standard. Mike Moreton, Synad Technologies

  4. RFC1925 • “In protocol design, perfection has been reached not when there is nothing left to add, but when there is nothing left to take away. “ Mike Moreton, Synad Technologies

  5. Motion • “Direct the editor to back out the following underlined changes from section 6.2.1.3.2: • b) Undeliverable (for unacknowledged directed MSDUs when the adot11ShortRetryMax or adot11LongRetryMax retry limit would otherwise be exceeded) [no longer used, listed because this status may be returned by MAC entities conformant to IEEE Std 802.11-1999] 10; • g) Undeliverable (TransmitMSDUTimer reached dot11MaxTransmitMSDULifetime before successful delivery) [no longer used, listed because this status may be returned by MAC entities conformant to IEEE Std IEEE Std 802.11-1999, see footnote in (b)]; • In all cases where delivery of the MSDU is attempted, the transmission status parameter returned by the MAC sublayer entity is either (a) or (f). In all cases where no MSDU delivery attempt can be made, the transmission status parameter returned by the MAC sublayer entity is one of (c), (d), (e), (h) or (i). • 10 Transmission status (b) and (g) should not be returned by implementations conformant to the present standard. Transmission status (b) and (g) are listed for completeness, since they were defined in IEEE Std 802.11-1999, but are not likely ever to be returned. It is not possible to determine the occurrence of either of these two cases of an MSDU delivery attempt being abandoned (due to excessive retries for status (b) or due to exceeding the limit on transmit lifetime for status (g)) from local state available within the MAC sublayer entity at the time the MA-UNITDATA.request is received from LLC. Because all MAC data service provided within IEEE Std 802.11 is connectionless, return of transmission status (b) or (g) is incompatible with the semantics of the MA-UNITDATA-STATUS.indication primitive. Implementers are advised that the existence of transmission status (b) and (g) should not be interpreted as a requirement that conformant implementations be able to return these status values, and are directed to the absence of any reference to this clause in Annex A.4 of IEEE Std 802.11-1999.” Mike Moreton, Synad Technologies

More Related