Hi Pete, The changes you proposed seem to clarify the intention of the section and fix the defects in the original text. There is one question that I have, though.

In the original text, it says in the third paragraph of section 8.4.6 that when an EP receives a non-empty TCS in this paused state, it shall reset its H.245 state to the beginning of phase B. This implies a new exchange of TCS and, more importantly, a new Master-Slave Determination cycle.

A new Master-Slave Determination, I think, can be important for a situation where an EP (A) which was connected to another EP (B) was transfered to an MCU. A might have been the master when it was talking to B, but when it is transfered to the MCU, the MCU should be the master. A new MSD cycle can facilitate this.

In the new text, what does transmitter side H.245 state in phase B (H.323 section 8.2) mean? Can a new MSD cycle happen when Ep receives a non empty TCS?

Regards, Santo Wiryaman

---------------------------------------- Santo Wiryaman VideoServer, Inc. Phone:+1.781.505.2348 Fax:+1.781.505.2101 email:swiryaman@videoserver.com http://www.videoserver.com

-----Original Message----- From: Pete Cordell [SMTP:pete.cordell@BTINTERNET.COM] Sent: Tuesday, May 25, 1999 4:33 AM To: ITU-SG16@mailbag.cps.intel.com Subject: Implementer's guide corrections for third-party pause

Dear SG16 meeting Rapporteurs and Delegates,

As you may know, some discussion took place on the implementer's e-mail list about the third-party initiated pause and re-routing feature. It emerged that the description of the feature contained a few defects, and could also be made clearer.

It would seem appropriate for the results of this discussion to be captured in the implementer's guide. Being slightly out of the loop on these issues now-a-days it did not occur to me to propose such changes in the normal way. However, as the principle author of the original text I still feel some responsibility for making the text as correct and clear as possible.

For this reason I've included a word document below that captures the resultant changes in the hope that someone, perhaps a rapporteur or the implementer's guide editor, can see the changes merged into the implementer's guide.

I'm not sure what form such a contribution will take (will it be a separate contribution, or go straight into the proposed text for the implementer's guide?) so I have included raw text without any boiler plate.

Many thanks,

Pete

============================================= Pete Cordell pete.cordell@btinternet.com ============================================= << File: New-third-party-pause.doc >>