IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 26 October 2023 21:52 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 79D44C17C528; Thu, 26 Oct 2023 14:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.086
X-Spam-Level:
X-Spam-Status: No, score=-7.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 6aUNcWGU5HTC; Thu, 26 Oct 2023 14:52:50 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B7EAC15106B; Thu, 26 Oct 2023 14:52:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 48ED11800F; Thu, 26 Oct 2023 17:52:28 -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 ewBvkLIDAcaG; Thu, 26 Oct 2023 17:52:27 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E46CB1800C; Thu, 26 Oct 2023 17:52:26 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1698357146; bh=cBrDmN7PF0kWL2PcNypeuBOjNhKhSfXZY00luroY8yc=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=BxrqjhS8EZJKIsSW8kU9jMk+iphrDdQbEB7+dSNTqwbUYDbWR1qzNjsIcDo1JOk5O Wk6QgPMmJ+qXGD27wgoErHaSiB/wTniv6hHBMoD0zytMGReccJqGTIOW4uhZ3mhufn 2I6K1PfWMx4zCWxAGDRYGgQkFrLSS7tdFI1eyNyhI+rqg1WCd1dzUPsJU+zKtpNWV2 sgMURI4PpIT/Khju+XCnejMcwQCIQewdDkkn00alISkDG+cKF0/skN6VFPIXz/p56l fiBoEFH9a89vhzUvT/ls3VbrR7zA14GrTpwVcE+47+BHSlDxAhjyy8dnDflNGa5Fh8 dK9bL96f+ycgw==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E0554C7; Thu, 26 Oct 2023 17:52:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Lars Eggert <lars@eggert.org>
cc: The IESG <iesg@ietf.org>, draft-ietf-core-sid@ietf.org, core-chairs@ietf.org, core@ietf.org
In-Reply-To: <169832632311.59761.11389369756506251047@ietfa.amsl.com>
References: <169832632311.59761.11389369756506251047@ietfa.amsl.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.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: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 26 Oct 2023 17:52:26 -0400
Message-ID: <18770.1698357146@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/N4K8nvvtizY4Hss4cDvlPJp3euM>
Subject: Re: [core] 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: Thu, 26 Oct 2023 21:52:57 -0000

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.


--
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