Re: [rtcweb] HTTP Fallback draft

Justin Uberti <juberti@google.com> Wed, 08 August 2012 03:23 UTC

Return-Path: <juberti@google.com>
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 C2F2611E80EA for <rtcweb@ietfa.amsl.com>; Tue, 7 Aug 2012 20:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.737
X-Spam-Level:
X-Spam-Status: No, score=-102.737 tagged_above=-999 required=5 tests=[AWL=0.239, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 5FApmmPCLHSz for <rtcweb@ietfa.amsl.com>; Tue, 7 Aug 2012 20:23:36 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 61A4511E8087 for <rtcweb@ietf.org>; Tue, 7 Aug 2012 20:23:36 -0700 (PDT)
Received: by qadz3 with SMTP id z3so2153286qad.10 for <rtcweb@ietf.org>; Tue, 07 Aug 2012 20:23:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=g3F19/v7uGw2pIEhHQf9FzNYyI1FL3cAPv+5EOVVH8Q=; b=T+V/MW7aw1hcjavXaF19BfeL6Y2poqMnrWMde3IAgTWheUQZDlfp3iAnRmskJLU7+u TILX1QPn82jbV70jcZapVVNlfKghjXIC2wBCXAp1m9nS3PKB01+HOwm9HjEf/25vpE+a 3p/QFaU/F653EYuKjDy6ZXA1iLU15tcPEeUnBMM/b5/qSjn9yvBl0clnv5M87uigWanl t/smRlZVujgtLDvquBCnhr/gAQd8gdihJfrAPIXNfpNl+ZhGIrvX0fEcUQUeNuE8uZGP kPF0cfzKNHnswNgd062c+S2gvTWmxPvDA0b3muL+KaESnI0MdJROdWps0ggq6YOC+039 0mTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=g3F19/v7uGw2pIEhHQf9FzNYyI1FL3cAPv+5EOVVH8Q=; b=FESWWYDJt+3C8m1yrAHtsCJPdSDoOKZMvD/ujmtBTnOcfs1iuE6uFVgIgUubHFCQSr EVmTqTTrj3ppe1QbnA4MrLkCeWhEO2aIWS0GPhOEMJ7vMMht7OaT3nAtVyWbVX6PlQsz lT7rlwwpRfjink5JEyi7+DMcPQ0RRfE/IE0Udf0f0v1PDhCBOPlU2pFOj92Nr8FsGXN+ a3NSPeIhX4/L/bWE/Un3F6r+rtQG9cPo+akslvQ4TFHpZ9f06g1iD3Rp+U10EPMPJhdO 6VCkRluFJ7LFZy0erltvf6TTc1k1QxerUIVmFmiTjLWYI5MyyoOIkhnRzH9o5+rFjp6J BbgQ==
Received: by 10.224.188.12 with SMTP id cy12mr27631345qab.68.1344396215916; Tue, 07 Aug 2012 20:23:35 -0700 (PDT)
Received: by 10.224.188.12 with SMTP id cy12mr27631337qab.68.1344396215812; Tue, 07 Aug 2012 20:23:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.218.80 with HTTP; Tue, 7 Aug 2012 20:23:15 -0700 (PDT)
In-Reply-To: <20120807205447.2212f617@rainpc>
References: <20120807180156.286e74d2@rainpc> <CA+9kkMDpnH12jkZ3DQD8uT4PF0Q7TW1f9NiGO=pSP1xLfRRiRg@mail.gmail.com> <20120807205447.2212f617@rainpc>
From: Justin Uberti <juberti@google.com>
Date: Tue, 7 Aug 2012 20:23:15 -0700
Message-ID: <CAOJ7v-3hg+kg+bXyZAS=0s68R5BFH4zJnRzHSY3Sv489-EgiPA@mail.gmail.com>
To: Lorenzo Miniero <lorenzo@meetecho.com>
Content-Type: multipart/alternative; boundary=20cf30363ebbe181b104c6b8a2b4
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQkZQ2tMS/wfj0EhgRDXATSGNcTC8b0X0+ik9zfv7gQpTzo4Vd/DG44aOF2SwIBSzqwq/49lZJ6pKJAaWgbnSXnP+g98i8sPhpZlkr8xXOuKZQESN2/IhOsY7xlfdDcbNI6Z26x2TM+M76DgHj3s1sQmr7gWLOCf/nJKadxNac8CXlURoMo4JjS5Y/bakSvoBC4BnWW2
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] HTTP Fallback draft
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: Wed, 08 Aug 2012 03:23:38 -0000

My perspective is that we can make a huge impact simply by codifying the
rules for doing basic things like TURN over 443 (with or without TLS), HTTP
CONNECT, etc. Running RTP over HTTP could help us get closer to 100%
coverage, but I think we start to enter the area of diminishing returns.

As such, I'd like to see us work towards a best practices document for
establishing sessions in these restricted environments; I think such a
document would be in scope for RTCWEB.


On Tue, Aug 7, 2012 at 11:54 AM, Lorenzo Miniero <lorenzo@meetecho.com>wrote;wrote:

> Hello Ted,
>
>
> On Tue, 7 Aug 2012 10:50:07 -0700
> Ted Hardie <ted.ietf@gmail.com> wrote:
>
> > On Tue, Aug 7, 2012 at 9:01 AM, Lorenzo Miniero <lorenzo@meetecho.com>
> wrote:
> > > That said, I guess there's a different question I should be asking to
> > > the chairs: since there seems to be no related item in the milestones,
> > > is such a work actually in line with what is the expected outcome of
> the
> > > WG? Considering the draft basically addresses a new transport for RTP
> > > and something that probably needs to be negotiated as well, I guess
> this
> > > could be seen as belonging elsewhere (AVTCORE and/or MMUSIC?).
> > > Nevertheless, my feeling is it belongs more here than somewhere else,
> > > especially considering we're specifying a solution that will be
> deployed
> > > in browsers and, as such, people will expect it to work wherever other
> > > web applications do.
> >
> > My take on this is that the actual work on developing the alternate
> > transport for RTP would have to occur elsewhere and, frankly, I think
> > it is a large enough task that it would likely require its own working
> > group (much as the RTP congestion control topic ended up as a BoF and
> > hopefully will become its own working group).  That doesn't mean that
> > the work couldn't be informed by the RTCWEB use cases, but I think it
> > would have to be done elsewhere.
> >
> > I'd personally suggest starting with a discussion with the ADs on
> > whether a BoF on this topic would be something they might consider.
> > (Note, however, that I have not talked to Cullen about this and Magnus
> > is on vacation, so this is not a "Chairs' response"; just my own
> > thoughts).
> >
>
>
> This makes sense. I'm a bit concerned about the additional time that may
> be needed by going through the process of forming a new WG (compared to
> just adding a milestone to an existing WG, that is), as the final result
> may end up being available much after the original WG completed its works,
> but I see your point.
>
> I'll wait for more feedback about this and, if enough people seem
> interested about doing something like this, contacting the ADs and consider
> the next steps may be a good idea.
>
> Lorenzo
>
>
> > regards,
> >
> > Ted Hardie
>
>
> --
> Lorenzo Miniero, COB
>
> Meetecho s.r.l.
> Web Conferencing and Collaboration Tools
> http://www.meetecho.com
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>