Re: [dispatch] X over websockets

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Thu, 13 February 2014 21:37 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3FE31A0555 for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 13:37:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ms1qvbTv_4x for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 13:37:52 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id ACD351A0520 for <dispatch@ietf.org>; Thu, 13 Feb 2014 13:37:51 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id q59so7955396wes.6 for <dispatch@ietf.org>; Thu, 13 Feb 2014 13:37:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=d1lW6stwq8vynuo9WgkfQOoBRGvWoZ0YBDIiGnCO3JQ=; b=nHy/IHYv7T5tlug+ls72w4QeFTSESo6e3A/czmRmSpQ43hPuOVnWkcNPG/r1NGvxJ6 JZlSodDZk58SbE3EJmWABgtXmg4VaoX8WSOLxcz1sWIMNpasx2kS8eeAE/ajXK2BwEge rjivcxRG9yKphfb36Znnw5ZBQR2PbaNdGH/9PMuBX40aBOeoEY6W3/qxwVo5D0aimnqp Ixv+A27voYP9lp0k23wCasT1Bo6xkw3tMaH5daFddgwAlnC+n/4echS5CGFsS/s99gKo +eqlUILo9Qqv8oMVjKisayZAx05INGNdE4n84YgYApIo5H9UYJhZNpFUG+I5YElT6cYf GI3w==
X-Received: by 10.194.170.133 with SMTP id am5mr3153962wjc.42.1392327469835; Thu, 13 Feb 2014 13:37:49 -0800 (PST)
Received: from [192.168.0.192] ([95.61.111.78]) by mx.google.com with ESMTPSA id uq2sm7513783wjc.5.2014.02.13.13.37.47 for <dispatch@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Feb 2014 13:37:48 -0800 (PST)
Message-ID: <52FD3B2B.9030905@gmail.com>
Date: Thu, 13 Feb 2014 22:37:47 +0100
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dispatch@ietf.org
References: <20131213005747.777.34301.idtracker@ietfa.amsl.com> <CAHBDyN4tSRO_nYy7_-V4xfmDbF0ZeLJ24_fEOQ1p9Z2BvJyinQ@mail.gmail.com> <97B47463-42D2-4BA9-AC2F-DF8C67702DDC@cisco.com> <52FCE70C.1030608@gmail.com> <CAHBDyN7hySvbiJYnvRXDQ2ZS_FYFDMaODXBDRarE6DhRwC=fHQ@mail.gmail.com> <CA+ag07bPBHzODTWGKFrKE00nO_wiMgRv2GEwUpGCiH25-Xf2Cw@mail.gmail.com> <52FD112B.5040209@alum.mit.edu> <52FD2AE0.7060600@gmail.com> <CAEqTk6TzODAWjpqJPRp_zfGcYm_MLHAvU57sq9h7njpifWiufg@mail.gmail.com> <52FD3883.6050402@gmail.com> <CAEqTk6RERBdfkhNc=70n57ADa0=CxVLekFedgRDVdrvx0mWjyA@mail.gmail.com>
In-Reply-To: <CAEqTk6RERBdfkhNc=70n57ADa0=CxVLekFedgRDVdrvx0mWjyA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040105020104060600080002"
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/CJMeWT_7uEpwUxnw8-sgDSf2wXM
Subject: Re: [dispatch] X over websockets
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 21:37:54 -0000

I completely agree, and I have argued and discussed about it in the 
past, but the topic keeps showing up in each draft discussion. So I 
would prefer to do something to prevent having the same discussion again 
and again in the future.

Best regards
Sergio
El 13/02/2014 22:32, Peter Dunkley escribió:
> My point was more that if we are going to have a discussion about how 
> we refer to WebSockets (in SDP or elsewhere) then let's have it, but 
> let's also keep it separate from a reopening of the WebSockets vs 
> DataChannel discussion.
>
> Which is the right transport (WebSockets/DataChannel) is a use-case 
> specific thing.  I don't see the need for any sort of "beauty contest" 
> as this is more like the difference between using TCP vs UDP - some 
> things work on both and some are better suited to one than the other. 
>  Why would we having this "contest" at all, it just doesn't make sense 
> to me.  Some things will be on WebSockets, some things will be on 
> DataChannel, some things will be on both, and what is wrong with that?
>
>
>
> On 13 February 2014 21:26, Sergio Garcia Murillo 
> <sergio.garcia.murillo@gmail.com 
> <mailto:sergio.garcia.murillo@gmail.com>> wrote:
>
>     El 13/02/2014 22:01, Peter Dunkley escribió:
>
>         Hello,
>
>         Wasn't Sergio's point about what the terminology (for example,
>         within SDP) should be rather than whether WebSockets is
>         appropriate as a transport or not?  And isn't this a totally
>         separate issue from the WebSockets vs. WebRTC question?
>
>
>     Yes and no. My point was that all "X over websockets" will have
>     some common issues, so instead of having the same discussion every
>     time, it would be better if we could address them once and for
>     all, so when someone wants to propose a new "X", it does not have
>     to spend time and effort on that issues.
>
>
>     Best regards
>     Sergio
>
>     _______________________________________________
>     dispatch mailing list
>     dispatch@ietf.org <mailto:dispatch@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dispatch
>
>
>
>
> -- 
> Peter Dunkley
> Technical Director
> Crocodile RCS Ltd
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch