Re: SEQs after channel close request?

> 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.

this is the same approach i used in beepcore-tcl: SEQs go first.
    
when the spec gets updated, i don't have a problem in changing the spec
to ignore SEQs on unknown channels.  it's hard to see any downside in
that.
    
/mtr