IETF Logo Mail Archive

Re: [core] Éric Vyncke's Discuss on draft-ietf-core-sid-16: (with DISCUSS and COMMENT)

Andy Bierman <andy@yumaworks.com> Wed, 14 July 2021 22:58 UTC

Return-Path: <andy@yumaworks.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 15F743A08C6 for <core@ietfa.amsl.com>; Wed, 14 Jul 2021 15:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.113
X-Spam-Level:
X-Spam-Status: No, score=0.113 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_OTHER_BAD_TLD=1.999, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QL-lMJtGvLEr for <core@ietfa.amsl.com>; Wed, 14 Jul 2021 15:58:40 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E6213A0891 for <core@ietf.org>; Wed, 14 Jul 2021 15:58:39 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id a18so6390428lfs.10 for <core@ietf.org>; Wed, 14 Jul 2021 15:58:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0safpUPt0f4bPK6FjWWyfb1pnJgt13ti72NRQvKAjcM=; b=2P/x1xfpcx60ROgfRMFEWKZxhGn7XiLbZ/g6pqX16QpmES/FNH/d+BAsntty83qOgM EqaT+T9x+1o81aav1GVVGtEsnZOBi4YqasDEfNOj2K9TfziLc9pAGgOXIsEFTRiJfjnH 6Hl8x9xXepoJmfsUMzj8pW3zjKrEII5cwU57ZQBY2aKX/rpk21k60KXaOubcK3nNykB1 MW95kMPQaeoAF/9zrkg/t5O18m0IFlTVE1UXagnLBSvyzDklLPVtq60lOINJ6/H3nEIh V7l6fyz6LU0GUa5w03Rw4HLs512CPl0pAzS8TJ5bApOK4ZyMoAJLohfMouDFbkl8yV8d yrMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0safpUPt0f4bPK6FjWWyfb1pnJgt13ti72NRQvKAjcM=; b=EC6HwLnwwycx9psvFtKwfiu6GjSvm9lKNHei12GrDR6oANDN0iJ5awBmaDudV9MMuT j74JJufcLiN6b2iIZf3PLF/Hmp9MwhXuxHDmzKW5wPnK+FiBdJMAFYBdtBCFRWyhdE5l eTmNB5litMFG1eNFAUQe7kgNvVJQKCP/99A1UVgVXUwvSSx9K1KClooxGm6raEJf4fQH naFcJc4uI9UjshVE9zXSsPYNx8WD1+NkZLSZkKFxP/rsTh4bwyTNpliKuD2wggo86q1M v67SyomAtTXpxtN3VQez/EidjVGZE1A0daXzDN9j0GIdVIHEJ+J0wWNwHcJn/+fVZKpq RK1A==
X-Gm-Message-State: AOAM531sJBpvgNewohcPpqXB1bjDjXBdSVcY+dspe8zr0Yv9z+bAE1fe 8OjoBaJd5mh18zzlDRBiWmDqlcIAWb68W3QmBKV+Mw==
X-Google-Smtp-Source: ABdhPJw7KMpLSD1mhvSgtYCNPJ07IUy/cyl5kjHOHf7pBgvK0rhDzH5vtbxMsLZJZdm+zUIOIf0G169XAstUS4IZzXE=
X-Received: by 2002:a19:c707:: with SMTP id x7mr344835lff.38.1626303512305; Wed, 14 Jul 2021 15:58:32 -0700 (PDT)
MIME-Version: 1.0
References: <162624127733.15124.15333004711651272795@ietfa.amsl.com> <24058.1626275711@localhost> <577D49C6-9071-49C3-90B6-8EC45D955A84@tzi.org>
In-Reply-To: <577D49C6-9071-49C3-90B6-8EC45D955A84@tzi.org>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 14 Jul 2021 15:58:21 -0700
Message-ID: <CABCOCHSbjz-VRmpND5vFzKV9tS42p-vUGzN7wZEb1FD1FijE3A@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Éric Vyncke <evyncke@cisco.com>, draft-ietf-core-sid@ietf.org, core-chairs@ietf.org, The IESG <iesg@ietf.org>, Core <core@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000025ff2f05c71d4b7a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/ImjEeJE8xVotDtNY9wRDVUouVDA>
Subject: Re: [core] Éric Vyncke's Discuss on draft-ietf-core-sid-16: (with DISCUSS and COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Jul 2021 22:58:48 -0000

On Wed, Jul 14, 2021 at 1:57 PM Carsten Bormann <cabo@tzi.org> wrote:

> On 2021-07-14, at 17:15, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> >
> > The authors originally operated a web interface, and were hoping to hand
> that
> > to IANA and/or secretariat.
>
> That interface is still there:
>
> https://comi.space



What is the official plan to assign ranges to each IETF YANG module?
(Sorry if this is a different draft).

Looking through this WEB site, the SID assignments seem very ad-hoc and
manually derived,
and extremely prone to human error.  I am not worried about hackers
tampering with the SID files as much as the administration of the
micro-ranges
to be sloppy and poorly done.

Hopefully there will be tools that detect overlapping assignment errors
and tools that automatically assign ranges to a module and record the
assignment in an official database. A "SID Lookup" tool would also help
developers and operators debug implementations.



>
> I just got myself a SID range of 1000 SIDs at 1010000.
> Obviously, this second megarange needs to be in the megarange registry.
>
> Grüße, Carsten
>
>
Andy


> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>

v2.23.0 | Report a Bug | By Email