FW: [IPTEL] CPL: H.323 issuesFrancois,
Thanks for alerting us to this. I responded to his questions over on IPTEL list.
Paul ----- Original Message ----- From: Francois Audet To: ITU-SG16@mailbag.cps.intel.com Sent: Friday, July 07, 2000 8:23 PM Subject: FW: [IPTEL] CPL: H.323 issues
For those interested.
-----Original Message----- From: Jonathan Lennox [mailto:lennox@cs.columbia.edu] Sent: Friday, July 07, 2000 3:17 PM mailto:iptel@lists.bell-labs.com Subject: [IPTEL] CPL: H.323 issues
The primary area still missing in the CPL spec is H.323 work. I'm unfortunately not very knowlegeable about this, so if some H.323 experts could assist with this it would be very helpful.
Here are the general issues that I feel need to be addressed:
1. I understand that work is in progress to define an H.323 url as an annex of the H.323 specification. What is the status of this? Are copies of available? Will these URLs be appropriate to use in CPL <location> and <address-switch> tags?
2. Is the unpacking of H.323 addresses as specified for CPL's <address-switch> address subfield matching correct, and complete for at least a useful subset of H.323 addresses?
3. What free-form strings does H.323 signalling carry that a CPL should be able to match? I understand H.225 has a "data" string, but it's not clear to me what it's for.
4. Is there some H.323 counterpart to SIP caller preferences and callee capabilities that should either be used or mapped into CPL, for <lookup> and <remove-location>?
Since Our Esteemed Working Group Chair has expressed a strong interest in moving CPL along to Proposed Standard soon, these points *need* to be addressed. If no one else comments on them, I'll have to guess based on my own (very limited) understanding of H.323, which will probably mean a much weaker CPL specification all around.
-- Jonathan Lennox lennox@cs.columbia.edu
_______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel