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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]