From: tom petch <ietfa@btconnect.com>
To: "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>
CC: TEAS WG Chairs <teas-chairs@ietf.org>, Italo Busi <Italo.Busi@huawei.com>, 
 "teas@ietf.org" <teas@ietf.org>
Thread-Topic: I-D Action: draft-ietf-teas-yang-path-computation-09.txt
Thread-Index: AQHWQNW3/PO3N7NmdUe4cS/zY2X/gajZzklAgAADaziAAAf9MIAABwpo
Date: Mon, 15 Jun 2020 16:24:40 +0000
Message-ID: <DB7PR07MB534050EBEECDD8EB5987343AA29C0@DB7PR07MB5340.eurprd07.prod.outlook.com>
References: <159197894856.11807.5837352993917365680@ietfa.amsl.com>,
 <AM6PR07MB5222C7C2ED957AD873A0C372919C0@AM6PR07MB5222.eurprd07.prod.outlook.com>
 <DB7PR07MB53403D4C6E342ED397D97438A29C0@DB7PR07MB5340.eurprd07.prod.outlook.com>,
 <AM6PR07MB522244B081B3859328B81A05919C0@AM6PR07MB5222.eurprd07.prod.outlook.com>
In-Reply-To: <AM6PR07MB522244B081B3859328B81A05919C0@AM6PR07MB5222.eurprd07.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2d1c4970-6a13-4859-f632-08d811489ac5
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jun 2020 16:24:40.3598 (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: V/AqJ4I+gkGVzl8Krj1pvX2b5h9jzKAd/4RvSn4Qz6QaOdV4AY+jjOeB+09MzW5IeYz7/CPxnIZ+ttQ5/docwQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBAPR07MB6773
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/cVB4kZcv0akXI2TYMz-8h5Ooi88>
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: Mon, 15 Jun 2020 16:24:45 -0000

From: Belotti, Sergio (Nokia - IT/Vimercate) <sergio.belotti@nokia.com>=0A=
Sent: 15 June 2020 17:02=0A=
To: tom petch=0A=
Cc: TEAS WG Chairs; Italo Busi; teas@ietf.org=0A=
Subject: RE: I-D Action: draft-ietf-teas-yang-path-computation-09.txt=0A=
=0A=
-----Original Message-----=0A=
From: tom petch <ietfa@btconnect.com>=0A=
Sent: Monday, June 15, 2020 5:31 PM=0A=
To: Belotti, Sergio (Nokia - IT/Vimercate) <sergio.belotti@nokia.com>; teas=
@ietf.org=0A=
Cc: TEAS WG Chairs <teas-chairs@ietf.org>; Italo Busi <Italo.Busi@huawei.co=
m>=0A=
Subject: Re: I-D Action: draft-ietf-teas-yang-path-computation-09.txt=0A=
=0A=
From: Teas <teas-bounces@ietf.org> on behalf of Belotti, Sergio (Nokia - IT=
/Vimercate) <sergio.belotti@nokia.com>=0A=
Sent: 15 June 2020 16:23=0A=
=0A=
Dear TEASers,=0A=
=0A=
we have updated the path computation RPC model to:=0A=
- align with the latest version of the TE tunnel YANG model (https://tools.=
ietf.org/html/draft-ietf-teas-yang-te-23)=0A=
=0A=
<tp>=0A=
teas-yang-te is no more - it is an RFC:-)=0A=
=0A=
<Sergio> Hi Tom, that is our hope asap, but now for the moment. Maybe you w=
ere referring to te-types , now RFC 8776 ?=0A=
=0A=
<tp>=0A=
Whoops, you are correct and I am wrong,  mixing the two and you have the co=
rrect reference in the I-D.  Sorry about that=0A=
=0A=
Tom Petch,=0A=
=0A=
=0A=
=0A=
=0A=
I have yet to check whether or not it is the same.  I will look again at yo=
ur I-D but may be not this week.=0A=
=0A=
<Sergio> Thanks=0A=
=0A=
=0A=
=0A=
=0A=
Tom Petch=0A=
(not a YANG Doctor)=0A=
=0A=
- add support of path computation for protected paths (as discussed in IETF=
 104)=0A=
- add support of path computation for bidirectional paths=0A=
- returning errors in case path computation fails=0A=
- add support for multi-layer path computation=0A=
=0A=
The changes to the YANG model are described in section 5.3 and 5.4 of the 0=
9 version of the draft.=0A=
=0A=
We think that with these changes the model is now ready for YANG doctor rev=
iew, however due to the significant amount of changes we would appreciate a=
 review from the WG before asking YANG doctor review.=0A=
=0A=
Thanks=0A=
Italo and Sergio (as editors)=0A=
=0A=
-----Original Message-----=0A=
From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of internet-dr=
afts@ietf.org=0A=
Sent: Friday, June 12, 2020 6:22 PM=0A=
To: i-d-announce@ietf.org=0A=
Cc: teas@ietf.org=0A=
Subject: I-D Action: draft-ietf-teas-yang-path-computation-09.txt=0A=
=0A=
=0A=
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.=0A=
This draft is a work item of the Traffic Engineering Architecture and Signa=
ling WG of the IETF.=0A=
=0A=
        Title           : Yang model for requesting Path Computation=0A=
        Authors         : Italo Busi=0A=
                          Sergio Belotti=0A=
                          Victor Lopez=0A=
                          Anurag Sharma=0A=
                          Yan Shi=0A=
        Filename        : draft-ietf-teas-yang-path-computation-09.txt=0A=
        Pages           : 94=0A=
        Date            : 2020-06-12=0A=
=0A=
Abstract:=0A=
   There are scenarios, typically in a hierarchical SDN context, where=0A=
   the topology information provided by a TE network provider may not=0A=
   be sufficient for its client to perform end-to-end path computation.=0A=
   In these cases the client would need to request the provider to=0A=
   calculate some (partial) feasible paths.=0A=
=0A=
   This document defines a YANG data model for an RPC to request path=0A=
   computation. This model complements the solution, defined in=0A=
   RFCXXXX, to configure a TE Tunnel path in "compute-only" mode.=0A=
=0A=
   [RFC EDITOR NOTE: Please replace RFC XXXX with the RFC number of=0A=
   draft-ietf-teas-yang-te once it has been published.=0A=
=0A=
   Moreover this document describes some use cases where a path=0A=
   computation request, via YANG-based protocols (e.g., NETCONF or=0A=
   RESTCONF), can be needed.=0A=
=0A=
=0A=
The IETF datatracker status page for this draft is:=0A=
https://datatracker.ietf.org/doc/draft-ietf-teas-yang-path-computation/=0A=
=0A=
There are also htmlized versions available at:=0A=
https://tools.ietf.org/html/draft-ietf-teas-yang-path-computation-09=0A=
https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation=
-09=0A=
=0A=
A diff from the previous version is available at:=0A=
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-teas-yang-path-computation-0=
9=0A=
=0A=
=0A=
Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.=0A=
=0A=
Internet-Drafts are also available by anonymous FTP at:=0A=
ftp://ftp.ietf.org/internet-drafts/=0A=
=0A=
=0A=
_______________________________________________=0A=
I-D-Announce mailing list=0A=
I-D-Announce@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/i-d-announce=0A=
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ie=
tf.org/ietf/1shadow-sites.txt=0A=
=0A=
_______________________________________________=0A=
Teas mailing list=0A=
Teas@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/teas=0A=