Re: [Teas] I-D Action: draft-ietf-teas-yang-path-computation-09.txt

tom petch <ietfa@btconnect.com> Tue, 07 July 2020 11:01 UTC

Return-Path: <ietfa@btconnect.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57263A0B1C; Tue, 7 Jul 2020 04:01:19 -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 XTkYzQC2pGWR; Tue, 7 Jul 2020 04:01:17 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150091.outbound.protection.outlook.com [40.107.15.91]) (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 C22DD3A0B87; Tue, 7 Jul 2020 04:01:12 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cLU6Epuqag5+B7rGpAq2GszD2WNyxoyaYm/MCkf+8dKTWy3OyXNhzFTUSeZTyQKwToGuM0HsWYeajUO+mHerQTJFXDiNGr436C9yUE9gcxF12BG2lA4p0mZYTleclZXkiKIs+KA0dE8aWKY5Gfj4EqgaZ1gBlKFYt57H8X08Ug/PbYVke3mvRGMX/znssSvMwGFkKvSIjQCCwtMTBDec/STubWuLR4TqQ3LAdaf7lX/+3duSGpMSSKV6KJyiNI1Ekxw74G6OwDmpvi0HZvcL8le1fntWec8S4zyuXaRY3hVrNGl5ZWm6njwV1UDExhY+xTUiqFOFVGSRLskbrQ2iIw==
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=cTuz8D+6uL2tkdxwYMp0UpdSCILKwhA287eY4O690BU=; b=aH3fqfBhW5Yh883BndFdcBGt2mubRk0M4+cNjueDBiVoRp+G7SxEjLHgwl2FbN4VThsO8VgUODxGdpG2Yl3f6XiL+Joa3z3xCJueVTsaBU4PADNNiYNwQG5kUmU1HjOrBIDlET5zkuVYtKs9dagSUFhu3LmP65JsRtQEVF16eC0WccbGNt6vNlCnXJQojhB3ojYAolg/m0CdNIzkXpvqtCZlaIU8ZMAn1cYBao8QRs4LK3/7GapfMNH3pQYA25QDRfzITFxE16d6hzezvSIzh25+wnhBvbiqSimkLTDnTvs1ccbQ0hoHAuHVHQUGUm0E6u6q+rqH4VyC/0tL/nKRjQ==
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=cTuz8D+6uL2tkdxwYMp0UpdSCILKwhA287eY4O690BU=; b=hr1zMul0dvz4ef+eWsA16HB/DHdo024dovj8TWKSi5jthPlacwiskLG/sKl/HwH9XTiLUYsW1PaEyDNL6jb1N4sS4G6zMgjjwmWVlSH+7B77ajOWS6H5hf935ld7KSJTkAXP8QfQAFaHT13aG47KTEnfWA4SPnMia6vKuuNWjOo=
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com (2603:10a6:10:69::25) by DB7PR07MB4988.eurprd07.prod.outlook.com (2603:10a6:10:6b::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.17; Tue, 7 Jul 2020 11:01:09 +0000
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com ([fe80::f911:a06:2f4e:a103]) by DB7PR07MB5340.eurprd07.prod.outlook.com ([fe80::f911:a06:2f4e:a103%4]) with mapi id 15.20.3174.020; Tue, 7 Jul 2020 11:01:09 +0000
From: tom petch <ietfa@btconnect.com>
To: Italo Busi <Italo.Busi@huawei.com>, "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>, "teas@ietf.org" <teas@ietf.org>
CC: TEAS WG Chairs <teas-chairs@ietf.org>
Thread-Topic: I-D Action: draft-ietf-teas-yang-path-computation-09.txt
Thread-Index: AQHWQNW3/PO3N7NmdUe4cS/zY2X/gajZzklAgAEi5d2AIQra8IAAGXE2
Date: Tue, 7 Jul 2020 11:01:09 +0000
Message-ID: <DB7PR07MB53406FC305C54E5ACCFB6010A2660@DB7PR07MB5340.eurprd07.prod.outlook.com>
References: <159197894856.11807.5837352993917365680@ietfa.amsl.com>, <AM6PR07MB5222C7C2ED957AD873A0C372919C0@AM6PR07MB5222.eurprd07.prod.outlook.com> <DB7PR07MB5340340D025E2A23C71EB5CDA29D0@DB7PR07MB5340.eurprd07.prod.outlook.com>, <3fba272cce3144fc9d5c24970297a128@huawei.com>
In-Reply-To: <3fba272cce3144fc9d5c24970297a128@huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.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: 0b9a94ca-a8dc-4e07-dea5-08d822650e42
x-ms-traffictypediagnostic: DB7PR07MB4988:
x-microsoft-antispam-prvs: <DB7PR07MB49882001F30A3CF1DBF5BB01A2660@DB7PR07MB4988.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: /VuQQ8VqH4V0VpQo9slQh5sJtRaV2rYD/97OMJFl3CQPJPDawQGzpLqqcvKFN/kjhrlED9kZcesqaM0050TscQyJzDXl5ybVRiJZ4ZfKptIPxQjyoCzpwRaIkYXV2EPqmaXFCWIc2RAFzmrUnP0w5qL9yEy7FfE88KyxWnR8J3PHiCGZf3Qqh4tKv60B+2h1RBT2J3lm0lyubbj0zGFzGemqJmPrKFCd6+Pvoq3YxODFwVhITe1WHb6l8pEKZcWC/mO7g8b9rBLFETFbfq8j1u/iAhjftfJ1LA15zJ2HnO+ozuVNkplkit9KRQSKaqHfIreeYUKyWX5FbQWF8cgzjgtPzgIJuSXj+EfXkTlkqxox5QlwE3cWVz1PJfvICzjPNl9osbTwRExUgZ3rvzX1PQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR07MB5340.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(39860400002)(136003)(366004)(346002)(396003)(376002)(86362001)(9686003)(33656002)(71200400001)(4326008)(186003)(8676002)(26005)(110136005)(8936002)(83380400001)(316002)(66574015)(966005)(478600001)(55016002)(7696005)(76116006)(5660300002)(66946007)(91956017)(52536014)(66476007)(66556008)(64756008)(66446008)(2906002)(6506007)(53546011); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: VSvUwR3XcKRaEwTaYjUl+wGuh41s/39xkoE4gufbsldDGkvllNyrkEsJlCBxhMlLF15t3WCRe1HwKJLDKjJliWf5UuIq4kWUFRjrefmHJIRN7kCuz1vn/mNbmUXIozahhgqhIFpKLK8d0CzIEpmrXB0zQiSkNRHJv/r3uy7EjKF8W9nrEoELy7EHVrDPMvHJNbLB+vN2qCqnt+11r8Q8Pn2aOUzqUecjF0jsfyhT0TrbE1Z+fxqOIIUBLEy4SDgIgBU9a4WJ9fNLfCZmNg6OGKAEYko3xG+0fyjmgk4uHB1vEIe6UfPtj366vL6kVezfW2/DfhZkXiEvObSRgH3dhAMRyfsO1ysL7WbXrYnIES99h7X2Wv97YAS0mem0xoOi+0ZpmrFPRxOtG6AFbKE2541gNmyueyJRa7ghUZCwlelt2Rx6BblTghdika9aQ457kP5K1rRZLlicvhUVGr06leprawPoFhEywNoBfYj+Pmc=
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: DB7PR07MB5340.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0b9a94ca-a8dc-4e07-dea5-08d822650e42
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jul 2020 11:01:09.7640 (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: 271TOr02vqaBUlC8mna/MeiLqmVeg8dDhtmh3lCmQO6Pb1e1180wqUTZBpoRLE+z3Nw+6LjMCpVVue+wybl2TQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB4988
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/n6W6I8v9btr2QdKJ9bY0IU34dvo>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-yang-path-computation-09.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2020 11:01:20 -0000

From: Italo Busi <Italo.Busi@huawei.com>
Sent: 07 July 2020 10:34

Hi Tom,

The length and complexity of the document seems a bit unavoidable considering the complexity of the problem statement (computing paths for TE tunnels which can be unidir/bidir/co-routed/protected/restored/...)

Regarding the open issue depending on te-types, we can remove the comment pending on updated on te-types since it is already an RFC and leave the encoding-and-switching-type and tunnel-common-attributes groupings in this model.

We think that the content of the draft is quite stable and that few minor changes regarding the YANG code are needed to address the pending open issues.

We would like to get some feedbacks from the WG and YANG experts during YANG doctor review and/or WG LC to address them.

<tp>
OK.  For a start

RFC 3945 needs adding to I-D References

ds or datastore?  I like consistency

RPC are validated against <operational>
as NMDA says. RPC are never configuration.  I think that 
/te:input/
is required in the path.

Indentation of section headings  in the text is inconsistent second level more than third.

I-D authors and YANG authors are different

IANA URI needs a contact

Most of the I-D references lack a DOI

Tom Petch

Sergio and Italo

> -----Original Message-----
> From: tom petch [mailto:ietfa@btconnect.com]
> Sent: martedì 16 giugno 2020 10:42
> To: Belotti, Sergio (Nokia - IT/Vimercate) <sergio.belotti@nokia.com>om>;
> teas@ietf.org
> Cc: TEAS WG Chairs <teas-chairs@ietf.org>rg>; Italo Busi
> <Italo.Busi@huawei.com>
> Subject: Re: I-D Action: draft-ietf-teas-yang-path-computation-09.txt
>
> From: Teas <teas-bounces@ietf.org> on behalf of Belotti, Sergio (Nokia -
> IT/Vimercate) <sergio.belotti@nokia.com>
> Sent: 15 June 2020 16:23
>
> we have updated the path computation RPC model to:
> - align with the latest version of the TE tunnel YANG model
> (https://tools.ietf.org/html/draft-ietf-teas-yang-te-23)
> - add support of path computation for protected paths (as discussed in IETF
> 104)
> - add support of path computation for bidirectional paths
> - returning errors in case path computation fails
> - add support for multi-layer path computation
>
> The changes to the YANG model are described in section 5.3 and 5.4 of the 09
> version of the draft.
>
> <tp>
> Try again.
>
> I had a look a the I-D (big, complicated:-) and see a number of open issues,
> require-instance, RPC reference, waiting for a te-types update!
>
> What do you plan to do about those?
>
>  I have not tracked the progress of this I-D and would like it to be +-stable
> before investing too  much time in it (having wasted an ocean on the unstable
> teas-te:-(
>
> Tom Petch.
>
>
>
> We think that with these changes the model is now ready for YANG doctor
> review, however due to the significant amount of changes we would
> appreciate a review from the WG before asking YANG doctor review.
>
> Thanks
> Italo and Sergio (as editors)
>
> -----Original Message-----
> From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of internet-
> drafts@ietf.org
> Sent: Friday, June 12, 2020 6:22 PM
> To: i-d-announce@ietf.org
> Cc: teas@ietf.org
> Subject: I-D Action: draft-ietf-teas-yang-path-computation-09.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Traffic Engineering Architecture and Signaling
> WG of the IETF.
>
>         Title           : Yang model for requesting Path Computation
>         Authors         : Italo Busi
>                           Sergio Belotti
>                           Victor Lopez
>                           Anurag Sharma
>                           Yan Shi
>         Filename        : draft-ietf-teas-yang-path-computation-09.txt
>         Pages           : 94
>         Date            : 2020-06-12
>
> Abstract:
>    There are scenarios, typically in a hierarchical SDN context, where
>    the topology information provided by a TE network provider may not
>    be sufficient for its client to perform end-to-end path computation.
>    In these cases the client would need to request the provider to
>    calculate some (partial) feasible paths.
>
>    This document defines a YANG data model for an RPC to request path
>    computation. This model complements the solution, defined in
>    RFCXXXX, to configure a TE Tunnel path in "compute-only" mode.
>
>    [RFC EDITOR NOTE: Please replace RFC XXXX with the RFC number of
>    draft-ietf-teas-yang-te once it has been published.
>
>    Moreover this document describes some use cases where a path
>    computation request, via YANG-based protocols (e.g., NETCONF or
>    RESTCONF), can be needed.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-teas-yang-path-computation/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-teas-yang-path-computation-09
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation-
> 09
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-yang-path-computation-09
>
>
> 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
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas