Review of draft-ietf-mmusic-4572-update-11

Elwyn Davies <> Tue, 24 January 2017 20:40 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 272E2129722; Tue, 24 Jan 2017 12:40:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Elwyn Davies <>
To: <>
Subject: Review of draft-ietf-mmusic-4572-update-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 24 Jan 2017 12:40:35 -0800
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Jan 2017 20:40:35 -0000

Reviewer: Elwyn Davies
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-mmusic-4572-update-11
Reviewer: Elwyn Davies
Review Date: 2017-01-24
IETF LC End Date: 2017-01-26
IESG Telechat date: Not scheduled for a telechat

Summary: Ready.  There are a couple of trivial nits mentioned below. 
Given that the draft has a minimal set of changes apart from the
addition of two sections, I have not read the unchanged pieces in

Major issues:

Minor issues:

Nits/editorial comments: 
s1, para 2: s/TLS protocol/The TLS protocol/ (as per RFC 4572)

s4, para 2: s/a new protocol identifier/the protocol identifier/ (it
isn't new any more)

s5.1: Suggest s/m- line/"m" line/  for consistency with s3.4

s5.1, para 1: s/e.g./e.g.,/

s5.1, para 4: s/that each used certificate matches/that each
certificate used matches/

s5.1, para 5: s/each used certificate matches/each certificate used

s8, para 5: ' This specification creates a new IANA registry named
"Hash Function Textual Names".'  
The registry is no longer new.  Perhaps s/creates a new IANA
registry/takes over the IANA registry from RFC 4572/