TD-50/Osaka - Changes to the conferenceGoal field

Pete Cordell pete at TECH-KNOW-WARE.COM
Wed Jun 21 18:37:50 EDT 2000


Forgot to respond to this bit...

> The problem is service that are mandatory, but have optional coding.
> L has two coding formats in order to use v2 clients.  I can seen some
> Packages services using the same technique - v4 uses Packages, v2 uses
> nonStandardControl.  I would prefer a negotiation process like that for
> negotiation - the originators asks for what is wanted, the response is
> is available.  Then the originators chooses what to do.  If this is done,
> there is no need to mess with conferenceGoals.

You would use desiredFeatures if you wanted to operate in this way.

neededFeatures is for when you absolutely must not go to CONNECT (ACTIVE)
state if features certain are not supported as this typically may imply a
billing event.  desiredFeatures means that you can work around any features
that are not supported.  Such a distinction was important in our tunnelling

> Bob
> ------------------------------------------------------------------
> Robert Callaghan
> Siemens Enterprise Networks
> Tel: +1.561.923.1756 Fax: +1.561.923.1403
> Email: Robert.Callaghan at
> ------------------------------------------------------------------


Pete Cordell
pete at
+44 1473 635863

For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at

More information about the sg16-avd mailing list