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

Italo Busi <Italo.Busi@huawei.com> Thu, 11 July 2019 10:10 UTC

Return-Path: <Italo.Busi@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id ADCD41200D6 for <teas@ietfa.amsl.com>; Thu, 11 Jul 2019 03:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id A0bxGVR7JQhK for <teas@ietfa.amsl.com>; Thu, 11 Jul 2019 03:10:42 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (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 A0F9D120045 for <teas@ietf.org>; Thu, 11 Jul 2019 03:10:42 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id B4F8E5FE09E9B5AB3C93 for <teas@ietf.org>; Thu, 11 Jul 2019 11:10:40 +0100 (IST)
Received: from LHREML504-MBS.china.huawei.com ([]) by lhreml707-cah.china.huawei.com ([]) with mapi id 14.03.0415.000; Thu, 11 Jul 2019 11:10:36 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] I-D Action: draft-ietf-teas-yang-path-computation-06.txt
Thread-Index: AQHVNag9Jo1RbR17CkW14ehazSF1uKbFNkDw
Date: Thu, 11 Jul 2019 10:10:36 +0000
Message-ID: <91E3A1BD737FDF4FA14118387FF6766B27787ED1@lhreml504-mbs>
References: <156259753927.1064.12157099434189557512@ietfa.amsl.com>
In-Reply-To: <156259753927.1064.12157099434189557512@ietfa.amsl.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/hCuZod469wcVSne4KKMXVEprbZ4>
Subject: [Teas] FW: I-D Action: draft-ietf-teas-yang-path-computation-06.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: Thu, 11 Jul 2019 10:10:45 -0000

This version of the draft addresses the comments from Olivier about using the Path Computation YANG model in a flat/distributed network (open issue #61 in github).

Text in section 2 has been updated to clarify that the use of the Path Computation YANG model is not restricted to these use cases but can be used in any other use case when deemed useful.
Sections 2.4 and 2.5 have been added to described two additional use cases (thanks to Julien and Olivier).
No changes are required to the current YANG model.

The editors and Olivier are satisfy with these text changes.

Please review and send your comments to the list.

Sergio and Italo (on behalf of co-authors)

> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: lunedì 8 luglio 2019 16:52
> To: i-d-announce@ietf.org
> Cc: teas@ietf.org
> Subject: [Teas] I-D Action: draft-ietf-teas-yang-path-computation-06.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
> 	Filename        : draft-ietf-teas-yang-path-computation-06.txt
> 	Pages           : 73
> 	Date            : 2019-07-08
> 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 a stateless RPC to
>    request path computation. This model complements the stateful
>    solution defined in [TE-TUNNEL].
>    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-06
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation-
> 06
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-yang-path-computation-06
> 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/