Re: [MMUSIC] Remove msid-semantic

Harald Alvestrand <harald@alvestrand.no> Sun, 29 March 2015 07:34 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 090C81AC399 for <mmusic@ietfa.amsl.com>; Sun, 29 Mar 2015 00:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level:
X-Spam-Status: No, score=-1.51 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzt8OEW6QUU6 for <mmusic@ietfa.amsl.com>; Sun, 29 Mar 2015 00:34:03 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 721221ABD3F for <mmusic@ietf.org>; Sun, 29 Mar 2015 00:34:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 240147C3A1A; Sun, 29 Mar 2015 09:34:01 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aT3HoIDWXOnU; Sun, 29 Mar 2015 09:34:00 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:b9dd:fde3:9372:4948] (unknown [IPv6:2001:470:de0a:27:b9dd:fde3:9372:4948]) by mork.alvestrand.no (Postfix) with ESMTPSA id CA0C27C394E; Sun, 29 Mar 2015 09:33:59 +0200 (CEST)
Message-ID: <5517AAE4.5070800@alvestrand.no>
Date: Sun, 29 Mar 2015 09:33:56 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>, mmusic@ietf.org
References: <CABkgnnX0xS_y-2O5kn=pfH-=VsRq=sxYdXikyvc2iQTca-G_hw@mail.gmail.com>
In-Reply-To: <CABkgnnX0xS_y-2O5kn=pfH-=VsRq=sxYdXikyvc2iQTca-G_hw@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/EpIaf1WUJJdv--IB1keH2V7Dwxo>
Subject: Re: [MMUSIC] Remove msid-semantic
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Mar 2015 07:34:09 -0000

On 03/27/2015 05:45 PM, Martin Thomson wrote:
>
> As we discussed in the meeting, I propose that we remove msid-semantic
> entirely. In a brief discussion after the meeting we couldn't identify
> a single case where it is needed.
>
> Apparently, it serves to indicate the potential for use of msid prior
> to having media to send.
>

As I said at the mike, the case where it's needed is described in
section 5.1 of the draft.
It's not very long, so I'll reproduce it below. (I got the section
number wrong at the mike...)


> Obviously, that isn't a good substitute for careful analysis, but
> unless someone wants to restore this rather vaguely specified
> capability, I'd rather have a simpler spec and implementation now and
> remove it.
>
> Can anyone actually make a case for keeping it?
>

5.1.  Handling of non-signalled tracks

   Entities that do not use the WMS semantic will not send "msid-
   semantic:WMS".  This means that there will be some incoming RTP
   packets that the recipient has no predefined MediaStream id value
   for.

   Note that this handling is triggered by incoming RTP packets, not by
   SDP negotiation.

   Handling will depend on whether or not the msid-semantic:WMS
   attribute is present.  There are two cases:

   o  No "msid-semantic:WMS" attribute is present.  The SDP session is
      assumed to be a backwards-compatible session.  All incoming media,
      on all m-lines that are part of the SDP session, are assumed to
      belong to tracks of the same media stream (the "default media
      stream").  The identifier of this media stream and of the media
      stream track is a randomly generated string; the WebIDL "label"
      attribute of this media stream will be set to "Non-WMS stream".

   o  An "msid-semantic:WMS" attribute is present.  In this case, the
      sender implements the WMS semantic, and the packets are either
      caused by a bug or by timing skew between the arrival of the media
      packets and the SDP description.  These packets MAY be discarded,
      or they MAY be buffered for a while in order to allow immediate
      startup of the media stream when the SDP description is updated.
      The arrival of media packets MUST NOT cause a new MediaStreamTrack
      to be signaled.

   If an entity wishing to use the WMS semantic sends a description, it
   MUST include the msid-semantic:WMS attribute, even if no media
   streams are sent.  This allows us to distinguish between the case of
   no media streams at the moment and the case of SDP generated by an
   entity that wishes to use the backwards-compatible mechanism.

I see three possible outcomes of the discussion:

- We don't need this ability; we can rewrite the cases above in a way
that is deterministic without being able to tell whether the sender
intends to send msid-semantic or not.

- We need this ability, but can do it without msid-semantic:

- We need this ability, and should keep msid-semantic.

Please discuss.