[rtcweb] JSEP-04: Nits and niggles

Harald Alvestrand <harald@alvestrand.no> Thu, 19 September 2013 12:53 UTC

Return-Path: <harald@alvestrand.no>
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 7304521F9385 for <rtcweb@ietfa.amsl.com>; Thu, 19 Sep 2013 05:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.239
X-Spam-Level:
X-Spam-Status: No, score=-110.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_HI=-8, 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 cBeghT+Qr8tF for <rtcweb@ietfa.amsl.com>; Thu, 19 Sep 2013 05:53:41 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id CE73821F9396 for <rtcweb@ietf.org>; Thu, 19 Sep 2013 05:53:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 0201E39E1B7 for <rtcweb@ietf.org>; Thu, 19 Sep 2013 14:53:33 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DzwSOrRW7kh for <rtcweb@ietf.org>; Thu, 19 Sep 2013 14:53:32 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:903a:6934:230b:9fc1] (unknown [IPv6:2001:470:de0a:27:903a:6934:230b:9fc1]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 6324939E04F for <rtcweb@ietf.org>; Thu, 19 Sep 2013 14:53:32 +0200 (CEST)
Message-ID: <523AF421.7000807@alvestrand.no>
Date: Thu, 19 Sep 2013 14:54:57 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [rtcweb] JSEP-04: Nits and niggles
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: Thu, 19 Sep 2013 12:53:46 -0000

I'm sure we'll have lots of things to discuss about JSEP. I just thought 
I'd get these out of the way.

- Usage of MSID. In addition to the a=msid: lines, the session-level 
generation procedure needs to say that a line "a=msid-semantic:WMS <id>" 
is added to the session-level description, containing the IDs of the 
MediaStreams that are signalled.

- a=ssrc lines. The spec (5.2.1 second list last bullet) simply says "an 
a=ssrc line". But RFC 5576 specifies that all ssrc lines contain an 
attribute. Suggestion: define one that does no harm (role=primary?)

- recycling of m= lines. The section in 5.2.2 (subsequent offers) that 
talks about this doesn't mention that the media in the m-line has to 
match, although section 5.3.1 (initial answer) actually talks about it. 
I'm assuming that's an oversight.

I'd suggest pulling the language about "selecting an appropriate m-line 
for a track" out in a separate subsection, so that we have one place to 
point to for this.

Out of time, let's get these ones out of the way for -05....