Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!sics.se!ifi!nuug!ncrnorw!bam From: bam@ncrnorw.Norway.NCR.NO (Asbjorn Muldbak) Newsgroups: comp.mail.uucp Subject: Re: UUCP Protocols Summary: g/f/e UUCP protocols. Short explanation. Keywords: uucp, protocols Message-ID: <1407@ncrnorw.Norway.NCR.NO> Date: 21 Apr 91 12:17:23 GMT References: <1991Apr19.125453.22@cutler.uucp> Reply-To: bam@ncrnorw.Norway.NCR.NO (Asbjorn Muldbak) Organization: NCR Corporation, Norway Lines: 45 In article <1991Apr19.125453.22@cutler.uucp> john@cutler.uucp (John E. Babbitt Jr.) writes: >The only uucp protocol I'm familiar with is "g", but I've seen floating >around some mention of "e" and "f". What are they, and why are they still >in use? What other uucp protocols are there? What do most sites use? >My package can only communicate in "g" protocol, so does that means I won't >be able to link up with others that are "e", "f", or "xyzzy"? :-) > The 'g' protocol sends in packets of 64 bytes in size. Acknowledgement on packet basis. Quite slow, but very reliable. It assumes 8-bit datapath. The f protocol is designed for 7 bit ASCII data paths with control character restrictions. Binary files are converted to ASCII format before transmission and back on the other side. Checksum is done on a total file basis, so the entire file must be retransmitted if a noisy channel introduces an error. On reliable channels 'f' protocol gives a faster transfer rate. I use the 'f' protocol for all uucp/X.25 connections with hosts able to handle it, as it seems to be the fastest and most reliable on these connections. (More reliable is of course the g-protocol, but slower) I have had terrible results using 'e' on far away X.25 connections. (Europe <-> USA). Just silent death, until of the machines gave up on the connection. The 'e' protocol assumes a 8-bit datapath, that is completely reliable NO, repeat NO error checking is done. The 'e' protocol sends a character count for a file, before transmitting the actual file. Data is transmitted in 1024 byte blocks. High throughput, greatest risk of undetected file corruption. I use 'e' protocol for uucp/LAN connections. You should have no problem connecting to sites with these protocols, as (as far as I know at least) all support the g-protocol. If a site have set a default of f, uucp will just step back to using 'g', and data is flowing. I do not know of any other uucp-protocols, than e/f/g. Hope these comments answered your question Asbjorn Muldbak -- Bo Asbjorn Muldbak NCR Corporation, Norway. Fax. +47 2 953601 Dept: APS - Application and Project Support. email:Asbjorn.Muldbak@Norway.NCR.NO or [ncrcom,ncrdkcp,ncrsth,nuug]!ncrnorw!bam Opinions stated are my own, and does not represent NCR Corporation.