[MMUSIC] AD Evaluation of draft-ietf-mmusic-msid-13
"Ben Campbell" <ben@nostrum.com> Tue, 10 May 2016 15:23 UTC
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0083F12D736; Tue, 10 May 2016 08:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level:
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
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 8Dhb_fCuNFf6; Tue, 10 May 2016 08:23:46 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 69F7612D707; Tue, 10 May 2016 08:23:20 -0700 (PDT)
Received: from [10.10.1.2] ([162.216.46.177]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u4AFNIWe076833 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 10 May 2016 10:23:19 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [162.216.46.177] claimed to be [10.10.1.2]
From: Ben Campbell <ben@nostrum.com>
To: draft-ietf-mmusic-msid.all@ietf.org, mmusic WG <mmusic@ietf.org>
Date: Tue, 10 May 2016 11:23:18 -0400
Message-ID: <972D269C-639E-4EC5-B836-BF42DAFD3785@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/KejxusGmZxF6IcEyKmlftpQqosw>
Subject: [MMUSIC] AD Evaluation of draft-ietf-mmusic-msid-13
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 10 May 2016 15:23:48 -0000
Hi,
This is my AD evaluation of draft-ietf-mmusic-msid-13. None of my
comments need block the IETF last call; we can resolve things in
parallel. I will start the last call shortly.
Thanks!
Ben.
----------
- General: There are a number of terms that are used without (or before)
definition. A terminology section might be helpful. (Most of these
should be known to a student of the art, but I think some definitions
would make this more accessible to those new to the subject.) Examples:
Binding, group, the various WebRTC API objects...
- 1.2, 2nd paragraph:
"SDP gives a description based on media descriptions."
That's sort of a circular definition. A one sentence definition of
"media description" would be helpful.
s/mulitple/multiple
- 1.3, first paragraph: "This complication is ignored below."
Ignored by the draft in general? Or just the section below?
- 2, last paragraph
"mux category" needs a citation. (There is a reference, which is cited
in 4.1, but a citation on first mention would be helpful.
- 3, 2nd paragraph:
Is the "Javascript API" mentioned here the same as the WebRTC API
mentioned previously? If so, consistent naming would be helpful.
-- 3rd and 4th paragraphs:
The antecedent for "its" is ambiguous (occurs twice)
-- 5th paragraph: "specific "msid-id"
Should that be specific "msid-id" value?
-- 2nd bullet in list: "When a session description is updated to have
media descriptions
with an msid "identifier" value, with one or more different
"appdata" values,"
Does that mean with the _same_ identifier value?
- [MMUSIC] AD Evaluation of draft-ietf-mmusic-msid-… Ben Campbell