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

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

Return-Path: <lhotka@nic.cz>
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 209F2120193; Wed, 10 Apr 2019 02:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 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] 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 xCnT74LFppT4; Wed, 10 Apr 2019 02:33:59 -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 18CDA120048; Wed, 10 Apr 2019 02:33:58 -0700 (PDT)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:b07d:53ff:fe0b:1bd6]) by mail.nic.cz (Postfix) with ESMTPSA id C669C6338C; Wed, 10 Apr 2019 11:33:56 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1554888836; bh=z8BLKg2BjfglMc8D9/v5zZv4HCTauPYkUsrhtYuSUQk=; h=From:To:Date; b=FfJi2G3R3JDaX1CHAlV6H22FQa3V2SfucmXcIEvzbk8ACn+QSnMPdMw1PLlz9L4AC DDkLpB0pQSe1O9t/kStH0KqoXW5Bz5n6H8ux1usUXO/Nd3N18yWM8IElIp1gD6iQeK uhpdtfmOaeFsjruEuQzZGKgJJL5NdVkRgOW4wsYg=
Message-ID: <061a6eba967d6223bbc99febb189d40d7fad21aa.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: 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 11:33:56 +0200
In-Reply-To: <alpine.LRH.2.21.1904100512290.14618@bofh.nohats.ca>
References: <4A95BA014132FF49AE685FAB4B9F17F66B363EB2@sjceml521-mbs.china.huawei.com> <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>
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/yang-doctors/IqPRxr8TILLZK--7s6R4DwVwKHs>
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 09:34:01 -0000

Paul Wouters píše v St 10. 04. 2019 v 05:13 -0400:
> On Wed, 10 Apr 2019, Ladislav Lhotka wrote:
> 
> > Mahesh Jethanandani <mjethanandani@gmail.com>; writes:
> > 
> > > For the record, I prefer Lada’s solution of having a union that takes
> > > both a number and an identity/enum.
> > 
> > To be concrete, it means, for example (without descriptions and references)
> > 
> >    typedef ike-integrity-algorithm-t {
> >        type union {
> >            type uint16;
> >            type enumeration {
> >                enum NONE {
> >                    value 0;
> >                }
> >                enum AUTH_HMAC_MD5_96 {
> >                    value 1;
> >                }
> >                ...
> >            }
> >        }
> >    }
> > 
> > The unassigned and private use values won't be present as enums but can
> > be used via the numeric value. 
> > 
> > This IMO provides the benefits of both approaches and, moreover, the
> > enum values are documented in place.
> 
> But that is a bug, not a feature. The location of the enum values are in
> the IANA registries which continiously are updated. Putting snapshots of
> those in RFCs is a bad idea.

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.

Lada 

> 
> Paul
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67