Re: [pntaw] Real-time media over TCP

Ted Hardie <ted.ietf@gmail.com> Tue, 15 October 2013 00:08 UTC

Return-Path: <ted.ietf@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 2E80121E813D for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:08:45 -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=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 qVtx6pjpqYNH for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:08:44 -0700 (PDT)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id E8EB021E80E5 for <pntaw@ietf.org>; Mon, 14 Oct 2013 17:08:41 -0700 (PDT)
Received: by mail-ie0-f182.google.com with SMTP id as1so12240732iec.27 for <pntaw@ietf.org>; Mon, 14 Oct 2013 17:08:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oMHalfgPlIOc8+CSVsEKEdNAmJb5IveqoJGPXXk/ThA=; b=GpkWINpcZ2VGwQmIFutinuxE4lVi5HHBbGPIVC/rs+9ji1Z7KLc9zK3jrdoJ4gK8+a mFO+NGFXAyxXlxA0sFYnwDX7uKOELjDh1c5teHg6KiP5ydEQRxoOL8BboLujun/TXUjF wp4xUyBf5LQDD5BVcnCNVAfSd26Hy0ymDpPDK1lCQFdmokoLelsjxfMlDmYj+gSO1IcB iubU5eoQvyCxKRVAka1rboeCiibDxi050FstfIInN97QNnPp8vz7hp9QzBhwJZmsny6P oHA3jPfRsg8afWg4WeXlecdkRYUVR1sIXMZIoIHVq1TU5POcnaFYmtXJuN/rs8k9lCis 4xXA==
MIME-Version: 1.0
X-Received: by 10.50.120.10 with SMTP id ky10mr15222233igb.29.1381795721467; Mon, 14 Oct 2013 17:08:41 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Mon, 14 Oct 2013 17:08:41 -0700 (PDT)
In-Reply-To: <0AE4085A-CE50-4813-B03C-9A5FB86277BD@cisco.com>
References: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.com> <522590EE.7070508@alvestrand.no> <C632A223-A55A-47F4-B083-9BDC447DA959@cisco.com> <52262657.3080208@alvestrand.no> <A2C315DB-1882-4BD1-A8C0-E8AF7DEA48F4@cisco.com> <00ca01cec387$f881cae0$e98560a0$@co.in> <BLU406-EAS274696C3D9DFE505F96B8E393130@phx.gbl> <004201cec44f$381a47f0$a84ed7d0$@co.in> <52544E0E.5080405@viagenie.ca> <003b01cec511$27e1abe0$77a503a0$@co.in> <E44893DD4E290745BB608EB23FDDB7620A0D672F@008-AM1MPN1-042.mgdnok.nokia.com> <9E34D50A21D1D1489134B4D770CE039768081AC9@SZXEMA504-MBX.china.huawei.com> <004e01cec5df$cf8daaf0$6ea900d0$@co.in> <E44893DD4E290745BB608EB23FDDB7620A0E2DC6@008-AM1MPN1-043.mgdnok.nokia.com> <9F33F40F6F2CD847824537F3C4E37DDF17BEFB3E@MCHP04MSX.global-ad.net> <BLU402-EAS357ECBFC621A567B9D3A7B4931A0@phx.gbl> <525C148F.8070502@gmail.com> <00d401cec90e$d688d5a0$839a80e0$@co.in> <E44893DD4E290745BB608EB23FDDB7620A0E7172@008-AM1MPN1-043.mgdnok.nokia.com> <525C655B.6020802@alum.mit.edu> <0AE4085A-CE50-4813-B03C-9A5FB86277BD@cisco.com>
Date: Mon, 14 Oct 2013 17:08:41 -0700
Message-ID: <CA+9kkMDofv4+nhAWhxVBT6dFy55uyCVCx=EEsatWiU=WvAhKKA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: multipart/alternative; boundary=047d7ba98232215de304e8bc6352
Cc: pntaw@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
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: Tue, 15 Oct 2013 00:08:45 -0000

On Mon, Oct 14, 2013 at 5:04 PM, Dan Wing <dwing@cisco.com>; wrote:

>
> On Oct 14, 2013, at 2:42 PM, Paul Kyzivat <pkyzivat@alum.mit.edu>; wrote:
>
> > But in practice I suppose the relay will be conveniently located
> relative to one of the two endpoints.
>
> I think that is a separate problem.  Smart ICE candidate prioritization
> would choose the "best candidate" (for some value of "best candidate").
>  The ICE connectivity check round-trip time is an oft-cited example of a
> reasonable metric (although it doesn't measure bandwidth and packet loss is
> considered by some to mislead [but if a path is lossy it may indeed be a
> very undesirable path]).  Geolocation of the TURN IP address versus my own
> IP address could also influence ICE candidate prioritization or candidate
> selection.
>
> -d
>
>
Hi Dan,

I don't think I understand who is running a geolocation algorithm in this
scenario.  Can you elaborate?

regards,

Ted



>
> >
> >       Thanks,
> >       Paul
> >
> >> Markus
> >>
> >>> -----Original Message-----
> >>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> >>> Of ext Parthasarathi R
> >>> Sent: 14 October, 2013 21:55
> >>> To: pntaw@ietf.org
> >>> Subject: Re: [pntaw] Real-time media over TCP
> >>>
> >>> Hi all,
> >>>
> >>> My point is that the direct media connection has to be given priority
> over
> >>> TURN based mechanism. In case of ICE-TCP, there is a possibility for
> the
> >>> direction connection between two browsers involved in the WebRTC
> session
> >>> and should be given priority over TURN based mechanism. So, 6) TCP
> based
> >>> candidates (ICE-TCP) - MUST
> >>>
> >>> There is an assumption in the discussion that the incoming TCP traffic
> is not
> >>> allowed through firewall. In case it is the problem to be solved,
> RTCWeb
> >>> usecase and requirement has to be updated. I noticed in
> >>> draft-ietf-rtcweb-use-cases-and-requirements-12 (published today) that
> >>> there is no such requirement. I'll write the mail in RTCWeb WG to get
> the
> >>> clarity on the requirement in case the firewall forbidding incoming
> TCP traffic
> >>> is a matter of missing text in the requirement.
> >>>
> >>> Thanks
> >>> Partha
> >>>
> >> _______________________________________________
> >> pntaw mailing list
> >> pntaw@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pntaw
> >>
> >
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
>
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw
>