Re: [EAT] [Rats] Attestation BoF charter updates?

"Smith, Ned" <ned.smith@intel.com> Wed, 24 October 2018 17:31 UTC

Return-Path: <ned.smith@intel.com>
X-Original-To: eat@ietfa.amsl.com
Delivered-To: eat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E689D129619; Wed, 24 Oct 2018 10:31:45 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 xCKFD613eCkr; Wed, 24 Oct 2018 10:31:44 -0700 (PDT)
Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (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 6D7AD1288BD; Wed, 24 Oct 2018 10:31:44 -0700 (PDT)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2018 10:31:20 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.54,421,1534834800"; d="scan'208,217";a="268466935"
Received: from orsmsx108.amr.corp.intel.com ([10.22.240.6]) by orsmga005.jf.intel.com with ESMTP; 24 Oct 2018 10:31:19 -0700
Received: from orsmsx155.amr.corp.intel.com (10.22.240.21) by ORSMSX108.amr.corp.intel.com (10.22.240.6) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 24 Oct 2018 10:31:19 -0700
Received: from orsmsx109.amr.corp.intel.com ([169.254.11.251]) by ORSMSX155.amr.corp.intel.com ([169.254.7.228]) with mapi id 14.03.0319.002; Wed, 24 Oct 2018 10:31:18 -0700
From: "Smith, Ned" <ned.smith@intel.com>
To: Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>, "Eric Voit (evoit)" <evoit@cisco.com>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, "eat@ietf.org" <eat@ietf.org>, "rats@ietf.org" <rats@ietf.org>
Thread-Topic: [EAT] [Rats] Attestation BoF charter updates?
Thread-Index: AQHUat5gF5XODrEVOE6MFEmu1KniJaUtlTEAgAEmEQCAABbTgP//1uwA
Date: Wed, 24 Oct 2018 17:31:18 +0000
Message-ID: <2AF948FC-A5F0-4067-82BA-20A9C2FD83F1@intel.com>
References: <5D773C02-5083-4B10-A705-782E28FD8ADB@island-resort.com> <f84515dd-2e1a-7e66-7c23-b16f8f425d2a@sit.fraunhofer.de> <3347AA26-3FA1-4067-8378-51B533BA77FB@island-resort.com> <570FEF0C-FD3A-4EBF-B8E6-7B13D2FD8E22@qti.qualcomm.com> <7544.1540242117@localhost> <46150D67-97E7-457F-9C8B-D2B3060978CA@qti.qualcomm.com> <f6602afcf1b0440d98f5ded158bfe572@XCH-RTP-013.cisco.com> <0771A502-32EF-46E9-95FB-55BE0FF04634@qti.qualcomm.com> <1F4B0DE5-32F4-4F09-B25A-1A088F108362@qti.qualcomm.com>
In-Reply-To: <1F4B0DE5-32F4-4F09-B25A-1A088F108362@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.3.181015
x-originating-ip: [10.24.14.77]
Content-Type: multipart/alternative; boundary="_000_2AF948FCA5F0406782BA20A9C2FD83F1intelcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/HwpHzzUUEHPjF9dHTHmcly4NAII>
Subject: Re: [EAT] [Rats] Attestation BoF charter updates?
X-BeenThere: eat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EAT - Entity Attestation Token <eat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eat>, <mailto:eat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eat/>
List-Post: <mailto:eat@ietf.org>
List-Help: <mailto:eat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eat>, <mailto:eat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2018 17:31:46 -0000

Agree. Hence the need for the charter scope to include terminology definition / clarification work (which it does).
+1 on the proposed markup/markdown changes.
-Ned

On 10/24/18, 5:59 AM, "EAT on behalf of Jeremy O'Donoghue" <eat-bounces@ietf.org<mailto:eat-bounces@ietf.org> on behalf of jodonogh@qti.qualcomm.com<mailto:jodonogh@qti.qualcomm.com>> wrote:

ยท         aligns more closely with NIST terminology - note that NIST does not have a clear set of definitions for all of the terminology used, so some of the text is my interpretation of the content of SP 800-64, aided by the input from Ned.