Re: CAP 10: 10.1. CAP Commands (CMD) (ABORT/CONTINUE)

[Lawrence Greenfield <leg+@xxxxxxxxxxxxxx>]

   From: Bruce_Kahn@xxxxxxxxxxxxxxxx
   Date: Wed, 29 Jan 2003 16:41:57 -0500
[...]
   So I still think the only way to terminate an unbounded command is to drop 
   the connection to the CS.  Ugh!!  Thats painful and costly...

This is what almost every other IETF application protocol
does. Establishing connections really isn't that costly if it's only
going to happen to what should be "rare" circumstances.

[...]
   So I must therefore question the CAP design and the rationale for 
   unbounded commands.  If there is no way to terminate an unbounded command 
   short of actual termination of the connection and there is no real world 
   case where an unbounded command is actually useful then why are we putting 
   them into CAP (and not clearly creating an in-protocol means to cancel 
   them)??  If we must put unbounded commands into CAP then there must be 
   some easy way in CAP to terminate them (ie: CANCEL). 

The addition of "cancel" and "bounded latency" commands are more
complicated than what's present in CAP's peer protocols (SMTP, IMAP,
LDAP, for instance).

Larry