IETF Logo Mail Archive

Re: [rtcweb] ROAP Example Application

Ted Hardie <ted.ietf@gmail.com> Fri, 21 October 2011 19:02 UTC

Return-Path: <ted.ietf@gmail.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 78C5D21F8B10 for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 12:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.26
X-Spam-Level:
X-Spam-Status: No, score=-3.26 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 sbX3eYv7gmqd for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 12:02:00 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id DD4E321F8B0C for <rtcweb@ietf.org>; Fri, 21 Oct 2011 12:01:59 -0700 (PDT)
Received: by yxj19 with SMTP id 19so4989536yxj.31 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 12:01:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+PI5+F8J8Dco6gqvc7YlYY8MY3LD/FItpmeVqJCtI8E=; b=IbTfaFbsgU3c5Az+K3XPR1bnipj/s0emE8zz6K1lVKVdcJh+G7127Ky4v96poPZEAd oVPbCMY6Z1AkG9yBWMxEBN8e1PGiMMXtdOrXUbdk5BOYB7QhHLW+3Xeqs3ZC9lzLO32z QpGyg8OSnAFcdpRoM2jGeHzw2cz8UHEk56uVg=
MIME-Version: 1.0
Received: by 10.236.168.2 with SMTP id j2mr23406533yhl.24.1319223719301; Fri, 21 Oct 2011 12:01:59 -0700 (PDT)
Received: by 10.236.105.169 with HTTP; Fri, 21 Oct 2011 12:01:58 -0700 (PDT)
In-Reply-To: <ED6F9988-76B3-4A0A-B885-E805CD131476@skype.net>
References: <EED7DD83-EFDF-43B3-B9EE-7D28D057FA37@cisco.com> <ED6F9988-76B3-4A0A-B885-E805CD131476@skype.net>
Date: Fri, 21 Oct 2011 12:01:58 -0700
Message-ID: <CA+9kkMBOSvKfp27xbBmVhtdfmO5imQ-owXayA-6DCpsizEUJmA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Matthew Kaufman <matthew.kaufman@skype.net>
Content-Type: multipart/alternative; boundary="20cf305b121e2b120304afd3b5e1"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] ROAP Example Application
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: Fri, 21 Oct 2011 19:02:00 -0000

On Fri, Oct 21, 2011 at 10:37 AM, Matthew Kaufman <matthew.kaufman@skype.net
> wrote:

> Thought experiment:
>
> If one had a connection object that supported an underlying protocol that
> could send one or more encrypted flows of both real-time media and reliable
> data, what information would you need to exchange between the two browser
> endpoints in order to ensure that any pair of browsers with any future audio
> or video codec could use the best mutually-supported codecs?
>
>
I think I am missing your point slightly.  Do you mean the connection object
talks to an abstraction layer that manages how the flows are sent, and the
swapping occurs in what it manages, or do you mean the connection object
should be able to swap out whether it is talking to ICE, DTLS-SRTP, or
TCP-over-UDP transparently?  or something else?

regards,

Ted

v2.23.0 | Report a Bug | By Email