Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb

Ted Hardie <ted.ietf@gmail.com> Fri, 26 April 2013 05:55 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 3301821F9080 for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 22:55:22 -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=[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 yQa5IVf0vQHe for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 22:55:20 -0700 (PDT)
Received: from mail-ia0-x234.google.com (mail-ia0-x234.google.com [IPv6:2607:f8b0:4001:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id AEB4421F965E for <rtcweb@ietf.org>; Thu, 25 Apr 2013 22:55:20 -0700 (PDT)
Received: by mail-ia0-f180.google.com with SMTP id t4so2437114iag.11 for <rtcweb@ietf.org>; Thu, 25 Apr 2013 22:55:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=LceFlVMk7UMXUz1Q40GSX1Ihm9uT25M4v9u0jrmvMTk=; b=jpjFdzKDwHOO77goTsA/OAHzoCeTCURgdjF0+1nPIc8j+WKIV0MMiqKkxDb8H7txhD M3575nw/GFGobQ5tMVw/gAVBfQ3Rozn71q/1tt4LuStXOVJ+ASEcJ+S81d4fp9FDJVsq 2IR28IR0buBgjvdkLrsTh62eX/y19NB0Dp8ROyo7UZB+lWFaZgTfVgjDlWddntcCccST sy+KVnuCGDeNVo9nh8NTbScbETrTdG1up7+59CLQuH6y/gUpVcQ6yxEziBfxLzUHCriD 3RuvS9jrfhHrQaKuNeOR9lnsSY2Eu8F6C1NOExTVbbEUJREfgrZDPx6LgLniMXy29yaI jYCA==
MIME-Version: 1.0
X-Received: by 10.42.64.69 with SMTP id f5mr23390268ici.29.1366955720325; Thu, 25 Apr 2013 22:55:20 -0700 (PDT)
Received: by 10.42.211.16 with HTTP; Thu, 25 Apr 2013 22:55:20 -0700 (PDT)
In-Reply-To: <517A0237.9030008@matthew.at>
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca> <20130425202238.74EF321F96A5@ietfa.amsl.com> <AE1A6B5FD507DC4FB3C5166F3A05A48416281FDB@tk5ex14mbxc272.redmond.corp.microsoft.com> <5179BEEF.4000600@jesup.org> <517A0237.9030008@matthew.at>
Date: Thu, 25 Apr 2013 22:55:20 -0700
Message-ID: <CA+9kkMAd6LxPTsA+3LfXFkoZQN-D4pwsAG9Oa9axiFt-QPOSOw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Matthew Kaufman <matthew@matthew.at>
Content-Type: multipart/alternative; boundary="90e6ba5bca8f224ad304db3d2e9f"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
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, 26 Apr 2013 05:55:22 -0000

On Thu, Apr 25, 2013 at 9:27 PM, Matthew Kaufman <matthew@matthew.at> wrote:

> O
>
>> Yes, some gateway scenarios might be cheaper/easier with SDES, but I see
>> the primary use-cases for WebRTC to be browser-to-browser, not
>> browser-legacy.
>>
>
> Just because the charter was mistakenly written that way doesn't mean it
> is true.
>

I remind you that the actual title of the group is:

"Real-Time Communication in WEB-browsers (rtcweb)".  While you may disagree
with the charter, please remember that it's not fundamentally a prediction
about what the eventual balance of flows will be.  It's a statement about
where the balance of effort in the group should go.   To me as an
individual, it implies that we should not make trade-offs that optimize a
non-browser use case at the expense of the browser use case except in
pretty extraordinary circumstances.

regards,

Ted Hardie