ml> i don't know that it is optional either... witness the following pascal
ml> structures and note the ABSOLUTE overlaying of variables... i don't know
ml> how other authors determine which PKT type they are working with but i
ml> like this method ;-)

PE> I'm sorry, but I don't understand what your code was trying to
PE> demonstrate.

sorry... the code was demonstrating the overlaying of different
structures onto one... basically, i read the PKT headers into a 58byte
buffer. then i use one structure (fsc-0039) and the details from
fsc-0048 to determine which PKT type (2, 2.2, or 2+) that i'm working
with...

PE> My question (stated above) was whether baud was
PE> optional.  E.g. does anyone care if you just stick in 0 all the
PE> time, is anyone's implementation going to break?  I'm not sure what
PE> the baud field is meant to mean anyway, in a packet standard.

in this day in time, i think that the term BAUD in this reference is
simply a variable name and a holdover from some ideas in the past.
technically speaking, you can name that field anything you want as long
as the field is used when/where necessary... in this specific instance,
it is one of a group of rules that help to determine which PKT type we
are working with. as far as breaking implementations, you cannot remove
it from the structures and yes, it needs to be completed according to
the FTS/FSC specs that you elect to follow...

)\/(ark