IETF Logo Mail Archive

Re: [netmod] [Anima] revising RFC8366 -- Re: BRSKI-AE enum issue -> empty, but what's he encoding ?

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 29 June 2021 22:36 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 4107F3A157B; Tue, 29 Jun 2021 15:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NO_DNS_FOR_FROM=0.001, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 111XHBetnbR4; Tue, 29 Jun 2021 15:36:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDB363A15A0; Tue, 29 Jun 2021 15:36:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1756038A2D; Tue, 29 Jun 2021 18:38:26 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4MhHBs6o1hGG; Tue, 29 Jun 2021 18:38:24 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id ECBBD38A2C; Tue, 29 Jun 2021 18:38:23 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7A2DF1801; Tue, 29 Jun 2021 18:36:20 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima@ietf.org" <anima@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
In-Reply-To: <AM7PR07MB62481F9B892B7942ACEABE2AA0029@AM7PR07MB6248.eurprd07.prod.outlook.com>
References: <20210625190512.GB30200@faui48e.informatik.uni-erlangen.de> <5025.1624653668@localhost> <20210625224810.GC30200@faui48e.informatik.uni-erlangen.de> <AM7PR07MB6248F9002860D02203B1CC71A0039@AM7PR07MB6248.eurprd07.prod.outlook.com> <20210628120924.xuuwnhnvz4jid7sp@anna.jacobs.jacobs-university.de> <26783.1624896286@localhost> <20210628161448.23zzsb2iazxgakmd@anna.jacobs.jacobs-university.de> <5322.1624898378@localhost>, <20210628182043.krqzcflymazra52d@anna.jacobs.jacobs-university.de> <AM7PR07MB62481F9B892B7942ACEABE2AA0029@AM7PR07MB6248.eurprd07.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Jun 2021 18:36:20 -0400
Message-ID: <25298.1625006180@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/tzVcJFBnKbTSsH7nLrwrx7VFGag>
Subject: Re: [netmod] [Anima] revising RFC8366 -- Re: BRSKI-AE enum issue -> empty, but what's he encoding ?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 29 Jun 2021 22:36:31 -0000

<#secure method=pgpmime mode=sign>

    > On Mon, Jun 28, 2021 at 12:39:38PM -0400, Michael Richardson wrote:
    >>
    >> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
    >> >> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
    > <snip>
    >> > You revise RFC 8366 and do the following:
    >>
    >> > - You define an IANA maintained module defining the enumeration type.
    >>
    >> This is the part that I don't know to do.
    >> https://www.rfc-editor.org/rfc/rfc7950.html#section-9.6
    >> says nothing about IANA.  Is RFC7224 the model for this?
    >>
    >> What document am I missing here?

    > Yes, RFC 7224 defining the iana-if-type module may serve as a
    > template. There are a couple of IANA maintained YANG modules, I am not
    > sure whether we have a good place listing them all. Well, you can
    > filter out the iana- modules from this list:

Okay, I understand now.
RFC7224 is an *IANA* maintained YANG module.  When new allocations are made,
then IANA rewrites the YANG module to include the new items.
It's not a YANG module that imports from a IANA registry, which I think we
have no YANG way to do that.

RFC7224 seems to use identity to create new subclasses.
RFC7217 seems to use typedef and feature.

Based upon my understanding, perhaps we don't need to revise RFC8366 completely,
it might be that we can just update it to include IANA Considerations and
turn the ietf-voucher YANG module into an IANA maintained YANG module?

That just avoids opportunity for more text churn.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email