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

Hi Oliver,

I understand your concerns. They could be addressed  via TE Topology model family that could be used by controllers to exchange  real/abstract TE information.

Cheers,
Igor
From:Olivier Dugeon
To:teas@ietf.org,internet-drafts@ietf.org,i-d-announce@ietf.org,
Date:2018-10-24 10:46:34
Subject:Re: [Teas] I-D Action: draft-ietf-teas-yang-path-computation-03.txt

Dear authors,

Regarding the different use cases expose in your draft, I'm wondering if you have take into account distributed path computation as per RFC5441 ? In particular, when several Network Controller are involved (figures 1, 4 and 5), you add  respectively a Packet/Optical Coordinator, a Multi-Domain Controller and a Cloud Network Orchestrator. However, when the different networks are own by different operators, or business unit within the same operator, it is not always feasible to add this centralized controller. In this case, TE information must be exchange directly between lower controller e.g. between TE Domain Controller, DC Controller and TE Network Controller, Packet and Optical Network Controller.

So, I would understand if the yang model described in your draft allows such direct exchange or if it must be modified to take into such scenario ?

Regards

Olivier

Le 22/10/2018 à 18:01, internet-drafts@ietf.org a écrit :
> 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
>                           Oscar Gonzalez de Dios
>                           Anurag Sharma
>                           Yan Shi
>                           Ricard Vilalta
>                           Karthik Sethuraman
>                           Michael Scharf
>                           Daniele Ceccarelli
>        Filename        : draft-ietf-teas-yang-path-computation-03.txt
>        Pages           : 61
>        Date            : 2018-10-22
>
> 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-03
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-yang-path-computation-03
>
>
> 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/
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas