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

Paul Wouters <paul@nohats.ca> Wed, 10 April 2019 09:13 UTC

Return-Path: <paul@nohats.ca>
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 2C7081202BB; Wed, 10 Apr 2019 02:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 tf-EOZDAAwbH; Wed, 10 Apr 2019 02:13:48 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 962051200A3; Wed, 10 Apr 2019 02:13:48 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 44fJP646xzz2G5; Wed, 10 Apr 2019 11:13:46 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1554887626; bh=bbS8KWnP+lcGL33u+f3UQkle8OQawzGHerX+tnEMwVI=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=jB4lIWa3TI1FzpUgNZ3hGCUI6GmkPQ5GaxVaDvqvpXYqxijEaYreZFl7lafig8szi p20i8MDDerBpWN7VZ/w6cwmUijkXwIxsOFHHL1Gk+KlQNcpXJTFLQBHK8J89Hkx2+6 4cHZFWoK40dRMKSKyDBlWv7WLCFKbbsWPNgzVeNA=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id MUGdnXcw3CkK; Wed, 10 Apr 2019 11:13:45 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 10 Apr 2019 11:13:44 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id E29E739A620; Wed, 10 Apr 2019 05:13:43 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca E29E739A620
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id D781740D358A; Wed, 10 Apr 2019 05:13:43 -0400 (EDT)
Date: Wed, 10 Apr 2019 05:13:43 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Ladislav Lhotka <lhotka@nic.cz>
cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
In-Reply-To: <87k1g2z0nj.fsf@nic.cz>
Message-ID: <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>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/wQEL2B9aWUXVWtFWDrHePW9QlYE>
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 09:13:50 -0000

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.

Paul