IETF Logo Mail Archive

Re: [netconf] Using Netconf in Segment Routing for Database exchange and Path request/reply

Jeff Tantsura <jefftant.ietf@gmail.com> Mon, 04 May 2020 21:23 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A47F43A10AB for <netconf@ietfa.amsl.com>; Mon, 4 May 2020 14:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTupA4t-ZfzM for <netconf@ietfa.amsl.com>; Mon, 4 May 2020 14:23:45 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 222803A10B9 for <netconf@ietf.org>; Mon, 4 May 2020 14:23:45 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id n11so2576pgl.9 for <netconf@ietf.org>; Mon, 04 May 2020 14:23:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=G3DlfDoKXCtj1tLirIg0o1RFG36X8xkXjm5k7GKB2I4=; b=kOvW79pFcZwrLCHe61TGGKNFeua2tgAL0wCix6yLnke6uTbsBm34/RbHYxg4Gyi37z e0n/fdphczxFcp2Oahq510Coqn9FCM23E/LI4O1dLalf9ZaRb8mSG+HmB0yOFwRLNqsh 9ZueQhAGMUB3SlaSw9oLrkDJ8wOfzpY00zKtlHSs5AesDwSmrO+PLb8ELCRYk3lfeXZV OSAooYEzLyAhwCkRHay79uNsIFunvCkWblkrQSOj4hJ7Ptz8flXl9H/fYi9gcxkF0Rm0 JKYsxhQ6gH1k/SmzSvhgdfr79bMpDEvu6jssF39wc/4wIEUEM5qNnvLoB07niF7EytEv zgZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=G3DlfDoKXCtj1tLirIg0o1RFG36X8xkXjm5k7GKB2I4=; b=UoEyHk4mcjFtptHCLiOVdPBxinNnaGIu4jggPXSPZnVvLwsUJqGV9IDTf1ePeJoI2i vrQaN0+xA3ls9gqv3StCqTnvTfJolebkpCEnRbiYpsPtydmlyM2SuMImI6nBQ05Pxj+D euJ+oAaqm6u/AavuJoAR7ky0BjNODPuWVVXxzomSQUHe7LLOyST59HaYC15FZ3g4jlRe uy1jpAaWUDIvqN+/a3eSxpWDBsbgbCxcXARhNon7ApQ4ZfWITJMBRNX3ImS7W/rE6ODV UoybBVenLsnP4WW4qxqPiguuodCoUKaTrVZYBUEFyw5jqh+p55D1M889/QBJncdCiUJj ZMag==
X-Gm-Message-State: AGi0PuYjVGWwFKaZh/XkzvOlppxPd+cXvWe4p/XRNN4wU7PAm3VJ4X2h uKWG6G9GPicK/3Tnnp+YAhB3/gtb
X-Google-Smtp-Source: APiQypLRb3/KCuyurlUIv2byTTAPD1g7SPT9x+XC3n+GswiaxD10sJKscwWKcaFUD4xaLI3pRvbzSQ==
X-Received: by 2002:a63:2485:: with SMTP id k127mr190606pgk.159.1588627424204; Mon, 04 May 2020 14:23:44 -0700 (PDT)
Received: from [192.168.1.5] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id a142sm28474pfa.6.2020.05.04.14.23.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 May 2020 14:23:43 -0700 (PDT)
Date: Mon, 04 May 2020 14:23:30 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "netconf@ietf.org" <netconf@ietf.org>, "Rakesh Adulkar (radulkar)" <radulkar=40cisco.com@dmarc.ietf.org>
Message-ID: <0217af62-62a7-4cd4-958f-c21e4b7cf8dd@Spark>
In-Reply-To: <BD96D980-8818-4F29-A1CE-12FD6DD3821C@contoso.com>
References: <BD96D980-8818-4F29-A1CE-12FD6DD3821C@contoso.com>
X-Readdle-Message-ID: 0217af62-62a7-4cd4-958f-c21e4b7cf8dd@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5eb087de_15b5af5c_2480"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/i3iZ-7jEDIDjbOYTq7-YjpJ358k>
Subject: Re: [netconf] Using Netconf in Segment Routing for Database exchange and Path request/reply
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2020 21:23:47 -0000

Rakesh,

You have mostly answered your question in its second part.
Leaving aside that this is a bad idea
- PCEP communication state is ephemeral, and as such, Restconf would have been a better candidate.
- there are already implementations streaming LSDB content over gNMI

Cheers,
Jeff
On May 4, 2020, 2:02 PM -0700, Rakesh Adulkar (radulkar) <radulkar=40cisco.com@dmarc.ietf.org>, wrote:
> Hi Team,
>
> Hope you are doing well.
>
> I have below idea, as off now I am not sure if it will work or not.
> In current Segment Routing implementation we are using BGP-LS to exchange database and PCEP for path request/reply between PE/P devices and SR controller. I am just thinking that can we use Netconf to exchange database and also path request and reply protocol between PE/P devices and SR controller?
> I Understand that the sole purpose of netconf is to manage the network devices with specific use cases to install, manipulate, and delete the configuration of network devices. It’s not meant to carry IGP and TE-related stuff, nor can it react to network topology changes. Each protocol is there for its reasons, and IMHO netconf is not intended to replace BGP-LS and PCEP, and even if it does, there needs to be various development on the netconf side.
>
> So I wanted to know if there is any development in Netconf is going in this direction? If yes, than I would like to share my thoughts on it.
>
> Thanks & Regards,
> --
> Rakesh Adulkar
> Technical Consulting Engineer – Customer Delivery | Cisco TAC
>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email