[core] draft-ietf-core-sid review

Laurent Toutain <laurent.toutain@imt-atlantique.fr> Wed, 15 March 2023 18:20 UTC

Return-Path: <laurent.toutain@imt-atlantique.fr>
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 A9451C151711; Wed, 15 Mar 2023 11:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 (1024-bit key) header.d=imt-atlantique.fr
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 YsElRC3XiKRE; Wed, 15 Mar 2023 11:20:30 -0700 (PDT)
Received: from zproxy130.enst.fr (zproxy130.enst.fr [IPv6:2001:660:330f:2::c2]) (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 5A82BC151554; Wed, 15 Mar 2023 11:20:27 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id DE0E11205B6; Wed, 15 Mar 2023 19:20:23 +0100 (CET)
Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 3B-d9as6grVW; Wed, 15 Mar 2023 19:20:23 +0100 (CET)
Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id 66903120597; Wed, 15 Mar 2023 19:20:23 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy130.enst.fr 66903120597
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1678904423; bh=VWzvWsz3aqEY/6Fiz+4xpXKNsI9mZVjyzNJXiea/3gY=; h=MIME-Version:From:Date:Message-ID:To; b=XHH6Rc17lNl0P5DeOXswkv9UGix86zqb/TbaUheeZUn4fp3uen4Dv76mOBc865KTi AOdvTRk8x6q5e3yPuv/KotVyLxRGfrGZJ844Q8sA9K5TgSKRT+GRGYXlWmeJzEFoGZ ZNPAeAuHkOoXfjWh+bcSHO+mKhNYhNsdP0dYcccs=
X-Virus-Scanned: amavisd-new at zproxy130.enst.fr
Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id NQsBzdNs0JlQ; Wed, 15 Mar 2023 19:20:23 +0100 (CET)
Received: from mail-wm1-f43.google.com (mail-wm1-f43.google.com [209.85.128.43]) by zproxy130.enst.fr (Postfix) with ESMTPSA id 346751205B6; Wed, 15 Mar 2023 19:20:23 +0100 (CET)
Received: by mail-wm1-f43.google.com with SMTP id l7-20020a05600c1d0700b003eb5e6d906bso1879064wms.5; Wed, 15 Mar 2023 11:20:23 -0700 (PDT)
X-Gm-Message-State: AO0yUKWKXkecoL9GPnpYfGffu8aV2NqmSDmm14D8X2cCrkfXC6qN7hOx eCKUiZm574BpJBqy+7ZLgEA3YtYnf9b3gQyHkd8=
X-Google-Smtp-Source: AK7set+wzoJsWHIjv4pkM7rjgw7VvnkQh50Ze2bMh4xgTHBKrr9mY6WhDqCw/wJHs56EWBbYNBnR9jXLMfP0INHH+v4=
X-Received: by 2002:a05:600c:1d02:b0:3e2:98f:1d76 with SMTP id l2-20020a05600c1d0200b003e2098f1d76mr5567190wms.8.1678904422869; Wed, 15 Mar 2023 11:20:22 -0700 (PDT)
MIME-Version: 1.0
From: Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Date: Wed, 15 Mar 2023 19:19:45 +0100
X-Gmail-Original-Message-ID: <CABONVQah0nMmZKs55rrhgu4KYbzgFSiPH0s5qKsTn4jAXp-HhA@mail.gmail.com>
Message-ID: <CABONVQah0nMmZKs55rrhgu4KYbzgFSiPH0s5qKsTn4jAXp-HhA@mail.gmail.com>
To: "core@ietf.org WG" <core@ietf.org>, lp-wan <lp-wan@ietf.org>, schc@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bcb08905f6f465ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/hzc7z4cEg-831l1SfVv5-xzb9EQ>
Subject: [core] draft-ietf-core-sid review
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, 15 Mar 2023 18:20:35 -0000

Hi,

II read draft-ietf-core-sid in the context of
draft-toutain-lpwan-sid-allocation, which assumes that SID allocation is
not done for an RFC, but managed by a WG.

The early allocation process (Section 6.5.3) may be the closer of this
context, since the WG manages a range of SID. Following this process, the
document must contain YANG DM and use its own SID values before being
accepted by the WG, after which the SID values are discussed.

The other process described in Section 6.4.2 does not explicitly refer to a
WG, the relationship is between the RFC authors and IANA. The WG may
nominate experts for review. And the WG can be seen as the SID assigner
(end of section 2.4).

So it is not clear to me if a WG is involved, how it can get a SID range to
assign to its RFCs.  What is the size of the range the WG can get from
IANA? Since LPWAN/SCHC is (re)chartering, perhaps the charter could
explicitly say "the WG will manage a pool of XXX SIDs" ?

In summary, there is nothing blocking, but nothing is specified for that
case.

Laurent