> >> 6.2 Join Response
> >> Should MUST ME be defined earlier than MAY ME?
> > This doesn't really break anything. I'm not sure we need to address 
> > this.
> I saw other message definitions always put MUST MEs in the beginning.

Well, I think this is really a nice to have, but while looking at the issue 
you are pointing out, I *just* noticed that there is a cut/paste error in this 
section since the text includes:
<bad text>
   One of the following message elements MUST be included in the
   Discovery Response Message:
</bad text>

Clearly, that should have been a Join Response, so since I'm add it, I will 
reorder the text to make sure that it is consistent with the rest of the 
message definitions, and fix the cut/paste error.

> 
> > 9.7 Data Transfer Response
> >
> >    Upon receipt of a Data Transfer Response message, the WTP transmits
> >    more information, if more information is available.
> >
> > What's this meaning of this? If the crash data or memory dump is too
> large, WTP will segment them, and transfer them
> > using multiple Data transfer req messages.
> > The AC should maintain the
> > data offset by itself?   Or you want to say, the WTP will first sent
> > crash dump. It will send the memory
> > dump after it receives the response?
> Yes, this is a series of back and forth, where the WTP will, if necessary, 
break the information to be sent across 
> multiple packets. The CAPWAP transmission layer will ensure it is 
reassembled in the proper order. Maybe I'm not 
> understanding the question you are asking.
> 
> then how the AC knows it has received all the debug data from the WTP?

I see the point you are raising, and this is something we fixed for the image 
transfer. Because of the scope of the issue, I will create a separate issue to 
track this one. So let's continue this conversation in a separate thread, 
which I will initiate shortly.