IETF Logo Mail Archive

Re: [Cbor] 🔔 Confirmation call for Working Group Adoption for draft-greevenbosch-appsawg-cbor-cddl

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 09 July 2017 20:11 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B22129B3A for <cbor@ietfa.amsl.com>; Sun, 9 Jul 2017 13:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 MC0tMHwAwowU for <cbor@ietfa.amsl.com>; Sun, 9 Jul 2017 13:11:25 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E8421270B4 for <cbor@ietf.org>; Sun, 9 Jul 2017 13:11:25 -0700 (PDT)
Received: from sandelman.ca (unknown [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 7D4DF205CB; Sun, 9 Jul 2017 16:11:53 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 153258007E; Sun, 9 Jul 2017 16:11:04 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "cbor@ietf.org" <cbor@ietf.org>
cc: Francesca Palombini <francesca.palombini@ericsson.com>, Jeffrey Yasskin <jyasskin@chromium.org>
In-Reply-To: <CANh-dXkWA6rm23NU9s-w2-oz6Sqqv7RhsDM5teup8EDGmUhRuA@mail.gmail.com>
References: <HE1PR0701MB25390DA8E0A1BEDE50EF206D98D40@HE1PR0701MB2539.eurprd07.prod.outlook.com> <CANh-dXkWA6rm23NU9s-w2-oz6Sqqv7RhsDM5teup8EDGmUhRuA@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 09 Jul 2017 16:11:04 -0400
Message-ID: <22969.1499631064@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/a32LVt7RB7izW-PDiZ-mwpUD3xY>
Subject: Re: [Cbor] 🔔 Confirmation call for Working Group Adoption for draft-greevenbosch-appsawg-cbor-cddl
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jul 2017 20:11:27 -0000

Jeffrey Yasskin <jyasskin@chromium.org> wrote:
    > The Chicago minutes [1] talk about people using CDDL to write
    > specifications, but the -11 document is on the informational track
    > rather than the standards track, meaning, I believe, that it's not
    > intended to be referenced normatively from specifications. If folks do
    > want to be able to use CDDL from standards, would the draft need to
    > change tracks before it becomes a working group item?

I didn't think that CDDL would always require a normative reference from a
standards track document.

My feeling is that if the structures are relatively simple that the CDDL is
self-describing.  Most readers and implementers won't need to go further.

I guess the question is what happens when more advanced constructs are
needed.  In that case, I guess a normative reference would be required,
and then the question would indeed arise.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email