Re: your mail

["Joseph Galbraith" <galb-list%vandyke.com@localhost>]

I believe VShell / SecureCRT also only bill the
actual length of data against the window size.

I do not think that the packet overhead should
be included; I believe the current behavior
is correct.

- Joseph

----- Original Message -----
From: "Niels Möller" <nisse%lysator.liu.se@localhost>
To: "Markus Friedl" <markus%openbsd.org@localhost>
Cc: "Yavor G Georgiev" <yasho%rambler.bg@localhost>; <ietf-ssh%netbsd.org@localhost>;
<openssh-unix-dev%mindrot.org@localhost>
Sent: Thursday, November 08, 2001 10:13
Subject: Re: your mail


> Markus Friedl <markus%openbsd.org@localhost> writes:
>
> > On Thu, Nov 08, 2001 at 01:34:43PM +0100, Yavor G Georgiev wrote:
> > > Yes you got me right.
> > > I assume the data to be the last part in the following example packet:
> > >          byte      SSH_MSG_CHANNEL_DATA
> > >          uint32    recipient channel
> > >          string    data
> > > the one that is type string, which includes 4 more bytes for the
> > > length.
> >
> > i think the 4 string-len bytes should _not_ be included, since
> > it should not matter for the window size whether a payload data
> > of 10 bytes arrives in one or in 4 messages.
>
> I agree with Markus. LSH and openssh have the same behaviour, I think.
>
> Regards,
> /Niels
>