Re: [Cbor] π Confirmation call for Working Group Adoption for draft-greevenbosch-appsawg-cbor-cddl
Carsten Bormann <cabo@tzi.org> Sun, 09 July 2017 20:37 UTC
Return-Path: <cabo@tzi.org>
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 5469212EC15 for <cbor@ietfa.amsl.com>; Sun, 9 Jul 2017 13:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 M_oS_niRqEwE for <cbor@ietfa.amsl.com>; Sun, 9 Jul 2017 13:37:48 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66102129482 for <cbor@ietf.org>; Sun, 9 Jul 2017 13:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v69KbiJk009739; Sun, 9 Jul 2017 22:37:44 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7E215.dip0.t-ipconnect.de [93.199.226.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3x5Ksh26hsz3Zqd; Sun, 9 Jul 2017 22:37:44 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <22969.1499631064@obiwan.sandelman.ca>
Date: Sun, 09 Jul 2017 22:37:43 +0200
Cc: "cbor@ietf.org" <cbor@ietf.org>, Jeffrey Yasskin <jyasskin@chromium.org>, Francesca Palombini <francesca.palombini@ericsson.com>
X-Mao-Original-Outgoing-Id: 521325463.577712-cf32471b0355360e59edcc31c98a59c7
Content-Transfer-Encoding: quoted-printable
Message-Id: <C813D747-26FF-493A-8215-A88B1F1828D3@tzi.org>
References: <HE1PR0701MB25390DA8E0A1BEDE50EF206D98D40@HE1PR0701MB2539.eurprd07.prod.outlook.com> <CANh-dXkWA6rm23NU9s-w2-oz6Sqqv7RhsDM5teup8EDGmUhRuA@mail.gmail.com> <22969.1499631064@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/_LMUuMp5dEKLRhGn07tV68VmpK8>
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:37:50 -0000
> 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 agree with the sentiment β but thatβs not what happened with COSE (RFC 8152); IESG is going to insist on either duplicating all the normative content that uses CDDL, in another format (read: plain English (*)), or having a normative reference for CDDL. I cannot really disagree with that from a formal point of view, so letβs make that happen. GrΓΌΓe, Carsten (*) I seriously started writing a CDDL to βplain Englishβ converter, but then the situation defused a bit when the WG almost unanimously decided they wanted to have the CDDL in the main document.
- [Cbor] π Confirmation call for Working Group Adopβ¦ Francesca Palombini
- Re: [Cbor] π Confirmation call for Working Group β¦ Jeffrey Yasskin
- Re: [Cbor] π Confirmation call for Working Group β¦ Carsten Bormann
- Re: [Cbor] π Confirmation call for Working Group β¦ Michael Richardson
- Re: [Cbor] π Confirmation call for Working Group β¦ Carsten Bormann
- Re: [Cbor] π Confirmation call for Working Group β¦ Brian E Carpenter
- Re: [Cbor] π Confirmation call for Working Group β¦ Henk Birkholz
- Re: [Cbor] π Confirmation call for Working Group β¦ Matthew A. Miller
- Re: [Cbor] π Confirmation call for Working Group β¦ Kepeng Li
- Re: [Cbor] π Confirmation call for Working Group β¦ Sean Leonard
- Re: [Cbor] π Confirmation call for Working Group β¦ Brian E Carpenter
- Re: [Cbor] π Confirmation call for Working Group β¦ Matthew A. Miller
- Re: [Cbor] π Confirmation call for Working Group β¦ Sean Leonard
- Re: [Cbor] π Confirmation call for Working Group β¦ Carsten Bormann
- Re: [Cbor] π Confirmation call for Working Group β¦ Sean Leonard
- Re: [Cbor] π Confirmation call for Working Group β¦ Carsten Bormann
- Re: [Cbor] π Confirmation call for Working Group β¦ Brian E Carpenter
- [Cbor] Does CDDL need to be standards track to be⦠Michael Richardson
- Re: [Cbor] Does CDDL need to be standards track t⦠Sean Leonard
- Re: [Cbor] Does CDDL need to be standards track t⦠Carsten Bormann
- Re: [Cbor] Does CDDL need to be standards track t⦠Michael Richardson
- Re: [Cbor] Does CDDL need to be standards track t⦠Brian E Carpenter
- Re: [Cbor] π Confirmation call for Working Group β¦ Francesca Palombini
- Re: [Cbor] Does CDDL need to be standards track t⦠Jim Schaad