Re: [core] [Ext] Re: Lars Eggert's Discuss on draft-ietf-core-sid-22: (with DISCUSS and COMMENT)

Amanda Baber <amanda.baber@iana.org> Fri, 27 October 2023 00:22 UTC

Return-Path: <amanda.baber@iana.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D6AC18770C; Thu, 26 Oct 2023 17:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VW2FY_YJMZ05; Thu, 26 Oct 2023 17:22:47 -0700 (PDT)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.78]) (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 2C818C187705; Thu, 26 Oct 2023 17:22:47 -0700 (PDT)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa3.lax.icann.org (8.17.1.24/8.17.1.24) with ESMTPS id 39R0MbW9020240 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 27 Oct 2023 00:22:37 GMT
Received: from MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.25; Thu, 26 Oct 2023 17:22:36 -0700
Received: from MBX112-W2-CO-2.pexch112.icann.org ([10.226.41.130]) by MBX112-W2-CO-2.pexch112.icann.org ([10.226.41.130]) with mapi id 15.02.1258.025; Thu, 26 Oct 2023 17:22:36 -0700
From: Amanda Baber <amanda.baber@iana.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Lars Eggert <lars@eggert.org>
CC: The IESG <iesg@ietf.org>, "draft-ietf-core-sid@ietf.org" <draft-ietf-core-sid@ietf.org>, "core-chairs@ietf.org" <core-chairs@ietf.org>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [Ext] Re: [core] Lars Eggert's Discuss on draft-ietf-core-sid-22: (with DISCUSS and COMMENT)
Thread-Index: AQHaCFbfU2TucoVCg0iG27Gr0B9XK7Bcxq4A
Date: Fri, 27 Oct 2023 00:22:36 +0000
Message-ID: <5234984F-3E97-4263-A05D-8EB6A8DF03AB@iana.org>
References: <169832632311.59761.11389369756506251047@ietfa.amsl.com> <18770.1698357146@localhost>
In-Reply-To: <18770.1698357146@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.63.22070801
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha256"; boundary="B_3781185754_2751157188"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.987,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-10-26_22,2023-10-26_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/3PkbL_jqVqpCOloTK6_vvLkhprg>
Subject: Re: [core] [Ext] Re: Lars Eggert's Discuss on draft-ietf-core-sid-22: (with DISCUSS and COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2023 00:22:49 -0000

Hi,

[AB] below. About the IANA-maintained YANG modules like iana-if-type and iana-routing-types:

On 10/26/23, 2:53 PM, "iesg on behalf of Michael Richardson" <iesg-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:

    Lars Eggert via Datatracker <noreply@ietf.org> wrote:
        > ### Section 6.5.3, paragraph 3
        > ```
        > After Working Group Adoption, any modification of a ".sid" file is
        > expected to be discussed on the mailing list of the appropriate
        > Working Groups.  Specific attention should be paid to implementers'
        > opinion after Working Group Last Call if a SID value is to change its
        > meaning.  In all cases, a ".sid" file and the SIDs associated with it
        > are subject to change before the publication of an internet draft as
        > an RFC.
        > ```
        > So IANA is not only hosting immutable files, they are also supposed to
        > support (frequent?) changes if these files. Unsure if IANA is set up
        > for this.

    The updates are likely not more frequent than issuing new RFCs.

    There is a class of YANG module which are IANA maintained, and which usually
    are "backed" (converted from) IANA maintained registries.  So those could be
    updated more often, based upon the IANA Considerations for those registries.

[AB] With a couple of exceptions, IANA uploads the revised registry and the updated YANG module simultaneously. Assuming that we already had a SID file in place for that registry/YANG, would we need to wait to make those updates until the experts could provide an updated SID file, or could the new SID follow later? It looks like IANA-maintained YANGs as a whole are updated on the order of 5x/year, mostly on an Expert Review or FCFS basis. (We've been asked to hold YANG-updating registrations until publication when they're made by an RFC. IIRC the reasoning was that otherwise we would need to update the module again in order to update the reference field when an RFC number was assigned.)   

Thanks,
Amanda