[pntaw] Real-time media over TCP

Victor Pascual Avila <victor.pascual.avila@gmail.com> Fri, 30 August 2013 10:12 UTC

Return-Path: <victor.pascual.avila@gmail.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 6622521E80A3 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 03:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 5Jlxsq8x0R9U for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 03:12:14 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id AFA0521E809C for <pntaw@ietf.org>; Fri, 30 Aug 2013 03:12:12 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id x18so1698767lbi.17 for <pntaw@ietf.org>; Fri, 30 Aug 2013 03:12:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Jks3NfnacfFtTvk/X7oi4dUI3XSQDhhSFRdEeyyNLtM=; b=lh819jD8cs0WiAV9AciBAtDk4TEyV+6dmtGLZEjjBPnj6wkk0gJ6A8vBc6dG192zUJ ErrTnq2OFa2QgRrqgDGrDyIpQd1kllU4w4Fvb1POY8PT321rg/9KOC87PJf8H9SO3ZqM OelH+zlTIMmFNp8S1/awuHqFtUS6g1pjum+M3kyjYhu0y3cYH9d0rV3Kym/5jE4oDBjN VpDTzzUGiy53g3XUevXNUn0Et/x84np4r81ymW5Oz23CB31pFSoeYMf2BN1zGv0zxcz8 6OeJ40JfwtE3ODfKqPGDb7o+K61MqgfQHiuUKdc1zUM9G1ysNdpiiluC4vfaTvQzE1b6 ooaw==
MIME-Version: 1.0
X-Received: by 10.112.167.3 with SMTP id zk3mr7283668lbb.23.1377857531027; Fri, 30 Aug 2013 03:12:11 -0700 (PDT)
Received: by 10.114.68.135 with HTTP; Fri, 30 Aug 2013 03:12:10 -0700 (PDT)
Date: Fri, 30 Aug 2013 12:12:10 +0200
Message-ID: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.com>
From: Victor Pascual Avila <victor.pascual.avila@gmail.com>
To: pntaw@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [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: Fri, 30 Aug 2013 10:12:14 -0000

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