Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!caen!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!labtam!eyrie!athos
From: athos@eyrie.img.uu.oz.au (David Burren)
Newsgroups: comp.mail.uucp
Subject: UUCP 'g' protocol question
Keywords: packet and window sizes
Message-ID: <3551@eyrie.img.uu.oz.au>
Date: 6 Feb 91 03:27:27 GMT
Organization: img Consultants, Melbourne, Australia
Lines: 47

Some background:

A local firm is working on a modem project that supports high speed transfers
by a "ping-pong" protocol, and are implementing front-ends that support
standard modem transfer protocols including Kermit, X, Y, Z-modem, etc.

I'm trying to convince them to include some level of UUCP-g support.  Whether
this will involve spoofing the 'g' transactions in the same manner as a
Trailblazer or just manipulation of the 'g' parameters, I do not yet know.

My hope is to get a relatively cheap 9600 bps UUCP solution for some of
the Usenet sites around here that are still on 2400 bps.

To ensure that we (they & I) get it right, I have some questions about
the protocol and the various implementations of it that are around.
This includes PC & Amiga versions as well as Unix...

My main reference for the protocol is the paper by Chesson.  Any quoted
passages are from that paper.

	... the UNIX implementations no longer generate or response to
	SRJ messages.  It is mentioned here for historical accuracy
	only, and one may assume that SRJ is no longer part of the protocol.

Does this mean that an implementation should not respond to SRJ messages
if they are received?  Do any existing implementations generate them?

With regard to INIT[ABC] messages, will existing implementations respond
to them if they are received during a session?  I understand that most
(if not all) implementations will not initiate such a transaction, but will
they respond to one?

How many implementations will use the full 7-window, 4096-byte packet
parameters?  Will most only do 3 x 64?  If appropriate, how can this be
modified on various systems? (adb patching instructions accepted)
I understand that some systems have problems with serial I/O buffers and
have trouble with windows larger than 256 characters, and thus don't cope
with the larger window and packet sizes.

Any help you can give clearing these questions up will be most appreciated.
Thanks!
___________________________________________________________________________
David Burren (Athos)				img Consultants
Systems Development (general dogs-body)		G.P.O. Box 3304GG
						Melbourne, VIC 3001
Email:	athos@img.uu.oz.au			Australia
Phone:	+61 3 819 4554