<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2651.65">
<TITLE>RE: On TD26 - Fast TCS and M/S negotiation in H.323v4</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>We've made it even clearer in v4. Including H.245 and H.225.0 elements.</FONT>
</P>
<P><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Paul Long [<A HREF="mailto:Plong@SMITHMICRO.COM">mailto:Plong@SMITHMICRO.COM</A>]</FONT>
<BR><FONT SIZE=2>> Sent: Saturday, May 20, 2000 5:21 PM</FONT>
<BR><FONT SIZE=2>> To: ITU-SG16@MAILBAG.INTEL.COM</FONT>
<BR><FONT SIZE=2>> Subject: Re: On TD26 - Fast TCS and M/S negotiation in H.323v4</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Pete,</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> This is already covered in H.323, so there is no need to say </FONT>
<BR><FONT SIZE=2>> it again or in</FONT>
<BR><FONT SIZE=2>> another way. Do you think that the text, below, is deficient </FONT>
<BR><FONT SIZE=2>> in some way?</FONT>
<BR><FONT SIZE=2>> Seems pretty clear to me.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> 8.2.2/H.323v3: "...intermediate entities shall ensure that </FONT>
<BR><FONT SIZE=2>> H.245 messages</FONT>
<BR><FONT SIZE=2>> encapsulated in Q.931 messages are forwarded to the other </FONT>
<BR><FONT SIZE=2>> endpoint even if</FONT>
<BR><FONT SIZE=2>> the Q.931 message in which the H.245 message is encapsulated would be</FONT>
<BR><FONT SIZE=2>> consumed and not forwarded to the other endpoint. This is </FONT>
<BR><FONT SIZE=2>> accomplished by</FONT>
<BR><FONT SIZE=2>> transferring the encapsulated H.245 message into a Facility </FONT>
<BR><FONT SIZE=2>> message with the</FONT>
<BR><FONT SIZE=2>> h323-message-body set to empty."</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Paul Long</FONT>
<BR><FONT SIZE=2>> Smith Micro Software, Inc.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Pete Cordell [<A HREF="mailto:pete@TECH-KNOW-WARE.COM">mailto:pete@TECH-KNOW-WARE.COM</A>]</FONT>
<BR><FONT SIZE=2>> Sent: Saturday, May 20, 2000 12:57 PM</FONT>
<BR><FONT SIZE=2>> To: ITU-SG16@MAILBAG.INTEL.COM</FONT>
<BR><FONT SIZE=2>> Subject: On TD26 - Fast TCS and M/S negotiation in H.323v4</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I note that TD-26 has been accepted to show how TCS can be conveyed in</FONT>
<BR><FONT SIZE=2>> parallel with fast start.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> However, the example shows the use of call proceeding for </FONT>
<BR><FONT SIZE=2>> receiving TCS</FONT>
<BR><FONT SIZE=2>> back</FONT>
<BR><FONT SIZE=2>> from the remote endpoint. This is not typically an </FONT>
<BR><FONT SIZE=2>> end-to-end message,</FONT>
<BR><FONT SIZE=2>> and</FONT>
<BR><FONT SIZE=2>> therefore how the procedure works with the gatekeeper routed </FONT>
<BR><FONT SIZE=2>> model needs</FONT>
<BR><FONT SIZE=2>> to</FONT>
<BR><FONT SIZE=2>> be addressed.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Possible solutions are:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> 1. Refer to the new text that says it is the responsibility of the</FONT>
<BR><FONT SIZE=2>> gatekeeper to forward any tunnelled message for which none is </FONT>
<BR><FONT SIZE=2>> available</FONT>
<BR><FONT SIZE=2>> using FACILITY. (There might be some objection from some to using a</FONT>
<BR><FONT SIZE=2>> facility message this early in the call setup process though.)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> 2. Restrict the tunnelling (and probably the fast start info) to</FONT>
<BR><FONT SIZE=2>> Alerting,</FONT>
<BR><FONT SIZE=2>> Connect and Facility, which generally are end-to-end. I </FONT>
<BR><FONT SIZE=2>> believe this is</FONT>
<BR><FONT SIZE=2>> compatible with the latest procedures for deciding when fast start has</FONT>
<BR><FONT SIZE=2>> been</FONT>
<BR><FONT SIZE=2>> ignored.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Which ever option is chosen, it would also be nice to have a </FONT>
<BR><FONT SIZE=2>> picture for</FONT>
<BR><FONT SIZE=2>> it</FONT>
<BR><FONT SIZE=2>> also!</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Pete</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> =============================================</FONT>
<BR><FONT SIZE=2>> Pete Cordell</FONT>
<BR><FONT SIZE=2>> pete@tech-know-ware.com</FONT>
<BR><FONT SIZE=2>> =============================================</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</FONT>
<BR><FONT SIZE=2>> For help on this mail list, send "HELP ITU-SG16" in a message to</FONT>
<BR><FONT SIZE=2>> listserv@mailbag.intel.com</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</FONT>
<BR><FONT SIZE=2>> For help on this mail list, send "HELP ITU-SG16" in a message to</FONT>
<BR><FONT SIZE=2>> listserv@mailbag.intel.com</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>