URL to support Number Portability [was: draft-yu-tel-url-00.txt]

James! After reviewing your draft, below are my comments. As in regards to H.323, H.323 doesn't currently have an explicit notion of two different fields carrying the exact meaning of "current destination" and "the final recipient", using SIP language. On the other hand, the definition of H.323 URL potentially allows for cascading of URLs of different kinds. This concept appear in the last draft of "Annex O" to be discussed next week. Therefore, tel url can be placed in the "user" part of H.323 URL. Since, in your proposal, the original "final recipient" information (i.e. the phone number itself) is preserved in the tel url after the NPDB deep is performed, I don't see a technical problem for using the proposed algorithm within H.323. I will bring your work to the attention of H.323 community next week, including the H.323 mobility WG. My question (and that of the H.323 community) would be: what level of consensus does the approach, presented in your draft, currently have within SIP and IPTEL working groups? Orit Levin RADVision Inc. 575 Corporate Drive Suite 420 Mahwah, NJ 07430 Tel: 1 201 529 4300 (230) Fax: 1 201 529 3516 www.radvision.com orit@radvision.com -----Original Message----- From: James Yu <james.yu@neustar.com> To: 'Orit Levin' <orit@radvision.com>; IPTEL WG <iptel@lists.bell-labs.com> Date: Monday, August 14, 2000 1:24 PM Subject: RE: [IPTEL] A draft of H323-URL to be presented during the IPTEL session
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
participants (1)
-
Orit Levin