Re: [Idr] some thoughts on draft-ietf-idr-bgp-model-09.txt

tom petch <ietfc@btconnect.com> Thu, 06 August 2020 09:17 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A153A1084 for <idr@ietfa.amsl.com>; Thu, 6 Aug 2020 02:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 q6mcP0G5RFme for <idr@ietfa.amsl.com>; Thu, 6 Aug 2020 02:17:13 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80110.outbound.protection.outlook.com [40.107.8.110]) (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 EA1AC3A1080 for <idr@ietf.org>; Thu, 6 Aug 2020 02:17:12 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IpqfJbgdjtc7ZEGSmRj6L1VuyOXEPAzGhyzhPg0QbJSTD4uNytTTp5oku3cZ8Ml/2dGvz0/j+m7GtZ2iDzFJgl51rpvEYAEc32O7MZUyVce762agdbB1xsrkugb1IYfOWIjdepiHpFiBVErGsM3t6AzZTSqBP6HFrHpRxXwm6N7IfJPCb6y1dqKvczXZZ95dStqSDFYCQUjIcUo9KNjulhG1cGgjBNjT/OjGA3oRNAuPQwkM0+AIu77hfDrFaNFKF0Emsb18S7NmBdMxJAMz7Hb8QDS0W4RPYf1fJG+ZSg/bgpzVzk2JmBmAXYAg34dG3X79Qkgu9qHvl/qlIS9C6w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kyDFfWvf4gKa2nIhxz7dvx1jA+v70JTbRtDs5JnJ6Xc=; b=m+4mOfljozlft+PEdMuHqhQzk7FU0XtvwtuBrPEsFWHr8LGgioTbjShWd5E43eXLGP4D1MkALJVyd111GMcQVlb9E1v/uR0xB+lz2E+/o62H2Pawkl1JiIo5BVktsyCCK1Kt2T0gzhqtb30Sq58naLkqpokfpe+DyRTQPZKLwY39Ryvxm5tit/vhFVLXiTC/3oaY4zLeOsaqyxx4dTMRc06cR9nGEEDElHHuuIsWoYWiUI3DpmDmcP5JSdG+ZggcVCTslEmnuqJIQAdq4G8xC2pE3f+7eGipWrJCswMATnq6zeJj5jPM5ZdJ8928kbirozijEtgFSUf3zesknfmhFA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kyDFfWvf4gKa2nIhxz7dvx1jA+v70JTbRtDs5JnJ6Xc=; b=gMrS9AyEzjWjnd7c6uxNsGLnQU87SKJdoGT5cUP0GRyg/bsUB4gLFweNPfnwImBmVyiYrRLfqiJENJ506BhMM1/r87s0Iy1uywmu+XHJBFHaDyK+Gays/25kMT744rgonEUHTGlt73wxBUDjc+gA0XbvErxVm6+at6pV+hVqJzw=
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com (2603:10a6:20b:134::11) by AM7PR07MB7012.eurprd07.prod.outlook.com (2603:10a6:20b:1bc::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.13; Thu, 6 Aug 2020 09:17:10 +0000
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::b570:437a:db46:400a]) by AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::b570:437a:db46:400a%9]) with mapi id 15.20.3261.015; Thu, 6 Aug 2020 09:17:10 +0000
From: tom petch <ietfc@btconnect.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: some thoughts on draft-ietf-idr-bgp-model-09.txt
Thread-Index: AQHWaXjJOhsnFoSdhUyxiufGjgmlVakpYPKAgAFnzr0=
Date: Thu, 6 Aug 2020 09:17:10 +0000
Message-ID: <AM7PR07MB624872D82257CDC43A508248A0480@AM7PR07MB6248.eurprd07.prod.outlook.com>
References: <005401d6659d$31ad4c40$9507e4c0$@ndzh.com> <133E5D36-A696-4314-8588-7992E52D190B@gmail.com>, <007101d66759$938f7150$baae53f0$@ndzh.com> <AM7PR07MB62485BC88F847F9EFE88CB1AA04D0@AM7PR07MB6248.eurprd07.prod.outlook.com>, <017c01d66b19$f25af510$d710df30$@ndzh.com>
In-Reply-To: <017c01d66b19$f25af510$d710df30$@ndzh.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ndzh.com; dkim=none (message not signed) header.d=none;ndzh.com; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [81.131.229.35]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d3d2f03a-d450-4dfc-f674-08d839e97fc0
x-ms-traffictypediagnostic: AM7PR07MB7012:
x-microsoft-antispam-prvs: <AM7PR07MB70126E57FA3B00461115FB25A0480@AM7PR07MB7012.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FhJCRnzqVBJ0s8uA2SEMzoTF8kAW1/mg0Hahxdemfx7VkOzNkBjKPQpEw0ejcStO1F7GnXJVS8enZTI1/Q/3NmgYpzX5e5RXKShMAztDsR7KBErOuIZE0QOkq+V1ZFHf/U0Kdl6LWA54wp8dYQ3QWk936spcMEQV39xUtxvl/IIjkRUCctaJ7Uun+60RvgakUOZZVvLpOQPvkdITADhMDlGMVLGZfqu0dgYZ1JAju15+swFzmu/7GVzp5wrsgBTx51WX5OaEuww5yPyviZlNqWKAQi9r7GVX8zc/5x8RkGmCzwIY54zZ/VNRZPEIehWF/CMhHQ+3ldF8dlITj5AkxQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM7PR07MB6248.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(396003)(346002)(376002)(366004)(39860400002)(136003)(478600001)(8676002)(33656002)(53546011)(52536014)(7696005)(6506007)(8936002)(86362001)(9686003)(66556008)(66946007)(316002)(110136005)(5660300002)(71200400001)(64756008)(55016002)(2906002)(76116006)(91956017)(66476007)(186003)(66446008)(26005)(83380400001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: +qEc5m9gOAycfrTOIbjNUdW4+EbC/T1U1Ddfju+WQZCsj4F1VQDHsND/js5SFj6ccd9IXFpsSC3pz0L++9tUvY4mdQlMFf+WQjhxc/qsxFKZHtC8R+tueP3XSulC9GtLxGziI56tpWK+J/d81/D6ojJXRuIhKdrowdVfHFQbR5w2hoFxKNBYjiWdqhsurZoIYW9K1bJE+kJ6J+BuzhYFjhVQMkdfGh9VCUfw5s277+Z0ARe6u9NYBKGvyq2XNn7003S7WcyvTf3fJ1IX18H208gM4GAZ+q7p9qTjfKzL67GtMwSARAP745SGxM3br8ZHhCpKICG1r5OYcEnxPD9DkSjmCoKITvtdlqU1wqvK96m23jbxZ9ditmkT6u8ZW/0RywSDzD6jxhnUJCo0StfYlgDPaotkEJD5mgUxp15TyokTtEQD8IlGp+IIsVQyMH/Ct5SZZV8KbtjWyU82iXM4RNMlJFrLHn4+6/zujfathkcZCx0e0ak19+4K4meyFARH+QmnPaO1oiqnXi3vEerfD94g6070L5EnM6p/EkGKtEvQTilO4W9vVamiyqhDtt4RcIJlh5f4jTAUFhTwJLVuOvX6s254spvB2WE3Wo8XICIoz6hUVR4iWSeMMFvEarrDE24i9MgZHMAtTzdjxTZXDw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM7PR07MB6248.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d3d2f03a-d450-4dfc-f674-08d839e97fc0
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Aug 2020 09:17:10.5027 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4NsQ+nNWkR7tYClm20okm0J3qC10mlO91S2+5d+ORANeyEK3t4B5tuNVq5HnocQEKljh+PT36yd2KuEuyx/8tw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR07MB7012
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Hy84nI_x_WUBflG3dEK83D5wX3A>
Subject: Re: [Idr] some thoughts on draft-ietf-idr-bgp-model-09.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Aug 2020 09:17:15 -0000

From: Susan Hares <shares@ndzh.com>
Sent: 05 August 2020 12:17

Tom:

Thank you for the comments.    The history of the BGP model has a long
history and it a large project.    Your feeling is probably correct.. but
we'll try to address these issues.   The sub-modules were the wisdom at the
start of this work.

As to the missing references, we'll ask John to hold the start of WG LC
until we address your comments.  This model is also out at the Yang Doctors
to review prior to start of WG LC.

Sue, John

I floated the question of the benefits of submodules on the NETMOD list to which everyone, so far, except Mahesh, said there are none and should be removed from YANG 2.  This I-D would be easier for me to review without submodules; the fact that the submodule names must be registered with IANA and are not in this I-D suggests to me an incomplete grasp of submodules.  I will be interested to see what the YANG doctor says in this regard.

Apart from submodules, the other big showstopper to my comprehension is prefix, with inconsistent use of prefix and the wrong prefix being used for existing, published modules.  YANG allows you to change the prefix - 'YANG Guidelines ' does not.  Along with the use of br.. prefix, there are probably over 100 places in this I-D where the prefix must be changed to conform to the rules.  Look for example at routing policy where rpol: is (mis)used instead of rt-pol:

This could be an interesting Last Call.

Sue, I hope you can get away from it all for your vacation.

Tom Petch


I am on vacation this week and most of next week. I saw your emails and I
wanted to make sure you got a response.   I'll dig in once I'm back full
time.

Thanks for pointing things out.

Sue


-----Original Message-----
From: tom petch [mailto:ietfc@btconnect.com]
Sent: Monday, August 3, 2020 5:31 AM
To: Susan Hares; idr@ietf.org
Subject: some thoughts on draft-ietf-idr-bgp-model-09.txt

This I-d needs a significant amount of work; for me it has a slight flavour
of a large project that has been subcontracted out and now needs (more)
systems integration.

I note that it uses submodules extensively, not something I can recall
seeing in an IETF module.

The YANG references 32 documents - good - of which 11 are missing from the
I-D references - not good.

scharf-tcpm-yang-tcp is an import and so MUST be a Normative (think about
it; TCPM just published an I-D that started life 10 years ago, while NETCONF
started work on modelling TCP many years ago and have yet to reach WGLC).

Do submodule names need registering?
"   Names of submodules published in RFC streams [RFC4844] MUST be
   assigned by IANA; see Section 14 in [RFC6020]."
That's another 12 entries needed in IANA.

There are 11 include by date which means that more recent versions will not
be picked up and that there are 11 places where the RFC editor must insert
the right date, probably something they have not done before.

YANG allows freedom over the choice of prefix but exercising that freedom is
not always helpful.  'bgp' is the obvious choice for the main module.
Elsewhere, with main and ancillary modules, a common pattern is for the main
to be e.g. axy and the ancillary axy...

Two letter prefix are best reserved for widely imported modules - interfaces
comes to mind. 'bt' will be a familiar abbreviation to many in the IETF
while 'bp' will have a resonance for those living near the Gulf of Mexico.

A table of imports and prefix used aids comprehension.

derived-from-or-self suggests that you expect other protocol to derive an
identity from bgp; what do you have in  mind?

action to clear neighbours can be invoked by anyone; perhaps a security
exposure.  'These ... operations ...' seems incomplete.

Overall, I wonder at the use of submodules.  Greater size, greater
complexity, more difficult to review, probably more mistakes; what benefit
offsets this?

From: Idr <idr-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com>
Sent: 31 July 2020 17:42
To: idr@ietf.org
Subject: Re: [Idr] IPR call prior to WG LC for
draft-ietf-idr-bgp-model-09.txt