Re: [netmod] Draft Normative references in a YANG module

Kent Watsen <kwatsen@juniper.net> Wed, 07 February 2018 21:56 UTC

Return-Path: <kwatsen@juniper.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDF51270AB for <netmod@ietfa.amsl.com>; Wed, 7 Feb 2018 13:56:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level:
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=juniper.net
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 O8uaXw327DiZ for <netmod@ietfa.amsl.com>; Wed, 7 Feb 2018 13:56:55 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 221CB127873 for <netmod@ietf.org>; Wed, 7 Feb 2018 13:56:55 -0800 (PST)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w17LnOMp007625; Wed, 7 Feb 2018 13:56:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=uerr1PmRPpCVE2f09BnFKNaASL2BspO8GpfB7nasZxY=; b=1oWbh9Lg8tyi/RfU101yZXW2jGLlDSwZGwbclRpnUEZuk1BAzT3k2IHOg3PhU30WioKD /f2Lo7/FzUodyq2XyOSX1OyOaAG8xsCe90WDEA59SeL51AwpMyKXt7PUQqFeuWUv2+Fg qhFTYH2wB+5yvKCpmJRWc8lQ7YQfLSLB14Uzb+e+q5kDSc1ZOc7ZV5HPkZjh725pq+WW qq5WxhmSl4DzljHdSk8sTm6Be+92wTTpinJRGnsnIf4BxxmaBQwR9RGEDrYEZ3FncVju onBv3wcyNEI1juY16MARKdvq1/HjDotiRHmqDz7HqmLYlFjj+fI/9NRcu6HaZbYLdVNM nw==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0052.outbound.protection.outlook.com [216.32.180.52]) by mx0a-00273201.pphosted.com with ESMTP id 2g09kkr0vg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 07 Feb 2018 13:56:50 -0800
Received: from DM5PR05MB3484.namprd05.prod.outlook.com (10.174.240.147) by DM5PR05MB3642.namprd05.prod.outlook.com (10.174.243.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.485.3; Wed, 7 Feb 2018 21:56:49 +0000
Received: from DM5PR05MB3484.namprd05.prod.outlook.com ([10.174.240.147]) by DM5PR05MB3484.namprd05.prod.outlook.com ([10.174.240.147]) with mapi id 15.20.0485.009; Wed, 7 Feb 2018 21:56:49 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "t.petch" <ietfc@btconnect.com>, NETMOD Working Group <netmod@ietf.org>
CC: RFC Editor <rfc-editor@rfc-editor.org>
Thread-Topic: [netmod] Draft Normative references in a YANG module
Thread-Index: AQHToDlhpKliwBaKp0GYEyk8iin3O6OZKNeA
Date: Wed, 7 Feb 2018 21:56:49 +0000
Message-ID: <F788BAC0-EB78-4AD8-ABD9-09C54AD7A52F@juniper.net>
References: <017b01d3a039$1d4c5c40$4001a8c0@gateway.2wire.net>
In-Reply-To: <017b01d3a039$1d4c5c40$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR05MB3642; 7:SfhaXFBWYuyQm9SXhvZX9E3Snt/yiRzPIOLfbexQvc/aNSbHNqzfJe2msyIyIrftoaByAMhK3lqtQlhUPiXrWez9tkbDOuZFKgMbegvw90bvzxLhtbFx3fbLV/yMrGH7SMmYXf95R7fQiF7K8Z9dD4+Pxgl7C0vlOFFvcbaY8dRn8lCl9t67UyAcKO8OrIWAcHnYx0xJjZ/wglS0Hv3kpDa0RYQlVUl/VJFpDkiSMWyZw+3VajIKGyflzgrwYITJ
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 05f82e2f-50e1-40f1-ca86-08d56e75b08f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(48565401081)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:DM5PR05MB3642;
x-ms-traffictypediagnostic: DM5PR05MB3642:
x-microsoft-antispam-prvs: <DM5PR05MB36421A8E399B5119154DF08BA5FC0@DM5PR05MB3642.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(17755550239193);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3231101)(2400082)(944501161)(3002001)(6055026)(6041288)(20161123560045)(20161123562045)(20161123558120)(201703131423095)(201703031522075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011); SRVR:DM5PR05MB3642; BCL:0; PCL:0; RULEID:; SRVR:DM5PR05MB3642;
x-forefront-prvs: 0576145E86
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(346002)(376002)(396003)(39860400002)(39380400002)(51444003)(189003)(199004)(6306002)(82746002)(6512007)(305945005)(106356001)(6506007)(8936002)(5890100001)(36756003)(2950100002)(102836004)(76176011)(966005)(97736004)(81166006)(6436002)(83506002)(6486002)(6246003)(105586002)(7736002)(81156014)(26005)(4326008)(5660300001)(83716003)(77096007)(2906002)(8666007)(186003)(3660700001)(99286004)(575784001)(86362001)(66066001)(110136005)(478600001)(8676002)(6116002)(14454004)(58126008)(3280700002)(2900100001)(68736007)(53936002)(33656002)(296002)(316002)(3846002)(25786009)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3642; H:DM5PR05MB3484.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: AK0i/dosaMmokiqzeyDuMILSs9y0udugZq1X8Jw7lDIItgR/9+pNoy9BkvBktPbdFSKv/KAjIxnvahEohepMLA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <F3798EF8AA226F4C9437BD1382594EBD@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 05f82e2f-50e1-40f1-ca86-08d56e75b08f
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Feb 2018 21:56:49.4610 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3642
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-02-07_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1802070276
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/leK9v92mLEfXiKhP6Tc-tdGuiX4>
Subject: Re: [netmod] Draft Normative references in a YANG module
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Feb 2018 21:56:57 -0000

I think that there should be a note attached to such references 
occurring inside of a YANG module.   I think that all of my drafts
do this, though I tend to use a single large Note to Editor at the
beginning of the draft, rather than a number of smaller notes 
sprinkled throughout the document.

Separately, I support your idea of tooling to catch the case when
a reference occurring inside a module isn't also hyperlinked in 
the draft, just above where the module is located in the draft.

Kent // yang doctor


===== original message =====

Will the RFC Editor know that

       reference "draft-ietf-netmod-rfc7223bis: A YANG Data Model
                  for Interface Management";
in

draft-ietf-rtgwg-ni-model-09

needs replacing by RFCxxxx when that I-D becomes an RFC?

Normally, such a reference would be [draft-ietf-netmod-rfc7223bis] with
the underlying HTML/XML anchor and automated tools can pick this up (I
assume that the RFC Editor is well automated:-)

But when the Normative Reference is in the text of a YANG module and
there is no underlying anchor, will this get noticed and actioned?

Or should there be a

Note to RFC Editor

attached to such references?

Tom Petch

_______________________________________________
netmod mailing list
netmod@ietf.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_netmod&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=QCThchs4JeGsrzrJeaUdQoPQi37pCz4FGgc_cilPLgg&s=EYIhtpotNaX09tQ5hR86BtUD04ov-Ynr9fwBCMa2Ue0&e=