IETF Logo Mail Archive

Re: [core] Roman Danyliw's No Objection on draft-ietf-core-sid-23: (with COMMENT)

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 08 November 2023 16:19 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 B0361C1519B8; Wed, 8 Nov 2023 08:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 Cm9Q2uck0JUv; Wed, 8 Nov 2023 08:19:26 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EDA5C1516E0; Wed, 8 Nov 2023 08:19:25 -0800 (PST)
Received: from dyas.sandelman.ca (unknown [IPv6:2001:67c:370:128:19d6:23d7:1878:a892]) by relay.sandelman.ca (Postfix) with ESMTPS id AAA74209C2; Wed, 8 Nov 2023 16:19:23 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 873D6A1BB1; Wed, 8 Nov 2023 17:19:19 +0100 (CET)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 84067A1BB0; Wed, 8 Nov 2023 17:19:19 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>, draft-ietf-core-sid@ietf.org, core-chairs@ietf.org, core@ietf.org
In-reply-to: <169945068028.16710.3713559036306309058@ietfa.amsl.com>
References: <169945068028.16710.3713559036306309058@ietfa.amsl.com>
Comments: In-reply-to Roman Danyliw via Datatracker <noreply@ietf.org> message dated "Wed, 08 Nov 2023 05:38:00 -0800."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 08 Nov 2023 17:19:19 +0100
Message-ID: <3637292.1699460359@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/QmibqdVZxRHfCl1Z3dtJMubn4KI>
Subject: Re: [core] Roman Danyliw's No Objection on draft-ietf-core-sid-23: (with 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: Wed, 08 Nov 2023 16:19:27 -0000

Roman Danyliw via Datatracker <noreply@ietf.org> wrote:
    > -- I have no experience with early allocation of an IANA code point
    > happening concurrent with a WG adoption of a document.  Is that common?

Not common, I think.

    > -- What difficulty is expected in changing SID values?

    > -- Why is early allocation happening if the draft is not stable (which
    > seems unlikely at adoption time)?

Because we want running-code before WGLC.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.23.0 | Report a Bug | By Email