[AVTCORE] [avtcore] nits of draft-ietf-avtcore-multiplex-guidelines

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Wed, 13 February 2019 06: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 55D18129A87; Tue, 12 Feb 2019 22:41:53 -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 SWWmxiSjmNqW; Tue, 12 Feb 2019 22:41:51 -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 438B012D4E6; Tue, 12 Feb 2019 22:41:51 -0800 (PST)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 713D27122762CA62BF61; Wed, 13 Feb 2019 06:41:49 +0000 (GMT)
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 13 Feb 2019 06:41:48 +0000
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.249]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0415.000; Wed, 13 Feb 2019 14:41:41 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "draft-ietf-avtcore-multiplex-guidelines@ietf.org" <draft-ietf-avtcore-multiplex-guidelines@ietf.org>
CC: "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [avtcore] nits of draft-ietf-avtcore-multiplex-guidelines
Thread-Index: AdTDZv/Z2ioXGLp7QaKfqkq7L3wcbQ==
Date: Wed, 13 Feb 2019 06:41:41 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBBAEFA3006@DGGEML532-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.153.152]
Content-Type: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBBAEFA3006DGGEML532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/yhJFfbzqEUX6azLlnrCwI6gqpUE>
Subject: [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: Wed, 13 Feb 2019 06:41:53 -0000

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