Re: [core] Genart last call review of draft-ietf-core-sid-15

Andy Bierman <> Tue, 16 March 2021 19:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F01723A0D75 for <>; Tue, 16 Mar 2021 12:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IsU97pEht_px for <>; Tue, 16 Mar 2021 12:37:05 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AECD13A0D3C for <>; Tue, 16 Mar 2021 12:37:00 -0700 (PDT)
Received: by with SMTP id u20so179436lja.13 for <>; Tue, 16 Mar 2021 12:37:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RiGjp5RrAomcvh3MRkY2zH0NmBMpmqIK/AWHhjrFxk0=; b=guc7802oxckATjzwzMWFVxj4syZwfjJ4g360JDnpWDRILYq57hVHVSe7H8BojnV+83 3iHFqg0PN1+1Lu40ZwccTrf5UkptrfW6E2aKZz7NxceIVAdKAp16w7YSUqHv2IbV2rA8 ndedB0yZxmY7uPomoliFm1pOz+4pfX2GyfADUJdP/va7eRVX4R99DPlvkaKGFFPWaOMC JjX6dQRfC5g9oecOXYsABgDYJ5ysj+9JwM0P5IZai+d9o8b/uaI9Tw7qCg6/Mqdcpmz0 7as0jFexAizLDRO7C2EUroSqyr1OZ7qgfrxVSLiPBzsNiq/VAtmB5rPEIu64FrgXkLPl A7cQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RiGjp5RrAomcvh3MRkY2zH0NmBMpmqIK/AWHhjrFxk0=; b=aZQc2Px73KgcE+NYKBnz65/QItRqLzOpj5nzhxcobpI3VMd9Fbk6GBljAvN1gVteIB A++ue39TkolBFAkbJqFQDp+ektfiDswFgeSgkHHUuinx0vPFUcr1urIVzVDhTYkOpybP TcQW2Qd3uZUoqCY3gETAYB4ywJbZG6dioZc6NWY6XS7gv/qxH4QEwdj8BpbQFyTTlIXI rkHmEe9fPFSbpThF48xEJC7fpG1S/0yiwG/FcZDm9IdB4MdiCfEAcR9dHW4rpRg8RFxN lrry8gNXFg85d0bp4Nk8tDISxbr+MdKgfBYpDm2f5y7rrf3CHDPta7PLpi8+G9zXhRmk W2fQ==
X-Gm-Message-State: AOAM530yyEWya7mODJ5Kd9bSt8DHaUMlgoRP1NX4ypS0WnhZKYjJo1Fu RAG0nXJ3CZ5pvEITDEWuIgvzCrWvKScuoctByjrqsQ==
X-Google-Smtp-Source: ABdhPJxnd1ESYo/L1WJX3L5G9wVdvw2Vu5uvATdwg1j/rPzPY3ay7g4pHCQSbcweb0UD/Mn2WdnfilF5tvqhQJ+VLbw=
X-Received: by 2002:a05:651c:2047:: with SMTP id t7mr157955ljo.325.1615923417988; Tue, 16 Mar 2021 12:36:57 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Andy Bierman <>
Date: Tue, 16 Mar 2021 12:36:47 -0700
Message-ID: <>
To: Linda Dunbar <>
Cc: General Area Review Team <>,,, Core <>
Content-Type: multipart/alternative; boundary="00000000000050527d05bdac7d8f"
Archived-At: <>
Subject: Re: [core] Genart last call review of draft-ietf-core-sid-15
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 16 Mar 2021 19:37:15 -0000

On Tue, Mar 16, 2021 at 10:34 AM Linda Dunbar via Datatracker <> wrote:

> Reviewer: Linda Dunbar
> Review result: Not Ready
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> For more information, please see the FAQ at
> <>.
> Document: draft-ietf-core-sid-15
> Reviewer: Linda Dunbar
> Review Date: 2021-03-16
> IETF LC End Date: 2021-03-17
> IESG Telechat date: Not scheduled for a telechat
> Summary:
> This document introduces the globally unique 63-bits integers to identify
> items which include data nodes, RPCs, their associated inputs/outputs,
> notifications, YANG modules, submodules, and features.
> Major issues:
> - One of the benefits of YANG is its explicit naming and
> human-understandable
> notations. It will be a nightmare if all the YANG items are represented by
> integers. YANG items being represented by integers will be worse than the
> values in the TLVs. At least, the TLV types are in the context of the
> protocols
> and their messages. - It will be a tremendous amount of work to map all
> items to globally unique integers. - YANG has been widely deployed without
> the
> numbering system. Which environment will need the integer representations?
> Who
> will validate the numbers used? How to validate the YANG modules
> represented by
> those "integers"?

My initial reaction to this work was that it would never fly in the wild.
But the CORE WG has developed tools and solved many of the problems with

There is a great deal of trust required in the tooling and procedures used
to manage the mapping of
YANG identifiers to globally unique integers.  These numbers are not
intended for
human usage (much like OID strings in SNMP).  If the client and server do
not agree
on the YANG-to-SID mapping, then the protocols will not work (same as OIDs
in SNMP).
I think the administration plan makes sense, but it is still unproven,
especially the
delegated subrange name assignments.

The mapping files are independent of the YANG modules so there is no need
to alter
any YANG module to use YANG SID.  There is a lot of work creating mapping
files instead. ;-)
The mappings are not used in YANG modules at all. They are only useful to
generate an
efficient binary message encoding for YANG data.  (Only. The delta-SID
encoding is extremely efficient
and really needed right now.)


- SID can be mistaken as Segment Identifiers (SID). Suggest using a
> different
> name.
> Minor issues:
> Nits/editorial comments:
> Best Regards,
> Linda Dunbar
> _______________________________________________
> core mailing list