Re: [MMUSIC] Updated MSID draft

Harald Alvestrand <harald@alvestrand.no> Sun, 04 May 2014 19:26 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 9DA891A01BE for <mmusic@ietfa.amsl.com>; Sun, 4 May 2014 12:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 EuFz5nki-Ycm for <mmusic@ietfa.amsl.com>; Sun, 4 May 2014 12:26:49 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id D81DA1A01A0 for <mmusic@ietf.org>; Sun, 4 May 2014 12:26:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 9D31E7C5245; Sun, 4 May 2014 21:26:31 +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 1CzjDbf2AWx1; Sun, 4 May 2014 21:26:30 +0200 (CEST)
Received: from [192.168.1.186] (unknown [188.113.88.47]) by mork.alvestrand.no (Postfix) with ESMTPSA id 4895C7C519B; Sun, 4 May 2014 21:26:30 +0200 (CEST)
Message-ID: <53669466.4020309@alvestrand.no>
Date: Sun, 04 May 2014 21:26:30 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
References: <531875E3.9000605@alvestrand.no> <53187758.1080403@cisco.com> <5364566D.5010601@cisco.com>
In-Reply-To: <5364566D.5010601@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qRWjmjfU-rN6W3hRAoVtGXFWltQ
Subject: Re: [MMUSIC] Updated MSID draft
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, 04 May 2014 19:26:53 -0000

On 05/03/2014 04:37 AM, Flemming Andreasen wrote:
> Hi Harald
>
> I have taken a closer look at msid-05 and have a number of comments. I
> will list the major ones and/or what might require list discussion
> here and send you a bunch of more detailed ones in an annotated
> version off-line:
>
> 1) There are some grammar inconsistencies between the way you use
> token and (some) of the text you have. In general, it seems the length
> should be limited and the set of characters you want to allow are less
> than what token allows for.
>
> 2) Offer/Answer procedures are lacking. We need to have an O/A section
> with subsections as per RFC 3264 (for unicast) to better specify the
> overall behavior here (Generating the Initial Offer, Generating the
> Answer, Offerer Processing of the Answer, Modifying the Session)

Hm. But MSID isn't an offer/answer field. It's an unilateral
declaration, and refers to no information coming from the other side.

Does it make sense to follow the offer/answer section format when the
answer doesn't depend on the offer?

>
> 3) There is some ambiguity as to what constitues an msid value and
> more specifically when it includes both the MediaStream identifier and
> the MediaStreamTrack and when (if ?) it doesn't.

Hm. Must make this clearer. The generic format has MST-identifier
optional, and the WMF usage has MST-identifier mandatory.

>
> 4) Unified-plan is being referenced in a normative manner (but is
> listed as an informative reference). Since unified-plan is not
> expected to go to RFC, having a normative reference to it is problematic.

Have to move this pointer to JSEP. I think JSEP has the necessary
targets now.

>
> Thanks
>
> -- Flemming
>
>
>
> On 3/6/14, 8:25 AM, Flemming Andreasen wrote:
>> I think the draft needs a bit more work in a few places (largely
>> editorial and more text on some of the procedures). I'll sign up to
>> do a pre-WGLC individual review to get you some more tangible and
>> constructive feedback on that.
>>
>> Thanks
>>
>> -- Flemming
>>
>>
>> On 3/6/14, 8:19 AM, Harald Alvestrand wrote:
>>> I have uploaded an updated msid draft, without the msid-control:
>>> section.
>>>
>>> As I said in the WG meeting, I think this is now uncontroversial, and
>>> should be ready for WG Last Call.
>>>
>>> I request that the WG chairs consider whether they agree with this
>>> opinion.
>>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>


-- 
Surveillance is pervasive. Go Dark.