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

Anthony Nadalin <tonynad@microsoft.com> Tue, 12 March 2019 22:03 UTC

Return-Path: <tonynad@microsoft.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 311B21279A4 for <rats@ietfa.amsl.com>; Tue, 12 Mar 2019 15:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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=microsoft.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 2CjYpQ3NCqZv for <rats@ietfa.amsl.com>; Tue, 12 Mar 2019 15:03:22 -0700 (PDT)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650093.outbound.protection.outlook.com [40.107.65.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61965131111 for <rats@ietf.org>; Tue, 12 Mar 2019 15:03:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bAGXmkcABSt8LV3n+cF0k/bpN2HAF7lFl6HGJjdQYaI=; b=QuNsC+OusJCSwFPOlh8xZw1wHdYLuZ7wO2Om+PyiGH/jIiv/SsV14h5ubpMtRb4SXflaXtHIO9MNclekGFUpyxQiIelfJSnZqw6vqKzJF3T9cIm3yFxhzJ6LiFUR+frwKgC0iG8tXygm7ZfCJKNl6t4KfD09yRd1BFK7VjHTt/g=
Received: from MW2PR00MB0396.namprd00.prod.outlook.com (52.132.148.160) by MW2PR00MB0426.namprd00.prod.outlook.com (52.132.149.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1741.0; Tue, 12 Mar 2019 22:03:19 +0000
Received: from MW2PR00MB0396.namprd00.prod.outlook.com ([fe80::2dc2:12da:f67f:9f4b]) by MW2PR00MB0396.namprd00.prod.outlook.com ([fe80::2dc2:12da:f67f:9f4b%7]) with mapi id 15.20.1743.000; Tue, 12 Mar 2019 22:03:19 +0000
From: Anthony Nadalin <tonynad@microsoft.com>
To: "rats@ietf.org" <rats@ietf.org>
Thread-Topic: draft-richardson-rats-usecases-00 comments
Thread-Index: AdTZH2WW+rxmtagrSLqGRlNOUrYHUw==
Date: Tue, 12 Mar 2019 22:03:19 +0000
Message-ID: <MW2PR00MB03963ABEB87211AD28A16240A6490@MW2PR00MB0396.namprd00.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e8:1:8da0:d937:3d47:2787]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6d60fec9-18f4-4663-82c5-08d6a7368991
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:MW2PR00MB0426;
x-ms-traffictypediagnostic: MW2PR00MB0426:
x-microsoft-antispam-prvs: <MW2PR00MB0426DF71D2897B432431E864A6490@MW2PR00MB0426.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 09749A275C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(39860400002)(136003)(396003)(366004)(189003)(199004)(7696005)(6506007)(99286004)(25786009)(102836004)(1240700005)(10290500003)(74316002)(486006)(6346003)(46003)(476003)(2906002)(478600001)(53936002)(316002)(2351001)(22452003)(54896002)(9686003)(6306002)(55016002)(6436002)(7736002)(86362001)(14454004)(86612001)(5640700003)(8936002)(33656002)(8676002)(6116002)(106356001)(81156014)(105586002)(81166006)(790700001)(71190400001)(71200400001)(5660300002)(2501003)(186003)(6916009)(68736007)(8990500004)(10090500001)(4744005)(97736004)(256004)(52536013)(1730700003); DIR:OUT; SFP:1102; SCL:1; SRVR:MW2PR00MB0426; H:MW2PR00MB0396.namprd00.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=tonynad@microsoft.com;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: UkqnZHfoqHazewfB9DpqVLB1kNaYyfYJRaAWysoTXUJZ2ubTgU/8MVwSToIGHzt8PCICBn2B0QpEIlzL+FR6N/nZQmnEdPvf9G0elmTcoEjlPyP/Ww8X6afaQIBtLZ/wkrTLE+kADhM/bddEzY5Zahk9ELMYAqF54tmtfk4xZnPiHNM/Elx0i7bQHkXjNFnD8/Hpl9KpMlu81WN7mkXiIfNX5JrmZS2DHaxL5CRQjbJBSF4SlYzzZYTfjPNoDbkO9ZX/D0jrb1l9DsoyuxP/064+FE9b8SJHLqDBrCX80DjbSma/1MHivtZECmD7SnewpXO34rrXrQ4/2RKETijxFdF7serRKSl1ZXgQgoAEugm72fHUW3tW5ONhcsBD8iscJqP1kXlZCayv9V7WgmsM9R86yNAfxrFeK1yZQ/cGxAw=
Content-Type: multipart/alternative; boundary="_000_MW2PR00MB03963ABEB87211AD28A16240A6490MW2PR00MB0396namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6d60fec9-18f4-4663-82c5-08d6a7368991
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Mar 2019 22:03:19.5632 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR00MB0426
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/W7z0-0UvGiF5gLtHm8hIS88xcVw>
Subject: [Rats] draft-richardson-rats-usecases-00 comments
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, 12 Mar 2019 22:03:25 -0000

The section on FIDO usecase (5.3) is out of date, as in FIDO/W3C there are many attestation formats that are acceptable from devices, the major concern that we have is the privacy issues as most all the attestation formats lead to potential collusion in one form or the other. The JS API is now the W3C WebAuthentication API that is a recommendation now, this is no longer in FIDO. I would be happy to send edits to this section.