Re: [Rats] Call for adoption (after draft rename) for Yang module draft

"Smith, Ned" <ned.smith@intel.com> Tue, 12 November 2019 16:30 UTC

Return-Path: <ned.smith@intel.com>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D50B120827 for <rats@ietfa.amsl.com>; Tue, 12 Nov 2019 08:30:30 -0800 (PST)
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, 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 XYCrKqqTEa_r for <rats@ietfa.amsl.com>; Tue, 12 Nov 2019 08:30:29 -0800 (PST)
Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) (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 4DDAE120836 for <rats@ietf.org>; Tue, 12 Nov 2019 08:30:27 -0800 (PST)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Nov 2019 08:30:27 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.68,297,1569308400"; d="scan'208";a="202463413"
Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by fmsmga008.fm.intel.com with ESMTP; 12 Nov 2019 08:30:26 -0800
Received: from orsmsx157.amr.corp.intel.com (10.22.240.23) by ORSMSX106.amr.corp.intel.com (10.22.225.133) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 12 Nov 2019 08:30:26 -0800
Received: from orsmsx109.amr.corp.intel.com ([169.254.11.161]) by ORSMSX157.amr.corp.intel.com ([169.254.9.64]) with mapi id 14.03.0439.000; Tue, 12 Nov 2019 08:30:26 -0800
From: "Smith, Ned" <ned.smith@intel.com>
To: Michael Richardson <mcr@sandelman.ca>, "rats@ietf.org" <rats@ietf.org>
Thread-Topic: [Rats] Call for adoption (after draft rename) for Yang module draft
Thread-Index: AQHVlCwI8/lytau3hU+AhCwtIdg/0ad/EtmAgAAHhgCAAAO0AIAGacyAgAAGuoCAAG6gAIAA8mEAgAABTID//5RNgIABPsAAgAAArYA=
Date: Tue, 12 Nov 2019 16:30:25 +0000
Message-ID: <FDAE1D3E-CEBA-4F29-8017-5CFDB9D28C55@intel.com>
References: <8B173958-FC2A-4D1D-A81C-F324AB632CD7@cisco.com> <147F9159-6055-4E55-ABDC-43DFE3498BF1@island-resort.com> <ce5f8206-74dc-36bb-0093-a93045d5c67f@sit.fraunhofer.de> <0A7E3A4F-8534-4E98-BCB7-1454E07699F4@island-resort.com> <C3AE2645-49C8-4313-BCED-02FEB576B614@cisco.com> <1C8A1884-A37D-45E3-8C11-2FC5A083B245@island-resort.com> <ba12a686-1b34-21a3-388c-bbe01c01a408@sandelman.ca> <4A83CDF5-D29F-4279-8B03-E9D23299EB53@island-resort.com> <0C6940B0-E93F-4274-9D00-DEC4119B8F69@island-resort.com> <3310947D-EA31-4107-8FF0-B917A027C955@intel.com> <b53545b0-66f5-8b08-f5dc-ee92f74e1517@sandelman.ca>
In-Reply-To: <b53545b0-66f5-8b08-f5dc-ee92f74e1517@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
x-originating-ip: [10.251.18.104]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A0ED8B7B13B7F4498FC4F40E8429F62B@intel.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/K6gPY88NsBZA-cdRJTY48zU7uqs>
Subject: Re: [Rats] Call for adoption (after draft rename) for Yang module draft
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 16:30:30 -0000

It wasn't my intention to assert that CDDL was a 'bits on the wire' format. 

On 11/12/19, 0:28 AM, "RATS on behalf of Michael Richardson" <rats-bounces@ietf.org on behalf of mcr@sandelman.ca>; wrote:

    
    
    On 2019-11-12 5:27 a.m., Smith, Ned wrote:
    >
    > You’re saying YANG fills a gap that is similar to what OpenAPI/RAML fills?
    >
    
    I don't know what those things are.
    I might say it was similar to CORBA, but I'd be dating myself and I
    never really knew CORBA very well.
    
    > Ideally CDDL can be mapped to other information modelling languages
    > (e.g. YANG) so that only one normative expression needs to be
    > canonized. However, that implies extra work on behalf of the YANG
    > drafts to come up with the CDDL equivalent. Maybe that is unnecessary
    > extra work for consistency sake? That would force the conversations
    > around whether ‘time’ and ‘ticks’ are the same information model
    > expression (for example).
    >
    
    CDDL could be used to explain how the YANG serialization to CBOR or JSON
    worked.
    But, CDDL is also not a bits-on-the-wire thing, it's also probably human
    and code generator.
    (Carsten says that this is not exclusive the case, anymore, but I think
    having Turing complete
    information modeling languages is a bad thing, and might lead to Daleks
    Invasions and Cybermen Kings)
    
    I would expect that an RFC or other industry document that detailed a
    series of claims might use CDDL to describe the contents of the data
    that made up the details of the claim.
    But, again, for the code generators (whether human or machine)