IETF Logo Mail Archive

Re: [Rats] More use cases for draft-richardson-rats-usecases-00

"Smith, Ned" <ned.smith@intel.com> Wed, 19 June 2019 20:34 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 20AFE12093C for <rats@ietfa.amsl.com>; Wed, 19 Jun 2019 13:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id peIdLpSxYRwP for <rats@ietfa.amsl.com>; Wed, 19 Jun 2019 13:34:11 -0700 (PDT)
Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (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 E2D211201F8 for <rats@ietf.org>; Wed, 19 Jun 2019 13:34:10 -0700 (PDT)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jun 2019 13:34:10 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.63,394,1557212400"; d="scan'208";a="243422156"
Received: from orsmsx105.amr.corp.intel.com ([10.22.225.132]) by orsmga001.jf.intel.com with ESMTP; 19 Jun 2019 13:34:09 -0700
Received: from orsmsx153.amr.corp.intel.com (10.22.226.247) by ORSMSX105.amr.corp.intel.com (10.22.225.132) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 19 Jun 2019 13:34:09 -0700
Received: from orsmsx109.amr.corp.intel.com ([169.254.11.17]) by ORSMSX153.amr.corp.intel.com ([169.254.12.252]) with mapi id 14.03.0439.000; Wed, 19 Jun 2019 13:34:09 -0700
From: "Smith, Ned" <ned.smith@intel.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: "rats@ietf.org" <rats@ietf.org>, Carl Wallace <carl@redhoundsoftware.com>, Anders Rundgren <anders.rundgren.net@gmail.com>
Thread-Topic: [Rats] More use cases for draft-richardson-rats-usecases-00
Thread-Index: AQHVIuFqWQBd9YaaOUe/YohgH2bb7KagGH2AgAPGugD//5e2AA==
Date: Wed, 19 Jun 2019 20:34:09 +0000
Message-ID: <44F9F5E6-EBE6-4571-8B4D-3E2474FDAAA2@intel.com>
References: <MW2PR00MB03963ABEB87211AD28A16240A6490@MW2PR00MB0396.namprd00.prod.outlook.com> <12503.1552447661@localhost> <58E37DB5-098C-4387-9A52-4AECD0F69F25@island-resort.com> <6495.1553219901@dooku.sandelman.ca> <BA6E28A7-0F6A-46A8-AB1B-A64B9229F149@intel.com> <507.1553725386@dooku.sandelman.ca> <24C0968B-32B0-4EF1-99C8-61D3F0955BA1@intel.com> <793F9A34-050F-4914-AF4B-08C072730A06@island-resort.com> <D8C23800.D851F%carl@redhoundsoftware.com> <19652.1553943890@dooku.sandelman.ca> <D8C50A67.D8999%carl@redhoundsoftware.com> <79ccb2d7-09a3-913d-f47d-1e702a23b341@gmail.com> <7B05ABC3-FE60-4879-9DEE-B896DD15507D@intel.com> <4607.1560537962@localhost> <6744BE53-4071-4349-ACB5-23FDE107F16E@intel.com> <20112.1560973644@localhost>
In-Reply-To: <20112.1560973644@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
x-originating-ip: [10.24.14.73]
Content-Type: text/plain; charset="utf-8"
Content-ID: <958B6F396A2A4B4DA29F523DE6E288D8@intel.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/D0nNrUFeneCKNiEBEbqP1tQNLco>
Subject: Re: [Rats] More use cases for draft-richardson-rats-usecases-00
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, 19 Jun 2019 20:34:13 -0000

The use case context for implicit attestation is that for example, the protocol between attester and verifier doesn't allow explicit inclusion of attestatation evidence but the verifier requires the attester to meet various trustworthiness criteria. Use of the attestation key provides the verifier with enough context to locate attestation evidence that was conveyed out-of-band (by some other path). For example, it could be supplied in a certificate for the signing key.
-Ned

On 6/19/19, 12:47 PM, "RATS on behalf of Michael Richardson" <rats-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:

    
    Smith, Ned <ned.smith@intel.com> wrote:
        >> The TUDA draft seems to resemble (i). (Henk can correct me).
    
        >> The yang draft seems to resemble (ii). (Henk can correct me).
    
        mcr>     I'm trying to figure out what to do this statement.
    
        nms> If there is value in categorizing the attestation approach taken by
        nms> various proposed RATS drafts in terms of (i) implicit attestation
        nms> and (ii) explicit attestation then it seems TUDA
        nms> (https://datatracker.ietf.org/doc/draft-birkholz-rats-tuda/ ) may be
        nms> classified as implicit attestation. Since TUDA is also using
        nms> time-based exchanges Henk may think it doesn't fit well into this
        nms> categorization. The YANG module draft
        nms> https://datatracker.ietf.org/doc/draft-birkholz-rats-basic-yang-module/
        nms> appears to me to be a case of explicit attestation.
    
    okay, but this is an analysis what the implementations/protocols provide,
    whereas the usecase document is trying to categorize what the users need :-)
    
    I'm violently agreeing that the terms are useful, but I don't think they
    belong here.
    
    --
    Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
     -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email