Path: utzoo!attcan!uunet!mailrus!ncar!boulder!stan!dancer!imp
From: imp@dancer.Solbourne.COM (Warner Losh)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Multiple versions of TALK? (was: Major bug in TALK on WIN/TCP for VMS)
Message-ID: <1990Jul5.025717.2732@Solbourne.COM>
Date: 5 Jul 90 02:57:17 GMT
References: <1990Jul3.181759.14369@athena.mit.edu> <14957@ucsd.Edu> <EMV.90Jul3171720@urania.math.lsa.umich.edu>
Sender: news@Solbourne.COM
Organization: Solbourne Computers Inc.
Lines: 16

In article <EMV.90Jul3171720@urania.math.lsa.umich.edu> emv@math.lsa.umich.edu (Edward Vielmetti) writes:
>a word as to actual usage of these two talks across the nsfnet
>backbone -- in the months where port-by-port statistics are kept on
>nis.nsf.net (the *PORTS files) talk+ntalk (517+518) is in about the
>0.2% - 0.3% range, with the amounts varying quite substantially and
>talk generally having more traffic than ntalk.  Must be 
>lots of suns, I guess.  

FYI, the talk/ntalk protocol is just used for connection setup.  Once
people agree to talk, both protocols contain "pointers" to TCP ports
to carry the actual conversation on.  In fact, these "pointers" are
what caused the inability for "talk" to function in a heterogeneous
environment (without all kinds of heuristic gyrations, that is).

-- 
Warner Losh			imp@Solbourne.COM