Re: [AVTCORE] [avtcore] nits of draft-ietf-avtcore-multiplex-guidelines
"Huangyihong (Rachel)" <rachel.huang@huawei.com> Thu, 14 February 2019 12:41 UTC
Return-Path: <rachel.huang@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB13312F1A2; Thu, 14 Feb 2019 04:41:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 KGIu6CF9eAqZ; Thu, 14 Feb 2019 04:41:03 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32B7812D4E6; Thu, 14 Feb 2019 04:41:03 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E80093E608A8A5F132C7; Thu, 14 Feb 2019 12:41:00 +0000 (GMT)
Received: from DGGEML422-HUB.china.huawei.com (10.1.199.39) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 14 Feb 2019 12:41:00 +0000
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.249]) by dggeml422-hub.china.huawei.com ([10.1.199.39]) with mapi id 14.03.0415.000; Thu, 14 Feb 2019 20:40:56 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, draft-ietf-avtcore-multiplex-guidelines <draft-ietf-avtcore-multiplex-guidelines@ietf.org>
CC: avt <avt@ietf.org>
Thread-Topic: [avtcore] nits of draft-ietf-avtcore-multiplex-guidelines
Thread-Index: AdTDZv/Z2ioXGLp7QaKfqkq7L3wcbQA+4eSN
Date: Thu, 14 Feb 2019 12:40:55 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBBAEFA6BC8@DGGEML532-MBX.china.huawei.com>
References: <51E6A56BD6A85142B9D172C87FC3ABBBAEFA3006@DGGEML532-MBX.china.huawei.com>, <DB6PR0701MB25176963957AE04BC254F27C95670@DB6PR0701MB2517.eurprd07.prod.outlook.com>
In-Reply-To: <DB6PR0701MB25176963957AE04BC254F27C95670@DB6PR0701MB2517.eurprd07.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBBAEFA6BC8DGGEML532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/hTLB5hEep_s79fH0unjaxMAH1cI>
Subject: Re: [AVTCORE] [avtcore] nits of draft-ietf-avtcore-multiplex-guidelines
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2019 12:41:06 -0000
Okay. ________________________________ 黄一宏 rachel huang M：+86-18114717307<tel:+86-18114717307> E：rachel.huang@huawei.com<mailto:rachel.huang@huawei.com> 产品与解决方案-网络标准专利部 Products & Solutions-Network Standard & Patent Dept 发件人： Magnus Westerlund 收件人： Huangyihong (Rachel)<rachel.huang@huawei.com<mailto:rachel.huang@huawei.com>>;draft-ietf-avtcore-multiplex-guidelines<draft-ietf-avtcore-multiplex-guidelines@ietf.org<mailto:draft-ietf-avtcore-multiplex-guidelines@ietf.org>> 抄送： avt<avt@ietf.org<mailto:avt@ietf.org>> 主题： Re: [avtcore] nits of draft-ietf-avtcore-multiplex-guidelines 时间： 2019-02-14 20:32:02 Hi, These are from a quote of RFC 3550. Thus, simply note that this is the reason in the write-up. Cheers Magnus On 2019-02-13 07:42, Huangyihong (Rachel) wrote: Hi, When running the idnits, following error is found: “ Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 559: '... SHOULD be carried in a separate RTP...' RFC 2119 keyword, line 562: '...nd video streams SHOULD NOT be carried...' ” Since it’s an informational draft, do we have reasons to use these normative words? If no, they should be lowercase. BR, Rachel -- Magnus Westerlund ---------------------------------------------------------------------- Network Architecture & Protocols, Ericsson Research ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Torshamnsgatan 23 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<mailto:magnus.westerlund@ericsson.com> ----------------------------------------------------------------------
- [AVTCORE] [avtcore] nits of draft-ietf-avtcore-mu… Huangyihong (Rachel)
- Re: [AVTCORE] [avtcore] nits of draft-ietf-avtcor… Magnus Westerlund
- Re: [AVTCORE] [avtcore] nits of draft-ietf-avtcor… Huangyihong (Rachel)