IETF Logo Mail Archive

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 18:11 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 B05E6C15108B; Fri, 27 Oct 2023 11:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 LlylS_YK3EZV; Fri, 27 Oct 2023 11:11:36 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 E8466C151077; Fri, 27 Oct 2023 11:11:36 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa2.lax.icann.org (8.17.1.24/8.17.1.24) with ESMTPS id 39RIBRH9022247 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 27 Oct 2023 18:11:27 GMT
Received: from MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.25; Fri, 27 Oct 2023 11:11:26 -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; Fri, 27 Oct 2023 11:11:26 -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: AQHaCFd6Go2+1NiOL0acWYFyjvZnSbBd8U+A
Date: Fri, 27 Oct 2023 18:11:26 +0000
Message-ID: <F8CED175-BD91-46FA-8505-07DF5D4BFABD@iana.org>
References: <169832632311.59761.11389369756506251047@ietfa.amsl.com> <19859.1698357456@localhost>
In-Reply-To: <19859.1698357456@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_3781249885_1948981826"
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-27_17,2023-10-27_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/6cWVg-DZK_XizSt9-ef3XFGGSj4>
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 18:11:40 -0000

Hi Michael,

[AB] below.

    Lars Eggert via Datatracker <noreply@ietf.org> wrote:
        > ### Section 6.3.3, paragraph 3
        > ```
        > The initial entry in this registry is allocated to IANA:

        > +=============+=========+============+===================+==========+
        > | Entry Point | Size    | Allocation | Organization      | URL      |
        > |             |         |            | name              |          |
        > +=============+=========+============+===================+==========+
        > | 0           | 1000000 | Public     | IANA              | iana.org |
        > +-------------+---------+------------+-------------------+----------+
        > ```
        > I would have expected the initial allocation to IANA (and the regions
        > defined within) to be MUCH larger, given the overall size of the
        > namespace.

    IANA can ask itself for more space.
    There are some advantages to everyone to keep everyone below 2^32.
    Although it's not large, since most entries are delta-encoded.

[AB] IANA could ask for more space from the Mega-Range registry, given that it's an Expert Review space, but it would take an RFC to add it to the IETF YANG SID Range and set registration procedures for it. We would prefer not to manage a separate registry w/internally-declared registration procedures ourselves, and have no mechanisms for designating experts, handling appeals, etc.

Amanda

v2.23.0 | Report a Bug | By Email