Re: [yang-doctors] [pim] I-D Action: draft-ietf-pim-msdp-yang-13.txt

zhang.zheng@zte.com.cn Mon, 02 March 2020 03:01 UTC

Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7C8A3A08BA; Sun, 1 Mar 2020 19:01:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 sH3C479yJYDv; Sun, 1 Mar 2020 19:01:24 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 2DE6B3A08C8; Sun, 1 Mar 2020 19:01:21 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id D4628ED779D50EEAF8E6; Mon, 2 Mar 2020 11:01:18 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 3129A944C3C707CC9CA2; Mon, 2 Mar 2020 11:01:18 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl2.zte.com.cn with SMTP id 02230NPX035092; Mon, 2 Mar 2020 11:00:23 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Mon, 2 Mar 2020 11:00:22 +0800 (CST)
Date: Mon, 02 Mar 2020 11:00:22 +0800
X-Zmail-TransId: 2afb5e5c76c6a832f301
X-Mailer: Zmail v1.0
Message-ID: <202003021100225100176@zte.com.cn>
In-Reply-To: <20200302014701.GC98042@kduck.mit.edu>
References: 5E564CFC.8090804@btconnect.com, 20200302014701.GC98042@kduck.mit.edu
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: kaduk@mit.edu, daedulus@btconnect.com
Cc: aretana.ietf@gmail.com, rrahman@cisco.com, xufeng.liu.ietf@gmail.com, meral.shirazipour@ericsson.com, vincent.roca@inria.fr, pim-chairs@ietf.org, sivakumar.mahesh@gmail.com, guofeng@huawei.com, zzhang_ietf@hotmail.com, anish.ietf@gmail.com, pete.mcallister@metaswitch.com, yang-doctors@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 02230NPX035092
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/Zblzc-NcjxUgb8o5Y8tSWayIQm4>
Subject: Re: [yang-doctors] [pim] I-D Action: draft-ietf-pim-msdp-yang-13.txt
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2020 03:01:30 -0000

Hi Ben, Tom,







Thank you very much!


I read the guideline before, and I am confused with the two sentences:

“Normative references specify documents that must be read to understand or implement the technology in the new RFC, or whose technology must be present for the technology in the new RFC to work."

"Note 1: Even references that are relevant only for optional features must be classified as normative if they meet the above conditions for normative references. "


The reason that I put the reference in "informative" is that the users can also use the model even if they know nothing about RFC4271.


But now, I think you are right, according to "note 1", the reference should be normative.


I'll update it.


Thank you again for your guidance!






Best regards,


Sandy












原始邮件



发件人:BenjaminKaduk <kaduk@mit.edu>
收件人:张征00007940;
抄送人:daedulus@btconnect.com <daedulus@btconnect.com>;aretana.ietf@gmail.com <aretana.ietf@gmail.com>;rrahman@cisco.com <rrahman@cisco.com>;xufeng.liu.ietf@gmail.com <xufeng.liu.ietf@gmail.com>;meral.shirazipour@ericsson.com <meral.shirazipour@ericsson.com>;vincent.roca@inria.fr <vincent.roca@inria.fr>;pim-chairs@ietf.org <pim-chairs@ietf.org>;sivakumar.mahesh@gmail.com <sivakumar.mahesh@gmail.com>;guofeng@huawei.com <guofeng@huawei.com>;zzhang_ietf@hotmail.com <zzhang_ietf@hotmail.com>;anish.ietf@gmail.com <anish.ietf@gmail.com>;pete.mcallister@metaswitch.com <pete.mcallister@metaswitch.com>;yang-doctors@ietf.org <yang-doctors@ietf.org>;
日 期 :2020年03月02日 09:47
主 题 :Re: [pim] I-D Action: draft-ietf-pim-msdp-yang-13.txt


On Thu, Feb 27, 2020 at 10:17:37PM +0800, zhang.zheng@zte.com.cn wrote:
> Hi Tom,
> 
> 
> 
> 
> 
> 
> Thank you very much for your review!
> 
> 
> Because the usage referenced to RFC4271 is an optional leaf. I am not sure if it can be in informatinve reference.
> 
> 
> If the rule is mandatory, I will change it. :-)

Per
https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
being an optional feature does not affect the normative vs. informative
status of the corresponding reference.

-Ben