Application Bridging for Federated Access Beyond web (ABFAB) Use Cases
draft-ietf-abfab-usecases-02

The information below is for an old version of the document
Document Type Active Internet-Draft (abfab WG)
Last updated 2012-02-21 (latest revision 2011-07-05)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ABFAB                                                      R. Smith, Ed.
Internet-Draft                                        Cardiff University
Intended status: Informational                         February 21, 2012
Expires: August 24, 2012

 Application Bridging for Federated Access Beyond web (ABFAB) Use Cases
                      draft-ietf-abfab-usecases-02

Abstract

   Federated authentication has so far been typically associated with
   Web-based services, but there is growing interest in the application
   of federated authentication for non-Web services.  The goal of this
   document is to document a selection of the wide variety of contexts
   whose user experience could be improved through the use of
   technologies based on the ABFAB architecture and specifications.

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 August 24, 2012.

Copyright Notice

   Copyright (c) 2012 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
   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

Smith                    Expires August 24, 2012                [Page 1]
Internet-Draft               ABFAB Use Cases               February 2012

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Context of Use Cases . . . . . . . . . . . . . . . . . . . . .  3
   4.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     4.1.  Cloud Services . . . . . . . . . . . . . . . . . . . . . .  4
     4.2.  High Performance Computing . . . . . . . . . . . . . . . .  5
     4.3.  Grid Infrastructure  . . . . . . . . . . . . . . . . . . .  5
     4.4.  Databases and Directories  . . . . . . . . . . . . . . . .  6
     4.5.  Media Streaming  . . . . . . . . . . . . . . . . . . . . .  7
     4.6.  Printing . . . . . . . . . . . . . . . . . . . . . . . . .  8
     4.7.  Accessing Applications from Devices on a Telecoms
           Infrastructure . . . . . . . . . . . . . . . . . . . . . .  8
     4.8.  Trust Router . . . . . . . . . . . . . . . . . . . . . . .  9
     4.9.  PLASMA . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     4.10. SIP  . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   5.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . .  9
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Appendix A.  Change Log  . . . . . . . . . . . . . . . . . . . . . 11
   Appendix B.  Open Issues . . . . . . . . . . . . . . . . . . . . . 12

Smith                    Expires August 24, 2012                [Page 2]
Internet-Draft               ABFAB Use Cases               February 2012

1.  Introduction

   Federated identity facilitates the controlled sharing of information
   about people (a.k.a. 'principals'), commonly across organisational
   boundaries.  This avoids redundant registration of principals who
   operate in and across multiple domains; both reducing administrative
   overhead for the organisations involved and improving usability for
   the principal.  Simultaneously, it can also help address privacy-
   related concerns, along with the regulatory and statutory
   requirements of some jurisdictions.

   The information that is passed between organisations may include
   authentication state and identity information that can be used for
   many purposes, including making access management decisions.  A
Show full document text