[core] Re: [Schc] Fwd: New Version Notification for draft-pelov-sid-procedure-00.txt
Laurent Toutain <Laurent@touta.in> Wed, 04 December 2024 10:31 UTC
Return-Path: <laurent.toutain@gmail.com>
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 A5715C151520; Wed, 4 Dec 2024 02:31:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level:
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, 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=no 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 QEdhvVIQom1O; Wed, 4 Dec 2024 02:31:26 -0800 (PST)
Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81154C1840F9; Wed, 4 Dec 2024 02:31:26 -0800 (PST)
Received: by mail-ed1-f49.google.com with SMTP id 4fb4d7f45d1cf-5d10f713ef0so1311858a12.0; Wed, 04 Dec 2024 02:31:26 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733308285; x=1733913085; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=gjoiJFcxILpLe4WAXI34bkHjGd/q0J1gHrhpL6va0lk=; b=H8R1/2TWpCqxGacYaEifOUtRyLAW/sw+9Ga4PtsJu9qat2VF8Ckj7IxM43vPwvHlei 41hDvrywc7iZsyZ5wyk6B0o5V3am+tcIR1lSlWTAKkyoVwGoaprebStnjDXvc7KBflHT ikPF5G4F/igc8bb7//MU/eJlAbC2/lsu7T1nHbKJsQ+1P9jMu2qYpmrqw/+ReCshGCaI gSXB3LZjuPrhfGEKR0Xzh4vAhhZogPvY4fvovDXTRMoJVrJbH09zTsdKV05apRw2FkOI G0L2RV+Apaa498vaVtHXjd2e50APOHeNYN4QI4C4uUyfoXryzk1LKYI8N+7lgyXqy03Y dczg==
X-Forwarded-Encrypted: i=1; AJvYcCUd0puAP/BvEUkrHyrDzePR3RYjfDVtnqSauKxc7G/Hb0WcbF4IoNq4n4kT3nyikzDeV64h@ietf.org, AJvYcCX0hi+HPYp+cXmyRe6iYBRIS8ZHzhom82vF7J4OSwBAMp2qvyhBWG07sUN7sFzNbq8RU4ilcw==@ietf.org
X-Gm-Message-State: AOJu0Yw3hUgHV/GjRn93bMVoHAs9SD/rVeg4wW+FK2DcwQ6cSE3YKbtz wVy8u3UXxuFvouc/JCl/4BZ1svD12Q1T5wfhbBebnQ7i6UXH1lsXF7qSvjOhlPx5zv1ZYzeMAXV D1f3CWm9CryefgsbIJSGfSvFLUkM=
X-Gm-Gg: ASbGncvZFkVM1gyW6xjQcKRhvSC5qQDnkv0l1BM93zqRG4TOOEmlLGNreZ0x8KcSRF/ G5p2QhnT/ouaQPpKCFrb2eBZuQ1WNrBTdHUw4egiRgvjXDLdnwEbOcWlQ/VvTueg=
X-Google-Smtp-Source: AGHT+IFMiPPFNKjp89Pn8AkgJJjAPhZ7IU4kB5ChUGMHstdwdi0QDilYzzticaXQzsCsQvyCBvL4tAB8JXLzueylxJQ=
X-Received: by 2002:a17:906:23e1:b0:aa5:26ac:18e2 with SMTP id a640c23a62f3a-aa5f73b6badmr553296166b.23.1733308284566; Wed, 04 Dec 2024 02:31:24 -0800 (PST)
MIME-Version: 1.0
References: <173081740880.50534.5317268382668428309@dt-datatracker-5f77bcf4bd-vglkb> <1390262650.15218404.1730822309376.JavaMail.zimbra@imt-atlantique.fr>
In-Reply-To: <1390262650.15218404.1730822309376.JavaMail.zimbra@imt-atlantique.fr>
From: Laurent Toutain <Laurent@touta.in>
Date: Wed, 04 Dec 2024 11:30:47 +0100
Message-ID: <CABONVQYNgYxMufgc33YDg_9F8N1=t+nwee0vn8U_ZcSJG0efCw@mail.gmail.com>
To: Alexander PELOV <alexander.pelov@imt-atlantique.fr>
Content-Type: multipart/alternative; boundary="0000000000009688f306286f486c"
Message-ID-Hash: LPQLYFTL6OPO62SP6LUEUHTINWLYPNSC
X-Message-ID-Hash: LPQLYFTL6OPO62SP6LUEUHTINWLYPNSC
X-MailFrom: laurent.toutain@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: yang-sid-logistics@ietf.org, core <core@ietf.org>, schc <schc@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [core] Re: [Schc] Fwd: New Version Notification for draft-pelov-sid-procedure-00.txt
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/_O1Q2NpQZCJd_eoQ5AvRvQj_-J0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Owner: <mailto:core-owner@ietf.org>
List-Post: <mailto:core@ietf.org>
List-Subscribe: <mailto:core-join@ietf.org>
List-Unsubscribe: <mailto:core-leave@ietf.org>
Thank you Alex for clarifying the procedures to get a SID range. I would like to start the allocation process for RFC 9363. So regarding your document, we are is step 0 where " *Authors, Chairs, WG discuss and agree on SID range *" Regarding IANA registry, I think we can ask for a block starting in 4000 or 5000 and the size could be of 500 SIDs. The current model needs 125 SIDs. I previously shared some thoughts about SCHC SID allocation strategies (documented in draft-toutain-schc-sid-allocation-01 <https://datatracker.ietf.org/doc/html/draft-toutain-schc-sid-allocation-01>). Given the size constraints we inherited from the lp-wan working group, we need a more optimized allocation method than simple alphabetical ordering, as mentioned in the draft. This topic needs further discussion on the mailing list. Laurent On Tue, Nov 5, 2024 at 4:59 PM Alexander PELOV < alexander.pelov@imt-atlantique.fr> wrote: > Dear all, > > We've been discussing for some time how SIDs can be allocated manually. > I think we need to discuss a process that can be used by the different WG. > This is a short documents that tries to take a stab at the question. > > It is of course open for discussion. > > Cheers, > Alexander > > > ------------------------------ > *De: *internet-drafts@ietf.org > *À: *"Alexander PELOV" <alexander.pelov@imt-atlantique.fr> > *Envoyé: *Mardi 5 Novembre 2024 14:36:48 > *Objet: *New Version Notification for draft-pelov-sid-procedure-00.txt > > A new version of Internet-Draft draft-pelov-sid-procedure-00.txt has been > successfully submitted by Alexander PELOV and posted to the > IETF repository. > > Name: draft-pelov-sid-procedure > Revision: 00 > Title: Procedure for YANG SID Allocation > Date: 2024-11-05 > Group: Individual Submission > Pages: 6 > URL: https://www.ietf.org/archive/id/draft-pelov-sid-procedure-00.txt > Status: https://datatracker.ietf.org/doc/draft-pelov-sid-procedure/ > HTMLized: https://datatracker.ietf.org/doc/html/draft-pelov-sid-procedure > > > Abstract: > > This document defines a standardized procedure for the allocation of > YANG SID Ranges (YANG Schema Item iDentifier ranges) and the > subsequent assignment of SIDs for IETF RFCs with YANG files. > > > > The IETF Secretariat > -- > Schc mailing list -- schc@ietf.org > To unsubscribe send an email to schc-leave@ietf.org > -- Laurent Toutain +------ VoIP (recommended) ---+--- Télécom Bretagne --- + | Tel: +33 2 22 06 8156 | Tel: + 33 2 99 12 7026 | Visit : | Fax: +33 2 22 06 8445 | Fax: +33 2 99 12 7030 | http://class.touta.in | Laurent@Touta.in | Laurent.Toutain@Telecom-Bretagne.eu +----------------------------------------+--------------------------------+
- [core] Fwd: New Version Notification for draft-pe… Alexander PELOV
- [core] Re: [Schc] Fwd: New Version Notification f… Laurent Toutain
- [core] Re: [Schc] New Version Notification for dr… Carsten Bormann
- [core] Re: [Schc] New Version Notification for dr… Laurent Toutain