KR> What is the meaning of /bis/ in protocols such as V.32bis?

Literally, 'twice'.  Or 'again'.  Or 'second'.  (e.g. biscuit: twice baked).

Similarly, ter = thrice, third.

 KR> If V.22 means 1200bps, V.22bis means 2400bps, and V.32
 KR> means 9600bps, does
 KR> this mean V.32bis should really be 19200 and not 14400?

:)  No, '.bis' recommendations are different, but related, to their primary.

 KR> Who was responsible for developing and releasing the V.fc standard?

It was an outtake of the ITU-T committee work on what had been code-named
'V.fast', maybe 2/3 to 3/4 of the way along.  Hayes / Rockwell committed
what they hoped the final specification might look like to silicon, making
a mint.

To my knowledge it's never been 'released' or openly published, such as
ITU-T recommendations are, but may be licenced from Rockwell.  I doubt that
too many people know just how much USR paid Rockwell to licence the
protocol, but USR figured it would help them make a mint, too - seemingly a
successful gamble.

 KR> Why is 33000bps referred to as V.34+ and not V.34bis?

Ask USR :)  V.fc (V.fast Class) was named to imply connection with the
ITU-T's 'V.' series recommendations; a stunningly successful marketing
move, also used by AT&T with their "V.32terbo" 19200bps
V.32bis protocol extension - which USR also licenced into their protocol
mix, extending it to 21600bps.

I guess 'V.32+' continues this fine old tradition.  Recent posts here
indicate that the additional V.34 rates of 31200 and 33600 (basically just
a refinement of existing V.34 technology) will likely be termed 'V.34
(1996)', if I've been paying attention .. V.34bis might yet be something
else, down the track?

Ian

--- MaltEd 1.0.b5