H.323 Annex O
Roy, Radhika R, ALARC
rrroy at ATT.COM
Tue May 30 11:34:10 EDT 2000
I fully agree with Ms. Levin's proposal.
Her proposal provides the opportunity to resolve all issues that I have been
I personally appreciate the foresightedness of Ms. Levin.
Radhika R. Roy
> -----Original Message-----
> From: Orit Levin [SMTP:orit at radvision.com]
> Sent: Tuesday, May 30, 2000 10:57 AM
> To: ITU-SG16 at MAILBAG.INTEL.COM
> Subject: Re: H.323 Annex O
> Hello all!
> As the editor of H.323 Annex O, I would like to expand Roni's precise
> and add a few words about the objectives of Annex O. (BTW, the full
> appears in APC-1776 and TD-40a from Osaka meeting)
> H.323 specification defines means for building multimedia communication
> services over any Packet Based Network, among them Internet. However, in
> order to deploy efficient and globally interoperable Internet based H.323
> systems, definitions for using Internet protocols and technologies
> (complementary to H.323) in context of H.323 Specification should be
> This work will be organized in Annex O named "Internet protocols and
> Technologies (complementary to H.323) in context of H.323 Specification".
> The first material towards Annex O addresses the use of DNS technology in
> context of H.323 and includes (1) definition of H323-URL scheme and (2)
> cases of H323-URL and other URL schemes in H.323 messages and H.323
> I hope and believe, that H.246 new Appendix (H.323-SIP Interworking) and
> corresponding attempts in IETF (listed by Mr. Roy) will define their
> solution(s) in accordance with the procedures of Annex O.
> Best Regards,
> Orit Levin
> RADVision Inc.
> 575 Corporate Drive Suite 420
> Mahwah, NJ 07430
> Tel: 1 201 529 4300 (230)
> Fax: 1 201 529 3516
> orit at radvision.com
> -----Original Message-----
> From: Roni Even <Roni_e at ACCORD.CO.IL>
> To: ITU-SG16 at MAILBAG.INTEL.COM <ITU-SG16 at MAILBAG.INTEL.COM>
> Date: Sunday, May 28, 2000 5:50 AM
> Subject: Re: H.323 Annex O
> >The summary from Q14 states that SIP-H.323 interworking will be an
> >that will map messages for simple audio calls. and would defines
> >interworking mode. See the text bellow from TD-21b
> >Roni Even
> >6.1.1 APC-1776 - Terms of Reference for H.323 - Internet Interworking
> >[H.323-Internet Interworking Group] [joint with Q.12, Q.13]
> >Q.15 discussed some SIP matters - SDP does not currently provide enough
> >detail to describe H.263+ parameters.
> >Call signaling could be captured in an appendix to H.246. This appendix
> >would first address simple audio interworking, covering topics such as
> >mapping messages between H.323 and SIP. This is work that is currently in
> >progress in the IETF (not an official work item at this time, but an
> >unofficial task in the SIP working group). This appendix would define the
> >"preferred interworking mode" of H.323; we'd expect the SIP experts to
> >define the preferred interworking mode of SIP. We need to capture the
> >essence of each of the functional entities. Contributions are requested.
> >There was agreement that a new annex to H.323 to address how H.323 could
> >utilize a variety of internet services. Section 3 of APC-1776 is a good
> >basis for this work.
> >> -----Original Message-----
> >> From: Roy, Radhika R, ALARC [SMTP:rrroy at ATT.COM]
> >> Sent: Fri, May 26, 2000 9:30 PM
> >> To: ITU-SG16 at MAILBAG.INTEL.COM
> >> Subject: H.323 Annex O
> >> Mr. M. F. TOSCO
> >> Chairman
> >> ITU-T SG16 WP2
> >> Dear Mr. TOSCO:
> >> We are very much pleased to see that an H.323 Annex O (Internet
> >> and Technologies Complementary to H.323) has been opened in the joint
> >> meeting of Q.13/16 and Q.13/16 held in Osaka, Japan on May 15-19, 2000.
> >> is expected that this annex will cover the following topics:
> >> 1. H.323-SIP Interworking
> >> 2. Inteworking between H.323 and other IETF Protocols (e.g., TRIP,
> >> etc.)
> >> With respect to item 1 (H.323-SIP Interworking), it has been noted in
> >> meeting report that the IETF is also working to develop an
> >> RFC
> >> (a standard track RFC is also a possibility) for the SIP-H.323
> >> interworking.
> >> The way this work in the IETF is progressing is as follows (I believe
> >> the editor of H.323 Annex O is also fully aware of this work of the
> >> 1. SIP-H.323 Interworking Requirements RFC (Informational): by
> >> July-December, 2000 (tentative)
> >> 2. SIP-H.323 Interworking RFC (Informational): December 2000 -
> >> 2001 (tentative)
> >> The Internet-Drafts and documents that are being provided to develop
> >> RFC
> >> are as follows:
> >> 1. Agrawal, Roy, and Palawat, "SIP-H.323 Interworking
> >> draft-agrawal-roy-palawat-sip-h323-interworking-00.txt, IETF, June
> >> 2. Singh and Schulzrinne, "Interworking Between SIP/SDP and
> >> draft- singh-sip-h323-00.txt, IETF, January 2000.
> >> 3. C. Agbah, "SIP and H.323 Signaling Gateway."
> >> It is expected that the SIP-H.323 Interworking RFC will be based
> >> on the above documents along with suggestions made via emails and
> >> conference
> >> calls.
> >> People could take many those contributions to the ITU-T SG16 for the
> >> SIP-H.323 Interworking in the last SG16 February'00 meeting. However,
> >> was
> >> found that many companies and institutions that invented the
> >> solution could not afford to provide the membership fees of the ITU-T,
> >> some of them even could not afford to make a foreign trip for the
> >> meeting. But this has not been the case for the IETF where the email
> >> been good enough to work for developing the standard.
> >> Therefore, I am proposing the following to harmonize the work of these
> >> organizations so that the complementary standards are created in the
> >> SG16 and IETF:
> >> 1. Let the IETF produce the SIP-H.323 interworking RFC, while we,
> >> ITU-T SG16, will develop the H.323-TRIP and/or other IETF protocols
> >> Interworking standard.
> >> 2. Should the IETF do not develop the standard track SIP-H.323
> >> we,
> >> the ITU-T SG16, might consider how IETF's SIP-H.323 Interworking
> >> (Informational) RFC can be made a formal standard.
> >> I hope this suggestion will be acceptable to all of us.
> >> Best regards,
> >> Radhika R. Roy
> >> AT&T Delegation Manager in the ITU-T SG16 (WP1, WP2, & WP3)
> >> 200 Laurel Avenue, Middletown, NJ 07748, USA
> >> +1 732 420 1580 Tel
> >> +1 732 368 1195 Fax
> >> rrroy at att.com
> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >> For help on this mail list, send "HELP ITU-SG16" in a message to
> >> listserv at mailbag.intel.com
> >For help on this mail list, send "HELP ITU-SG16" in a message to
> >listserv at mailbag.intel.com
> For help on this mail list, send "HELP ITU-SG16" in a message to
> listserv at mailbag.intel.com
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com
More information about the sg16-avd