[Rats] how many use cases in Architecture?
Michael Richardson <firstname.lastname@example.org> Thu, 06 February 2020 11:36 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE8D9120907 for <email@example.com>; Thu, 6 Feb 2020 03:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([220.127.116.11]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WcS49QuavfXi for <firstname.lastname@example.org>; Thu, 6 Feb 2020 03:36:11 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [18.104.22.168]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7F991208C6 for <email@example.com>; Thu, 6 Feb 2020 03:36:11 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2a02:8109:b6c0:52b8::5]) by relay.sandelman.ca (Postfix) with ESMTPS id 680391F45A for <firstname.lastname@example.org>; Thu, 6 Feb 2020 11:36:10 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 619FF11CE; Thu, 6 Feb 2020 06:36:07 -0500 (EST)
From: Michael Richardson <email@example.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 06 Feb 2020 12:36:07 +0100
Subject: [Rats] how many use cases in Architecture?
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:email@example.com?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2020 11:36:17 -0000
The architecture design team would like some feedback from the WG about inclusion of use cases into the Architecture draft. There are several options, and you might have more: * include no use cases in this document, they aren't important. * include no use cases in this document, they should go in another document. * include four-five high-level use cases, not distinguishing whether they are passport, background-check, or combination * include five to eight mid-level use cases, detailing what the data flow for each would be. * include as many use cases as previously described as feasible. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] firstname.lastname@example.org http://www.sandelman.ca/ | ruby on rails [