Re: [pntaw] Real-time media over TCP

Bernard Aboba <bernard_aboba@hotmail.com> Mon, 02 September 2013 18:06 UTC

Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DECF21F9B12 for <pntaw@ietfa.amsl.com>; Mon, 2 Sep 2013 11:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.741
X-Spam-Level:
X-Spam-Status: No, score=-101.741 tagged_above=-999 required=5 tests=[AWL=-0.538, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
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 qK3S93HnLwBH for <pntaw@ietfa.amsl.com>; Mon, 2 Sep 2013 11:06:36 -0700 (PDT)
Received: from blu0-omc2-s11.blu0.hotmail.com (blu0-omc2-s11.blu0.hotmail.com [65.55.111.86]) by ietfa.amsl.com (Postfix) with ESMTP id D50FF21F9D52 for <pntaw@ietf.org>; Mon, 2 Sep 2013 11:06:27 -0700 (PDT)
Received: from BLU403-EAS189 ([65.55.111.73]) by blu0-omc2-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 2 Sep 2013 11:06:22 -0700
X-TMN: [bOn92dNG27JmkFeFfZotDGpJTx8tj5q1]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU403-EAS1892673E94E650BC6E7798C93300@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
References: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.com>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.com>
Date: Mon, 2 Sep 2013 11:06:20 -0700
To: Victor Pascual Avila <victor.pascual.avila@gmail.com>
X-OriginalArrivalTime: 02 Sep 2013 18:06:22.0525 (UTC) FILETIME=[21C6FED0:01CEA807]
Cc: "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] Real-time media over TCP
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Sep 2013 18:06:41 -0000

Can you describe the usage scenario? Is this about media traversal of highly restrictive firewalls? (E.g. HTTP-only)? 

On Aug 30, 2013, at 3:12 AM, "Victor Pascual Avila" <victor.pascual.avila@gmail.com> wrote:

> Hi,
> 
> Real-time media over TCP has some inherent challenges -- is this
> something we're planning to discuss here? We did RTP over TCP (+ HTTP
> CONNECT) in the past and ended up using multiple connections along
> with application-layer redundancy. I'm wondering whether we'll be able
> to do the same when moving to WebRTC
> 
> Thanks,
> -Victor
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw