Re: [Lsr] When to augment LSR base YANG modules...

Mikael Abrahamsson <swmike@swm.pp.se> Sun, 31 March 2019 07:07 UTC

Return-Path: <swmike@swm.pp.se>
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 86E1A120179 for <lsr@ietfa.amsl.com>; Sun, 31 Mar 2019 00:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 MK4Idqm13CR7 for <lsr@ietfa.amsl.com>; Sun, 31 Mar 2019 00:07:35 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 59F941200B6 for <lsr@ietf.org>; Sun, 31 Mar 2019 00:07:35 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 28BD0B1; Sun, 31 Mar 2019 09:07:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1554016052; bh=xg2Q1cQr/+ZlTnG2nVUaTiEbhA4uhfesDYlyTirg+qg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=B6XZy3cpDerebLq83crwgRdzey9Li8GE5O9lNCg8IgXfFAg3u48I7PL4SDoHB/Utd 6DKcfkjj5BFI1iiQVPU6JXmGOVqQ7lUHny+r5hTzCiUr75PmlhOq6QI1p9fdvsvoqG vLXPIT6ojC5iuAty3p+2YeSamkoa9MUzStw+imBg=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 2685AB0; Sun, 31 Mar 2019 09:07:32 +0200 (CEST)
Date: Sun, 31 Mar 2019 09:07:32 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Acee Lindem (acee)" <acee@cisco.com>
cc: "lsr@ietf.org" <lsr@ietf.org>
In-Reply-To: <B838962D-BDEA-46C9-9B9A-587484819784@cisco.com>
Message-ID: <alpine.DEB.2.20.1903310903140.3161@uplift.swm.pp.se>
References: <sa6wokiayd9.fsf@chopps.org> <2E6CA4AD-AD65-4A20-9545-1C81ED8B8968@tony.li> <B838962D-BDEA-46C9-9B9A-587484819784@cisco.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/qKBITVYkxwibBgGYbXDAG2TrjyA>
Subject: Re: [Lsr] When to augment LSR base YANG modules...
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: Sun, 31 Mar 2019 07:07:37 -0000

On Sat, 30 Mar 2019, Acee Lindem (acee) wrote:

> Additionally, I agree with Yingzhen's comment that it is not clear that 
> we want a separate YANG module for every OSPF/IS-IS feature.

As an operator, I expect to manage my routers using YANG modules. Thus, 
every feature that is introduced that would provide requirement for 
management and/or provide operational data needs to have an YANG module 
come with it, otherwise this new feature isn't useful.

I don't want YANG to be second class citizen compared to CLI the way SNMP 
has been. I also want to avoid having vendor-specific YANG modules if 
possible. Thus it makes sense to require YANG module with every new work.

If this is in the same document or an accompanying document is not of 
importance to me, as long as it gets the YANG module shows up in roughly 
the same timeframe as the feature.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se