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

Ladislav Lhotka <lhotka@nic.cz> Wed, 10 April 2019 11:58 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6FB712017B; Wed, 10 Apr 2019 04:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 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_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 71y0lV6Rv1Wl; Wed, 10 Apr 2019 04:58:33 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 C922B1200D8; Wed, 10 Apr 2019 04:58:32 -0700 (PDT)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:9c6b:9bff:fee6:6583]) by mail.nic.cz (Postfix) with ESMTPSA id C028863160; Wed, 10 Apr 2019 13:58:30 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1554897510; bh=h5v8O1DG7KBcn9dh8/YRqRuahmCjUrbThRFlzfulnok=; h=From:To:Date; b=Vd3av4BctJfl9VpGqymQSLVyLJ+1ha/5DYEJ3atpQsEHpiYodtcxWTyVhuGUiHMJ4 BXEbBN+e91G/PQP0O/VjQFmEAgVYLaMAzcpdxhRZjHgj9vzl/r/eJYvT3Ss+jmgaiC yokumHIkeuDuKQzBQT9XG3aAYaO7j66dtUlZmxwg=
Message-ID: <bfc1838cd4d2bf626eb3977bff37b1758e5d2750.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: "Acee Lindem (acee)" <acee@cisco.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Paul Wouters <paul@nohats.ca>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Date: Wed, 10 Apr 2019 13:58:30 +0200
In-Reply-To: <2DA48994-C8DB-4CCD-B87F-552AB88F35F4@cisco.com>
References: <420D3E9A-9E3C-4575-9C92-200CAA0B868C@gmail.com> <CABCOCHRf3iGUt9wb3htpDYGJ+pAKErvq8OrozndgELUVKYT4Kg@mail.gmail.com> <80347D5B-C4DB-4F0C-BD73-A927585442BF@gmail.com> <D19CB266-D1D8-429E-A215-6BE866098E90@um.es> <6CC456A8-69B9-4D87-9A29-2DCE65E60EB2@gmail.com> <05E72A30-E28B-487A-A38C-EB7720F5B360@gmail.com> <87k1g2z0nj.fsf@nic.cz> <alpine.LRH.2.21.1904100512290.14618@bofh.nohats.ca> <061a6eba967d6223bbc99febb189d40d7fad21aa.camel@nic.cz> <alpine.LRH.2.21.1904100700080.20947@bofh.nohats.ca> <20190410111047.2s6n5plppk6bhdc4@anna.jacobs.jacobs-university.de> <2DA48994-C8DB-4CCD-B87F-552AB88F35F4@cisco.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.0
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/-RXVWek6W1SWfQ0V6YoTAybIhRw>
Subject: Re: [I2nsf] [yang-doctors] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 11:58:36 -0000

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.

Lada

>  
> 
> Thanks,
> Acee
> 
> 
>     
>     /js
>     
>     -- 
>     Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>     Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
>     Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>
>     
>     _______________________________________________
>     yang-doctors mailing list
>     yang-doctors@ietf.org
>     https://www.ietf.org/mailman/listinfo/yang-doctors
>     
> 
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67