Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!amdahl!terry
From: terry@uts.amdahl.com (Lewis T. Flynn)
Newsgroups: comp.dcom.lans
Subject: Re: What services does X.25 provide?
Keywords: x.25, services, login, e-mail, file transfer, IPC
Message-ID: <08Ck02pp5aoP01@amdahl.uts.amdahl.com>
Date: 25 Sep 89 19:47:01 GMT
References: <796@maxim.erbe.se> <3279@wasatch.utah.edu> <522@wet.UUCP> <1989Sep18.020822.16329@cit5.cit.oz> <727@idacom.UUCP> <17683@bellcore.bellcore.com> <6576@pdn.paradyne.com> <17701@bellcore.bellcore.com>
Reply-To: terry@amdahl.uts.amdahl.com (Lewis T. Flynn)
Organization: Amdahl Corporation, Sunnyvale CA
Lines: 17

In article <17701@bellcore.bellcore.com> karn@ka9q.bellcore.com (Phil Karn) writes:
>>Seems like a quantum leap from an obvious hack to a blanket condemnation
>>of X.25.  It would be easy (and obvious?) for a private X.25 network to
>>open the window size to a more optimal value based on number of hops.
>
>The specific situation I was describing (IP on Telenet) involved a public
>data network, and Telenet didn't support any way to negotiate the window
>size to a more optimum value.

If my memory is correct (it's been three years), X.25 requires the
implementation to allow window sizes from 1 to 7 with other sizes up
to 127 optional. If Telenet doesn't allow other than 2 (the required
default), then it doesn't meet the standard.

Terry