IETF Logo Mail Archive

Re: [rtcweb] draft-sipdoc-rtcweb-open-wire-protocol-00 (Open In-The-Wire Protocol for RTC-Web)

Iñaki Baz Castillo <ibc@aliax.net> Fri, 28 October 2011 14:55 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 7CDBC21F8A64 for <rtcweb@ietfa.amsl.com>; Fri, 28 Oct 2011 07:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.643
X-Spam-Level:
X-Spam-Status: No, score=-2.643 tagged_above=-999 required=5 tests=[AWL=0.034, 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 Hc0IgwFSNZV3 for <rtcweb@ietfa.amsl.com>; Fri, 28 Oct 2011 07:55:24 -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 E819E21F8A71 for <rtcweb@ietf.org>; Fri, 28 Oct 2011 07:55:23 -0700 (PDT)
Received: by vws5 with SMTP id 5so4135916vws.31 for <rtcweb@ietf.org>; Fri, 28 Oct 2011 07:55:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.107.81 with SMTP id a17mr470895vcp.96.1319813723457; Fri, 28 Oct 2011 07:55:23 -0700 (PDT)
Received: by 10.220.159.134 with HTTP; Fri, 28 Oct 2011 07:55:23 -0700 (PDT)
In-Reply-To: <CAAJUQMiwyEREv_7pqeYjJXvrYXW2OWXZdEnzK6CtsUvLvG9whA@mail.gmail.com>
References: <CALiegfmvWWMf6dSikgfZqnSPuN-6UZKwAMfKu9HP2uqJxHMVCQ@mail.gmail.com> <CAAJUQMiwyEREv_7pqeYjJXvrYXW2OWXZdEnzK6CtsUvLvG9whA@mail.gmail.com>
Date: Fri, 28 Oct 2011 16:55:23 +0200
Message-ID: <CALiegf=FDrxGVzae2_yeBCcs7NwW6HNg4nCfUs1GA0gDSyaYYg@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Wolfgang Beck <wolfgang.beck01@googlemail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] draft-sipdoc-rtcweb-open-wire-protocol-00 (Open In-The-Wire Protocol for RTC-Web)
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 14:55:24 -0000

2011/10/28 Wolfgang Beck <wolfgang.beck01@googlemail.com>:
> Your document gives a nice overview how RTCWEB (WEBRTC? *sigh*)
> messages may look. Section 4 is a bit confusing as Bob calls Alice
> instead of the other way round.

IMHO it is time for Bob to call Alice :)



> It illustrates nicely that trapezoid -style interconnection would only
> work with a common server-to-server protocol like SIP. Nobody would
> try to implement all possible combinations of protocol translators to
> interconnect your four example protocols. With SIP, they "only" have
> to agree on the subset to implement. If SIP does not support a feature
> they support, they can't interconnect.

Right, but the same already occurs when attempting to interconnect two
pure SIP domains. Nothing new here :)


Thanks a lot.



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

v2.23.0 | Report a Bug | By Email