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

<olivier.dugeon@orange.com> Thu, 14 February 2019 18:11 UTC

Return-Path: <olivier.dugeon@orange.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 13DEF128CE4; Thu, 14 Feb 2019 10:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.279
X-Spam-Level:
X-Spam-Status: No, score=-0.279 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 zJWYMZM79aLP; Thu, 14 Feb 2019 10:11:49 -0800 (PST)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88570129441; Thu, 14 Feb 2019 10:11:48 -0800 (PST)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 440kxG6d92z5vpD; Thu, 14 Feb 2019 19:11:46 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.76]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 440kxG6c25zDq7d; Thu, 14 Feb 2019 19:11:46 +0100 (CET)
Received: from OPEXCLILM6F.corporate.adroot.infra.ftgroup (10.114.31.34) by OPEXCAUBM7E.corporate.adroot.infra.ftgroup (10.114.13.76) with Microsoft SMTP Server (TLS) id 14.3.435.0; Thu, 14 Feb 2019 19:11:46 +0100
Received: from [10.193.71.231] (10.168.234.2) by OPEXCLILM6F.corporate.adroot.infra.ftgroup (10.114.31.34) with Microsoft SMTP Server (TLS) id 14.3.435.0; Thu, 14 Feb 2019 19:11:46 +0100
To: Igor Bryskin <Igor.Bryskin@huawei.com>, "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>, "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
CC: "teas@ietf.org" <teas@ietf.org>, Italo Busi <Italo.Busi@huawei.com>
References: <154022406162.6304.4708808854863399271@ietfa.amsl.com> <f810c738-ef38-fafe-3e90-1749b159fb9f@orange.com> <DB6PR0701MB27277506AD5E479F721DD17E91F00@DB6PR0701MB2727.eurprd07.prod.outlook.com> <939c6a39-d6a6-d6e8-93cf-c59222dc2728@orange.com> <0C72C38E7EBC34499E8A9E7DD00786391C5B502A@SJCEML521-MBB.china.huawei.com>
From: <olivier.dugeon@orange.com>
Organization: Orange Labs
Message-ID: <29890_1550167907_5C65AF62_29890_335_1_da9a1e77-7892-849e-1d8e-48f30d7e08f5@orange.com>
Date: Thu, 14 Feb 2019 19:11:47 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <0C72C38E7EBC34499E8A9E7DD00786391C5B502A@SJCEML521-MBB.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------DF6DEF76916A686D6B1ED850"
Content-Language: en-GB
X-Originating-IP: [10.168.234.2]
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/4V_0lP5XPltTKoPmtXolJcljUxY>
Subject: Re: [Teas] I-D Action: 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: Thu, 14 Feb 2019 18:11:52 -0000

Hello Igor,

After spending some times to analyse your proposal, I'm not sure where is the simplication regarding BRPC. See below my comments

Regards

Olivier


Le 28/11/2018 à 19:32, Igor Bryskin a écrit :
>
> Hi Oliver,
>
>  
>
> The process you described seems quite lengthy and complex.  What exacerbates things further is the fact that the described distributed path computation is sequential in nature because each step of VSPT computation depends on the previous one.
>
I disagree with that. Each PCE computes its own VSPT based on source / destination and border node that connect the domain to its neighbours. It is the same as the point 2 in your proposal.Then, merge process is done backward once answer receives. But, each PCE is free to start the path computation once it received the request forward. It is not mention in the BRPC to wait the answer to start the computation. Only the merge process need the answer. Thus, it is no so 'sequential' as you mention. It is possible to anticipate the path computation, doing some parallel computation which start with a small delay i.e. this delay is equal to the propagation of the PCReq to the next PCE + the time to process this message.

> I’d like to have your opinion on the alternative approach:
>
>  
>
> 1)      The domains that could be involved in the eventual end-to-end path(s) (including all domains) are identified;
>
It is the same with BRPC. It not mention in the RFC5441 how the AS Path is determine. It is out of the scope of the RFC. Note that in hierarchical way, you need to also determine this AS Path and again, it is not mention in the RFC and draft how to do it. A simply mechanism is to follow BGP path. In our current implementation we perform a CSPF on the abstracted topology.
>
> 2)      T he PCEs of the domains are simultaneously instructed to compute or use pre-computed  abstract topologies in the form of stateful paths connecting:
>
> Source/destination node to all border nodes in case of source/destination domains;
>
> Each border node to every other  border node in case of transit domains;
>
It exactly what PCE do when they receive the PCReq message in the BRPC chain.
>
> 3)      Merge via inter-domain links the provided in 2) abstract topologies into a single topology homogenously describing the multi-domain network;
>
Same as standard BRPC, except that this is done backward hop by hop (I mean PCE by PCE). And because each PCE must prune or if you prefer keep only the best paths, the number of possible solutions will not explode. I'm not sure if it the case in your proposal.
>
> 4)      Use said merged topology to select one or more end-to-end paths connecting the path computation request source to destination;
>
This is done during the backward merge process in BRPC by keeping only the best solution. So, at the end, the first PCE (i.e. the initiator of the request) got the best solution. Thus, compared to BRPC your proposal add one more step as step 3) and 4) are done simultaneously in BRPC.
>
> 5)      Release the abstract topologies or preserve them (e.g. provided by transit domains) for future similar path computations
>
Again, this is a matter of choice of the PCE developer to keep previous path computation in cache in case of.
>
>  
>
> Note the parallelism of the approach and the ability to yield multiple paths, including diverse paths crossing different domain sequences, which would be very hard to achieve with the BRPC approach IMHO.
>
I don't see the difference here. With BRPC, you could achieved the same path computation with a similar complexity.

In our implementation (done in OpenDayLight / BGPCEP), the BRPC algorithm is less than 500 lines of java. And from a performance point of view, we could compute and end-to-end path in less than 500ms with 3 PCE, and less than 1s with 6 PCE. So, I don't think it is too much complicate and doesn't required heavy intensive computation.

>  
>
> Thanks,
>
> Igor
>
>  
>
> *From:*Teas [mailto:teas-bounces@ietf.org] *On Behalf Of *Olivier Dugeon
> *Sent:* Wednesday, November 28, 2018 11:16 AM
> *To:* Belotti, Sergio (Nokia - IT/Vimercate); internet-drafts@ietf.org; i-d-announce@ietf.org
> *Cc:* teas@ietf.org; Italo Busi
> *Subject:* Re: [Teas] I-D Action: draft-ietf-teas-yang-path-computation-03.txt
>
>  
>
> Hello Sergio,
>
> Apologize for the long delay.
>
> For me, "flat" approach, I prefer the wording 'distributed', versus 'hierarchical' approach are quite similar. They only differ by the fact that there is one parent asking to different child about the per-domain path computation, while in the others, the per-domain path computation is done on a per domain basis.
>
> In the case of distributed approach, there is two possibilities to trigger the end-to-end path computation:
>
>  - An external top controller e.g. NMS, Orchestrator
>
>  - A PCC
>
> In both cases, the request reach the local PCE i.e. the PCE of the domain where the top controller or PCC are connected to. In fact, as there is no central PCE i.e. the parent PCE, the first PCE which is solicited and that trigger the distributed path computation is the PCE of the source domain i.e. the domain where the IP source address of the end point object is located. Normally, once check that the source end point belongs to its domain, the PCE determine which is the next peer PCE that it must contact to start the BRPC process. Once the destination domain is reached, the last PCE i.e. in the destination domain, starts to compute its part of the end-to-end path and send back the ERO. As it could be compute several path, the return paths are named VSPT (Virtual Source Path Tree). The previous PCE when it received the ERO from the latest PCE start merging its own path computation with the received one and sends the result to its predecessor. At the end, the computed paths
> are received by the first PCE which merge them with its local path and select the best result.
>
> What it is not mention in RFC5441, is the way the AS path i.e. which AS, this which PCE will be involve in the end-to-end path computation. But, if I remember right, it is the same in RFC6805. PCE could simply follow the BGP path or perform some local policy or some computation to determine the next peer PCE. But, this is independent of the the yang model except if we would provide the AS path. The best way to do this is to encode in IRO the AS path. We do that in our implementation.
>
> So, from a yang model perspective, I think that what is missing in your model it is just an indication to precise if the end-to-end path is computed in a hierarchical or distributed way. Adding VSPT flag (like it is defined in RFC5441) could be a preliminary approach. And in a second time, is the possiblity to specify the AS path. IMHO, it is not too many entries to add in the current version of the model.
>
> As already mention in previous mail, it is important to address this scenario as the hierarchical scenario is not always possible in particular when the domains are controlled by different operators.
>
> Regards
>
> Olivier
>
>  
>
> Le 26/10/2018 à 18:29, Belotti, Sergio (Nokia - IT/Vimercate) a écrit :
>
>     Hi Olivier,
>
>     Thanks for your interest in the draft and for your question.
>
>     draft-ietf-teas-path-computation is providing a Yang model request to permit a client-controller to ask server-controller for path computation , in particularly when client has not complete knowledge of the domain topology for which he has to calculate path.
>
>     The typical case is multi-domain , and I would say RFC 5441 is approaching the problem to create a path in a multi-domain environment from a different angle with respect what our draft is doing.
>
>     RFC5441 is a "flat" scenario and controllers have peer to peer relationship.
>
>     Our case is a typical hierarchical scenario as mentioned in the introduction. We assume information exchange  is top-down and bottom-up no horizontal information is exchanged . I would say we are trying to solve multi domain issue in a scenario close to what RFC 6805 is doing for PCE prospective.
>
>     Anyway if you envisage SDN scenarios  in which YANG models are used for peer to peer communication among controllers we are interested to further investigate them and evaluate whether the existing models can be adapted to the scope.
>
>     One aspect we would like to better understand in these scenarios is how the end-to-end path computation is triggered and coordinated.
>
>     In the hierarchical scenario, the end-to-end path computation is triggered by some requests (e.g., LxSM) from the top-level controller which, from the abstract topology view it gets from the lower-level controllers, understands what are the ingress and egress points of the end-to-end path, compute the path in terms of which domains it has to cross (using path computation RPC when needed) and coordinate the end-to-end path setup (requesting each domain to setup its path segment).
>
>     In a flat scenario, it is not clear how the overall process is started: which is the controller that coordinates the end-to-end path setup and how the customer knows which controller is going to request the service (e.g., LxSM) to trigger the whole process?
>
>      
>
>     If you'll be in Bangkok for IETF meeting we would be happy to discuss with you face to face.
>
>      
>
>     Thanks
>
>      
>
>     Italo and Sergio
>
>      
>
>      
>
>     -----Original Message-----
>
>     From: Teas <teas-bounces@ietf.org>; <mailto:teas-bounces@ietf.org> On Behalf Of Olivier Dugeon
>
>     Sent: Wednesday, October 24, 2018 4:46 PM
>
>     To: teas@ietf.org <mailto:teas@ietf.org>; internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>; i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
>
>     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 <mailto: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-comput
>
>         ation-03
>
>          
>
>         A diff from the previous version is available at:
>
>         https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-yang-path-computatio
>
>         n-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 <mailto:Teas@ietf.org>
>
>         https://www.ietf.org/mailman/listinfo/teas
>
>          
>
>      
>
>      
>
>     _______________________________________________
>
>     Teas mailing list
>
>     Teas@ietf.org <mailto:Teas@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/teas
>
>  
>


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.