Re: [Lsr] Shepherd review comments on draft-ietf-isis-yang-isis-cfg-29

<stephane.litkowski@orange.com> Tue, 22 January 2019 16:18 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67468130F3A; Tue, 22 Jan 2019 08:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 mz-AEZe4b1kx; Tue, 22 Jan 2019 08:18:51 -0800 (PST)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 020CB12E043; Tue, 22 Jan 2019 08:18:51 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 43kYWX649Fz104P; Tue, 22 Jan 2019 17:18:48 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.18]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 43kYWX5B0DzyQN; Tue, 22 Jan 2019 17:18:48 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM34.corporate.adroot.infra.ftgroup ([fe80::cba:56d0:a732:ef5a%19]) with mapi id 14.03.0415.000; Tue, 22 Jan 2019 17:18:48 +0100
From: <stephane.litkowski@orange.com>
To: tom petch <ietfc@btconnect.com>, "Acee Lindem (acee)" <acee@cisco.com>, Yingzhen Qu <yingzhen.qu@huawei.com>, "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-isis-yang-isis-cfg@ietf.org" <draft-ietf-isis-yang-isis-cfg@ietf.org>
Thread-Topic: [Lsr] Shepherd review comments on draft-ietf-isis-yang-isis-cfg-29
Thread-Index: AdSvfV6+mHVGNqpKR26/bX73rx4nrAC8GRIg
Date: Tue, 22 Jan 2019 16:18:47 +0000
Message-ID: <14660_1548173928_5C474268_14660_472_1_9E32478DFA9976438E7A22F69B08FF924B791E9B@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <594D005A3CB0724DB547CF3E9A9E810B011230B1@sjceml521-mbx.china.huawei.com> <56F6AF71-F733-40E4-8C46-08C2803A3F90@cisco.com> <03aa01d4b250$9139d040$4001a8c0@gateway.2wire.net>
In-Reply-To: <03aa01d4b250$9139d040$4001a8c0@gateway.2wire.net>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/O03lIgOZRJ6DyV_lODhhg_zXCtY>
Subject: Re: [Lsr] Shepherd review comments on draft-ietf-isis-yang-isis-cfg-29
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2019 16:18:53 -0000

Hi Tom,

This is plaintext. You can see it in the XML source of the draft, there is no link in the YANG module.
Is your concern coming from the "[" "]" characters ? Just a copy/paste from the text version of the boilerplate, but there is no link behind.


-----Original Message-----
From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of tom petch
Sent: Tuesday, January 22, 2019 13:48
To: Acee Lindem (acee); Yingzhen Qu; lsr@ietf.org; draft-ietf-isis-yang-isis-cfg@ietf.org
Subject: Re: [Lsr] Shepherd review comments on draft-ietf-isis-yang-isis-cfg-29

-32 has the RFC2119 boilerplate in the YANG module - thank you - but...
YANG modules must be plain text and

         "are to be interpreted as described in BCP 14 [RFC2119]
          [RFC8174] when, and only when, they appear in all capitals, as
          shown here."

looks rather like XML/HTML anchors and not plain text.

Time idnits learnt what a YANG module looks like!

Tom Petch

----- Original Message -----
From: "Acee Lindem (acee)" <acee@cisco.com>;
To: "Yingzhen Qu" <yingzhen.qu@huawei.com>;; <lsr@ietf.org>;;
<draft-ietf-isis-yang-isis-cfg@ietf.org>;
Sent: Monday, January 21, 2019 9:07 PM
Subject: Re: [Lsr] Shepherd review comments on
draft-ietf-isis-yang-isis-cfg-29


> Hi Yingzhen,
> All the idnits warnings are fixed in the -32 version of the drafts.
> Thanks,
> Acee
>
> From: Yingzhen Qu <yingzhen.qu@huawei.com>;
> Date: Friday, January 18, 2019 at 5:35 PM
> To: "lsr@ietf.org"; <lsr@ietf.org>;,
"draft-ietf-isis-yang-isis-cfg@ietf.org";
<draft-ietf-isis-yang-isis-cfg@ietf.org>;
> Subject: Shepherd review comments on draft-ietf-isis-yang-isis-cfg-29
> Resent-From: <alias-bounces@ietf.org>;
> Resent-To: Stephane Litkowski <stephane.litkowski@orange.com>;, Derek
Yeung <derek@arrcus.com>;, Acee Lindem <acee@cisco.com>;, Jeffrey Zhang
<zzhang@juniper.

_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.