Application Bridging for Federated Access Beyond web (ABFAB) Usability and User Interface Considerations
draft-smith-abfab-usability-ui-considerations-03

ABFAB                                                           R. Smith
Internet-Draft                                        Cardiff University
Intended status: Informational                           January 8, 2013
Expires: July 12, 2013

 Application Bridging for Federated Access Beyond web (ABFAB) Usability
                   and User Interface Considerations
            draft-smith-abfab-usability-ui-considerations-03

Abstract

   The use of ABFAB-based technologies requires that each user's device
   is configured with the user's identities that they wish to use in
   ABFAB transactions.  This will require something on that device,
   either built into the operating system or a standalone utility, that
   will manage the user's identities and identity to service mappings.
   Anyone designing that "something" will face the same set of
   challenges.  This document aims to document these challenges with the
   aim of producing well-thought out UIs with some degree of
   consistency.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 12, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Smith                     Expires July 12, 2013                 [Page 1]
Internet-Draft           ABFAB UI Considerations            January 2013

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Smith                     Expires July 12, 2013                 [Page 2]
Internet-Draft           ABFAB UI Considerations            January 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Context  . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Considerations around Terminology  . . . . . . . . . . . . . .  6
     5.1.  Identity . . . . . . . . . . . . . . . . . . . . . . . . .  6
     5.2.  Services . . . . . . . . . . . . . . . . . . . . . . . . .  6
     5.3.  Identity to Service Mapping  . . . . . . . . . . . . . . .  6
   6.  Considerations around Management of Identities . . . . . . . .  7
     6.1.  Information associated with each Identity  . . . . . . . .  7
     6.2.  Adding/Association of an Identity  . . . . . . . . . . . .  8
       6.2.1.  Manual Addition  . . . . . . . . . . . . . . . . . . .  8
       6.2.2.  Manually Triggered Automated Addition  . . . . . . . .  9
       6.2.3.  Fully Automated Addition . . . . . . . . . . . . . . . 10
     6.3.  Modifying Identity Information . . . . . . . . . . . . . . 10
       6.3.1.  Manual Modification  . . . . . . . . . . . . . . . . . 10
       6.3.2.  Automated Modification . . . . . . . . . . . . . . . . 11
     6.4.  Verifying an identity  . . . . . . . . . . . . . . . . . . 11
     6.5.  Removing an Identity . . . . . . . . . . . . . . . . . . . 11
       6.5.1.  Manual Removal . . . . . . . . . . . . . . . . . . . . 11
       6.5.2.  Automated Removal  . . . . . . . . . . . . . . . . . . 11
   7.  Considerations around Management of Service to Identity
       Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     7.1.  Listing Services and Identities  . . . . . . . . . . . . . 12
     7.2.  Showing the Identity currently in use  . . . . . . . . . . 12
     7.3.  Associating a Service with an Identity . . . . . . . . . . 12
       7.3.1.  User-driven Manual Association . . . . . . . . . . . . 12
       7.3.2.  Automated Rules-based Association  . . . . . . . . . . 13