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

Iñaki Baz Castillo <ibc@aliax.net> Fri, 26 April 2013 14:02 UTC

Return-Path: <ibc@aliax.net>
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 D622521F9975 for <rtcweb@ietfa.amsl.com>; Fri, 26 Apr 2013 07:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.426
X-Spam-Level:
X-Spam-Status: No, score=-2.426 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 BEJIxhGKNkZy for <rtcweb@ietfa.amsl.com>; Fri, 26 Apr 2013 07:02:18 -0700 (PDT)
Received: from mail-qe0-f53.google.com (mail-qe0-f53.google.com [209.85.128.53]) by ietfa.amsl.com (Postfix) with ESMTP id 5104221F9955 for <rtcweb@ietf.org>; Fri, 26 Apr 2013 07:02:18 -0700 (PDT)
Received: by mail-qe0-f53.google.com with SMTP id i11so2792208qej.12 for <rtcweb@ietf.org>; Fri, 26 Apr 2013 07:02:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=0uaD/1IIJiDFDH0oaxYWjrzQhW4walXTGSLNusv0OCc=; b=dRv7oOU5htdRiEH6J9i00RqaBp14FpbqQK6i861BYdp2MND/a7sC+N9uFsuVBT/JAn MJaPJkOHPZmB/7xu41W2y5mxDPYm4nGfPAdxZBh6K4MNOZN/6LimHO8zRbNoMiqM1WcK AiOwIQhO8e8q2my9b8F+kFKvwXqgMeTwU41wnVsU41oO1rZMTPJWAoC+Ajw0oaEGoffS Y/MI1yrK3l26llXFW5Glthbs+zi6lz7rXj5FXBLPXgAhvwlKwayKXIL1oGIn9c8Oe80e sHfHNNpsfEO7qr8q6275eipE9CpURM1FvqRVORZdxqsQJpytdEK3j3cWaQ9MK4V16w1h 5KTg==
MIME-Version: 1.0
X-Received: by 10.224.184.204 with SMTP id cl12mr40712545qab.0.1366984937440; Fri, 26 Apr 2013 07:02:17 -0700 (PDT)
Received: by 10.49.81.175 with HTTP; Fri, 26 Apr 2013 07:02:17 -0700 (PDT)
Received: by 10.49.81.175 with HTTP; Fri, 26 Apr 2013 07:02:17 -0700 (PDT)
In-Reply-To: <1BF967D4-2EEA-489D-977E-E5D711966753@phonefromhere.com>
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> <CA+9kkMAd6LxPTsA+3LfXFkoZQN-D4pwsAG9Oa9axiFt-QPOSOw@mail.gmail.com> <517A8248.4020604@matthew.at> <1BF967D4-2EEA-489D-977E-E5D711966753@phonefromhere.com>
Date: Fri, 26 Apr 2013 16:02:17 +0200
Message-ID: <CALiegfkk=AjzmDpB8iHMQJhjFTDyaNzWjey=YFh=oxZgrbmYSw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Tim Panton <tim@phonefromhere.com>
Content-Type: multipart/alternative; boundary="20cf302ef9d89c1c6f04db43fbf7"
X-Gm-Message-State: ALoCoQkw+DYgqvlpRj+cLHZZZeqP1qnl1fCBO9KeIos4LOsSjR7BQYAENFzHrQmqgJ4s05WwDh3I
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 14:02:18 -0000

> If anyone still thinks that SDP is just a blob not an API surface, take a
look at the 'reference implementation' of browser to browser interop.
>
https://code.google.com/p/webrtc-samples/source/browse/trunk/apprtc/index.html
>
> I count around 100 lines of javascript munging the SDP.

IMHO the WG should really consider the above mess due to the usage of SDP
as an API surface. It is just terrible.