Re: [Lsr] I-D Action: draft-ietf-isis-yang-isis-cfg-35.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Fri, 07 June 2019 15:47 UTC

Return-Path: <ginsberg@cisco.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 AFB8C1201C5 for <lsr@ietfa.amsl.com>; Fri, 7 Jun 2019 08:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=lKqR7Ko9; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=I+L1atKQ
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 jQHyw5qqLfwV for <lsr@ietfa.amsl.com>; Fri, 7 Jun 2019 08:46:56 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A20E71200B3 for <lsr@ietf.org>; Fri, 7 Jun 2019 08:46:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7920; q=dns/txt; s=iport; t=1559922416; x=1561132016; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=RlcXOYqzj0om5ftJ70gQF0opf4afF/rmjjc6sToTZ8E=; b=lKqR7Ko9gra2zXlyJ5A7JD4RjeTcrCMEgK5fNUmqvNCCoPjd4yISTHT7 ZcdRJQckuIxlQ1t9yUTSDhIJ6CI72MP+Pn0hFhOn8p8UNbgI2Y2tJNIDs TpcxTA713xAXfhM5fuun2q+6mleDzji0t8iIqp5mMApVPZZsc1Njd/YNH Q=;
IronPort-PHdr: =?us-ascii?q?9a23=3ARDAA4hLS1Io4AtkV0tmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXEL6KuXgYjY1NM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A1AAD4hfpc/4gNJK1mGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBUwQBAQELAYE9UANqVSAECyiEFYNHA45hgleXMYEuFIEQA1QJAQE?= =?us-ascii?q?BDAEBGAsKAgEBhEACF4JTIzYHDgEDAQEEAQECAQRtHAyFSgEBAQEDAQEQERE?= =?us-ascii?q?MAQEsCwELBAIBCBEEAQEBAgIjAwICAiULFAEICAIEAQ0FCAEZgwGBagMdAQI?= =?us-ascii?q?MnFICgTiIX3GBMYJ5AQEFgTIBAwIOQYJ8GIIPCYEMKAGLWheBQD+BEAFGgkw?= =?us-ascii?q?+glYLAQEBAQEBFoEUARIBIRUPgmQygiaLP4JmmwMJAoIOhkONGYIkaYYPjXW?= =?us-ascii?q?ND4cThC+KdAIEAgQFAg4BAQWBVgkoZ3FwFRohgmwJggaDcIUUhT9yAYEojEm?= =?us-ascii?q?CQwEB?=
X-IronPort-AV: E=Sophos;i="5.63,563,1557187200"; d="scan'208";a="571481520"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Jun 2019 15:46:54 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x57FkseG007914 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Jun 2019 15:46:54 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 7 Jun 2019 10:46:53 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 7 Jun 2019 10:46:52 -0500
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 7 Jun 2019 10:46:52 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RlcXOYqzj0om5ftJ70gQF0opf4afF/rmjjc6sToTZ8E=; b=I+L1atKQdfzt2h2yvTgOt5N751I61gCZlF8ehRTu6Ojj5rMvznK2X8vWHwn8SFnIcfO5TwkuC/GOLxJa/vAWDNmpQZj4W5fB4CwabnFn45k7yoWHUs/8NMFxa5UcUi2Dy0SMUDQWw+AMN9hfYpGQZCzsjKeD3FVnJ5tGolEIWJQ=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB2583.namprd11.prod.outlook.com (52.135.227.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.15; Fri, 7 Jun 2019 15:46:51 +0000
Received: from BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::ace2:8693:202d:5a30]) by BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::ace2:8693:202d:5a30%7]) with mapi id 15.20.1965.011; Fri, 7 Jun 2019 15:46:51 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, tom petch <ietfc@btconnect.com>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] I-D Action: draft-ietf-isis-yang-isis-cfg-35.txt
Thread-Index: AQHVHSyP8GbkW+/9dku42ESSaT1C16aQVPkg
Date: Fri, 7 Jun 2019 15:46:50 +0000
Message-ID: <BYAPR11MB36388E4C262C733A952899C2C1100@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <BB5E639D-13A8-4D81-AA23-9B3B78FB896A@cisco.com>
In-Reply-To: <BB5E639D-13A8-4D81-AA23-9B3B78FB896A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ginsberg@cisco.com;
x-originating-ip: [2001:420:c0c8:1003::6f7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e8e04e80-4700-43a6-7159-08d6eb5f5b8f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB2583;
x-ms-traffictypediagnostic: BYAPR11MB2583:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <BYAPR11MB2583556EFA6910318E77D384C1100@BYAPR11MB2583.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0061C35778
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(366004)(396003)(376002)(346002)(136003)(199004)(189003)(13464003)(8676002)(305945005)(81166006)(81156014)(76116006)(99286004)(2906002)(7736002)(73956011)(486006)(4326008)(7696005)(64756008)(9686003)(68736007)(6306002)(2501003)(8936002)(186003)(66556008)(6246003)(66946007)(66476007)(55016002)(14454004)(5660300002)(86362001)(14444005)(71190400001)(66446008)(316002)(71200400001)(76176011)(53936002)(6436002)(446003)(110136005)(478600001)(6116002)(74316002)(66574012)(11346002)(6506007)(53546011)(966005)(102836004)(256004)(25786009)(46003)(5024004)(229853002)(476003)(33656002)(52536014); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2583; H:BYAPR11MB3638.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: jF12BoYH6wAKJv0VcNJJTfkXFn9MjOJ6EWP+H99U8dcHVmf1Z63nNgu4jX5tPK8sRI9wDu/m7DiymeH5BwTxQdn+yhlDui7ibTbom8lSPC+SylIvh/2RCWcv7hwVtGEyFnA9yWPWur06LlRrYTJvZ1TebUoQZyNL03skH6Dxu1DUMhmyqmD+pG9ODNfEBoLWlW5V1opX48NZTw/z0N/wuN86UjuKuTGpyHBlc0SzYQJCdLIJBebrdPoC6bRod8SyzRjkIr2nLbrlBHMg2o8NT+3pMO80GS/e0E4gG7ipJk8t0BXbhyXZ9FA4chPEDNpPk3s37YOEY3YeruqsXWRlVUbxaGllXf7isJ2cN+DsvBCpQRKH+nzKB7KstxPy38pnNpyFieh/pvy2zaOxgbSf01LTQVufvYn4u093peZtH8A=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e8e04e80-4700-43a6-7159-08d6eb5f5b8f
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jun 2019 15:46:50.8372 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ginsberg@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2583
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.27, xch-aln-017.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/f36IOgpbb8jf-iHKHEFnO9ATp6Q>
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-yang-isis-cfg-35.txt
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: Fri, 07 Jun 2019 15:47:07 -0000

In regards to system-ids reserved for documentation, I am not aware that this exists.

Note that the most common practice used in assigning system-ids is to use the MAC address of some interface associated with the router.
Therefore I don’t think Tom's example in regards to IP addresses translates here.

   Les


> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org>; On Behalf Of Acee Lindem (acee)
> Sent: Friday, June 07, 2019 5:29 AM
> To: stephane.litkowski@orange.com; tom petch <ietfc@btconnect.com>;
> Cc: lsr@ietf.org
> Subject: Re: [Lsr] I-D Action: draft-ietf-isis-yang-isis-cfg-35.txt
> 
> Hi Stephane, Tom,
> 
> On 6/7/19, 4:03 AM, "Lsr on behalf of stephane.litkowski@orange.com"; <lsr-
> bounces@ietf.org on behalf of stephane.litkowski@orange.com>; wrote:
> 
>     Hi Tom,
> 
>     Thanks for your feedback.
>     Pls find some comments inline
> 
>     Stephane
> 
>     -----Original Message-----
>     From: tom petch [mailto:ietfc@btconnect.com]
>     Sent: Thursday, June 06, 2019 18:59
>     To: LITKOWSKI Stephane OBS/OINIS
>     Cc: lsr@ietf.org
>     Subject: Re: I-D Action: draft-ietf-isis-yang-isis-cfg-35.txt
> 
>     Stephane
> 
>     The YANG module has RFC5307 in a description clause but I do not see
>     this in the References of the I-D
> 
>     [SLI] That's a mistake, I will fix it
> 
> 
>     I commented before on the lack of  a conditional when on
>          augment "/if:interfaces/if:interface"
>     so every interface will get this object; is that intended?
> 
>     [SLI] It looks good to me, if a device supports the ISIS model, all the
> interfaces should get the clns-mtu config statement.
> 
>     In the example, is the system-id one reserved for documentation?
>     [SLI] No, but I'm personally not aware of system IDs reserved for
> documentation as we could have for IP addresses. If someone from the WG
> knows about it, I will be happy to change it.
> 
> [ACEE] ISO owns the definition of the IS-IS system ID definition. I don't know
> that they've set aside any reserved system IDs for examples.
> 
> Thanks,
> Acee
> 
> 
> 
>     Tom Petch
> 
>     ----- Original Message -----
>     From: <internet-drafts@ietf.org>;
>     To: <i-d-announce@ietf.org>;
>     Cc: <lsr@ietf.org>;
>     Sent: Friday, March 08, 2019 3:37 AM
>     Subject: I-D Action: draft-ietf-isis-yang-isis-cfg-35.txt
> 
> 
>     >
>     > A New Internet-Draft is available from the on-line Internet-Drafts
>     directories.
>     > This draft is a work item of the Link State Routing WG of the IETF.
>     >
>     >         Title           : YANG Data Model for IS-IS Protocol
>     >         Authors         : Stephane Litkowski
>     >                           Derek Yeung
>     >                           Acee Lindem
>     >                           Jeffrey Zhang
>     >                           Ladislav Lhotka
>     > Filename        : draft-ietf-isis-yang-isis-cfg-35.txt
>     > Pages           : 111
>     > Date            : 2019-03-07
>     >
>     > Abstract:
>     >    This document defines a YANG data model that can be used to
>     configure
>     >    and manage IS-IS protocol on network elements.
>     >
>     >
>     >
>     > The IETF datatracker status page for this draft is:
>     > https://datatracker.ietf.org/doc/draft-ietf-isis-yang-isis-cfg/
>     >
>     > There are also htmlized versions available at:
>     > https://tools.ietf.org/html/draft-ietf-isis-yang-isis-cfg-35
>     > https://datatracker.ietf.org/doc/html/draft-ietf-isis-yang-isis-cfg-35
>     >
>     > A diff from the previous version is available at:
>     > https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-yang-isis-cfg-35
>     >
>     >
>     > Please note that it may take a couple of minutes from the time of
>     submission
>     > until the htmlized version and diff are available at tools.ietf.org.
>     >
>     > Internet-Drafts are also available by anonymous FTP at:
>     > ftp://ftp.ietf.org/internet-drafts/
>     >
>     > _______________________________________________
>     > I-D-Announce mailing list
>     > I-D-Announce@ietf.org
>     > https://www.ietf.org/mailman/listinfo/i-d-announce
>     > Internet-Draft directories: http://www.ietf.org/shadow.html
>     > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> 
> __________________________________________________________
> __________________________________________________________
> _____
> 
>     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.
> 
>     _______________________________________________
>     Lsr mailing list
>     Lsr@ietf.org
>     https://www.ietf.org/mailman/listinfo/lsr
> 
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr