Hello all!

We are in favor of "nonStandardSequence" proposal. I would like to mention, that for truly backward compatibility, v2 entities should use the old nonStandardData field along with the new one. It means that the NonStandardParameter value (or in case of more then one: the most important among the NonStandardParameter values) should be inserted by v2 entities into both nonStandardData and nonStandardSequence fields.

As to the use of H.450.1 h4501SupplementaryService field for this purpose, since H.450 is an optional subset of H.225.0, it seems more proper to keep the nonStandardData basic capability apart from it, for the sake of H.323 "light" implementations, that don't support H.450.

============

...

H323-UU-PDU ::= SEQUENCE { h323-message-body CHOICE { setup Setup-UUIE, callProceeding CallProceeding-UUIE, connect Connect-UUIE, alerting Alerting-UUIE, userInformation UI-UUIE, releaseComplete ReleaseComplete-UUIE, facility Facility-UUIE, ... }, nonStandardData NonStandardParameter OPTIONAL, ... nonStandardSequence SEQUENCE of NonStandardParameter OPTIONAL }

============

Orit Levin RADVision Inc. E Mail: orit@radvision.com 575 Corporate Dr., Suite 420 Tel: 201-529-4300 ext. 230 Mahwah, NJ 07430 Fax: 201-529-3516