IETF Logo Mail Archive

Re: [rtcweb] RTCWeb Forking usecase [was RE: draft-kaplan-rtcweb-sip-interworking-requirements-00]

Iñaki Baz Castillo <ibc@aliax.net> Fri, 28 October 2011 20:04 UTC

Return-Path: <ibc@aliax.net>
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 EBCA811E8081 for <rtcweb@ietfa.amsl.com>; Fri, 28 Oct 2011 13:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.644
X-Spam-Level:
X-Spam-Status: No, score=-2.644 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 VVN2YJoDvkOI for <rtcweb@ietfa.amsl.com>; Fri, 28 Oct 2011 13:04:59 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6389111E807F for <rtcweb@ietf.org>; Fri, 28 Oct 2011 13:04:59 -0700 (PDT)
Received: by vws5 with SMTP id 5so4462238vws.31 for <rtcweb@ietf.org>; Fri, 28 Oct 2011 13:04:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.107.81 with SMTP id a17mr617178vcp.96.1319832296772; Fri, 28 Oct 2011 13:04:56 -0700 (PDT)
Received: by 10.220.159.134 with HTTP; Fri, 28 Oct 2011 13:04:56 -0700 (PDT)
In-Reply-To: <2E239D6FCD033C4BAF15F386A979BF51159D7C@sonusinmail02.sonusnet.com>
References: <20111024224257.28459.65554.idtracker@ietfa.amsl.com> <6EB8679A-13D5-4AD7-97F2-BC35FC0966F0@acmepacket.com> <2E239D6FCD033C4BAF15F386A979BF51159C32@sonusinmail02.sonusnet.com> <CALiegfnVaZjh1K+brd180Z9Ufheau3v6OJe6Ejv8P7wzw6ROQw@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF51159D7A@sonusinmail02.sonusnet.com> <4EAAF413.8030501@alvestrand.no> <2E239D6FCD033C4BAF15F386A979BF51159D7B@sonusinmail02.sonusnet.com> <CALiegfm4FXVBkeGLtAY7Fp=GQB8SxVtamPemUjgwdbSBGydn-w@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF51159D7C@sonusinmail02.sonusnet.com>
Date: Fri, 28 Oct 2011 22:04:56 +0200
Message-ID: <CALiegfmFyYVZgweXwjCj94teWNQvMEzDWOaDU-Dc7fG4Qse2Cg@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Ravindran Parthasarathi <pravindran@sonusnet.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTCWeb Forking usecase [was RE: 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: Fri, 28 Oct 2011 20:05:00 -0000

2011/10/28 Ravindran Parthasarathi <pravindran@sonusnet.com>:
> ISTM, SIP specific functionality is pushed into WebRTC client unnecessary without well-defined WebRTC usecase.

It's unnecessary for you. For me it's *necessary*. Are you propossing
that the specs should prevent this use case just because it seems
unnecessary for you?

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email