Re: [netmod] rfc7223bis (interfaces) enabled leaf vs SNMP admin-state

Martin Bjorklund <mbj@tail-f.com> Fri, 27 October 2017 07:50 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1813713F486 for <netmod@ietfa.amsl.com>; Fri, 27 Oct 2017 00:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 ZtO3yv10BmHk for <netmod@ietfa.amsl.com>; Fri, 27 Oct 2017 00:50:16 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 25370139507 for <netmod@ietf.org>; Fri, 27 Oct 2017 00:50:16 -0700 (PDT)
Received: from localhost (h-40-225.A165.priv.bahnhof.se [94.254.40.225]) by mail.tail-f.com (Postfix) with ESMTPSA id 656961AE030A; Fri, 27 Oct 2017 09:50:15 +0200 (CEST)
Date: Fri, 27 Oct 2017 09:50:15 +0200 (CEST)
Message-Id: <20171027.095015.776466334584979124.mbj@tail-f.com>
To: jason.sterne@nokia.com
Cc: netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <AM3PR07MB11249AEAE9F4C6FB8CB46E2F9B450@AM3PR07MB1124.eurprd07.prod.outlook.com>
References: <VI1PR07MB113551260F552B8CF644A1FB9B450@VI1PR07MB1135.eurprd07.prod.outlook.com> <20171026.205053.2059947918997412077.mbj@tail-f.com> <AM3PR07MB11249AEAE9F4C6FB8CB46E2F9B450@AM3PR07MB1124.eurprd07.prod.outlook.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/3jK3u6UAC0QyBvGGnytL6JtQuWE>
Subject: Re: [netmod] rfc7223bis (interfaces) enabled leaf vs SNMP admin-state
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 07:50:18 -0000

"Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com> wrote:
> Hi Martin,
> 
> I'm OK with that direction ('enabled' affects ifAdminStatus).  I'm questioning the other direction.  I think a change in ifAdminStatus should be reflected in 'enabled'.

How about simply:

              Changes in this leaf in the intended configuration are
              reflected in ifAdminStatus.

This would allow implementations that separate the two to not update
"enabled" when ifAdminStatus is updated, and allow your implemenation
to do the update (how do you handle 'testing' btw?).


/martin


> 
> Rgds,
> Jason
> 
> > -----Original Message-----
> > From: Martin Bjorklund [mailto:mbj@tail-f.com]
> > Sent: Thursday, October 26, 2017 14:51
> > To: Sterne, Jason (Nokia - CA/Ottawa) <jason.sterne@nokia.com>
> > Cc: netmod@ietf.org
> > Subject: Re: [netmod] rfc7223bis (interfaces) enabled leaf vs SNMP admin-
> > state
> > 
> > "Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com> wrote:
> > > Hi all,
> > >
> > > The issue I'm raising isn't new to the 'bis' version of RFC7223, but
> > > I'm questioning whether we should consider changing something about it
> > > while we're in there.
> > >
> > > The 'enabled' leaf has this in the description:
> > >
> > >              Changes in this leaf in the intended configuration are
> > >              reflected in ifAdminStatus, but if ifAdminStatus is
> > >              changed over SNMP, this leaf is not affected.
> > >
> > > As an example of "working code", Nokia's SR OS has supported full
> > > router configuration via SNMP for many years.  When someone enables an
> > > interface via CLI, that is reflected in ifAdminStatus and vice-versa.
> > > i.e. configuration via two different interfaces (SNMP & CLI) that use
> > > different data models, map rw leafs from the two interfaces/models to
> > > the same underlying internal object.
> > >
> > > In general, many SNMP rw objects will map to the same underlying
> > > internal rw object as the equivalent rw leaf in a YANG model (for
> > > products that actually support config management via SNMP as well as
> > > NETCONF).  Changing the leaf/object via SNMP affects the equivalent
> > > leaf/object in NETCONF.  Why make this one a special case ?
> > 
> > Note how ifAdminStatus is defined:
> > 
> >             "The desired state of the interface.  The testing(3) state
> >             indicates that no operational packets can be passed.  When a
> >             managed system initializes, all interfaces start with
> >             ifAdminStatus in the down(2) state.  As a result of either
> >             explicit management action or per configuration information
> >             retained by the managed system, ifAdminStatus is then
> >             changed to either the up(1) or testing(3) states (or remains
> >             in the down(2) state)."
> > 
> > Note the *per configuration information*.  It is clear that ifAdminStatus is not
> > the same as the "per configuration information".
> > The config object can affect ifAdminStatus.  "enabled" in the YANG model is
> > supposed to be that config object that can affect ifAdminStatus.
> > 
> > 
> > 
> > /martin
> > 
> > 
> > >
> > > I'd propose that we remove that sentence.
> > >
> > > Rgds,
> > > Jason
> > >
> > > > -----Original Message-----
> > > > From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of internet-
> > > > drafts@ietf.org
> > > > Sent: Monday, October 16, 2017 9:25
> > > > To: i-d-announce@ietf.org
> > > > Cc: netmod@ietf.org
> > > > Subject: [netmod] I-D Action: draft-ietf-netmod-rfc7223bis-00.txt
> > > >
> > > >
> > > > A New Internet-Draft is available from the on-line Internet-Drafts
> > > > directories.
> > > > This draft is a work item of the Network Modeling WG of the IETF.
> > > >
> > > >         Title           : A YANG Data Model for Interface Management
> > > >         Author          : Martin Bjorklund
> > > > 	Filename        : draft-ietf-netmod-rfc7223bis-00.txt
> > > > 	Pages           : 47
> > > > 	Date            : 2017-10-15
> > > >
> > > > Abstract:
> > > >    This document defines a YANG data model for the management of
> > network
> > > >    interfaces.  It is expected that interface-type-specific data models
> > > >    augment the generic interfaces data model defined in this document.
> > > >    The data model includes definitions for configuration and system
> > > >    state (status information and counters for the collection of
> > > >    statistics).  This document obsoletes RFC 7223.
> > > >
> > > >
> > > > The IETF datatracker status page for this draft is:
> > > > https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc7223bis/
> > > >
> > > > There are also htmlized versions available at:
> > > > https://tools.ietf.org/html/draft-ietf-netmod-rfc7223bis-00
> > > > https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc7223bis-0
> > > > 0
> > > >
> > > >
> > > > Please note that it may take a couple of minutes from the time of
> > > > submission until the htmlized version and diff are available at
> > > > tools.ietf.org.
> > > >
> > > > Internet-Drafts are also available by anonymous FTP at:
> > > > ftp://ftp.ietf.org/internet-drafts/
> > > >
> > > > _______________________________________________
> > > > netmod mailing list
> > > > netmod@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/netmod
> > >
> > > _______________________________________________
> > > netmod mailing list
> > > netmod@ietf.org
> > > https://www.ietf.org/mailman/listinfo/netmod
> > >
>