Limitation of nonStandardData

Jim Toga jtoga at ideal.jf.intel.com
Mon Dec 1 14:42:53 EST 1997


Pete,

An easy fix for backward compatability is to simply define a particular
'nonStandardParameter' as a "SEQUENCE OF nonStandardParameter".


Regards,
jimt.


At 07:02 PM 12/1/97 -0000, you wrote:
>Dear All,
>
>I have noticed that there is a limitation in H.225 (and H.245) on how
>nonStandardData is included in messages.  Basically only one
>non-standard element can be included in each PDU.  This is because of
>the syntax:
>
>        nonStandardData NonStandardParameter,
>
>What is really required for a truly extensible protocol is:
>
>        nonStandardData SEQUENCE OF NonStandardParameter,
>
>This is especially important if a gatekeeper wants to insert
>nonStandardData into a message that already has nonStandardData added in
>to it by an endpoint.
>
>This may be too late to fix for H.225, but we can fix this for the
>H.450.x protocols.
>
>Pete
>=================================
>Pete Cordell
>BT Labs
>E-Mail: pete.cordell at bt-sys.bt.co.uk
>Tel: +44 1473 646436
>Fax: +44 1473 645499
>=================================
>
>

*************************************************************************
***  +1-503-264-8816(voice)             +1-503-264-3485(fax)          ***
***  jtoga at ibeam.intel.com              Intel - Hillsboro, OR.        ***
***  PGP keyID 36 07 86 49 7D 74 DF 57  50 CB BA 32 08 9C 7C 41***
*************************************************************************



More information about the sg16-avd mailing list