[plasma] Plasma Use Cases

"James Schaad" <jimsch@nwlink.com> Tue, 05 April 2011 17:57 UTC

Return-Path: <jimsch@nwlink.com>
X-Original-To: plasma@core3.amsl.com
Delivered-To: plasma@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id EA18528C13E for <plasma@core3.amsl.com>; Tue, 5 Apr 2011 10:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1LzN5vBvGuvt for <plasma@core3.amsl.com>; Tue, 5 Apr 2011 10:57:03 -0700 (PDT)
Received: from new-smtp02.pacifier.net (new-smtp02.pacifier.net []) by core3.amsl.com (Postfix) with ESMTP id 6B17D28C136 for <plasma@ietf.org>; Tue, 5 Apr 2011 10:57:03 -0700 (PDT)
Received: from TITUS (unknown []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by new-smtp02.pacifier.net (Postfix) with ESMTPS id C04702CA25 for <plasma@ietf.org>; Tue, 5 Apr 2011 10:58:45 -0700 (PDT)
From: James Schaad <jimsch@nwlink.com>
To: plasma@ietf.org
Date: Tue, 05 Apr 2011 11:23:38 -0700
Message-ID: <00ba01cbf3be$9acdde70$d0699b50$@nwlink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AcvzvYROYBKQoWPqREi/HzJy+oayZg==
Content-Language: en-us
Subject: [plasma] Plasma Use Cases
X-BeenThere: plasma@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "The PoLicy Augmented S/Mime \(plasma\) bof discussion list." <plasma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/plasma>, <mailto:plasma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/plasma>
List-Post: <mailto:plasma@ietf.org>
List-Help: <mailto:plasma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/plasma>, <mailto:plasma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 17:57:04 -0000

I have been thinking about use cases, as well have having a couple of
discussions since the BOF meeting at Prague.  I think that among other
things I would like to see use cases divided into three different classes,
but I want to see multiple cases potentially come out of each of the

Class #1 - The Email usage case:  These are the cases that I want to have
the Plasma discussions focus on initially.  These are the cases which are
currently (and too briefly) covered in the current requirements draft.

Class #2 - The "easy" extension cases:  This class would include the simple
things that people like PHB brought up at the BOF.  These would include the
ability to do some other simple things.  For example any CMS encrypted file
could use all of the things that are covered in class #1, since S/MIME is
built on top of CMS, but these would require that new or additional UI be
established in something other than a simple mail client.  For example to
encrypt and decrypt files might involve changes/extensions either to a file
system, a file browser or a user application (such as Microsoft Word).

Class #3 - The "hard" extension cases:  There were some questions about how
this could be looked at as a framework rather than as something that is only
for S/MIME or CMS.  Examples of this range as far as how could this be
extended into PGP or the new WOES framework.  I think this set of items is
much more fuzzy, but it seemed to have a large number of people who were
suggesting things along this line.  If that is so then I would like to get
some of these usage cases nailed down in more detail.