IETF Logo Mail Archive

Re: [rtcweb] RTT Education: Neat Demonstration of NON-peer-to-peer RTT (for future webrtc standardization purposes)

Gunnar Hellstrom <gunnar.hellstrom@omnitor.se> Fri, 31 May 2013 22:59 UTC

Return-Path: <gunnar.hellstrom@omnitor.se>
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 D0BEE21F8607 for <rtcweb@ietfa.amsl.com>; Fri, 31 May 2013 15:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wlMmehquSeS4 for <rtcweb@ietfa.amsl.com>; Fri, 31 May 2013 15:59:12 -0700 (PDT)
Received: from vsp-authed-02-02.binero.net (vsp-authed02.binero.net [195.74.38.226]) by ietfa.amsl.com (Postfix) with SMTP id 9F7E221F85E0 for <rtcweb@ietf.org>; Fri, 31 May 2013 15:59:09 -0700 (PDT)
Received: from smtp01.binero.se (unknown [195.74.38.28]) by vsp-authed-02-02.binero.net (Halon Mail Gateway) with ESMTP for <rtcweb@ietf.org>; Sat, 1 Jun 2013 00:58:12 +0200 (CEST)
Received: from [192.168.50.38] (h79n2fls31o933.telia.com [212.181.137.79]) (Authenticated sender: gunnar.hellstrom@omnitor.se) by smtp-06-01.atm.binero.net (Postfix) with ESMTPA id BE8A23A10F for <rtcweb@ietf.org>; Sat, 1 Jun 2013 00:58:11 +0200 (CEST)
Message-ID: <51A92B07.7030207@omnitor.se>
Date: Sat, 01 Jun 2013 00:58:15 +0200
From: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAA79oDkcKr6rWy=uJe2P7TuabiUeizJoHqtRMs=zYK7z3AW8OQ@mail.gmail.com> <51A8F85F.4090900@nostrum.com> <CAA79oDmXF=cnWqzaUE3dr3ZCbLqms=KhRgPOWWg1hMD=hOAArA@mail.gmail.com> <51A908AC.2000901@stpeter.im>
In-Reply-To: <51A908AC.2000901@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] RTT Education: Neat Demonstration of NON-peer-to-peer RTT (for future webrtc standardization purposes)
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, 31 May 2013 22:59:17 -0000

On 2013-05-31 22:31, Peter Saint-Andre wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 5/31/13 1:31 PM, Mark Rejhon wrote:
>> Actually, it's not quite that simple.
>>
>> Some countries made RFC4103 part of their government legislation.
>> There are two open real-time text standards that is necessary to
>> make provisions for, to cover world-wide usage.
>>
>> Everytime SIP is used for anything, it should always use RFC4013.
>> If WebRTC implementations touch SIP and not XMPP, and utilize
>> real-time text, then it needs to use RFC4103, even if it has to use
>> the sockets feature.  Thus, we need to make sure that it's also
>> usable for RFC4103. So it's not a 100% solved problem; there is
>> still a SIP need.
> Although I have not read the legislation that mandates use of RFC 4103
> (and I'm not particularly interested in the Layer 8 issues), I don't
> quite agree that one can't use SIP and XMPP in concert. For example,
> one could use SIP to negotiate use of XMPP with XEP-0301 as the RTT
> channel, similar to draft-sparks-simple-jabber-sessions from way back
> in 2002:
>
> http://tools.ietf.org/id/draft-sparks-simple-jabber-sessions-00.txt
>
> That might not be palatable to the politicians, but it might be an
> acceptable technical solution.
Well formulated requirements do not say that you must always USE RFC 
4103 for real-time text.
The requirements rather say that you must SUPPORT RFC 4103 in SIP call 
control environment, and you must provide real-time text functionality 
with good flow, sufficiently short delay and sufficient reliability.
To support means to be possible to activate through negotiation.

So there is room for USING other protocols.

Gunnar


>
> Peter
>
> - -- 
> Peter Saint-Andre
> https://stpeter.im/
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJRqQisAAoJEOoGpJErxa2pCMoP/R4pRxPbfMcP3UF1WWTlYVcN
> qT+tlq2s4YFH8luttDzFf0V66yBQvPlJ1cedhxqJxlWZeK9xrsGqzVI2LVj4/mhP
> e64yGToTvdHTuayD+q41gXsrLcpTxaUviSCMOI/zr1Gqv5lfXUV/qXH9V195gmZ8
> V0EgRebCHhFPFiEKZknUfhFLrqrLBEQ4xGna+dvWZREMolRLx0qGdtdkWRJbWZEZ
> VqjG/S5JBQGGfON/Cmww/Rcfzb1nopEGC0ff/k7DgZFaHxX7CcjaFq2b9wOl7udf
> k8PposwpaZ5KNCpsUB7H7qdrqTUi11JHVUj3DLVmp9fZVwuZfT0+2aLiqYV9NsdJ
> l0werWpTeGTY8ynq8qlgecBv9LE4Oqh+u6PDoJf9TdmVtetS1vZHH/P77rUZ98Fp
> mgcXYxOxTDOXTq1/d2TVGylWXIV0kajxr1jKC5G40ksH85b9imkqSzirtLa/Wx3L
> y5RHiXjO0Uoj3ic65VrPYqNRKLYk1U2NHZ6+YvRVOPBuhsNcq2vTbQ3X2QlIOGk2
> FCd0CVxHUt98Ku5ypr1hHgjxDzDsqHvsAo5yyCWuDkHQHKeHGGGeDqasEmwourUt
> EC8nIcd5s4/Pc78+NPf3iOtLoyXQmSnqnubaWYyzP8lCe+ZhijfKYomYddlIKrzO
> kB8Vt6gf8mtWnuczRsAj
> =itx6
> -----END PGP SIGNATURE-----
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email