[BEEPwg] Trouble with TLS and transport mappings

Marshall T. Rose mrose+mtr.netnews@dbc.mtview.ca.us
Wed, 21 Nov 2001 15:33:36 -0800


> I believe that my most recent concern is addressed by the
> following change in Section 3.1.3.1:
>
>   [...]; similarly, the receiving BEEP peer must wait until any
>   pending replies have been generated and sent before it processes
>   a "ready" element.
>
> changes to:
>
>   [...]; similarly, the receiving BEEP peer may wait until any
>   pending replies to messages that have been fully received
>   have been generated and sent before it processes a "ready"
>   element.

this would work, although you probably meant to say "must" instead of "may".

thanks,

/mtr