New draft of H.245

Jim Toga jtoga at IDEAL.JF.INTEL.COM
Mon Sep 22 17:20:16 EDT 1997

At 02:04 PM 9/22/97 -0700, Corey wrote:
>Dear Colleagues,
>Below are some comments on the latest draft H.245, ordered by page number,
>not importance:

>- (Page 29) Since we are importing elements from H.235 that are required to
>compile the syntax, should we not put the IMPORTS statement at the
>beginning of the syntax? Or at least at the beginning of the Encryption
>section?  This is not a big issue, but it is kind of buried in the syntax
>and an implementor needs to know that the imported types are required to
>build a correct implementation.


I sent some changes to Mike on Friday - I guess he didn't get them
incorporated.  The intent is to *NOT* require H.235 ASN.1 in order to
compile H.245.  There are changes along the lines of H.45x, that will allow
the octet string (from H.235) to be carried in the H.245 PDU.


***  +1-503-264-8816(voice)             +1-503-264-3485(fax)          ***
***  jtoga at              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