Re: Please publish attached draft-ietf-secsh-break-01

["Phillip Remaker" <remaker%cisco.com@localhost>]

> On Sat, Mar 29, 2003 at 09:48:21AM -0700, Joseph Galbraith wrote:
> >            uint32             break-length in milliseconds
>
> what's the reason for including this in the protocol?
>
> shouldn't the server decide what break-length is reasonable?  e.g.
> depending on what kind of devices is attached?

 Historically, there are some devices which will react differently to a
short break or a long break (KERMIT has two different break lengths, for
example: 250ms and 1500ms).  In order that the varied break length has a
means to be transmitted, the break-length field is added.  Conceivabely, it
could be a long break or short break boolean, but for maximum flexibility,
the length field was added.

 For Cisco devices, the break length is hard coded at 500ms, so Cisco
servers will ignore the field when present.  SSH servers providing RS-232
port access can deal with the field as they feel appropriate.