[rtcweb] draft-kaplan-rtcweb-sip-interworking-requirements-00

Hadriel Kaplan <HKaplan@acmepacket.com> Mon, 24 October 2011 23:30 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01E5611E81E8 for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 16:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.426
X-Spam-Level:
X-Spam-Status: No, score=-2.426 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NaDz-GLDP9Hu for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 16:30:14 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id E171F11E81DE for <rtcweb@ietf.org>; Mon, 24 Oct 2011 16:30:13 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 24 Oct 2011 19:30:12 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.230]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Mon, 24 Oct 2011 19:30:12 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: draft-kaplan-rtcweb-sip-interworking-requirements-00
Thread-Index: AQHMkqTg+ZnmTyb6QUGCzFAZ7bjkHA==
Date: Mon, 24 Oct 2011 23:30:11 +0000
Message-ID: <6EB8679A-13D5-4AD7-97F2-BC35FC0966F0@acmepacket.com>
References: <20111024224257.28459.65554.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7164EA7634B8554E8387A2DC90738B2A@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Subject: [rtcweb] draft-kaplan-rtcweb-sip-interworking-requirements-00
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 23:30:15 -0000

Howdy,
I've submitted a draft listing some use-cases and resulting requirements for interworking from RTCWeb (or "WebRTC" as the case may be), to deployed SIP domains/devices.
The draft also discusses the functions which may be required in an interworking device, should some of the requirements not be met.

The purpose of the draft is to put pen-to-paper on some of the emails flying around the past month, to stimulate discussion, and hopefully drive consensus decisions sooner rather than later.
Info below.

Note that most of the doc is about media-plane issues, rather than about SIP/SDP as I expect Cullen's soon-to-be-announced ROAP signaling-gateway draft will be.

-hadriel


Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: I-D Action: draft-kaplan-rtcweb-sip-interworking-requirements-00.txt
> Date: October 24, 2011 6:42:57 PM EDT
> To: <i-d-announce@ietf.org>
> Reply-To: <internet-drafts@ietf.org>
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 	Title           : Requirements for Interworking RTCWeb with Current SIP Deployments
> 	Author(s)       : Hadriel Kaplan
> 	Filename        : draft-kaplan-rtcweb-sip-interworking-requirements-00.txt
> 	Pages           : 22
> 	Date            : 2011-10-24
> 
>   The IETF RTCWEB WG has been discussing how to interwork with
>   deployed SIP equipment and domains.  Doing so may require an
>   Interworking Function middlebox in the media-plane.  This document
>   lists some RTCWeb-to-SIP use-cases, the RTCWeb requirements to
>   support such, and the complexity involved in interworking if the
>   requirements cannot be met.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-kaplan-rtcweb-sip-interworking-requirements-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-kaplan-rtcweb-sip-interworking-requirements-00.txt
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt