Re: [MMUSIC] Opsdir last call review of draft-ietf-mmusic-rfc4566bis-34

wangzitao <> Thu, 11 April 2019 07:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ED2AB12007A; Thu, 11 Apr 2019 00:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ygszvW3e4RRc; Thu, 11 Apr 2019 00:29:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 347C412017D; Thu, 11 Apr 2019 00:29:23 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 0EF8398C3FC3A375A446; Thu, 11 Apr 2019 08:29:21 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 11 Apr 2019 08:29:20 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 11 Apr 2019 08:29:20 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Thu, 11 Apr 2019 08:29:20 +0100
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Thu, 11 Apr 2019 15:29:04 +0800
From: wangzitao <>
To: Paul Kyzivat <>, "" <>
CC: "" <>, "" <>, "" <>
Thread-Topic: [MMUSIC] Opsdir last call review of draft-ietf-mmusic-rfc4566bis-34
Thread-Index: AdTwOA+WHtBjfNJUSRGniaW2r1dQNw==
Date: Thu, 11 Apr 2019 07:29:04 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [MMUSIC] Opsdir last call review of draft-ietf-mmusic-rfc4566bis-34
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Apr 2019 07:29:25 -0000

Thank you for updating. It make sense to me.

Best Regards!

发件人: Paul Kyzivat [] 
发送时间: 2019年4月11日 4:25
收件人: wangzitao <>om>;
主题: Re: [MMUSIC] Opsdir last call review of draft-ietf-mmusic-rfc4566bis-34

Please see inline.

On 4/9/19 11:03 PM, wangzitao wrote:
> Hi Paul,
> Please find my comments at [MW].
> B.R.
> -Michael
> -----邮件原件-----
> 发件人: Paul Kyzivat []
> 发送时间: 2019年4月10日 1:11
> 收件人: wangzitao <>om>;
> 抄送:;; 
> 主题: Re: [MMUSIC] Opsdir last call review of 
> draft-ietf-mmusic-rfc4566bis-34
> Thank you for the comments. I have some questions:
> On 4/8/19 2:37 AM, Zitao Wang via Datatracker wrote:
>> Reviewer: Zitao Wang
>> Review result: Has Issues
>> Summary:    This memo defines the Session Description Protocol (SDP).  SDP is
>> intended for describing multimedia sessions for the purposes of 
>> session announcement, session invitation, and other forms of 
>> multimedia session initiation.  This document obsoletes RFC 4566. I 
>> think the document make sense and is written very clear, except some small nits:
>> # In Section 5, there are
>> several terms that miss references, such as "US-ASCII subset of 
>> UTF-8",  "ASN.1 or XDR", etc.
> There is already a reference to the definition of UTF-8 [RFC3629] in section 4.5. Do you think the reference needs to be included with every use? The US-ASCII subset of UTF-8 is also defined in RFC3629, so I am inclined to use the same reference for that. There are also a couple of uses of US-ASCII without mention of UTF-8. I'm inclined to change those to "the US-ASCII subset of UTF-8".

I changed the naked uses of US-ASCII to reference the US-ASCII subset of UTF-8. I also added another reference to RFC3629 to the *first* use of "US-ASCII subset of UTF-8". I haven't added references to other places with the same usage.

> Regarding ASN.1 and XDR, I can add references if you think it important.
> But their use is very peripheral, and it isn't necessary to know what they are to read the text.
> [MW]: I am OK if it is not commonly used.
> # s/session- specific/session-specific/
> Regarding "session- specific" vs. "session-specific":
> The context for this is:
> "Attribute scopes in addition to media- and session- specific may also..."
> The space was intentional so that there are equivalent constructions for "media" and "session". The intent is as a shorthand for:
> "Attribute scopes in addition to media-specific and session-specific may also..."
> To avoid confusion I think I'll just change to the latter.
> [MW]: I agree.


> # Suggest to add tags on
>> "overview optional items" to identified now-obsolete items, such as 
>> "a=cat", "a=keywds", "k=".
> I'm not clear what you want me to do.
> I guess you are suggesting adding something to the first figure in section 5.
> [MW]: Yes, IMO, adding some tag/description to the figure is better.
> I don't see how that would be possible for a=cat and a=keywds, since the figure doesn't mention individual attributes.
> [MW]: Agree. For a=cat and a=keywds, it is difficult to show on the figure.
> While it is possible to add something for k=, IMO it is better to leave that level of detail to the complete description in section 5.12.
> [MW]: Maybe it can be updated as following:
>        Before :
>         k=* (encryption key)
>        After:
>         k=* (encryption key, this line is obsoleted)

I changed these to

           k=* (obsolete)

I have these changes in my working copy for inclusion the next time I submit a revision.