IETF Logo Mail Archive

Re: [rtcweb] RTT (was :No Plan )

Iñaki Baz Castillo <ibc@aliax.net> Mon, 03 June 2013 12:14 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 119EF21F9622 for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 05:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 ZV2A+LHdXWES for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 05:14:32 -0700 (PDT)
Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 76C7E21F95DD for <rtcweb@ietf.org>; Mon, 3 Jun 2013 05:14:32 -0700 (PDT)
Received: by mail-qa0-f44.google.com with SMTP id hu16so1768304qab.10 for <rtcweb@ietf.org>; Mon, 03 Jun 2013 05:14:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=JK2+qiCSeSNSw8safNhLAKtWuI8MCDYKFjUPp1D6Lrw=; b=MmQ6Vvt5P/s4O3UzEyVIqiHGHwmC5D7VTssDzGfz96a1vX0BJ99ZNss4bbdZuh6sUx xIB3Ne60+rVzGSTOHqK5jz9NEMjVO7AnylUOoGuAFSONVdvm+WbFPHVWmUaL6HviYaxg 7pMhWZ6kFtgDCR1Y3sW1csQkyLPvVdOamqHeh/9Q98h9bBjIO0HkfNxBayP+PpG/46wM Zdk1oX0Em/QUZdLmqjpO/v4Cg8GhYKkB6TsEtMctQrGHmKyl+XzXz4z7z9WGDtqR9rKx KhK4UaxiN/xdKQuClZiPPowHU6XbvqW67G/B9umiwc0H6bztaK9p3oNWGQVKofRqQyOb FfHA==
X-Received: by 10.49.0.244 with SMTP id 20mr21613428qeh.50.1370261671738; Mon, 03 Jun 2013 05:14:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.26.103 with HTTP; Mon, 3 Jun 2013 05:14:11 -0700 (PDT)
In-Reply-To: <51AC8547.1060400@omnitor.se>
References: <51A65017.4090502@jitsi.org> <51A7BEBE.2040302@omnitor.se> <CALiegfk6XchF4U1Orpd6oJsydz-VGtBQ=CwaWrPa_KjsaQynYQ@mail.gmail.com> <51A7CD81.2060805@gmail.com> <51A835D7.9060603@omnitor.se> <CALiegfm4R=3mGqTOxBfvCfnsRg=fe=XapA6s-QQNjrsAkg5HEA@mail.gmail.com> <51A8F3EF.9080702@alum.mit.edu> <CALiegfkfz=qVM_wB21BBOypMTwTjkyG97zAmzHVpA6WHK2DA6w@mail.gmail.com> <51AC7D4F.6090708@omnitor.se> <CALiegfkxfb4qk+bS_EWbcxkNv-BSOwDw6eR-b86Z-hyMY60z3Q@mail.gmail.com> <51AC8547.1060400@omnitor.se>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 03 Jun 2013 14:14:11 +0200
Message-ID: <CALiegfmeQtzAD_=6bPt77zNYC79iKjneycFS5RGssckNwSqptg@mail.gmail.com>
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQm6KlvuGfSB3yBmLLrkHpd/YT7dmUFF9hbkKlktVvSLLl4WE46sUp9VVmNGzia5cBrZy7eY
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] RTT (was :No Plan )
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: Mon, 03 Jun 2013 12:14:33 -0000

2013/6/3 Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>:
> The use cases draft includes a case titled:
>
> 4.2.10.  Simple video communication service with inter-operator calling
>
> See:
> http://tools.ietf.org/html/draft-ietf-rtcweb-use-cases-and-requirements-10#page-9

That will just work if both websites want to offer such a
inter-website-communication. And that's already feasible. But we don't
need a new standard (RTT-over-RTP) for allowing two users in different
websites to intercommunicate via RTT. That can be achieved in multiple
ways with existing technology (WebSocket, DataChannel) but, still,
both websites must allow it.


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

v2.23.0 | Report a Bug | By Email