IETF Logo Mail Archive

[Rats] draft-richardson-rats-usecases-00

Hannes Tschofenig <Hannes.Tschofenig@arm.com> Wed, 08 May 2019 13:34 UTC

Return-Path: <Hannes.Tschofenig@arm.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 11C78120119 for <rats@ietfa.amsl.com>; Wed, 8 May 2019 06:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com
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 6f4SFUpSdLFZ for <rats@ietfa.amsl.com>; Wed, 8 May 2019 06:34:39 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40085.outbound.protection.outlook.com [40.107.4.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C24FA1200F6 for <rats@ietf.org>; Wed, 8 May 2019 06:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=60UiiHvhrXtQ9VkQYwDGiVMsqrzo5ieH+JqFF0zl9vo=; b=aJHRXKkZA/GbwsDuqjmY+JjYutIczAmKtzcct5YPclUX/t1+HnrJ9+H6MspW+ZNGJ1LCWIbXKHjzQKD8vmLDFExkZeIDqJtyogDCUm/Tex9SU/9Ee3WTEck73V6E+diLTIAZfN1/waxdXt/GckHqaJWUQgA5LWw3B62Vbd0bHQc=
Received: from DBBPR08MB4539.eurprd08.prod.outlook.com (20.179.44.144) by DBBPR08MB4348.eurprd08.prod.outlook.com (20.179.42.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.11; Wed, 8 May 2019 13:34:36 +0000
Received: from DBBPR08MB4539.eurprd08.prod.outlook.com ([fe80::3803:e042:abea:cd93]) by DBBPR08MB4539.eurprd08.prod.outlook.com ([fe80::3803:e042:abea:cd93%5]) with mapi id 15.20.1856.012; Wed, 8 May 2019 13:34:36 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "rats@ietf.org" <rats@ietf.org>
Thread-Topic: draft-richardson-rats-usecases-00
Thread-Index: AdUFoQO6lL0A0elHTsyEP9//ysFj4Q==
Date: Wed, 08 May 2019 13:34:36 +0000
Message-ID: <DBBPR08MB4539242330D4322BCA6C0E56FA320@DBBPR08MB4539.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Hannes.Tschofenig@arm.com;
x-originating-ip: [80.92.123.90]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 40e782b0-2507-4d5e-d7c9-08d6d3b9e9c4
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:DBBPR08MB4348;
x-ms-traffictypediagnostic: DBBPR08MB4348:
x-microsoft-antispam-prvs: <DBBPR08MB4348D657D30C3B5BC759A071FA320@DBBPR08MB4348.eurprd08.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-forefront-prvs: 0031A0FFAF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(396003)(346002)(376002)(136003)(189003)(40434004)(199004)(74316002)(54896002)(52536014)(790700001)(7696005)(7736002)(86362001)(64756008)(66446008)(66476007)(2351001)(8676002)(99286004)(66556008)(76116006)(72206003)(81166006)(68736007)(71200400001)(71190400001)(66066001)(478600001)(81156014)(2501003)(5660300002)(33656002)(8936002)(1730700003)(66946007)(6306002)(9326002)(476003)(9686003)(486006)(5640700003)(3846002)(102836004)(5024004)(6436002)(14454004)(6916009)(6116002)(316002)(73956011)(186003)(256004)(26005)(53936002)(14444005)(55016002)(2906002)(6506007)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:DBBPR08MB4348; H:DBBPR08MB4539.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 1Rrdaz2GNODEwbQs1MwjAdEjLoWW3ouBXdR1iVq+VUJSSe9NazXpr7+4dfBQX+AUQFlna4mMoys+LKkLNQ3xlzk8TTuXmeLjtNeaxge3TNWVUVpfloa2eqpZxNxtLhcvkb6SS9uj39jfKShrYu503eyb9I5sXbRKEUdkaIDyHfFMgDoDKCN0RNsZcgxUA97JYyD0C7+cJRPHw2edqvldvsRVvje/h6pUo9Te7EOuPa6vqFTvReg47AB9SQe+x+yY4GPZb7qCUOenm06X3wfguo2QeiAN8mtFxRsGZBqUjS3oWKy0oC3LTgSpOdst66I1Do194T9TfLbVq/dM/QnhcJp2K7Qa/Gslg3zr7V/MgyH5vxQmc5gcjeWOSnNikQ2ptWIoQBPZmbFaiCxIOfjmFCuItwMD/A0G9OHiq4+y6yM=
Content-Type: multipart/alternative; boundary="_000_DBBPR08MB4539242330D4322BCA6C0E56FA320DBBPR08MB4539eurp_"
MIME-Version: 1.0
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 40e782b0-2507-4d5e-d7c9-08d6d3b9e9c4
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2019 13:34:36.3285 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBBPR08MB4348
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/ynjTyRvfSwZoh83DJO4sU4o0zwU>
Subject: [Rats] 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, 08 May 2019 13:34:41 -0000

Hi Michael,

I read through your document.

I am confused about the mismatch between the title and the content. I am also not sure about the direction it should go.

Currently, the document is an attempt to survey existing technologies that contain attestation functionality. That's not a use case document. There is also an attempt to define terminology in the document.

Are you going to change the content of the document to turn it into a use case document or do you plan to change the title?

Which direction you go depends on what you want to accomplish.

Doing a technology survey is useful but of course only a snapshot in time because the organizations are still working on their protocols and mechanisms. Additionally, the most interesting information is very hard to collect (such as deployment information).

Doing use cases is useful if they let you identify design constraints or new requirements. Getting meaningful use cases is, as I had to learn the hard way myself, difficult.

What do you plan to do?

Ciao
Hannes

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

v2.23.0 | Report a Bug | By Email