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

Elwyn Davies <elwynd@dial.pipex.com> Wed, 25 January 2017 15:13 UTC

Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96CB3129847; Wed, 25 Jan 2017 07:13:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level:
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=no 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 so6G2M39UtRK; Wed, 25 Jan 2017 07:13:53 -0800 (PST)
Received: from b-painless.mh.aa.net.uk (b-painless.mh.aa.net.uk [81.187.30.52]) (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 9BE4F12998C; Wed, 25 Jan 2017 07:13:53 -0800 (PST)
Received: from d.b.e.5.0.8.d.b.f.6.1.b.0.8.c.7.1.0.0.0.f.b.0.0.0.b.8.0.1.0.0.2.ip6.arpa ([2001:8b0:bf:1:7c80:b16f:bd80:5ebd]) by b-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <elwynd@dial.pipex.com>) id 1cWObl-00013x-Nd; Wed, 25 Jan 2017 14:31:34 +0000
Date: Wed, 25 Jan 2017 14:31:29 +0000
Subject: Re: Review of draft-ietf-mmusic-4572-update-11
Message-ID: <s9ubcupjutekv1baydfw2bpi.1485353373053@email.android.com>
Importance: normal
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, gen-art@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_6905722906156110"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WAUJIeCxxqVnbANq6lseyWmk16s>
Cc: draft-ietf-mmusic-4572-update.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jan 2017 15:13:56 -0000

Hi, Christer.
Thanks for the rapid response.
That's all fine.  Re s4, para 2: First, i realised I missed another instance of 'new' in the abstract.  I think that 'the' is correct in the new [sic] version in both places.  It's pernickety but when it was 'a new' what you have is shorthand for "a new protocol identifier to be called 'TCP/TLS'..."  (an addition to the existng list) whereas because the identifier is no longer new we now have "the protocol identifier [named] 'TCP/TLS'...".   
Cheers,Elwyn
Sent from Samsung tablet.
-------- Original message --------From: Christer Holmberg <christer.holmberg@ericsson.com> Date: 25/01/2017  13:40  (GMT+00:00) To: Elwyn Davies <elwynd@dial.pipex.com>om>, gen-art@ietf.org Cc: draft-ietf-mmusic-4572-update.all@ietf.org, ietf@ietf.org, mmusic@ietf.org Subject: Re: Review of draft-ietf-mmusic-4572-update-11 
Hi Elwyn,

Thanks for your review! See inline.

Nits/editorial comments:

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

I will fix as suggested.


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

I am happy to remove ³new², but doesn¹t ³a² still sound better than ³the²?


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

I will replace with single quotes (Œm¹), for consistency with s3.4 and s4.


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

I will fix as suggested.


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

I will fix as suggested.


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

I will fix as suggested.

>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/

I suggest:

 "This specification takes over the IANA registry named "Hash Function
 Textual Names², that was created in RFC 4572.  It will not be part of
 the SDP Parameters.²


Regards,

Christer