[Rats] YANG fills a gap that is similar to what OpenAPI/RAML fills?

"Smith, Ned" <ned.smith@intel.com> Wed, 13 November 2019 00: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 []) by ietfa.amsl.com (Postfix) with ESMTP id DD2331201EF for <rats@ietfa.amsl.com>; Tue, 12 Nov 2019 16:30:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id aRgQwWHG4ISM for <rats@ietfa.amsl.com>; Tue, 12 Nov 2019 16:30:40 -0800 (PST)
Received: from mga05.intel.com (mga05.intel.com []) (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 41CA0120044 for <rats@ietf.org>; Tue, 12 Nov 2019 16:30:40 -0800 (PST)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga001.jf.intel.com ([]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Nov 2019 16:30:39 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.68,298,1569308400"; d="scan'208";a="287720077"
Received: from orsmsx108.amr.corp.intel.com ([]) by orsmga001.jf.intel.com with ESMTP; 12 Nov 2019 16:30:38 -0800
Received: from orsmsx151.amr.corp.intel.com ( by ORSMSX108.amr.corp.intel.com ( with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 12 Nov 2019 16:30:38 -0800
Received: from orsmsx109.amr.corp.intel.com ([]) by ORSMSX151.amr.corp.intel.com ([]) with mapi id 14.03.0439.000; Tue, 12 Nov 2019 16:30:38 -0800
From: "Smith, Ned" <ned.smith@intel.com>
To: Michael Richardson <mcr@sandelman.ca>, "rats@ietf.org" <rats@ietf.org>
Thread-Topic: YANG fills a gap that is similar to what OpenAPI/RAML fills?
Thread-Index: AQHVmbmScDZkaxQbPECVQGFRAbTVAg==
Date: Wed, 13 Nov 2019 00:30:37 +0000
Message-ID: <E4DB3304-0E5B-4326-9CAA-A465B31F6F76@intel.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.1e.0.191013
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <5D6B5E98DECC72409DB3C550915890E0@intel.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/jsAkGMF6sfo9UJaEnWEsR76qM7Q>
Subject: [Rats] YANG fills a gap that is similar to what OpenAPI/RAML fills?
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: Wed, 13 Nov 2019 00:30:42 -0000

Yes, they are rough analogs. RAML is a schema (metadata) that describes payloads for RESTful requests (get, put, push, delete) and responses. It is roughly CRUD semantics. The payload is where the complexity can hide. Payloads can be expressed using a data model language such as JSON. RAML and OpenAPI organizations merged recently. I presume that means RAML and OpenAPI will become one - OpenAPI-next.

In the context of RATS, Evidence, Attestation Results (and maybe Reference Values?) could be the payloads to a RAML/OpenAPI description of a RESTful interaction. The RATS interaction models (e.g. Passport) also called "message flow" could be realized in a RESTful protocol. 

Both data (payload) and protocol can be modeled using IM/DM expressions before being realized in a 'wire format'. 

I haven't seen CDDL used to model protocols. But I believe YANG can be used for that purpose. Both can be used to model data (payloads or data at rest objects). 

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