Re: submission of I-D draft-ietf-rtgwg-yang-rip

tom petch <ietfa@btconnect.com> Fri, 30 August 2019 10:33 UTC

Return-Path: <ietfa@btconnect.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 001E3120C21; Fri, 30 Aug 2019 03:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.247
X-Spam-Level:
X-Spam-Status: No, score=0.247 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 WcoEajQS63fH; Fri, 30 Aug 2019 03:33:27 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00114.outbound.protection.outlook.com [40.107.0.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F149A120918; Fri, 30 Aug 2019 03:33:26 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=J3ZaXUCa6qHys1pwvD9PoK6/sljtbLAFRwmtJzbMzcnk1GIU3mif2Ja1k2N4SSSTQHoYxVQZJxUsUbmZG3ECIu3SY3F6WClcQ0jYhHKP52VwmHxW1ltVrHvVnZYvKDaaj+uPERPbC9vCrYyr1XE1d6Sf4uskj1Uvx90nbT5Hb5Vxl6KgjtNZ+RuFIMHEmPuIsBFtcvuju786i6eRYGShfuFU/Llnhg1qQNEGS3CuNkVqzNaQuNVdehIbCMta78ZeyksPX4YBV2MNAC8pMAnm1j83+NH0gMIg0o7iL3l07mpbrG5rZpEfS6SdDDB2rb2ljFeFs8aFclhYQSuaZqRtyA==
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=x9h1VtkjxGtI8uI2lMetEEWaaRk4/BkyBniEKI2Ums8=; b=ZHYghZSoLzxi31iRi/uOb1iT2PU7s0JKM9uUeGiOAqzBiBaz9ie9LZmhi8We18OAqYy+uJax5uWhi/1MFRLj/t4xdniqf7OgKtmPdQrY8tlT9uOYRCUdd96Z9HDeI7MYjL3HyfY74VOYfbdf0D/lEc2WBaoZPa6MSyDy3opqPqmdSsZRHHffJjvKa87AbLR+ErPKmN3cvAkagdapXIKu1t6QdWxc+YCV28q9QERISQi+SfVHr3EK3Vx1lsf+JXYan1OCK8zVuf/FBvxxeod+WDRar3mBpK55nCm8cWDxzJeZoHVOC2O6gPEIsKE23FymuU0fBVfj1ylDfnf3pI+87w==
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=x9h1VtkjxGtI8uI2lMetEEWaaRk4/BkyBniEKI2Ums8=; b=lrof/wW7jTCFKEkxCjxntS662zbU5hrf6k2zXhzwN94uFT7om0BooqROWXMKeoBc3JQjRWfvgO7hV6q5vh++CGWnm5+ARH1HYK8QAIXxfJhXXb3GjusBctHZHQCviAVdppicmN7jM2G7WkrR0hdWu8cpXqeyQRuQ0pEm3z/9Djg=
Received: from DB7PR07MB5451.eurprd07.prod.outlook.com (20.178.45.149) by DB7PR07MB4474.eurprd07.prod.outlook.com (52.135.141.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.14; Fri, 30 Aug 2019 10:33:24 +0000
Received: from DB7PR07MB5451.eurprd07.prod.outlook.com ([fe80::2489:e7f4:2d1e:a819]) by DB7PR07MB5451.eurprd07.prod.outlook.com ([fe80::2489:e7f4:2d1e:a819%5]) with mapi id 15.20.2241.006; Fri, 30 Aug 2019 10:33:24 +0000
From: tom petch <ietfa@btconnect.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>
CC: Xufeng Liu <xufeng_liu@jabil.com>, Prateek Sarda <prateek.sarda@ericsson.com>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, Vikram Choudhary <vikschw@gmail.com>
Subject: Re: submission of I-D draft-ietf-rtgwg-yang-rip
Thread-Topic: submission of I-D draft-ietf-rtgwg-yang-rip
Thread-Index: AQHVXx5avoL4UtawnkyDdY8jYtM9og==
Date: Fri, 30 Aug 2019 10:33:24 +0000
Message-ID: <038801d55f1e$2bf60a20$4001a8c0@gateway.2wire.net>
References: <156702929351.1132.12424099863960540517.idtracker@ietfa.amsl.com> <3DB595EF-B912-4C75-9529-34F2026F47BE@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0368.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a3::20) To DB7PR07MB5451.eurprd07.prod.outlook.com (2603:10a6:10:76::21)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfa@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.211.103]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9bff23bc-dbf8-4a4d-aa2a-08d72d357c81
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DB7PR07MB4474;
x-ms-traffictypediagnostic: DB7PR07MB4474:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DB7PR07MB447496C6625FB02F42321A27A2BD0@DB7PR07MB4474.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 0145758B1D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(346002)(136003)(39860400002)(376002)(13464003)(189003)(199004)(478600001)(5660300002)(6486002)(110136005)(54906003)(4720700003)(6436002)(1556002)(8676002)(86362001)(7736002)(44736005)(81156014)(81166006)(44716002)(62236002)(2906002)(14454004)(66066001)(229853002)(486006)(476003)(52116002)(8936002)(61296003)(14444005)(446003)(14496001)(99286004)(256004)(305945005)(6246003)(71190400001)(102836004)(66946007)(186003)(66446008)(53546011)(81686011)(25786009)(76176011)(81816011)(53936002)(6506007)(64756008)(386003)(66556008)(316002)(50226002)(9686003)(4326008)(71200400001)(6512007)(3846002)(66476007)(6116002)(6306002)(26005)(966005)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB4474; H:DB7PR07MB5451.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ulDKRxM9OwVWI63673oBrswfgOAQzUqtWopXmwebeRD7Lr9J3G/jpBWTKuEEel7turYUqN057wFMtJo5sn6LeyooHXpMybuVoQ0gz44lBKXsOAUTEuXupLxSPEkhSeMCyA0XvYFCcjsUF8mc7XaMYqpcpJnREQvON8mT9Q9SU13vME/HqM18cRBQrNpFsYGnk4lckSBn16UkQZv3bJb3GztMk+m/Q9X7cNVvgi2k458oKz7JcYrb+0e8yFQQbo2wMHhGEJGNWOAc3cu1W/lHe92qQkKd7NiQkeiVhD3KqeAMD3Nec5oBF+Ze1R1e5rzRkUjMGs85xz89aJ/Crd/WdK3M6ByQpkUamCtXwYeP+kG3mEjfy05ebB36/SdZA+gx3HJJKOcapm85vdAkmfxCPwS1+94c0ia6pi7ft2nmP3Q=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E9EED24B97A8594298213722950F1B93@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9bff23bc-dbf8-4a4d-aa2a-08d72d357c81
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Aug 2019 10:33:24.5341 (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: vVnfyjOMFQp1LYtZqUTXsH+8sQKLpRfXWwBCRrCR1dWEtRgyzBC40k3u62Y5qK/yDRvzFXgjDlGWeLNIUlwduA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB4474
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/e8_bwUq9ix1eK6OPi5gilYMItNw>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2019 10:33:29 -0000

and while you are at it;

RFC2119 boiler plate is out of date.

no note to RFC Editor asking them to replace the dates in the YANG
module

YANG module woefully short of references - about 15 needed; this to me
is a show stopper, i.e. puts me off a more detailed review

curious use of identities for RIP - most protocols have a base identity
for any flavour of the protocol and then derive further identities for
particular versions

in light of which, the introduction leaves me uncertain about support
for RIP v1

curious use of derived-from-or-self in many places - if the condition is
for e.g. ripng, then why not a simple equality?

/cooresponding /corresponding/

for IANA considerations RFC7950 is not a good reference since all it
says is go read RFC6020

Tom Petch


----- Original Message -----
From: "Jeff Tantsura" <jefftant.ietf@gmail.com>
Sent: Thursday, August 29, 2019 5:04 AM

> Dear co-authors,
>
> Please fix YANG validation errors and re-submit.
>
> Regards,
> Jeff
>
> > On Aug 28, 2019, at 14:54, IETF I-D Submission Tool
<idsubmission@ietf.org> wrote:
> >
> >
> > Hi,
> >
> > The IETF datatracker draft submission service has received your
draft
> > draft-ietf-rtgwg-yang-rip-11, and requires a
> > confirmation step in order to be able to complete the posting of
> > the draft.
> > Please follow this link to the page where you can confirm the
posting:
> >
> >
https://datatracker.ietf.org/submit/status/106193/confirm/a680bfc6b2d12c
d346dac00b89b0daa2/
> >
> >
> > Best regards,
> >
> >    The IETF Secretariat
> >    through the draft submission service
> >
> >
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg