IETF Logo Mail Archive

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

Wolfgang Beck <wolfgang.beck01@googlemail.com> Fri, 28 October 2011 14:40 UTC

Return-Path: <wolfgang.beck01@googlemail.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 5B00721F86EC for <rtcweb@ietfa.amsl.com>; Fri, 28 Oct 2011 07:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.809
X-Spam-Level:
X-Spam-Status: No, score=-2.809 tagged_above=-999 required=5 tests=[AWL=-0.132, 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 Bv4HKBb4uwXH for <rtcweb@ietfa.amsl.com>; Fri, 28 Oct 2011 07:40:30 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id A8C6921F8AFD for <rtcweb@ietf.org>; Fri, 28 Oct 2011 07:40:30 -0700 (PDT)
Received: by qadc10 with SMTP id c10so4679806qad.31 for <rtcweb@ietf.org>; Fri, 28 Oct 2011 07:40:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XAHzxQe0QytxwNLs5xqLjB2OIvI5cjlWrD+wj6enR8I=; b=r1+cUSXF11c+OdnClfD5xP65CCgbulJMq98xYj6BGlrzfPXJzVOff1acX0ry+i8ECz oqHdtf0QatA4vsYGedQhgNhviMjcIOiLRD7Erlvf04CxmkuFysLgiFHryn0Mzatu/rVs NuPqOjj0H1FdDEc5qDuffMaCrnAkDUusyasPs=
MIME-Version: 1.0
Received: by 10.68.31.132 with SMTP id a4mr4649655pbi.26.1319812829760; Fri, 28 Oct 2011 07:40:29 -0700 (PDT)
Received: by 10.68.49.169 with HTTP; Fri, 28 Oct 2011 07:40:29 -0700 (PDT)
In-Reply-To: <CALiegfmvWWMf6dSikgfZqnSPuN-6UZKwAMfKu9HP2uqJxHMVCQ@mail.gmail.com>
References: <CALiegfmvWWMf6dSikgfZqnSPuN-6UZKwAMfKu9HP2uqJxHMVCQ@mail.gmail.com>
Date: Fri, 28 Oct 2011 16:40:29 +0200
Message-ID: <CAAJUQMiwyEREv_7pqeYjJXvrYXW2OWXZdEnzK6CtsUvLvG9whA@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: text/plain; charset="ISO-8859-1"
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:40:31 -0000

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.

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.


Wolfgang Beck

v2.23.0 | Report a Bug | By Email