IETF Logo Mail Archive

Re: [core] js review of draft-ietf-core-yang-cbor-12

Carsten Bormann <cabo@tzi.org> Tue, 07 April 2020 21:47 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 BB7E73A08E8; Tue, 7 Apr 2020 14:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 inHpQufP9K3d; Tue, 7 Apr 2020 14:47:39 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88BAA3A08EA; Tue, 7 Apr 2020 14:47:39 -0700 (PDT)
Received: from [172.16.42.112] (p548DCD70.dip0.t-ipconnect.de [84.141.205.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48xgxP72H4z103C; Tue, 7 Apr 2020 23:47:37 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAJFkdRwhxa2T-LVoYfwbMcjjo-dWhwonf_q4B6vGGLuWy5K+BA@mail.gmail.com>
Date: Tue, 07 Apr 2020 23:47:37 +0200
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, core <core@ietf.org>, netmod@ietf.org
X-Mao-Original-Outgoing-Id: 607988857.468165-4e4ed4fbdd2e49242546b03b071d8958
Content-Transfer-Encoding: quoted-printable
Message-Id: <C355953B-7715-4CD9-B064-6B9D58B7D11A@tzi.org>
References: <20200331110237.zbo3zw74xlccur3w@anna.jacobs.jacobs-university.de> <CAJFkdRwhxa2T-LVoYfwbMcjjo-dWhwonf_q4B6vGGLuWy5K+BA@mail.gmail.com>
To: Ivaylo Petrov <ivaylo@ackl.io>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/yBzbKC5mwf8uJkhVdlgfkulT6yc>
Subject: Re: [core] js review of draft-ietf-core-yang-cbor-12
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: Tue, 07 Apr 2020 21:47:42 -0000

On 2020-04-07, at 15:35, Ivaylo Petrov <ivaylo@ackl.io> wrote:
> 
> - If this work gets approved, will other specifications like
>   draft-ietf-netmod-yang-data-ext-05.txt be expected to cover CBOR
>   encoding in addition to XML and JSON? This is more a procedural
>   question.
> 
> [IP]: From our discussions, I could say that that is desirable, but not something these drafts can enforce.  (Also, for drafts that already are well-advanced, one would expect a companion draft on a later timeline instead of the original text-based (JSON/XML) draft.)

Right.  Are we creating any special hardship for draft-ietf-netmod-yang-data-ext?

Grüße, Carsten

v2.15.0 | Report a Bug | By Email