Skip to main content

Session Initiation Protocol (SIP)-H.323 Interworking Requirements
RFC 4123

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: RFC Editor <>
Cc: The IESG <>, <>,
Subject: Re: Informational RFC to be: 

The IESG has no problem with the publication of 'Session Initiation 
Protocol (SIP)-H.323 Interworking Requirements' 
<draft-agrawal-sip-h323-interworking-reqs-08.txt> as an Informational 

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Jon Peterson.

A URL of this Internet-Draft is:

The process for such documents is described at

Thank you,

The IESG Secretary

Ballot Text

Technical Summary

This document provides a set of requirements for interworking the H.323
protocol developed by the ITU-T with the Session Inititation Protocol (SIP). The
focus in on telephone interworking applications and gatewaying as a means to
interoperability. We do not intend to execute on a corresponding mechanism here
within the IETF, but we hope that these requirements may be useful to other
standards bodies or implementers that undertake interworking.
Working Group Summary
This document is not the product of a working group.
Protocol Quality
This document was reviewed for the IESG by Jon Peterson.

RFC-Editor Note:

Please add the following IESG Note to this document:

      This RFC is not a candidate for any level of Internet Standard.
      The IETF disclaims any knowledge of the fitness of this RFC for
      any purpose and in particular notes that the decision to publish
      is not based on IETF review for such things as security,
      congestion control, or inappropriate interaction with deployed
      protocols.  The RFC Editor has chosen to publish this document at
      its discretion.  Readers of this document should exercise caution
      in evaluating its value for implementation and deployment.  See
      RFC 3932 for more information.

RFC Editor Note