Re: [Rats] Call for Adoption: EAT draft

"Eric Voit (evoit)" <evoit@cisco.com> Tue, 28 May 2019 23:25 UTC

Return-Path: <evoit@cisco.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 474391200B5 for <rats@ietfa.amsl.com>; Tue, 28 May 2019 16:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=kV6OpguP; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Y/VdJ/w1
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 uRBTDQw3g93F for <rats@ietfa.amsl.com>; Tue, 28 May 2019 16:25:44 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C0031200F9 for <rats@ietf.org>; Tue, 28 May 2019 16:25:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=46780; q=dns/txt; s=iport; t=1559085942; x=1560295542; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=sR55lvQmNtEmPQNM3QigDuK+U8tbdR1jDpFOO6i07Tg=; b=kV6OpguPcAHyM6XxK4Ujpn+8KYhqv7mL15W8HejZ7/m6LqiOi4fuoIgG fcL0uuRw4qtD3fg6wwSd+vxGGdTIHE1BS3Vl6auTca3Kiczv3Su5CSl72 U07Ph4tVmxRYXeaR02M+pIZAVrb7zr0+KzrBd3a7HCy/2U5oAWy6c4zSk M=;
IronPort-PHdr: =?us-ascii?q?9a23=3AP7uUzRYkiOEBJTU4VOiYyGr/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20Q+bRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn?= =?us-ascii?q?1NksAKh0olCc+BB1f8KavncSs7AOxJVURu+DewNk0GUMs=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BIAABSwu1c/5FdJa1kHAEBAQQBAQc?= =?us-ascii?q?EAQGBUQcBAQsBgQ4vUANpVSAECygKhAmDRwOEUoosgleXK4EuFIEQA1AECQE?= =?us-ascii?q?BAQwBARgBCgoCAQGBS4J1AheCTCM0CQ4BAwEBBAEBAgEEbRwMhUoBAQEBAgE?= =?us-ascii?q?BARALBgoTAQEFIAQDBAgECwIBBgIRBAEBFgQCBQEGAwICAiULFAkIAgQBEgg?= =?us-ascii?q?agwGBHU0DDg8BAgyNbpBgAoE4iF9xgS+CeQEBBS6BBAEDBAxBgwEYgXUaAwa?= =?us-ascii?q?BNAGLUheBQD+BEUaBTn4+gmEBAQIBAYEYEgESASEVFgkJBRqCLDKCJoskgmi?= =?us-ascii?q?EY4gljUMJAoINhjSHAYV7gh+KZolEjG6HAo52AgQCBAUCDgEBBYFPOGZxcBU?= =?us-ascii?q?7gmyCD4NwgmSCMIU+AXIBgSiLNQ0XB4EEAYEgAQE?=
X-IronPort-AV: E=Sophos;i="5.60,524,1549929600"; d="scan'208,217";a="566364930"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 May 2019 23:25:40 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x4SNPdOW009002 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 28 May 2019 23:25:40 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 28 May 2019 18:25:39 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 28 May 2019 18:25:38 -0500
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 28 May 2019 19:25:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sR55lvQmNtEmPQNM3QigDuK+U8tbdR1jDpFOO6i07Tg=; b=Y/VdJ/w1KauH39jZ8uyAhu51q/P5UiWvIAeA5OE7nfEIbjKAyFL4GQmo4XpmpKGukyuasEesDimwMrvx+vv+heJM2WlP00akRAEppGpJZ+7RAhbnFlgwtoDhxkd4BouKk4ap++EFbOYCBLIbgtlwyPDDg2R+9YsbV4R4LHehoZI=
Received: from DM6PR11MB4089.namprd11.prod.outlook.com (20.176.126.30) by DM6PR11MB3049.namprd11.prod.outlook.com (20.177.218.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.16; Tue, 28 May 2019 23:25:36 +0000
Received: from DM6PR11MB4089.namprd11.prod.outlook.com ([fe80::d014:d7a3:270:e5a9]) by DM6PR11MB4089.namprd11.prod.outlook.com ([fe80::d014:d7a3:270:e5a9%3]) with mapi id 15.20.1922.021; Tue, 28 May 2019 23:25:36 +0000
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Giridhar Mandyam <mandyam@qti.qualcomm.com>, "rats@ietf.org" <rats@ietf.org>
Thread-Topic: [Rats] Call for Adoption: EAT draft
Thread-Index: AQHVB0JFcFAs6WTeOkGyPcUokje8h6Z3eNuAgAk1ZmCAAAUqAIAAM0SggAAo3oCAAAwUgIAAA5hwgAAjyQCAAAKyoA==
Date: Tue, 28 May 2019 23:25:36 +0000
Message-ID: <DM6PR11MB4089BF4C3F319894DAE8722AA11E0@DM6PR11MB4089.namprd11.prod.outlook.com>
References: <CAHbuEH6Mdwp+neWbcecA-pMYZoXKiNda2A0EnMh-8WX=W9_edA@mail.gmail.com> <DM6PR11MB408991CBF9B50672E12A8F61A1000@DM6PR11MB4089.namprd11.prod.outlook.com> <DM6PR11MB4089818BBEF529569DC1250DA11E0@DM6PR11MB4089.namprd11.prod.outlook.com> <bdcaa9f2ca2344aa98287acd0b80d8f3@NASANEXM01C.na.qualcomm.com> <DM6PR11MB408939CC9EA79D479B76586DA11E0@DM6PR11MB4089.namprd11.prod.outlook.com> <E09EB1B2-ED56-4F1B-8D80-BF0D227199A3@island-resort.com> <82b0a75e5b5645d1a43d240373bca6dc@NASANEXM01C.na.qualcomm.com> <DM6PR11MB4089DAD248EEAAF9F92F2C0AA11E0@DM6PR11MB4089.namprd11.prod.outlook.com> <50ddca72a9074e229976ca88f78e340a@NASANEXM01C.na.qualcomm.com>
In-Reply-To: <50ddca72a9074e229976ca88f78e340a@NASANEXM01C.na.qualcomm.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=evoit@cisco.com;
x-originating-ip: [173.38.117.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 28d6b622-48ac-4a3a-24f5-08d6e3c3c9e9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:DM6PR11MB3049;
x-ms-traffictypediagnostic: DM6PR11MB3049:
x-ms-exchange-purlcount: 8
x-microsoft-antispam-prvs: <DM6PR11MB304968682111BD7AF17041EEA11E0@DM6PR11MB3049.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:4125;
x-forefront-prvs: 00514A2FE6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(39860400002)(376002)(396003)(366004)(136003)(189003)(199004)(76274002)(66946007)(316002)(52536014)(66066001)(73956011)(26005)(186003)(236005)(66574012)(74316002)(66476007)(66556008)(64756008)(66446008)(76116006)(55016002)(9686003)(229853002)(68736007)(6306002)(102836004)(2501003)(54896002)(5660300002)(33656002)(6506007)(53546011)(561944003)(7736002)(76176011)(14444005)(2906002)(476003)(790700001)(81156014)(71190400001)(8676002)(7696005)(8936002)(486006)(478600001)(9326002)(53936002)(446003)(6436002)(606006)(25786009)(110136005)(99286004)(256004)(14454004)(966005)(11346002)(71200400001)(86362001)(6246003)(81166006)(3846002)(6116002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3049; H:DM6PR11MB4089.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: jG2Ds2ORxT2xcBKI9EM55n6Gnw7aC+vV+2VwgYl+LtFIr57wYckiTD3M/46XVeiD+u6M6XLZay3kbipAdfnRPzV48fnYbfVj2cZX24CVdmVbIBOP4FIT04wBzfF2r6GaF+QYpDYHlf+I5/3frrEFpf06HJ6dSPpriIl7mkbE0goacHrD/4z1NJQ88Bclp4peh3yDQ7X+n+AZ5RTSZwDWxBy0zqxp1pnNJXqgyuiRYyWECUB+rbvKEgnEor9jaiqopQjniXew95ZDYsQHKQI22fGrdnpHM03DdRS/kYEgwP+j47jzZla3nGrW+dW5Fjuyx9U/vzG8Np4y44Jv2BnIOpwLBaBLDKOaEKSLdIP4/seJFWuHOJA/juyN3/2Z/aGXp9O+6GqzP6oyGVZCDygXyPbeDjb3fXzz2LsOu/KR6aU=
Content-Type: multipart/alternative; boundary="_000_DM6PR11MB4089BF4C3F319894DAE8722AA11E0DM6PR11MB4089namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 28d6b622-48ac-4a3a-24f5-08d6e3c3c9e9
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 May 2019 23:25:36.3352 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: evoit@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3049
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.27, xch-aln-017.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/jBCYPK2hly554HGYTXZXa2t_AGw>
Subject: Re: [Rats] Call for Adoption: EAT 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, 28 May 2019 23:25:48 -0000

Hi Giri,

I like where this is going.  Are you willing to add text into this draft defining:
(a) some principles/guidance to CWT claims registry people on avoiding the mass registration of lightly-used or unused claims
(b) a requirement to map claims to existing YANG objects, if these YANG objects exist

Eric

From: Giridhar Mandyam, May 28, 2019 6:58 PM

> If the number of claims stays in the 10's, I think your proposal will work fine.   But what if the scale is more?
…
> So with the current open-ended scoping of the domain of possible claims, would it be possible for any of these thousands of YANG objects to  being asserted by a device as a claim?  And would we have a way of explicitly defining the relationship/mapping between that claim and a corresponding YANG object?

Is your assumption that there could be thousands of registered YANG claims that extend the CWT registry?  For a claim being proposed for the registry, expert review is supposed to take into account the corresponding claim specification (which should document the relationship/mapping between a claim and a YANG object).  Writing a specification that would pass expert review should (in theory) be a high enough barrier to prevent mass registration of lightly-used or unused claims.

For unregistered claims - we cannot really stop implementations in the wild from using them.  I am not sure we would want to stop use of unregistered claims anyways as it could allow for pre-registration validation of any proposed claims.

Granted – I am putting a lot of faith in expert review for the CWT claims registry.  But I know that some of the designated CWT claims registry expert reviewers are reading this list and are quite diligent in carrying out their responsibilities.

-Giri

From: Eric Voit (evoit) <evoit@cisco.com<mailto:evoit@cisco.com>>
Sent: Tuesday, May 28, 2019 2:27 PM
To: Giridhar Mandyam <mandyam@qti.qualcomm.com<mailto:mandyam@qti.qualcomm.com>>; Laurence Lundblade <lgl@island-resort.com<mailto:lgl@island-resort.com>>
Cc: rats@ietf.org<mailto:rats@ietf.org>
Subject: RE: [Rats] Call for Adoption: EAT draft


CAUTION: This email originated from outside of the organization.
Taking a look at the CWT Claims from:
https://www.iana.org/assignments/cwt/cwt.xhtml
there are less than 10 claim defined currently.  And some of these appear as if they are not specified to allow interoperation. E.g., from RFC7519 #4.1.3, the audience claim passes "values is generally application specific".

If the number of claims stays in the 10's, I think your proposal will work fine.   But what if the scale is more?

When I look at what is going on with YANG right now, I see many thousands of objects.  The administrative effort involved with understanding the semantic bindings between these objects consumes multiple Working Groups' time.

So with the current open-ended scoping of the domain of possible claims, would it be possible for any of these thousands of YANG objects to  being asserted by a device as a claim?  And would we have a way of explicitly defining the relationship/mapping between that claim and a corresponding YANG object?

I do like EAT.  I think it is useful.  I just want to avoid the creation/assignment of new, parallel universe of managed object definitions.  And I especially want to avoid undefined mappings between the two.  It would be great for the draft to explore how to minimize such complexities.

Eric


From: Giridhar Mandyam, May 28, 2019 4:37 PM
> There is a CWT claims registry, so if you want to be sure no one collides with your, register them. (Looks like EAT didn’t say this explicitly, but that is the intent. Anyone can add any claim. All claims are optional. This is just like CWT).


Clarification:  The EAT draft didn’t need to state the above, as EAT is making use of the existing CWT registry.  Each claim submitted to the CWT registry will undergo expert review – see https://tools.ietf.org/html/rfc8392#section-9.1.  The designated experts should verify that not only claim ID’s in a submitted registration are not overlapping with existing entries, but they should also determine “whether the proposed registration duplicates existing functionality”.



-Giri


From: Laurence Lundblade <lgl@island-resort.com<mailto:lgl@island-resort.com>>
Sent: Tuesday, May 28, 2019 12:54 PM
To: Eric Voit (evoit) <evoit@cisco.com<mailto:evoit@cisco.com>>
Cc: Giridhar Mandyam <mandyam@qti.qualcomm.com<mailto:mandyam@qti.qualcomm.com>>; rats@ietf.org<mailto:rats@ietf.org>
Subject: Re: [Rats] Call for Adoption: EAT draft


CAUTION: This email originated from outside of the organization.
Hi Eric,

CWT says it in the start of section 3 of RFC 8932: “…all claims that are not understood by implementations MUST be ignored.” So anyone can add any claims. There is a CWT claims registry, so if you want to be sure no one collides with your, register them. (Looks like EAT didn’t say this explicitly, but that is the intent. Anyone can add any claim. All claims are optional. This is just like CWT).

It quite the intention that a token can be generated on a general purpose CPU. However the idea is to mark it as such so the receiver knows. Of course, if a token in generated on a special security-oriented CPU, it will be signed there and the general purpose CPU will just be a middle man that can’t change it.

I foresee the work we do here as a general frame up for EAT including the definition of a lot of common and useful claims.  Then individual applications and use case and such will define profiles that say what claims are allowed or disallowed. The ARM PSA document is more-of-less an example of that. FIDO is interested in workin on a profile. I expect Global Platform to define a TEE-oriented profile.

LL




On May 28, 2019, at 11:19 AM, Eric Voit (evoit) <evoit@cisco.com<mailto:evoit@cisco.com>> wrote:

Hi Giridhar,

I expect we will want to expand the claims over time.  Based on that, what are the limits to what can plausibly be populated as an EAT claim?

This is an important question at adoption time.  One of the things I like about Section 3 (everything but section 3.4) is that all the proposed claims are very specific/well defined.   And also importantly, each of these claims feel to be something which could plausibly be supported and signed within a hardware chip.  This is goodness.

However Section 3.4 defines "unrestricted" security environments which provide "no meaningful security assurances".    I can see why this might feel interesting: it provides flexibility for future use/applicability of EAT anywhere.  But a downside is that this could be read to mean that a general purpose CPU could add their own Claim types and then sign them.

Initially that seems like this flexibility would be ok.  But there are lots of protocols in the Internet.  And  I expect each of those protocols would want to maintain an explicit the list of attributes which might be passed on top.    So if those protocols are to someday carry EAT information, it would be good to define the universe of what might conceivably be carried within.  Without this, there could be unnecessary fights on who owns the purview of various nested protocol objects.

Eric

From: Giridhar Mandyam, May 28, 2019 10:24 AM
Sorry for the failure to respond.

Yes, your assessment is correct.  A custom claim can be created to carry the entire TPM attestation as a payload, similar to what is done in FIDO/Webauthn where the TPM relevant fields are included in a CBOR structure – see https://w3c.github.io/webauthn/#sctn-tpm-attestation.

Note that we would like to include claims into EAT that would cover measured boot.  There is no reason that entries in a PCR map couldn’t be represented as individual COSE structures (assuming the COSE algm. registry is consistent with the TPM specifications).  If so, then each measurement can nested within an EAT.

-Giri Mandyam

From: Eric Voit (evoit) <evoit@cisco.com<mailto:evoit@cisco.com>>
Sent: Tuesday, May 28, 2019 7:09 AM
To: draft-mandyam-rats-eat@ietf.org<mailto:draft-mandyam-rats-eat@ietf.org>
Cc: rats@ietf.org<mailto:rats@ietf.org>
Subject: RE: [Rats] Call for Adoption: EAT draft

CAUTION: This email originated from outside of the organization.
Resending a question to the authors...   (It looks like it got skipped during the blizzard of emails on JWT/CWT)

Eric

From: RATS <rats-bounces@ietf.org<mailto:rats-bounces@ietf.org>> On Behalf Of Eric Voit (evoit)
Sent: Wednesday, May 22, 2019 1:53 PM
I like the draft, but there is one thing I would like to hear from the authors before answering the poll.

This YANG model is exposed by software on a networking device like a router.  The router can examine information from local cryptoprocessors such as a TPM.

In looking at the proposed YANG model (draft-birkholz-rats-basic-yang-module), the tpms-attest-result structure from this YANG model can contain the raw result from a TPM.  This to me seems to be a binary blob which could also carry CBOR encoded EAT claims.  Do you agree with this assessment?

Eric

From: RATS <rats-bounces@ietf.org<mailto:rats-bounces@ietf.org>> On Behalf Of Kathleen Moriarty
Sent: Friday, May 10, 2019 11:07 AM
To: rats@ietf.org<mailto:rats@ietf.org>
Subject: [Rats] Call for Adoption: EAT draft

Greetings!

At IETF 104, a poll was taken to determine interest in the RATS WG adopting:

The Entity Attestation Token (EAT)
https://datatracker.ietf.org/doc/draft-mandyam-rats-eat/

This begins a 2 week period to determine interest in adopting this draft as a working group item.  The poll will close on May 24th EOD PDT.

Minutes from IETF 104:
https://datatracker.ietf.org/doc/minutes-104-rats/
--

Best regards,
Kathleen
_______________________________________________
RATS mailing list
RATS@ietf.org<mailto:RATS@ietf.org>
https://www.ietf.org/mailman/listinfo/rats