[Teas] FW: New Version Notification for draft-ietf-teas-yang-path-computation-03.txt

Italo Busi <Italo.Busi@huawei.com> Tue, 23 October 2018 12:16 UTC

Return-Path: <Italo.Busi@huawei.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 2E9E2130E35 for <teas@ietfa.amsl.com>; Tue, 23 Oct 2018 05:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 V6t27ZW-NmmJ for <teas@ietfa.amsl.com>; Tue, 23 Oct 2018 05:16:53 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 93051130E7A for <teas@ietf.org>; Tue, 23 Oct 2018 05:16:53 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E68AE34305E24 for <teas@ietf.org>; Tue, 23 Oct 2018 13:16:47 +0100 (IST)
Received: from LHREML504-MBS.china.huawei.com ([10.201.109.59]) by lhreml703-cah.china.huawei.com ([10.201.108.44]) with mapi id 14.03.0415.000; Tue, 23 Oct 2018 13:16:46 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-teas-yang-path-computation-03.txt
Thread-Index: AQHUaiBz40A2CBRicUGEk6zgFcEJWqUsvoAw
Date: Tue, 23 Oct 2018 12:16:46 +0000
Message-ID: <91E3A1BD737FDF4FA14118387FF6766B1590ABD1@lhreml504-mbs>
References: <154022406175.6304.1005965173385368438.idtracker@ietfa.amsl.com>
In-Reply-To: <154022406175.6304.1005965173385368438.idtracker@ietfa.amsl.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.246.81]
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/t5R8nsGhsIx6VOddyu6J5s4Y6lY>
Subject: [Teas] FW: New Version Notification for draft-ietf-teas-yang-path-computation-03.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, 23 Oct 2018 12:16:57 -0000

Dear TEAS WG,

We have just uploaded a revised version of the I-D. The main changes are:

- new text based on the mailing list and offline discussions to clarify that the path being setup is not necessarily the same as the computed path and therefore that a path verification phase is needed to check that the actual path being setup meets the required end-to-end metrics and constraints (thanks to all who contributed to the mailing list discussion and to Dhruv for the suggestion about the path verification)
 
- YANG model updates to allow requesting the path srlgs and affinities being returned together with the result of path computation

We welcome further review and comments from the WG

Thanks, Sergio and Italo (on behalf of co-authors)

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, October 22, 2018 6:01 PM
To: Ricard Vilata <ricard.vilalta@cttc.es>;; Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>;; Oscar Gonzalez de Dios <oscar.gonzalezdedios@telefonica.com>;; Michael Scharf <michael.scharf@gmail.com>;; Oscar de Dios <oscar.gonzalezdedios@telefonica.com>;; Yan Shi <shiyan49@chinaunicom.cn>;; Ricard Vilalta <ricard.vilalta@cttc.es>;; Sergio Belotti <sergio.belotti@nokia.com>;; Victor Lopezalvarez <victor.lopezalvarez@telefonica.com>;; Victor Lopez <victor.lopezalvarez@telefonica.com>;; Italo Busi <Italo.Busi@huawei.com>;; Anurag Sharma <ansha@google.com>;; Karthik Sethuraman <karthik.sethuraman@necam.com>;
Subject: New Version Notification for draft-ietf-teas-yang-path-computation-03.txt


A new version of I-D, draft-ietf-teas-yang-path-computation-03.txt
has been successfully submitted by Italo Busi and posted to the
IETF repository.

Name:		draft-ietf-teas-yang-path-computation
Revision:	03
Title:		Yang model for requesting Path Computation
Document date:	2018-10-22
Group:		teas
Pages:		61
URL:            https://www.ietf.org/internet-drafts/draft-ietf-teas-yang-path-computation-03.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-teas-yang-path-computation/
Htmlized:       https://tools.ietf.org/html/draft-ietf-teas-yang-path-computation-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-yang-path-computation-03

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.

                                                                                  


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.

The IETF Secretariat