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

Hadriel Kaplan <HKaplan@acmepacket.com> Tue, 25 October 2011 06:45 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 2301711E80D9 for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 23:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164, 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 VGsqLSaT-XHD for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 23:45:20 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8425011E8086 for <rtcweb@ietf.org>; Mon, 24 Oct 2011 23:45:20 -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; Tue, 25 Oct 2011 02:45:19 -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; Tue, 25 Oct 2011 02:45:19 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Ravindran Parthasarathi <pravindran@sonusnet.com>
Thread-Topic: [rtcweb] draft-kaplan-rtcweb-sip-interworking-requirements-00
Thread-Index: AQHMkuGo4oKL9jzYW0yCTTm4OInomQ==
Date: Tue, 25 Oct 2011 06:45:18 +0000
Message-ID: <DEBEFABA-99D8-4762-A4C1-C700C51BAA06@acmepacket.com>
References: <20111024224257.28459.65554.idtracker@ietfa.amsl.com> <6EB8679A-13D5-4AD7-97F2-BC35FC0966F0@acmepacket.com> <2E239D6FCD033C4BAF15F386A979BF51159C4A@sonusinmail02.sonusnet.com>
In-Reply-To: <2E239D6FCD033C4BAF15F386A979BF51159C4A@sonusinmail02.sonusnet.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F8897EDB6B6A4845830B8706E415D8F5@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [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: Tue, 25 Oct 2011 06:45:21 -0000

On Oct 25, 2011, at 2:06 AM, Ravindran Parthasarathi wrote:

> Just adding one more point regarding architecture, Media plane
> interworking function is an optional element for the next generation
> (release) of SIP devices wherein Media agent of SIP UA will be able to
> interop directly with browser media plane without intermediate
> media-plane gateways.

Do you mean that statement as an argument against the draft?  That was why I kept using the term "deployed" throughout the draft. :)

Or did you mean it in the sense of an additional requirement that should be added to draft?  That would make sense and I can add it.  Something like:

"It MUST be possible to determine whether interworking is required on a session-by-session basis in order to avoid performing interworking when it is not needed."

Does that capture what you meant?

I think that's possible to do for pretty much everything in the draft, except RTCP generation. (which is possibly the ugliest interworking to have to do in the whole doc)

-hadriel