Re: [Lsr] [Bier] PCE Controller & SDN Controller & Netconf/Yang NMS Controller - lines blurred and can the names be used ubiquitously meaning the same

Adrian Farrel <adrian@olddog.co.uk> Sat, 21 November 2020 15:47 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE063A0DED; Sat, 21 Nov 2020 07:47:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 7a_VHaktI76Q; Sat, 21 Nov 2020 07:47:03 -0800 (PST)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 9599A3A0E33; Sat, 21 Nov 2020 07:46:58 -0800 (PST)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 0ALFkssH025045; Sat, 21 Nov 2020 15:46:55 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C2BF62203A; Sat, 21 Nov 2020 15:46:54 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS id AD19722032; Sat, 21 Nov 2020 15:46:54 +0000 (GMT)
Received: from LAPTOPK7AS653V ([195.166.134.90]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 0ALFkroZ020064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 21 Nov 2020 15:46:54 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Gyan Mishra'" <hayabusagsm@gmail.com>
Cc: "'BESS'" <bess@ietf.org>, "'BIER WG'" <bier@ietf.org>, "'IDR List'" <idr@ietf.org>, "'SPRING WG'" <spring@ietf.org>, "'TEAS WG'" <teas@ietf.org>, "'lsr'" <lsr@ietf.org>, <pce@ietf.org>
References: <CABNhwV2hACuvVJxQVihP2ejfq1NHKOwxHLCq=_o9DgoWBZag=w@mail.gmail.com> <00d501d6bb47$7ee160a0$7ca421e0$@olddog.co.uk> <CABNhwV03n0F2bSpZWfSVhgRnTjSd=drEfrhiP+v2orpsaiKT3w@mail.gmail.com>
In-Reply-To: <CABNhwV03n0F2bSpZWfSVhgRnTjSd=drEfrhiP+v2orpsaiKT3w@mail.gmail.com>
Date: Sat, 21 Nov 2020 15:46:53 -0000
Organization: Old Dog Consulting
Message-ID: <039401d6c01d$893ded90$9bb9c8b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0395_01D6C01D.893E62C0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQF9YbXHIOSWBk8yeY9fu/naMBX0BwJnuPwTAbmwFjqqZGg3wA==
Content-Language: en-gb
X-Originating-IP: 195.166.134.90
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25804.001
X-TM-AS-Result: No--19.728-10.0-31-10
X-imss-scan-details: No--19.728-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25804.001
X-TMASE-Result: 10--19.728200-10.000000
X-TMASE-MatchedRID: TmlY9+XBoTmx4Q5iE/G4VXFPUrVDm6jth4A8KRmrGe2qvcIF1TcLYEwi cw3eWSo0YLQ3+9wW9SYaHpAEsECl+h0HHInBeaK9JOMhINYq80wHgh3sKJBzP8pj/9aYiP+h3SZ uwROk0qHmLM5grIF7CSLuZAk1qAxOehY/DCk+INGecgASc+pqBczdhaN37iAM5lhx0mBJyPEcUn IIyt02Sa9sD66wAjsxf6x5zoWNtEgpNfI+R65HNc50DGuIExk9fiA7Y+GFqDOsaBVGMabQl+//v bMLiEkVS23jFwoI7b1+1uW3cIJ1vBWVVkGuW6Jr3zSg/bkXzGmOz/LLJUcaHsmqrXFLFjsW6aX8 TYIrj1uFZCZln65Hjpt6E4YKOIuohfUatHkEWNT4Wr1WT+bU2pkShYcLpGH9dPj9LUBj/ks8Pun 5tcXDXI0id0pIhqxT48CdlKt5w6+7Cjv/4LgPYmhQCsqhuTNihlL5/PVMMhK+vSKPcZwFluCfwd Xr9Uztu7C4hieFwVKAMuqetGVettLvsKjhs0lda9+JVKonO7eLZAVphLW/bXkguuQorcgMg5IQ3 dbS17M+Pal/bipFlwhigbA7cP7I6E96vWKSeR9+3BndfXUhXQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/1jpzT2uFDeBQUqcX2gYstMwqGzI>
Subject: Re: [Lsr] [Bier] PCE Controller & SDN Controller & Netconf/Yang NMS Controller - lines blurred and can the names be used ubiquitously meaning the same
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Nov 2020 15:47:05 -0000

Hi again Gyan,

 

I think we’re narrowing down and getting somewhat esoteric for the mailing lists we’re spamming.

> Similarly other use cases such as with TEAS TS-Transport slice and being able
> to provision TS and capturing the TS Enhanced VPN RT & resource information
> and leveraging BGP-LS to do the same data gathering & ZTP like controller style
> provisioning. 

Is there a fundamental difference between ZTP & Day N provisioning and path computation for traffic engineering provisioning? It’s all determining how to configure the network to best carry traffic. 

Gyan> In my mind the fundamental difference would be TE - control plane TEDs and
forwarding plane routing action path computation and instantiation of path action
as compare to a NMS type Netconf/Yang configuration snippet push function not
routing or TE related.

 

[Adrian] I think it depends. The protocols are just tools. You could have a centralised TE system with a PCE to preform computations, but you can use any combinations of protocols to extract information from the network (IGPs, BGP-LS, PCEP-LS, Netconf, …) and any combination of protocols to program the network devices to install TE paths, reserve resources, and configure traffic forwarding rules (PCEP, RSVP-TE, Netconf, …).

 

Cheers,

Adrian