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

Gyan Mishra <hayabusagsm@gmail.com> Sat, 10 October 2020 19:32 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 95F083A16A9; Sat, 10 Oct 2020 12:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3J2Equ1DT48J; Sat, 10 Oct 2020 12:32:44 -0700 (PDT)
Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B04DB3A16A8; Sat, 10 Oct 2020 12:32:44 -0700 (PDT)
Received: by mail-ua1-x930.google.com with SMTP id j15so4190590uaa.8; Sat, 10 Oct 2020 12:32:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=C4XmRFX1FdrrRzHy07a2GSoJiSgJ3YIKxx06VY1GuZo=; b=l/wT/6n79CIUOTv4pqm/K8lEE1kblzGre8C3S9aI7zSBJSmtJtUkXa/Oc2X7cZrOxx tPG2GJZoI2BMACc1gCsxIdz4YToMqMoSiCzoBOXZPBAtIM/mvFoZSlI6hqOFLS5jg1Z2 Tn1IB8Ni9ZZ9w4UcCTLTxD+js/PiGn9/vJIqaS3P8k0mW8zTeMHon59vKRFGdL99a7Mz z49KwWP4jw1O8WfZ744LzDfDiYMziEm5Z6jBczBBrcgqxSc0THiTQ9+j/JPgn4iJOa9b ZUXIpTTk9q9nULW4NCnLFgXSn9305pRe9vlJ2k5Lja7dEYCZvR5r9gYqUvFa83eGG7x4 ImPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=C4XmRFX1FdrrRzHy07a2GSoJiSgJ3YIKxx06VY1GuZo=; b=VQermoRALA2KkWdwNg3v0Wd8mG3BGjMcsKBz8tBv5rs6bHe3vgmdL/W3s0C/rLYBmH NLTaIbEVzS5S3fxhM9+oZ+6it9RBwSlp3ItoXDo/zgMKEXei9Bmmix/KmV74EAp84tjw ceCQYp3IkfPZjvLG/56tpdNaZDoYJaaqoeDCpxpZTvX9AgkZh2PHoIusavRIHB6sPX5T BDWzcq/GlQQm2W/gHoEggJI9xsRYtzPrATsTSE5H3j/oZCyMKSs3wDgB7qxBs1nZEpDM WabvICI5TRX8tnwaj8K1VnxnFRlFTnGCp9wvtnzDinwCg3sL9jCiATAFGsrCG/1EOYwM 6olQ==
X-Gm-Message-State: AOAM530ZTFK9LllVcyFQIYSmvsFSzqlT1QKc/OsV+gDiO5RTaLggDjuN W1jk7PR6/EwQ1fUgdIum7KMQm1nSHVMl+ZV5R+xteQMvxX6Q/Q==
X-Google-Smtp-Source: ABdhPJyZ1k487MCskVdLlZNFlktDkewQsyuThKUxkuffWPOYTUDMTHhIxwhcpLmJa3JAeOY/f4u9n3FFMi/gmCi+dCc=
X-Received: by 2002:a9f:25c3:: with SMTP id 61mr10691059uaf.111.1602358363286; Sat, 10 Oct 2020 12:32:43 -0700 (PDT)
MIME-Version: 1.0
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 10 Oct 2020 15:26:56 -0400
Message-ID: <CABNhwV2hACuvVJxQVihP2ejfq1NHKOwxHLCq=_o9DgoWBZag=w@mail.gmail.com>
To: TEAS WG <teas@ietf.org>, pce@ietf.org, IDR List <idr@ietf.org>, lsr <lsr@ietf.org>, BESS <bess@ietf.org>, BIER WG <bier@ietf.org>, SPRING WG <spring@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000bf09f05b15621d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ApvmgvL_PN_pdcKEjBMPNYnA7as>
Subject: [Idr] PCE Controller & SDN Controller & Netconf/Yang NMS Controller - lines blurred and can the names be used ubiquitously meaning the same
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Oct 2020 19:32:47 -0000

Dear TEAS, PCE, IDR, LSR, BESS, BIER  Spring Working Groups,

I have noticed that after reviewing many drafts across many WGs it seems in
the industry that the lines seem to be blurred between a PCE controller,
ODL or Openflow SDN Controller and a Netconf/Yang NMS Controller ZTP & Day
X provisioning.

As this is a software sitting on a server you can have a swiss army knife
server that does everything from PCE path computation to  Netconf/Yang ZTP
& Day N provisioning as well as any SDN Controller ODL or Openflow
controller type functions as well.

How this comes into play and realization of the lines being blurred is the
use of BGP-LS in building the IGP topological graph of the network which
was designed for PCEP and PCE & PCC active & passive off line path
computation for both RSVP-TE or SR-TE path instantiation.

However now BGP-LS can also be used for other functions now such as usage
as I am a Shepherd reviewing a draft for BGP-LS usage for BIER to use
BGP-LS to gather the elements internals within BIER using the same BGP-LS
data structures to populate with BIER specific information to graph the
BIER topology.  So here we are not doing any path computations as we are
using in this use case  for NMS type function to gather data for ZTP & Day
N provisioning.

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.

It does seem as though BGP-LS as its a means of "data gathering" "dump
truck" of anything with the kitchen sink included to build any type of
topological graph of literally anything under the sun.  I see that is a
nice to leverage but it does in fact blur the lines of NMS Netconf/Yang
Controller based functionality and  PCE path computation functionality and
SDN controller based ZTP functionality into a single ubiquitous server that
can do all of the above and use BGP-LS to accomplish the "kitchen sink"
tasks.  It does however transform BGP to be an NMS tool but a "tool" and
not just the original function which it was intended NLRI network

Am I off base and please let me know as its BGP-LS is being way over
leveraged.  There are pros & cons to everything but I thought I would bring
up to the WG as an important discussion point.

Lots of food for thought.  Welcome all comments as well as concerns related
to this topic.

Kind Regards,


*Gyan Mishra*

*Network Solutions A**rchitect *

*M 301 502-134713101 Columbia Pike *Silver Spring, MD