Re: [core] removing names from yang-cbor rules
Carsten Bormann <cabo@tzi.org> Thu, 23 September 2021 04:35 UTC
Return-Path: <cabo@tzi.org>
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 7F4FF3A1DDC for <core@ietfa.amsl.com>; Wed, 22 Sep 2021 21:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ZNIUCjV073ye for <core@ietfa.amsl.com>; Wed, 22 Sep 2021 21:35:48 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 795533A1DDB for <core@ietf.org>; Wed, 22 Sep 2021 21:35:47 -0700 (PDT)
Received: from smtpclient.apple (unknown [194.156.182.213]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HFMmH26JMz2xLL; Thu, 23 Sep 2021 06:35:43 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-61FF55D3-1425-48AF-858F-B262D41F983A"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CABCOCHQUYSq05gFhJ=48pZu=kuRmXDOcaHMVecFia1UFKSxNnA@mail.gmail.com>
Date: Thu, 23 Sep 2021 06:35:41 +0200
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "Murray S. Kucherawy" <superuser@gmail.com>, Core <core@ietf.org>
Message-Id: <B8EE08AB-A3EA-44EF-A885-08F81D8947A4@tzi.org>
References: <CABCOCHQUYSq05gFhJ=48pZu=kuRmXDOcaHMVecFia1UFKSxNnA@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: iPhone Mail (18H17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/TD7QOV0l8b3f5VfTtlUhvKrH1KY>
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: Thu, 23 Sep 2021 04:35:54 -0000
Clearly, SIDs are the major innovation here and they are the normal way to use Yang-cbor. I don’t agree the string variant should be removed. This takes Yang-cbor out of the game for “big-web” applications. Instead, we should make sure to explain that strings are a special option that you chose wholesale when you need it, not something you switch to from SIDs randomly. Sent from mobile, sorry for terse > On 23. Sep 2021, at 01:02, Andy Bierman <andy@yumaworks.com> wrote: > > > > >> 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 > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core
- [core] removing names from yang-cbor rules Michael Richardson
- Re: [core] removing names from yang-cbor rules Murray S. Kucherawy
- Re: [core] removing names from yang-cbor rules Michael Richardson
- Re: [core] removing names from yang-cbor rules Andy Bierman
- Re: [core] removing names from yang-cbor rules Carsten Bormann
- Re: [core] removing names from yang-cbor rules Michael Richardson
- Re: [core] removing names from yang-cbor rules Andy Bierman
- Re: [core] removing names from yang-cbor rules Michael Richardson
- Re: [core] removing names from yang-cbor rules Carsten Bormann
- Re: [core] removing names from yang-cbor rules Andy Bierman
- Re: [core] removing names from yang-cbor rules Andy Bierman