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

tom petch <ietfa@btconnect.com> Tue, 16 June 2020 08:42 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 5E8E13A1139; Tue, 16 Jun 2020 01:42:15 -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 BiygnT6zNpNC; Tue, 16 Jun 2020 01:42:13 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70103.outbound.protection.outlook.com [40.107.7.103]) (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 CACD83A1136; Tue, 16 Jun 2020 01:42:12 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=R2igflhSVAO9lJQ0NsqWO3EtUMeqpfgRs7EdbsArZSQxBajujYkzJemtv7j4IAUCZB4WJa2hZHAQH83BtK3aMJjEIudwWuR8yVST9c4xT5Qko83AypZJ7aXgwrhRJyJ6f5sVCqlumUm1FjIBRw2I1SM00xapZXJj3nBIoSDrFc7JW9H7PYUoTn4GQoddUhNAk4vdmGxx2E2st499c9CG3PzikfFSqpZX1youlULicwX1+9N670/E+GoZVNScXoSim+q3IZcORabqOVzUJ3RydIzihfvkvA6Jto4Acw1ONvMfiP+gxKx46Y9zGkLUqEQ7etlCvmUhT5cfYdK/Ov5Pcg==
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=2u1gSRAd+3RJ/5MdLToIyEtAFgEs4C7/RfifCbDcfFU=; b=jON1nFgvNMkPTCI9RfIOiySQ0iGmd0x4bhv5JekCYcQFx6JcIZXEE/Cpb+t0wf3/zDdjU77ZU+ZSpqeSUl3Vk9LNbopIcJLuPdNtQRNHAIgKEGGRgXnC8Uqd4neox50DiFXRtV0e57EUxTvwq3fGDPAl2SCJbm0//4xQGY88rSE0yYyWZshq/HEInA0D3IVa7N4N3XTsd1m6lonBr39PS+Zlg9958TJpmFWKt7/aTpDBq34gZdGWOOaowIf8/XRwUSkFXuXAdwzA+b+E6/DZWkZX7nuR9j0DacbC+MtylOzynGE0yEY+ELL2fkstBrIaI+vGydckXAudLmNSmkZO3Q==
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=2u1gSRAd+3RJ/5MdLToIyEtAFgEs4C7/RfifCbDcfFU=; b=NTMkn8w+QJPs3ZDvabyjntzjDJuhSLoaaOgLz8v0RfXIQ0l+Tv8O2iaRV4KSrcZTsC9Cvb/el4mYF3ZSmx0nkyqrRfPKE+dYUGWeEPr3NC6bHoxtT87xqJedGaMVh8bQjoFnt98I6Uih1x9pCYyI8Kb9oWo5RNmInoZCLcYFl5A=
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com (2603:10a6:10:69::25) by DB6PR0701MB2901.eurprd07.prod.outlook.com (2603:10a6:4:71::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.13; Tue, 16 Jun 2020 08:42:10 +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.3109.013; Tue, 16 Jun 2020 08:42:09 +0000
From: tom petch <ietfa@btconnect.com>
To: "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>, "teas@ietf.org" <teas@ietf.org>
CC: TEAS WG Chairs <teas-chairs@ietf.org>, Italo Busi <Italo.Busi@huawei.com>
Thread-Topic: I-D Action: draft-ietf-teas-yang-path-computation-09.txt
Thread-Index: AQHWQNW3/PO3N7NmdUe4cS/zY2X/gajZzklAgAEi5d0=
Date: Tue, 16 Jun 2020 08:42:09 +0000
Message-ID: <DB7PR07MB5340340D025E2A23C71EB5CDA29D0@DB7PR07MB5340.eurprd07.prod.outlook.com>
References: <159197894856.11807.5837352993917365680@ietfa.amsl.com>, <AM6PR07MB5222C7C2ED957AD873A0C372919C0@AM6PR07MB5222.eurprd07.prod.outlook.com>
In-Reply-To: <AM6PR07MB5222C7C2ED957AD873A0C372919C0@AM6PR07MB5222.eurprd07.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: nokia.com; dkim=none (message not signed) header.d=none;nokia.com; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [86.139.211.29]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4a81913c-e8e1-44da-c229-08d811d12895
x-ms-traffictypediagnostic: DB6PR0701MB2901:
x-microsoft-antispam-prvs: <DB6PR0701MB2901E37B2C365244AE07D63BA29D0@DB6PR0701MB2901.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 04362AC73B
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: XkeCyJwg9oX/5WsQb4Xb8HVR7acHxI2f4VyTWyWFmbPMQT2YSqxgs+1h8FLuWBtNVJCJx2nXE6DLYI/AAiEptPdpfhc6U/4Zjk66FNc54/2rAbhP4Y93fyAo+O9M4w1mu1MYensLS2fldsZXDdRISnCmlVepr+Sho39E81lJ2MV+vQZcJN8ZJkWVEg7aj8X4aXjjZDeRnTY1zEHdopCq4ek8x5c/9UnXd8k/9rgcv9dMPpb4pwQeTBKpoHwfW92wYyUNvB74Ua/vToJzZHXSa1BHTq325scgzqDZ47ZlmdkIH8GeVM0zeq0XGZocf2VvEHGrokYqNM5n4VejZTbRKwmTC1pYbcyJJMNudCdkFPv+x5uA7Qpomw64NJyCue8jo3W+eMlwfbWKh5cOEbNGJA==
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:(366004)(39860400002)(136003)(346002)(396003)(376002)(316002)(66446008)(296002)(966005)(4326008)(2906002)(110136005)(478600001)(186003)(54906003)(86362001)(83380400001)(6506007)(71200400001)(9686003)(55016002)(52536014)(64756008)(8676002)(66556008)(33656002)(53546011)(7696005)(91956017)(26005)(76116006)(8936002)(66946007)(66476007)(5660300002)(66574015); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: RkyG+gBFH5aj7Ya4T2PStqkClLHG0knywGBe5LymkLdSGkFCCQ9XWqD3/2j66oXKQfJI7STC619VYpALVOosM3wXK6SpFnUK1L9XgbBlCcO715roj4ww9whWdemVajTLWztG0nwzeTSQOWOdlLPot/v0YqPbJlH0dL6k/kbcfrLxf78NoXJKKTlT04wm6s2r5e97ZMQ/yuSB0ZEtzdj/q1nE6+hiQjJAxFLObch6QBE5ZPWQRFvWtJJ0D8DGfvbVEogSKrRkZQVR6ReTtVpGq/dTnXcR2z/Ja/k6qyDVtAzSiJz8PncDW7gtEjgW/UsozzFm6heeduIqWPtn57UURwVX3PWfzSfuojFYzvTyKzMwA5yYz0/DzN0QcQZ0MnrdGaxcX28hiZiqDa28EYauoSu/+c1iUfPOqajMB9ywM8xpIYMqrNPDVX3R8GuYClkfwbWoZfY5J05sKTHCkHOGAb9pBaM41VtacTi8jRiWjf4=
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-Network-Message-Id: 4a81913c-e8e1-44da-c229-08d811d12895
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Jun 2020 08:42:09.8496 (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: BnuKMQAD5gIbkCX7SD4PkxP2lOv6H2fGE2CvvrC3wOmmla+ApBiuslHSiKzKCS4H3/8Phl2wjHmYke8OV+Uapw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2901
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/RyqYuf2mxqSpwNNWINlMvkSU600>
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, 16 Jun 2020 08:42:15 -0000

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