Dear all,

As I've been involved in 3GPP working group discussions regarding these 3GPP H.248 extentions, I'd like to provide some additional information/comments.

Although the 3GPP working groups view is that the 3GPP specification that contains the package definations in question is 95% complete.  In my opinion these packages are not currently technically stable, during the last meeting the technical details for the encoding of the TFO package were not agreed.

Additionally, there is the open issue within 3GPP as to whether these 3GPP H.248 specifications should be specified for both text and binary encodings, or whether only one encoding type should be chosen. 

However from reading clause 13.1 of H.248 (reproduced below) it seems that its a mandatory requirement to specify both a text and binary encoding of additional packages.

13.1    Packages
The following considerations SHALL be met to register a package with IANA:
1)      A unique string name, unique serial number and version number is registered for each package. The string name is used with text encoding. The serial number shall be used with binary encoding. Serial Numbers 60000-64565 are reserved for private use. Serial number 0 is reserved.

..."

Regards,

Kevin.




-----------------
Kevin Gorey
Nortel Networks, UMTS Strategic Product Planning
Tel: +44 (0)1628 434606
Fax: +44 (0)1628 434034
kgorey@nortelnetworks.com