Re: [mpls] Review of draft-ietf-mpls-ldp-yang-09

Erik Auerswald <auerswald@fg-networking.de> Thu, 20 January 2022 16:24 UTC

Return-Path: <auerswald@fg-networking.de>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B708A3A17CD; Thu, 20 Jan 2022 08:24:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 1k-3qVK_WU_V; Thu, 20 Jan 2022 08:24:50 -0800 (PST)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (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 DB72B3A17D4; Thu, 20 Jan 2022 08:24:44 -0800 (PST)
Received: from mail.fg-networking.de (mail.fg-networking.de [IPv6:2001:638:208:cd01::23]) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 20KGOd9S184736 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 20 Jan 2022 17:24:39 +0100
Received: from login.fg-networking.de (login.fg-networking.de [131.246.197.41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.fg-networking.de (Postfix) with ESMTPS id 80DC32009B; Thu, 20 Jan 2022 17:24:30 +0100 (CET)
Received: by login.fg-networking.de (Postfix, from userid 11002) id 11E54173; Thu, 20 Jan 2022 17:24:30 +0100 (CET)
Date: Thu, 20 Jan 2022 17:24:30 +0100
From: Erik Auerswald <auerswald@fg-networking.de>
To: Renato Westphal <renato@opensourcerouting.org>
Cc: draft-ietf-mpls-ldp-yang.all@ietf.org, mpls@ietf.org
Message-ID: <20220120162429.GE83846@fg-networking.de>
References: <CAB6ZmXEzijShLEHkNQuhFchvpZ8GRTuzf=76WMxF-PqRX5xQeQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAB6ZmXEzijShLEHkNQuhFchvpZ8GRTuzf=76WMxF-PqRX5xQeQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/quMZmZ-Vbd7_wzF3ieJecTjzeHY>
Subject: Re: [mpls] Review of draft-ietf-mpls-ldp-yang-09
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 16:24:53 -0000

Hello Renato,

On Thu, Jan 20, 2022 at 12:40:48PM -0300, Renato Westphal wrote:
> [...]
> 4) I wonder if the following leaf is necessary:
> 
>   leaf lsr-id {
>     type rt-types:router-id;
>     description
>       "Specify the value to act as the LDP LSR ID.
>        If this attribute is not specified, LDP uses the router
>        ID as determined by the system.";
>   }
> 
> Shouldn't the router-id leaf from the ietf-routing module be enough for
> this purpose?

Many currently available routers allow to configure per-protocol and
(if applicable) per-process router-id values.  I would not like if
implementing YANG based management would lose this capability.

> [...]

Best regards,
Erik Auerswald
-- 
Dipl.-Inform. Erik Auerswald
Gesellschaft für Fundamental Generic Networking mbH
Geschäftsführung: Volker Bauer, Jörg Mayer
Gerichtsstand: Amtsgericht Kaiserslautern - HRB: 3630