fastStart element in all Q.931 messages up to andincludingConnect

[Paul E. Jones]

Bob,

[snip Annex F section ]

OK.. it seemed pretty clear that fastStart could be sent multiple times to
reconfigure the streams.

> I suppose the rule would be: if you're not a SET, ignore; if you are,
react.
>
> (As you know, I'd like to see every endpoint process the subsequent
messages
> - then the SET wouldn't be so special, and the redirection problem would
be
> solved.)

This might be ideal, but we can't even seem to come to an agreement on
whether a single reply is required or multiple replies are required for
fastStart.  Worse, I believe people have implemented it differently, which
makes the situation even more difficult.

(I assume you have been observing the "debate" on the H.323 Implementers
list.)

Now, what was this about Fast Open again? :-)

Paul

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com