Re: [yang-doctors] [I2nsf] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC

Martin Bjorklund <mbj@tail-f.com> Wed, 10 April 2019 12:28 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917611202E2; Wed, 10 Apr 2019 05:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 rE22m8gCYw6j; Wed, 10 Apr 2019 05:28:02 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7AEDF12004F; Wed, 10 Apr 2019 05:28:02 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 6C03C1AE0312; Wed, 10 Apr 2019 14:28:01 +0200 (CEST)
Date: Wed, 10 Apr 2019 14:28:03 +0200 (CEST)
Message-Id: <20190410.142803.1294517269946848163.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: acee@cisco.com, j.schoenwaelder@jacobs-university.de, paul@nohats.ca, i2nsf@ietf.org, yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <633ce13212c66a7a531b5a84870591717154b19a.camel@nic.cz>
References: <bfc1838cd4d2bf626eb3977bff37b1758e5d2750.camel@nic.cz> <20190410.140414.60651087922997525.mbj@tail-f.com> <633ce13212c66a7a531b5a84870591717154b19a.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/h5v6GE_L9exBfa-_VsFgD4Zrv_4>
Subject: Re: [yang-doctors] [I2nsf] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 12:28:04 -0000

Ladislav Lhotka <lhotka@nic.cz>; wrote:
> Martin Bjorklund píše v St 10. 04. 2019 v 14:04 +0200:
> > Ladislav Lhotka <lhotka@nic.cz>; wrote:
> > > Acee Lindem (acee) píše v St 10. 04. 2019 v 11:36 +0000:
> > 
> > > > 
> > 
> > > > On 4/10/19, 7:11 AM, "yang-doctors on behalf of Juergen Schoenwaelder" <
> > 
> > > > yang-doctors-bounces@ietf.org on behalf of 
> > 
> > > > j.schoenwaelder@jacobs-university.de>; wrote:
> > 
> > > > 
> > 
> > > >     On Wed, Apr 10, 2019 at 07:04:30AM -0400, Paul Wouters wrote:
> > 
> > > >     > On Wed, 10 Apr 2019, Ladislav Lhotka wrote:
> > 
> > > >     > 
> > 
> > > >     > > Not necessarily. If you look, for example, at RFC 7224, it is
> > IANA's
> > 
> > > >     > > responsibility to keep the registry in sync with the YANG module.
> > No
> > 
> > > > further
> > 
> > > >     > > effort is required from the WG that prepared the initial revision
> > of
> > 
> > > > the module.
> > 
> > > >     > 
> > 
> > > >     > What is "the YANG module" ?
> > 
> > > >     > 
> > 
> > > >     > I don't think IANA has any responsibility other than RFCs directing
> > them
> > 
> > > >     > to update IANA registries. How do you imagine any updates to happen,
> > and
> > 
> > > >     > how would IANA "sync" this automatically?
> > 
> > > >     >
> > 
> > > >     
> > 
> > > >     There are IANA maintained YANG modules (and before we had YANG there
> > 
> > > >     were IANA maintained MIB modules). Numbers maintained in registries
> > 
> > > >     sometimes need to be in machine readable formats and then IANA
> > 
> > > >     documents procedures to make updates both in their internal registry
> > 
> > > >     and in an IANA maintained YANG module.
> > 
> > > > 
> > 
> > > > It seems this could all be done with tooling. However, AFAIK, generation
> > of
> > 
> > > > new versions of IANA YANG models had not be implemented yet.
> > 
> > > 
> > 
> > > If it is so, then we have work to do. I am going to open this issue in the
> > 
> > > NETMOD mailing list.
> > 
> > 
> > Hold on.  IANA do publish new revisions of the YANG modules when the
> > registries are updated.  (perhaps they have a manual process, but
> > that's not really the point of this thread).
> 
> What about the iana-if-types module? It only exists in the initial revision
> 2014-05-08

No, see below.

> but new interface types since then in
> 
> https://www.iana.org/assignments/ianaiftype-mib/ianaiftype-mib
> 
> Apart from this, are there any other published YANG modules based on IANA
> registries?

Short answer, see
https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml

I replied to the netmod list, I suggest we continue the discussion
there.



/martin