FW: RFC 4123 on Session Initiation Protocol (SIP)-H.323 Interwork

Euchner Martin martin.euchner at SIEMENS.COM
Fri Jul 8 03:40:01 EDT 2005

FYI: After a long time, the SIP-H.323 Interworking Requirements have made
it into an RFC.
So SG16 can now consider the next steps ahead on H.323-SIP Interworking
beyond the requirements stage.

With kind regards

Martin Euchner.
| Dipl.-Inf.                     Rapporteur
| Martin Euchner                 Phone: +49 89 722 55790
| Siemens AG.....................Fax  : +49 89 722 62366
| COM GC PS 3                    mailto:Martin.Euchner at siemens.com
|                                mailto:martin.euchner at ties.itu.int
| Hofmannstr. 51                 Intranet:
| D-81359 Muenchen               Internet: http://www.siemens.de/
| __________________
| Germany     

-----Original Message-----
From: ietf-announce-bounces at ietf.org
[mailto:ietf-announce-bounces at ietf.org] On Behalf Of
rfc-editor at rfc-editor.org
Sent: Donnerstag, 7. Juli 2005 20:26
To: ietf-announce at ietf.org
Cc: rfc-editor at rfc-editor.org
Subject: RFC 4123 on Session Initiation Protocol (SIP)-H.323 Interworking

A new Request for Comments is now available in online RFC libraries.

        RFC 4123

        Title:      Session Initiation Protocol (SIP)-H.323
                    Interworking Requirements
        Author(s):  H. Schulzrinne, C. Agboh
        Status:     Informational
        Date:       July 2005
        Mailbox:    hgs at cs.columbia.edu, charles.agboh at packetizer.com
        Pages:      16
        Characters: 29244
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-agrawal-sip-h323-interworking-reqs-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4123.txt

This document describes the requirements for the logical entity known
as the Session Initiation Protocol (SIP)-H.323 Interworking Function
(SIP-H.323 IWF) that will allow the interworking between SIP and

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 17503 bytes
Desc: not available
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20050708/75d23b08/attachment-0003.bin>

More information about the sg16-avd mailing list