Re: Cipher block boundaries and the TCP mapping

james woodyatt wrote:
> Is it my imagination, or does the TCP mapping for the BEEP protocol not 
> specify any way for frames to be spaced properly so that they always 
> begin (or end) on a cipher block boundary?

Is there a need for this to be part of the protocol? There wouldn't seem 
to be. Part of an API, perhaps, but not part of a protocol, I would think.

 >  If you wanted to do that,
> would declaring it as a "feature" in the greeting be the right choice?  
> What would a specification of this extension look like?

That would be a request for the other side to ensure that frames match 
cypher blocks? It would seem to make more sense to make that an option 
of the TLS or SASL profiles, than as an option of the entire session.

Consider, what would be the meaning of this feature if TLS was never 
invoked? What would be the meaning if TLS was already invoked?

-- 
   Darren New / San Diego, CA, USA (PST)
   "You may mail in the form, and wait 4 to 6 weeks, or call us and
    get your answer right over the phone... after being on hold for
    4 to 6 weeks."