Re: [rtcweb] Making progress on the signaling discussion (NB: Action items enclosed!)

Neil Stratford <neils@belltower.co.uk> Wed, 12 October 2011 12:45 UTC

Return-Path: <neils@vipadia.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 D232F21F8C4C for <rtcweb@ietfa.amsl.com>; Wed, 12 Oct 2011 05:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.926
X-Spam-Level:
X-Spam-Status: No, score=-2.926 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 Hnl814ymsrZm for <rtcweb@ietfa.amsl.com>; Wed, 12 Oct 2011 05:45:07 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id EBFE721F8CBD for <rtcweb@ietf.org>; Wed, 12 Oct 2011 05:45:06 -0700 (PDT)
Received: by iaby26 with SMTP id y26so930953iab.31 for <rtcweb@ietf.org>; Wed, 12 Oct 2011 05:45:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.24.96 with SMTP id u32mr12223035ibb.61.1318422172235; Wed, 12 Oct 2011 05:22:52 -0700 (PDT)
Sender: neils@vipadia.com
Received: by 10.231.200.146 with HTTP; Wed, 12 Oct 2011 05:22:52 -0700 (PDT)
In-Reply-To: <13C2526B-E7B1-408C-BD1D-EC5E8C8F6472@phonefromhere.com>
References: <CA+9kkMBi9BzDu=WOq3RG-o5nbfnUTftDg3LRBU3DFh=Kc4W5ZQ@mail.gmail.com> <CALiegfmYgQ+yb=pDp1J2_PVa1SkxTOuaUCM02Vt6-iGabwif1g@mail.gmail.com> <CA+9kkMCUTiPO3eASjn0mbRA9YCF6TMmGGOjQ4NkVkvzVMN39Gg@mail.gmail.com> <CALiegfnx=qoS_pqyC45WVEYEFqj-3eP9g_kyhAUaOO6He_UEfw@mail.gmail.com> <CA+9kkMCibnPLrEq1234bUMXpiKBK0+22mqwYOM__CpcO2nOayg@mail.gmail.com> <CALiegfms2bt-WPtMeosFQz3-aSf2L6mfX+i68tw45sSgix561Q@mail.gmail.com> <4E8D6507.8000707@ericsson.com> <CALiegf=VyViX2arp0gr0dK4WN_jv=bjwP0LUAxRf=quTxrYrUQ@mail.gmail.com> <CALiegfn15szv-2yXeWptWjsQC2CwVODg_X90gD4odZkCR0LzvA@mail.gmail.com> <4E955775.10206@alvestrand.no> <CABRok6n6UA_nFfLzQ4K+H0+idspEsymW29OZH0J5q1ewF3PpRw@mail.gmail.com> <4E956526.2090604@alvestrand.no> <380E325E-A7EF-489A-AA24-0270224FC87A@phonefromhere.com> <4E957C55.9020706@alvestrand.no> <13C2526B-E7B1-408C-BD1D-EC5E8C8F6472@phonefromhere.com>
Date: Wed, 12 Oct 2011 13:22:52 +0100
X-Google-Sender-Auth: imeJ_Ig8xUKe63RRG5eIFkm47HM
Message-ID: <CABRok6nXLV2RMeVMi-aNRBZecaqMSM=HXjhXefXPJmYNnh2XwQ@mail.gmail.com>
From: Neil Stratford <neils@belltower.co.uk>
To: Tim Panton <tim@phonefromhere.com>
Content-Type: multipart/alternative; boundary=0015177414283d782704af1915aa
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Making progress on the signaling discussion (NB: Action items enclosed!)
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, 12 Oct 2011 12:45:08 -0000

On Wed, Oct 12, 2011 at 1:13 PM, Tim Panton <tim@phonefromhere.com>; wrote:

>
> So, to paraphrase (and make sure I understand) - your argument is that if
> we don't use SDP,
> we will have to specify all the fields and associated meanings for every
> codec we expect to support.
>
> If we do use SDP, then we just point at existing usage and say - 'there,
> use that' .
>
> If we use a subset or variant on SDP we can say - 'use that, except for
> this bit to do with port allocation'.
>
> Is that a fair (if informal) summary?
>

It's interesting to look at how XMPP/Jingle addressed this concern in
XEP-0167:
http://xmpp.org/extensions/xep-0167.html#sdp

The SDP definitions are mapped to name/value pairs where possible according
to defined rules.

Neil