IETF Logo Mail Archive

[SIP] FW: 47th IETF: SIP323 BOF

S_S_Dinesh/India/IBM@au1.ibm.com Mon, 08 May 2000 21:34 UTC

Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20367 for <sip-archive@odin.ietf.org>; Mon, 8 May 2000 17:34:34 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 2565F44532; Mon, 8 May 2000 17:18:53 -0400 (EDT)
Delivered-To: sip@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by lists.bell-labs.com (Postfix) with SMTP id CB83D44533 for <sip@share.research.bell-labs.com>; Mon, 8 May 2000 17:17:58 -0400 (EDT)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Mon May 8 17:23:53 EDT 2000
Received: by lists.bell-labs.com (Postfix) id CE274443B3; Mon, 8 May 2000 14:21:36 -0400 (EDT)
Delivered-To: sip@lists.bell-labs.com
Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id A2DBF443AF for <sip@lists.bell-labs.com>; Mon, 8 May 2000 14:21:36 -0400 (EDT)
Received: by lists.research.bell-labs.com (Postfix) id E4DF352AB; Mon, 8 May 2000 14:21:35 -0400 (EDT)
Delivered-To: sip@lists.research.bell-labs.com
Received: from chair.dnrc.bell-labs.com (chair [135.180.161.201]) by lists.research.bell-labs.com (Postfix) with ESMTP id 049A652BB for <sip@lists.research.bell-labs.com>; Mon, 8 May 2000 14:19:26 -0400 (EDT)
Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by chair.dnrc.bell-labs.com (8.9.3/8.9.3) with SMTP id GAA18575 for <sip@lists.research.bell-labs.com>; Mon, 8 May 2000 06:12:17 -0400 (EDT)
From: S_S_Dinesh/India/IBM@au1.ibm.com
Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Mon May 8 05:59:05 EDT 2000
Received: from ausmtp01.au.ibm.com ([202.135.136.97]) by dusty; Mon May 8 05:59:03 EDT 2000
Received: from f03n05e.au.ibm.com by ausmtp01.au.ibm.com (IBM AP 1.0) with ESMTP id TAA198270; Mon, 8 May 2000 19:53:27 +1000
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67]) by f03n05e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id TAA28400; Mon, 8 May 2000 19:58:43 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id CA2568D9.0036D006 ; Mon, 8 May 2000 19:58:41 +1000
X-Lotus-FromDomain: IBMAU@IBMIN@IBMAU
To: "Sip (E-mail)" <sip@lists.research.bell-labs.com>, "ITU-T Study Group 16 (E-mail)" <ITU-SG16@mailbag.cps.intel.com>, "Sip-H323 (E-mail)" <sip-h323@egroups.com>
Message-ID: <CA2568D9.0036C233.00@d73mta05.au.ibm.com>
Date: Mon, 08 May 2000 14:10:08 +0530
Mime-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-Disposition: inline
Subject: [SIP] FW: 47th IETF: SIP323 BOF
Sender: sip-admin@lists.bell-labs.com
Errors-To: sip-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
X-BeenThere: sip@lists.bell-labs.com


For those who may have missed it, here is the official announcement
of the BOF.

Dave Walker
SS8 Networks
Ottawa, Canada

-----Original Message-----
From: mbeaulie@cnri.reston.va.us [mailto:mbeaulie@cnri.reston.va.us]On
Behalf Of ietf-secretariat@ietf.org
Subject: 47th IETF: SIP323 BOF


SIP and H.323 Interworking BOF (sip323)

Monday, March 27 at 1300-1500
=============================

CHAIRS: Joon Maeng <joon_maeng@vtel.com>
        Dave Walker <drwalker@ss8networks.com>

DESCRIPTION:

There are two competing standards in the industry for establishing and
managing real-time interactive media communications over IP.  One is the
proposed IETF standard, Session Initiation Protocol (RFC 2543), and the
other is the ITU recommendation, H.323.  Although they use the same
protocol (RTP) for media streaming, they cannot establish calls between
them.  In the absence of any formal interoperability standards, many
vendors are beginning to develop proprietary application gateways for
interworking between SIP and H.323.

In order to provide interoperability between the two standards, it is
urgent to define a common interworking specifications for the industry.
The recognition of the need for this interworking specification has lead
to calls for its development from both manufacturers and service
providers, individually and through industry consortia (such as IMTC)
and other bodies concerned with interoperability (such as ETSI).

In this BOF, we are going to discuss SIP and H.323 interworking issues,
execution plans and the scope of the work.

AGENDA:

- Do we need SIP-H.323 interworking?
- Coordination with other groups?
- Scope of interworking
- Outcome of the work?
- Suggestions?

Helpful reading:
    - draft-singh-sip-h323-00.txt
    - SIP: Session Initiation Protocol (RFC 2543)
    - SDP: Session Description Protocol (RFC 2327)
    - ITU recommendations: H.323, H.225.0, H.245






_______________________________________________
SIP mailing list
SIP@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/sip

v2.23.0 | Report a Bug | By Email