[Rats] aligning the use case documents appropriately

Michael Richardson <mcr@sandelman.ca> Wed, 19 June 2019 16:02 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 C3BA1120140 for <rats@ietfa.amsl.com>; Wed, 19 Jun 2019 09:02:44 -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, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 Kq0NyhKn-Szw for <rats@ietfa.amsl.com>; Wed, 19 Jun 2019 09:02:40 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 874BF120026 for <rats@ietf.org>; Wed, 19 Jun 2019 09:02:39 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 75DDC380BE for <rats@ietf.org>; Wed, 19 Jun 2019 12:01:03 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id E7816E9E; Wed, 19 Jun 2019 12:02:36 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E508EE47 for <rats@ietf.org>; Wed, 19 Jun 2019 12:02:36 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "rats@ietf.org" <rats@ietf.org>
In-Reply-To: <79ccb2d7-09a3-913d-f47d-1e702a23b341@gmail.com>
References: <MW2PR00MB03963ABEB87211AD28A16240A6490@MW2PR00MB0396.namprd00.prod.outlook.com> <12503.1552447661@localhost> <58E37DB5-098C-4387-9A52-4AECD0F69F25@island-resort.com> <6495.1553219901@dooku.sandelman.ca> <BA6E28A7-0F6A-46A8-AB1B-A64B9229F149@intel.com> <507.1553725386@dooku.sandelman.ca> <24C0968B-32B0-4EF1-99C8-61D3F0955BA1@intel.com> <793F9A34-050F-4914-AF4B-08C072730A06@island-resort.com> <D8C23800.D851F%carl@redhoundsoftware.com> <19652.1553943890@dooku.sandelman.ca> <D8C50A67.D8999%carl@redhoundsoftware.com> <79ccb2d7-09a3-913d-f47d-1e702a23b341@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25579.1560960156.1@localhost>
Date: Wed, 19 Jun 2019 12:02:36 -0400
Message-ID: <25581.1560960156@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/-KxlEbpmoh37FWA55gEWwyr-ux0>
Subject: [Rats] aligning the use case documents appropriately
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: Wed, 19 Jun 2019 16:02:45 -0000

"I am editing the usecase document prior to next Thursday's virtual interim"
This has taken longer than I would have liked, and Thursday is now tomorrow,
and you might want time to read it, so I have mostly failed here.
I am putting out a -02 document anyway.

I realized as I was processing the various comments that I and many others
are perhaps confused about what we need here.  I kept thinking that
this document was going to collect *end user* use cases, and of course some
people were wondering why I was talking about specific verticals.

Let me propose the following text:

+This document exists as place to collect use cases for the common RATS
+technologies in support of the IETF RATS charter point 1.  This document is
+not expected to be published as an RFC, but remain open as a working
+document.  It could become an appendix to provide motivation for a protocol
+standards document.
+
+This document will probably not deal with use cases from an end-user
+point of
+view, but rather on the technology verticals that wish to use RATS concepts
+(such as EAT) in their deployments.
+
+End-user use cases that would either directly leverage RATS technology, or
+would serve to inform technology choices are welcome, however.

I would be very happy if it turned out that we only discussed this point at
the virtual interim!   That we wind up with a strong consensus.

====