Re: SEQs after channel close request?

Jered Floyd wrote:
> I think the latter item there will work but, well, it seems overly
> complicated.  What have other implementors done?

While doing Beepcore-C's core, I noticed this problem. I only send SEQs 
*before* sending outgoing packets. That is, I send the SEQ just before 
sending the RSP or ANS, so it really isn't a problem. As long as the SEQ 
isn't the last packet you send, the other side should always be waiting 
for your response and therefore hasn't processed the close yet.

The other problem you run into is when a response to a close carries 
more data than your window can accept. This is more of a doctor-doctor 
problem. ("Doctor, Doctor, it hurts when I do this!"  "Then don't do that.")

Hope this helps.

-- 
Darren New, San Diego CA USA (PST)
Things to be thankful for, #187:
  There is no Chinese tradition of changing from
  shoes to slippers to get off an escalator.