Pete,

We sure have different opinions on how this gets done, and I look forward to discussing issues with you next week in Berlin. This is exactly the purpose for submitting this contribution.

Best regards,

--Hong

Pete Cordell wrote:

Well it seems the Telcordia crowd still haven't read my proposal!!!!!!

What I am proposing is an ASN.1-LIKE specification. That means similar to, but not exactly the same as. In my proposal your line:

quarenteenProcessing QuarenteenProcessing OPTIONAL

would be represented as:

quarenteenProcessing AS q QuarenteenProcessing OPTIONAL.

and q would be used as the on the wire tag for precisely the reasons quoted in APC-1636.

If there are worries that this isn't ASN.1 (if that is worth worrying about!), then all you have to do is go through removing any AS specifiers either manually or automatically. It's no big deal.

Pete

============================================= Pete Cordell pete@tech-know-ware.com =============================================

-----Original Message----- From: Hong Liu lhong@RESEARCH.TELCORDIA.COM To: ITU-SG16@MAILBAG.INTEL.COM ITU-SG16@MAILBAG.INTEL.COM Date: 26 July 1999 17:01 Subject: Documents uploaded

...

Hi, all,

I have uploaded two contributions from Telcordia Technologies to the ftp incoming directory for the Berlin meeting:

APC-1635: Mapping H.245 Semantics to SDP APC-1636: Comparing EBNF and ASN.1 for Text Encoding

Cheers,

--Hong