[core] Murray Kucherawy's No Objection on draft-ietf-core-sid-22: (with COMMENT)

Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 26 October 2023 07:10 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C12AC1519AB; Thu, 26 Oct 2023 00:10:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-core-sid@ietf.org, core-chairs@ietf.org, core@ietf.org, Carsten Bormann <cabo@tzi.org>, jaime@iki.fi
X-Test-IDTracker: no
X-IETF-IDTracker: 11.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <169830425849.60370.8571387158946572818@ietfa.amsl.com>
Date: Thu, 26 Oct 2023 00:10:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/CRh-9N8JREODTGGrbOAKlRyG7u8>
Subject: [core] Murray Kucherawy's No Objection on draft-ietf-core-sid-22: (with COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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 07:10:58 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-core-sid-22: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-core-sid/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Focusing again on Section 6 (IANA Considerations), which has got to be the most
complex one I've ever seen:

* Please don't use BCP 14 keywords here, as this section isn't the place to
discuss interoperability.  Lowercasing the ones you have should be fine.

* In 6.3.1, why is "policy of SID range" considered part of "contact
information"?

* In 6.3.2, seems to me the first and last bullets both talk about sustainable
operation and could be merged.

* Also in 6.3.2, how do you imagine the designated expert evaluating "technical
capacity" to operate a registry?  I note that Robert raised a similar concern.

* Sections 6.4 and 6.5 create registries that are going to be complicated for
the Designated Expert to work, and for the DE to present to the IESG proof that
the process was followed if asked.  I have to trust that all this complexity is
necessary.

* In 6.5.1, by "link", do you mean a URI?