Re: [rtcweb] RTP usage: requirement levels

Martin Thomson <martin.thomson@gmail.com> Mon, 16 July 2012 22:22 UTC

Return-Path: <martin.thomson@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 3B3E711E82F3 for <rtcweb@ietfa.amsl.com>; Mon, 16 Jul 2012 15:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.744
X-Spam-Level:
X-Spam-Status: No, score=-3.744 tagged_above=-999 required=5 tests=[AWL=-0.145, BAYES_00=-2.599, 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 fsYiJDPsE4Al for <rtcweb@ietfa.amsl.com>; Mon, 16 Jul 2012 15:22:55 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 43A7411E82BB for <rtcweb@ietf.org>; Mon, 16 Jul 2012 15:22:55 -0700 (PDT)
Received: by bkty7 with SMTP id y7so4705874bkt.31 for <rtcweb@ietf.org>; Mon, 16 Jul 2012 15:23:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0LCH5anlzjXrGph1XSGSavUzCeN3sojBbc6ddT2T8ts=; b=xC9N7/cuaDQOup0YrPm+KEUGrg1xKt7NvoNtk2rmqFNfTUDFvTf5o3lGVdmC2IxXBz 7fRyeifgQ5kCt683fisS4y2QINEpSMTOKfvJV7tP9AkIkI1YexE2766wC72+viq/a8qI cxzy7dgcWADAMTVvMkhnQVrT1kswbACAlqeSTnzaXc2GrV99Co2XSB/P7IOfRzDjh67n ObHOYmXvWrwIIxmKLBS6uSZZX13+KjxQMu+Ox5/9g/tOnZZ57AVCcGA1aDaq/EAyKgGD CnmnGzQAvkInYv5XLjgUPosGmW6BMRPfEkIWNKhQxaGiGB6kv8rI8nZsVgbnlxpWQKpo oivQ==
MIME-Version: 1.0
Received: by 10.205.123.134 with SMTP id gk6mr56764bkc.3.1342477420144; Mon, 16 Jul 2012 15:23:40 -0700 (PDT)
Received: by 10.204.66.17 with HTTP; Mon, 16 Jul 2012 15:23:40 -0700 (PDT)
In-Reply-To: <BLU169-W123C346AD7917D9B55DB9FE93D40@phx.gbl>
References: <CABkgnnXWeAKNwUv70Uusujz0k11iA7a7g7ZHME99Vbq3RKQj5Q@mail.gmail.com> <BLU169-W123C346AD7917D9B55DB9FE93D40@phx.gbl>
Date: Mon, 16 Jul 2012 15:23:40 -0700
Message-ID: <CABkgnnUvT8WG3p3X3pbkaEWdRrSjO--t4w0AaOb_NFB594XeWg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: text/plain; charset="UTF-8"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTP usage: requirement levels
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: Mon, 16 Jul 2012 22:22:56 -0000

On 16 July 2012 15:15, Bernard Aboba <bernard_aboba@hotmail.com> wrote:
> [BA] Overall, I think we need a cleaner understanding of the meaning of the
> term "signal" in this document.

Ah yes, that was an unfortunate choice of words.  To be absolutely
clear, I am talking about the nature of the information that is
required to pass between browser and javascript, not some sort of
signaling protocol.  SDP is a signaling protocol.

That said, if you need to use SDP, then you need to follow the rules
established by SDP.  That means that you might have to include some
things that are optional in SDP but not rtcweb, and you might feel
inclined to reject SDP that would be otherwise valid.