TIP: Click on subject to list as thread! ANSI
echo: hs_modems
to: CAREY BLOODWORTH
from: DAVID BOWERMAN
date: 1998-02-09 11:08:00
subject: Negociations (SP)

Carey Bloodworth wrote in a message to David Bowerman:
DB>DB>Now name the company that originated v.32terbo.
DB> CB> AT&T.  I don't remember what year, but it was definitly AT&T and
DB> CB> not USR or Hayes or Rockwell.  And they made their improvment
DB>Really?  I had better tell those callers to my system who were
DB>using several brands of 19200 modems that they weren't connecting at 
DB>16800 or 19200 (AT&T,
 CB> ???  Who said anything about whether somebody connected at 16.8k or
 CB> 19.2k?  You were talking about USR (vs. Rockwell) and v.32terbo as
 CB> if they had done it.  They didn't.  AT&T did.  The only
 CB> contribution USR made at all was to take AT&T's public domain
 CB> v.32terbo and come out with a proprietary extension to v.32terbo
 CB> but still call it 'v.32terbo', as if it was all theirs, or still
 CB> the same old method that everybody else was doing.  And they
 CB> publicized it as if they had created v.32terbo and that everybody's
 CB> v.32terbo was the same. They didn't.  They just created their own
 CB> extension.  And USRs version was not the same as those by any other
 CB> maker.
You stated that USR's implementation of v.32terbo was "proprietary and unable 
to work with other v.32terbo modems".  As for the rest of your comments, 
could you supply a source for for your statement that v.32terbo was public 
domain.  
Given that USR's version of v.32terbo would connect with any other 
manufacturer's version of v.32terbo as evidenced by the number of people who 
connected to my system at those speeds, it's hard to see where you found a 
basis for your claim that USR's implementation of v.32terbo was unable to 
work with other v.32terbo modems.
 CB> All USR did was to create an incompatible extension with the same
 CB> name, and to confuse the protocol naming situation.
What standard?  V.32terbo was an AT&T proprietary protocol which was never an 
ITU-T standard though AT&T did try to fit the name to the ITU-T naming 
convention (V.27ter for example).  USR fully supported the AT&T protocol with 
an extension that only affected v.32terbo connects between USR Couriers -- 
that extension was covered under the ASL catch-all.  You could always set 
S34.1=1 to disable the 21600 link speed.
Regards,
       David
--- timEd/2 1.10+
---------------
* Origin: Frog Hollow -- a scenic backroad off the Infobahn (1:153/290)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.