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

Iñaki Baz Castillo <ibc@aliax.net> Thu, 27 October 2011 08: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 24B5221F86A5 for <rtcweb@ietfa.amsl.com>; Thu, 27 Oct 2011 01:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.64
X-Spam-Level:
X-Spam-Status: No, score=-2.64 tagged_above=-999 required=5 tests=[AWL=0.037, 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 5ENE2E+7Ld88 for <rtcweb@ietfa.amsl.com>; Thu, 27 Oct 2011 01:55:05 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 898E421F8672 for <rtcweb@ietf.org>; Thu, 27 Oct 2011 01:55:05 -0700 (PDT)
Received: by qyk34 with SMTP id 34so419693qyk.10 for <rtcweb@ietf.org>; Thu, 27 Oct 2011 01:55:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.73.36 with SMTP id i4mr6215773obv.24.1319705704679; Thu, 27 Oct 2011 01:55:04 -0700 (PDT)
Received: by 10.182.220.66 with HTTP; Thu, 27 Oct 2011 01:55:04 -0700 (PDT)
In-Reply-To: <CALiegfmvWWMf6dSikgfZqnSPuN-6UZKwAMfKu9HP2uqJxHMVCQ@mail.gmail.com>
References: <CALiegfmvWWMf6dSikgfZqnSPuN-6UZKwAMfKu9HP2uqJxHMVCQ@mail.gmail.com>
Date: Thu, 27 Oct 2011 10:55:04 +0200
Message-ID: <CALiegfmFE0zhBg6aZMtRMO5q-k6_jeHAn9q2XivNw8yjNVqyag@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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: Thu, 27 Oct 2011 08:55:06 -0000

2011/10/25 Iñaki Baz Castillo <ibc@aliax.net>:
> A new I-D draft-sipdoc-rtcweb-open-wire-protocol-00.txt has been
> successfully submitted by Iñaki Baz Castillo,  Saúl Ibarra Corretgé
> and José Luis Millán Villegas, and posted to the IETF repository.
>
> Filename:        draft-sipdoc-rtcweb-open-wire-protocolRevision:
>  00Title:           Open In-The-Wire Protocol for RTC-WebCreation
> date:   2011-10-25WG ID:           Individual SubmissionNumber of
> pages: 22
>
>
> http://tools.ietf.org/html/draft-sipdoc-rtcweb-open-wire-protocol-00
> http://www.ietf.org/id/draft-sipdoc-rtcweb-open-wire-protocol-00.txt
>
>
> Abstract:  RTC-Web clients communicate with a server in order to
> request or  manage realtime communications with other users.  This
> document  exposes four hypothetical and different RTC-Web scenarios
> and  analyzes the requirements of the in-the-wire protocol in each of
> them.
>   The aim of this document is to make RTC-Web properly fit in the
> nature of the Web.


Hi, just wondering if somebody has read this informational draft. I'd
would really appreciate if folks agree with the conclusiones and
requirements exposed in the document or want to discuss about them.
The draft tries to clarify the scope of RTC-Web, and IMHO that's an
important milestone before we can move on.

Thanks a lot.


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