Re: [core] removing names from yang-cbor rules

Andy Bierman <andy@yumaworks.com> Wed, 22 September 2021 23:01 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 D33F23A08B1 for <core@ietfa.amsl.com>; Wed, 22 Sep 2021 16:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20210112.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 qXmJFggIosRN for <core@ietfa.amsl.com>; Wed, 22 Sep 2021 16:01:45 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 08DDB3A089B for <core@ietf.org>; Wed, 22 Sep 2021 16:01:44 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id t10so18490521lfd.8 for <core@ietf.org>; Wed, 22 Sep 2021 16:01:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wE/jRxl3iSS85uCs2fxYM36BeAHOCg5jAD31YsJbM0Q=; b=QodwStkC1H65EeklHOQxIEQXZuujVMWiJu7tsX36PG+F0ge2xJu4Ko1lW406YdYC5r HuNLS4XL6rlluN5kJsejZEH5HLNpmyKyHUhfJOe3iem+3wgXNSJjn/wwpwnSHFPNhXjV fUOMKsp+aAif5g4Kkoai06mn+akvTNqQaHrtmav8v5q+bRgxgKoETB3Bqm6x/nY40FtY t2E5HZwSOQkse4MB1gXGwtxN38jsOphqD8D4d196otvAiVdxVml33n4zXGeLYrNLolhl SsabaWkxhqOVk1Ae68pEZrcuMrOMwUHz4pz+exeJ0pIEM299gXtnrq1ZRns3v5YQpDul FhKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wE/jRxl3iSS85uCs2fxYM36BeAHOCg5jAD31YsJbM0Q=; b=brSWTtTJY/BKO6010gjPATgmVPqkwsaA+AM0AUIHhE5X1HXB8m7Iiw+jn8LUUb5bnS IBg4o/8mK0iS3a/4ww1I4iVbH6NVPSIj+18wGiTpRg/FWo3mcu7HJnwtnrwnY/9qUEtu 2svaRN1un78bb41h2q65FUtyl5TOlOIUNc1Xuv7ilAbnsYTNWsr0OoJc4E3WfvXQgRYe QGEJQ1SCGyvwj83dOKj1oxD5UT1VEste9R7I/c5k3qyjKozHynroic3xiL4gCrD9lA1D ZGH1Zyjgu5HaMfmM0vpmnZu+AWlQ5ReVgubFpLWakmT88OrILL/N4AY7VpUC+uKOzi7z 2PgA==
X-Gm-Message-State: AOAM531RKng+q0GKbNG+37EIEI67GqW/pBdgKl2kHRs16k2YZqOo25r/ Yea4s6zBpwo1xMrdlMqBngsvqpoJ63Pwob4+5EZxYL8onrc=
X-Google-Smtp-Source: ABdhPJyiHXEsod1bMXzKeys6rsMUgezR6CvBny6nFtEFnnd48G21jl+5XBazayzRXL8z4bkAHUO6azPRMjJRk6Beqt0=
X-Received: by 2002:a2e:804c:: with SMTP id p12mr1953222ljg.344.1632351702919; Wed, 22 Sep 2021 16:01:42 -0700 (PDT)
MIME-Version: 1.0
References: <106211.1632084796@dooku> <CAL0qLwa2_7-3ic2PqEDv_UvcSchB8Enhigg=eS09XvGc9cdXeg@mail.gmail.com> <3892.1632347624@localhost>
In-Reply-To: <3892.1632347624@localhost>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 22 Sep 2021 16:01:32 -0700
Message-ID: <CABCOCHQUYSq05gFhJ=48pZu=kuRmXDOcaHMVecFia1UFKSxNnA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, Core <core@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000066bd7d05cc9d7f40"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/9D5Z_RYuE5F_bjV0sKyeBwwgKKY>
Subject: Re: [core] removing names from yang-cbor rules
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, 22 Sep 2021 23:01:53 -0000

On Wed, Sep 22, 2021 at 2:54 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Murray S. Kucherawy <superuser@gmail.com> wrote:
>     > I'm happy to take credit for a keen observation such as this, but
> this
>     > was actually Eric Vyncke.
>
> sorry, if I screwed that attribution up when creating the issues.
>
>     >> I also wonder about this.  I think that the SID concept is advanced
>     >> enough that we can just rely upon it.  Murray's comment is that if
> we
>     >> support two things, then an encoder needs to pick one, and it's
> likely
>     >> wrong.  Since this is often data at rest, there is no possible
>     >> negotiation either.
>     >>
>     >> I propose to remove section 4.1.2:
>
> There are also other parts of the document which refer to names as well.
> I have no use for names.
>
>
I agree it is better to remove the string name variant and only support
SIDs as names.
It will be important for the client to be able to obtain the SID File URL
list
representing all SIDs used by the server. This is needed before the client
can
use any data from the server (including the CORECONF YANG library).

The client will have to be hard-wired with the SIDs or capable of consuming
SID files in JSON format.



> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>

Andy


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