Re: [rtcweb] My SDP doesn't interoperate

Justin Uberti <juberti@google.com> Wed, 01 May 2013 15:44 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 2763121F9A51 for <rtcweb@ietfa.amsl.com>; Wed, 1 May 2013 08:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[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 55K1cao2hidU for <rtcweb@ietfa.amsl.com>; Wed, 1 May 2013 08:44:17 -0700 (PDT)
Received: from mail-qe0-f44.google.com (mail-qe0-f44.google.com [209.85.128.44]) by ietfa.amsl.com (Postfix) with ESMTP id A440E21F9A47 for <rtcweb@ietf.org>; Wed, 1 May 2013 08:44:06 -0700 (PDT)
Received: by mail-qe0-f44.google.com with SMTP id w7so958605qeb.17 for <rtcweb@ietf.org>; Wed, 01 May 2013 08:44:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=l/LcIgin8M74otkfbwEWxRaimtNGGpI2ZV+ZZb7OayQ=; b=cJYufE3D5MduMVZGxvcMPzwOkk2hy7KS5Ynon5+WYNXPDVljT99JGdzwb+VQN4LPPv Z02SffS9lV4TXYo5yYt5iiGaWxAo406ZmXRnMvKoJYr9PobAdahw2qmj4Sy93A/TLt// oXBDWmiom7pRF37LM0AEhquW6vPg4mFPh9RFUK9KPGhyzH78xr3X8TFdNZjuDcvBAhmX 8eHg4me7wwd3gGS9TlO7aynl3eSm8YBdulrwMh2lEZ+Ocx+HKpQnNDMpoGDYehM2I4X/ qAqwj/YJh7fi77gfXw59YnN3PienD4T4zAPPK0e10Zk0cuio5GH+8XFNrweuiRky3iJV 1J1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=l/LcIgin8M74otkfbwEWxRaimtNGGpI2ZV+ZZb7OayQ=; b=Nz4USVRZdCRFgt8f6z/x+mMIezByxhXaC0TnBQir8zPomyFTukgfABePRoEJTanhCz HAtFXQw2OEpBDrIkupw0GwBMZSV8IiJ4PiM8SK8Ch7Ho1OsQcq7SuPUMBe60N+tmqCFG 15AFtI4v6ZAConGOsKR+6LTHp47e1XGx9XMw6n6aJAoAWXAYOeKbvqtfhqgOpeKC50Of DRn2QGxrrUS/dZORgUCH/eh+h9PgGQpjCRxOWqgMigfq8+uafz6yRBVlfFUuv0qCyrLy DHIyw5/qVh5JfZrtbBNmJZEoOGnOJ1hPS1P/f4NE5gUbB3F3wntQtwiajlWm8x/zyh7k mUCA==
X-Received: by 10.49.35.72 with SMTP id f8mr3992113qej.4.1367423045840; Wed, 01 May 2013 08:44:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.93.28 with HTTP; Wed, 1 May 2013 08:43:44 -0700 (PDT)
In-Reply-To: <CABkgnnUbWHU79Co2+UDq5Pptburpmy8ajVsJiSXvO8ig0yzaUQ@mail.gmail.com>
References: <CABkgnnUbWHU79Co2+UDq5Pptburpmy8ajVsJiSXvO8ig0yzaUQ@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 01 May 2013 08:43:44 -0700
Message-ID: <CAOJ7v-1RpDCS_f8nRCYP1Aah_pAzrHzN8_GbZ8+XAkyhkOGi_g@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b6776eae7fb7b04dba9fc6b"
X-Gm-Message-State: ALoCoQncb5FnC6KBWAuuXFu4ibra0qWspO08fIj92ajYKa7lisOf0F+J3AwelSCCB0KhbJl4y5KVpyB8a/BMWoeS5emp4UXW+8jbVXSRfmzfNaR3ax1hvwhqqNItGbOX38IagWfkygiGPnbIyqxGutsXPtHesq7CJmeGTVYJPnmfgcLtPRWUwOG46iHKu+/4QEmDPsLTmqGf
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] My SDP doesn't interoperate
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, 01 May 2013 15:44:21 -0000

The one SDP issue mentioned in that document has been fixed; that document
is now outdated by events.

Regarding the "100 lines", that code promoted Opus to be the preferred
codec, as well as disabling CN. This munging is also no longer needed; we
have now added support for the VoiceActivityDetection constraint to control
use of CN.


On Fri, Apr 26, 2013 at 12:00 PM, Martin Thomson
<martin.thomson@gmail.com>wrote:

> (was Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb)
>
> On 26 April 2013 11:07, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
> >
> > On Apr 26, 2013, at 7:47 AM, Tim Panton <tim@phonefromhere.com> wrote:
> >
> >> 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.
> >
> > Could you just summarize what the 100 lines do and which theses would be
> needed for browsers that implemented the drat standards? I'm trying to dig
> into what we need to fix.
>
> http://www.webrtc.org/interop
>
> That's probably out of date, but you get the idea.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>