IETF Logo Mail Archive

Re: [MMUSIC] Remove msid-semantic

Martin Thomson <martin.thomson@gmail.com> Tue, 31 March 2015 16:33 UTC

Return-Path: <martin.thomson@gmail.com>
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 097D71A009C for <mmusic@ietfa.amsl.com>; Tue, 31 Mar 2015 09:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 x1nNW3_LDsVc for <mmusic@ietfa.amsl.com>; Tue, 31 Mar 2015 09:33:09 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 269451A00BF for <mmusic@ietf.org>; Tue, 31 Mar 2015 09:33:09 -0700 (PDT)
Received: by obbgh1 with SMTP id gh1so33393143obb.1 for <mmusic@ietf.org>; Tue, 31 Mar 2015 09:33:08 -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=gVeZZrX9FmoIkghWiHk0wnPzyQ/LcViDDjFTj/vhrQI=; b=aD66KDr7aRC0KqsQ+As6kPqUqze7kPE2q8IwCMPyN826PJ1+9a52Shrl8Ykwsh0/aY UQm8c7p8F/WYqJoXYOUllLg1iIAZnlRXcDDxFopFrybjRJm2J8Prt5PQCTicvKvGp+O+ wfieuLpPlsDYhnB3us/FqV6UjguTJa1mTQyCnji3/zA4zhhJqJr+TweWx23oyfxipKtj srdi35jgEaN4O6DbUkG17tatN95S6SNHL5i02zPTXsp9eFdFhTJOQL5M4KZp5Uc5Stbb a1qucWOPPuSQ14LMfkTvaezngdPb8V3P9k+MPBSJmLHg9zfEUwIel4DUI61IU/k2ADv/ lZMQ==
MIME-Version: 1.0
X-Received: by 10.182.128.199 with SMTP id nq7mr34622319obb.47.1427819574537; Tue, 31 Mar 2015 09:32:54 -0700 (PDT)
Received: by 10.202.48.151 with HTTP; Tue, 31 Mar 2015 09:32:54 -0700 (PDT)
In-Reply-To: <551A63D2.1030006@ericsson.com>
References: <CABkgnnX0xS_y-2O5kn=pfH-=VsRq=sxYdXikyvc2iQTca-G_hw@mail.gmail.com> <5517AAE4.5070800@alvestrand.no> <CABkgnnVtNrBFjQtNNEUne3RfRFbjXDeGxzXYB3CtDwZfo3=8Gw@mail.gmail.com> <551A63D2.1030006@ericsson.com>
Date: Tue, 31 Mar 2015 09:32:54 -0700
Message-ID: <CABkgnnXHBTUtWjSEKY6_Dhcq9mCLZsUtoNLo2qnBy_HVrVi47w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/RezS50Tk_2t193BSV1q1gF-DjA8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
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: Tue, 31 Mar 2015 16:33:12 -0000

On 31 March 2015 at 02:07, Magnus Westerlund
<magnus.westerlund@ericsson.com> wrote:
> Just to be clear here and ensure that I haven't missed anything. RTP
> usage requires all WebRTC endpoint to provide synchronization
> information when sending. However, it is up to the receiver to decide if
> they want to synchronize the playout. Thus this LS group would only be
> there to indicate a strong preference by the sender that the receiver
> should/shall playout in synchronization?


Correct, the information in RTP will make it possible to synchronize
tracks, but whether that is acted upon will ultimately depend on
whether the tracks are rendered in the same stream.  I think that the
intent with the LS groups is to make this clear, not just to a WebRTC
receiver, but to legacy receivers as well.

v2.23.0 | Report a Bug | By Email