IETF Logo Mail Archive

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

tom petch <ietfc@btconnect.com> Mon, 03 August 2020 09:31 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 06B873A0D18 for <idr@ietfa.amsl.com>; Mon, 3 Aug 2020 02:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[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 GOSOJDk3xoLO for <idr@ietfa.amsl.com>; Mon, 3 Aug 2020 02:30:58 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80111.outbound.protection.outlook.com [40.107.8.111]) (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 4A8013A0D19 for <idr@ietf.org>; Mon, 3 Aug 2020 02:30:57 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KgiuvdFXDCPP4ZPcmHchtqIg5iM0lQNnreiGuPe/TW2wUO5Z8c6E6oQIyWmIU0y/4qsRK5+oi/4FScPWhFqARJFZOuQ9au2IUxh5Quvg+xULk7w+uOLY7G+dbeBUI/S7H/MTLMHfSFAFGZ3Q27JtrXUJaxOSkVi3ok979hcADW8EJuzmg8TwPRQvtY8NubyRorp1/ovhXkz5bsE8yBhpDu6+w53nLXnApZjsS3JUr7N8nmk08/CGVGKeMYDmoOhwhmGwXk98OmAQENJBRvUSY7ph8sJExW7YnbQhgq8DRKqEgiMS31McXWw+BRN+FhYIZ2t9Iu0UuP67aVYx8FbJ7w==
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=KG04wJejlnra0iz471F55dWfB/m6rehB18NPTg0Y0Lo=; b=AM0GOAr+OJzyhQ/MeqvMBiTYwrTfrXKMWuYnRz3oBFIBjKCAeQxz92sPfiPt7j9FTZwsdSo0F9YAMarjyP3AsX/IfkznWrmlX5hJwgZSJeLWpCkcL+GQ/JV6v6wkm25zsjPno7ih+tzJ7hXRypUXB/iA+whsadfW7b/QpP+SBY6IzWuUHN1Y9hwR4tbTzJKSDMJAxTQb/4zycBUJ8i6MwGayLYjaZ5A9e95e/l4fD9LTkCsPxASX4uy/NLvGA246f8h+82Y82ath9XtYAJqQ8sqmkQ+0SqbG3iZXAqturoJ4Nod9orD5BwFclDQulIjoH0+k0eLKPHQr0EmjJQOfXQ==
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=KG04wJejlnra0iz471F55dWfB/m6rehB18NPTg0Y0Lo=; b=q2g1hKVSjopkn0Gi/kR4KUkmkKNUc4UQjqTnb8t8QT1Yb13HTdpP2HgB8ZN7sKqOqBLH+Ar0akeyf8ri7iHjN0Kh9GQYpxld0Fv65yPqaezh75sH90sTtOkozbo+YguNTWRmthvvI/v7abRFPxpev7AI7qMCJzC8lzt9MbzQ8i8=
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com (2603:10a6:20b:134::11) by AM5PR0701MB2771.eurprd07.prod.outlook.com (2603:10a6:203:77::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.13; Mon, 3 Aug 2020 09:30:55 +0000
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::893c:ca97:acbf:1c76]) by AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::893c:ca97:acbf:1c76%5]) with mapi id 15.20.3239.021; Mon, 3 Aug 2020 09:30:55 +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: AQHWaXjJOhsnFoSdhUyxiufGjgmlVQ==
Date: Mon, 03 Aug 2020 09:30:55 +0000
Message-ID: <AM7PR07MB62485BC88F847F9EFE88CB1AA04D0@AM7PR07MB6248.eurprd07.prod.outlook.com>
References: <005401d6659d$31ad4c40$9507e4c0$@ndzh.com> <133E5D36-A696-4314-8588-7992E52D190B@gmail.com>, <007101d66759$938f7150$baae53f0$@ndzh.com>
In-Reply-To: <007101d66759$938f7150$baae53f0$@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: 03a32b40-5a94-445a-dcfb-08d8378fec12
x-ms-traffictypediagnostic: AM5PR0701MB2771:
x-microsoft-antispam-prvs: <AM5PR0701MB2771EC5B41486FDDBCC76E25A04D0@AM5PR0701MB2771.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: CMHfMumLg9/4nO263A3QP2gLpqyC17jgRpJO3D5IioTL9n+MIcHxfIHZ+toogG7fRnEOIhTdkMn1uQvnrTcqsz0s2/LUtU6pS4s8diidqe9jG/snrMzqEyWyrOwwmj6NFfmI3w0uOl1fSMsIPnWQfu6tsIjdXUIP+fdZd7rh1WyZ+kguQ119a5bTImTkDHofRT3/DWHTroLNYToNDu3Me6XEVHPibrL6+Q3fxt1N0KTIMy6Kb3IS1mk3nkJ9xO3n79r3RMqPov7AOz/V08do2Ns3lgR3aVqF5J3ioRhI7fZffZyr1ABDB+5X424QBMviq7qTAq8bumNTYIzm0ayhHg==
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)(366004)(376002)(346002)(136003)(39860400002)(2906002)(8676002)(71200400001)(186003)(33656002)(478600001)(7696005)(83380400001)(86362001)(76116006)(66946007)(5660300002)(66476007)(66556008)(66446008)(64756008)(9686003)(26005)(8936002)(110136005)(55016002)(316002)(52536014)(6506007)(53546011)(91956017); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: S0eUqsjvAxKC+NGXcCbMkiUOvZ94jzJeaCHNTFHaYPXPemOchZP+QUpNocru8VpoXzch6LIfryBgrjxgWRb5njxfheFzah5D0ULN96E1moS9COVoRYjVicZjRF7lHTtrgvCsbORtkzXFFoyIJZnIDClW8JrxcHJxul2v0VQycuBLX99+tHYjIoTagX6hdeFot5q+ZcqdsMg6oi9EYStuRs+3QCgp5ou1F+2u3F0YEd4qpILc5maC59Gl8pSeqJLAMp5FFbL+yfF1zuvSIjbQUjuo75KXs5D/yQLiJYMLnASvFF0tnULktFDVWE9TcTWL4x197p0Xev9Q905gLXYgSzAflgxaTEpNMqsYooTO9UtPPlLj0cvZIRf4aJBb+kpedwQyHd1rUHdg/NpRoVGPJCxTXPVRN1j8LYNh9s/T2HasmyYZ8vRJwq7tw+6AVvhPdqTZwTMvLoG9mOmfHpr1a6q+J9TFPIcdEJzVPJ8B0tD88gFDSjjM/wGYVOwRwC4e+bPfMgBNlsJOJOmRmXsOck6kHR+5wE/P7ViliRKyWIHkQRxGhWpnbqAlrkfg3nALAfvaLzJwC3usRPEUtbzQWAaoPj2s2y12vF48+DKdozbovf+MNd5kRt9vRq7e0EqeQDRtWmp7aexAv7FbLJKPJA==
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: 03a32b40-5a94-445a-dcfb-08d8378fec12
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Aug 2020 09:30:55.2151 (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: +nn1CTb8GO1DBgZZLHdTxZvNLhAPsYOgTIbAIZz/8jzQwIY/xDpG0XYSWBdeyTd9BdGZ8JfRli1x8X7xjwbyNw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2771
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/FnSzRjQ4LS4Ek4gQoIZ4CoId7Tc>
Subject: [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: Mon, 03 Aug 2020 09:31:00 -0000

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

v2.23.0 | Report a Bug | By Email