4. Run to Run. I now understand the point you are trying to make. The text for 
Clear Configuration Request/Response is not consistent with the other commands 
in this section. I am proposing the following changes, which does not change 
any behavior, but only creates more consistency in the text:

<text>
   Run to Run (q):  This is the normal state of operation.

      WTP:  This is the WTP's normal state of operation.  There are many
         events that result this state transition:
[...]
         Clear Config Request:  The WTP receives a Clear Configuration
            Request message (see Section 8.8) and MUST generate a
            corresponding Clear Configuration Response message (see
            Section 8.9).  The WTP MUST reset its configuration back to
            manufacturer defaults.
[...]
      AC:  This is the AC's normal state of operation:
[...]
         Clear Config Response:  The AC sends a Clear Configuration
            Request message (see Section 8.8) to the WTP to clear its
            configuration.  The AC receives a Clear Configuration
            Response message from the WTP (see Section 8.9).
</text>

5. Unfortunately, I'm still not understanding the issue you are trying to 
raise. I am not claiming that the AC sends echo requests, I am simply stating 
that requests (in general) can be transmitted by either the WTP or the AC, 
while certain requests may have restrictions which are clearly documented in 
the spec. So regardless of whether a request is an echo request, or any other 
request, the retransmission, and subsequent timeout, is the same. Therefore 
there is no need to add a specific clause for echo requests timing out.