Changes between Version 7 and Version 8 of 802.11/MAC/Lower/Retransmissions

Timestamp:

May 5, 2015, 11:00:04 AM (9 years ago)

Author:

chunter

Comment:

--

802.11/MAC/Lower/Retransmissions

@@ -1 +1 @@
 [[TracNav(802.11/TOC)]]
 
-= 802.11 Reference Design: Frame Retries =
+= 802.11 Reference Design: Recovery Procedures and Retransmit Limits =
 
 An important role of the 802.11 DCF is to detect the presence of transmission failures and properly recover from those errors through the use of a retransmission mechanism. This behavior is subtle and often misunderstood. This document serves two roles:
 
 1. To describe the behavior implemented in the Mango 802.11 Reference Design.
-1. To defend the behavior with references to the 802.11 standard.
+1. To provide reference to the portions of the 802.11 standard where the behavior is specified.
 
 The organization of this document is a series of examples that build on one another and show corner cases in the behavior. The retransmission mechanism in 802.11 is further complicated by the presence of RTS/CTS medium reservation handshakes prior to the transmission of an MPDU, so examples are broken up into sections depending on whether RTS/CTS is not used (i.e. an MPDU is "short") or RTS/CTS is used (i.e. an MPDU is "long"). Without loss of generality, the examples in this document assume the following parameters:
@@ -36 +36 @@
 == Example S.2 ==
 
+{{{
+#!div style="overflow-x:scroll; border:1pt solid"
 [[Image(ex_s_2.png)]]
+}}}
+
 
 The above example shows a scenario where 2 MPDUs are ultimately successful. However, the first transmission attempt of the first MPDU does not result in the successful reception of an ACK. Instead, a timeout occurs and the originator infers a transmission failure. The illustrated behavior in the originator's retry counts and contention window are described by the following paragraphs in the standard
@@ -57 +61 @@
 == Example S.3 ==
 
+{{{
+#!div style="overflow-x:scroll; border:1pt solid"
 [[Image(ex_s_3.png)]]
+}}}