[Rats] how many use cases in Architecture?

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 06 February 2020 11:36 UTC

Return-Path: <mcr@sandelman.ca>
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 AE8D9120907 for <rats@ietfa.amsl.com>; Thu, 6 Feb 2020 03:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WcS49QuavfXi for <rats@ietfa.amsl.com>; Thu, 6 Feb 2020 03:36:11 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (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 <rats@ietf.org>; 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 <rats@ietf.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 <mcr+ietf@sandelman.ca>
To: rats@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 06 Feb 2020 12:36:07 +0100
Message-ID: <8944.1580988967@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/1rfE41ZZeSfSG_b9X0dsZq4FFuQ>
Subject: [Rats] how many use cases in Architecture?
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: 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  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [