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

Italo Busi <Italo.Busi@huawei.com> Wed, 11 December 2019 08:28 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 67EB01200E9 for <teas@ietfa.amsl.com>; Wed, 11 Dec 2019 00:28:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 poyMR-9FlVGC for <teas@ietfa.amsl.com>; Wed, 11 Dec 2019 00:28:11 -0800 (PST)
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 8D1A412022A for <teas@ietf.org>; Wed, 11 Dec 2019 00:28:11 -0800 (PST)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 6CBE7D00E7DA67B12F56 for <teas@ietf.org>; Wed, 11 Dec 2019 08:28:08 +0000 (GMT)
Received: from fraeml718-chm.china.huawei.com (10.206.15.14) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 11 Dec 2019 08:28:07 +0000
Received: from fraeml715-chm.china.huawei.com (10.206.15.34) by fraeml718-chm.china.huawei.com (10.206.15.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 11 Dec 2019 09:28:07 +0100
Received: from fraeml715-chm.china.huawei.com ([10.206.15.34]) by fraeml715-chm.china.huawei.com ([10.206.15.34]) with mapi id 15.01.1713.004; Wed, 11 Dec 2019 09:28:07 +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-08.txt
Thread-Index: AQHVr5SybMyDhlnKn0md5UyVP3JtIae0mmjg
Date: Wed, 11 Dec 2019 08:28:07 +0000
Message-ID: <fd7ebe1de71646cd9932ceca47a88c56@huawei.com>
References: <157599669254.9909.17715952889807449729@ietfa.amsl.com>
In-Reply-To: <157599669254.9909.17715952889807449729@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.192]
Content-Type: multipart/alternative; boundary="_000_fd7ebe1de71646cd9932ceca47a88c56huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/1XWWnyWZL_o3yr7SAGLHcVT9Pls>
Subject: [Teas] FW: I-D Action: draft-ietf-teas-yang-path-computation-08.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: Wed, 11 Dec 2019 08:28:14 -0000

We have just uploaded an updated version of the I-D addressing the comments received during the discussions @ IETF 106

The updated description of the proposed mechanism is provided in section 5.3 and the overview of the YANG Tree that would results from these proposed changes is provide in Appendix B

These are the changes to the YANG tree with respect to the previous proposal:

OLD
           +---- path-request* [request-id]
           |  +--- request-id                       uint32
           |  +---- (tunnel-information)?
           |  |  +----:(tunnel-association)
           |  |  |  +---- (tunnel-exist)?
           |  |  |  |  +----:(tunnel-ref)
           |  |  |  |  |  +---- tunnel-ref                 leafref
           |  |  |  |  +----:(tunnel-association-id)
           |  |  |  |    +---- tunnel-association-id      uint32
           |  |  +----:(tunnel-attributes)
           |  |  |  +---- tunnel-name?                    string
           |  |  |  +--- encoding?                        identityref
           |  |  |  +--- switching-type?                  identityref
           +---- tunnel-associations* [tunnel-association-id]
           |  +---- tunnel-association-id?           uint32
           |  +---- tunnel-name?                     string
           |  +---- encoding?                        identityref
           |  +---- switching-type?                  identityref

NEW

           +---- path-request* [request-id]
           |  +--- request-id                       uint32
           |  +---- (tunnel-attributes)?
           |  |  +----:(reference)
           |  |  |  +---- (tunnel-exist)?
           |  |  |  |  +----:(tunnel-ref)
           |  |  |  |  |  +---- tunnel-ref                 leafref
           |  |  |  |  +----:(tunnel-attributes-ref)
           |  |  |  |    +---- tunnel-attributes-ref       leafref
           |  |  |  +---- path-name?                       string
           |  |  +----:(values)
           |  |  |  +---- tunnel-name?                     string
           |  |  |  +--- encoding?                         identityref
           |  |  |  +--- switching-type?                   identityref
           +---- tunnel-attributes* [tunnel-name]
           |  +---- tunnel-name                      string
           |  +---- encoding?                        identityref
           |  +---- switching-type?                  identityref

Note that:
•       tunnel-ref is a leafref to the tunnel-name in the te-tunnel model
•       tunnel-attributes-ref is a leafref to the tunnel-name in the tunnel-attributes* list within the path-computation rpc request

Please review section 5.3 and Appendix B and let us know if you have any comments with this proposal.

Thanks

Sergio and Italo (on behalf of co-authors)

> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: martedì 10 dicembre 2019 17:52
> To: i-d-announce@ietf.org
> Cc: teas@ietf.org
> Subject: [Teas] I-D Action: draft-ietf-teas-yang-path-computation-08.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-08.txt
>       Pages           : 78
>       Date            : 2019-12-10
>
> 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-08
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation-<https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation-08>
> 08
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-yang-path-computation-08
>
>
> 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/
>