datatracker.ietf.org
Sign in
Version 5.6.2.p3, 2014-07-31
Report a bug

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

Document type: Active Internet-Draft (abfab WG)
Document stream: IETF
Last updated: 2012-09-26 (latest revision 2012-09-25)
Intended RFC status: Informational
Other versions: plain text, xml, pdf, html

IETF State: Submitted to IESG for Publication Oct 2010 Dec 2010
Consensus: Unknown
Document shepherd: Klaas Wierenga
Shepherd Write-Up: Last changed 2012-07-17

IESG State: RFC Ed Queue
RFC Editor State: MISSREF
Responsible AD: Stephen Farrell
IESG Note: Klaas Wierenga (klaas@cisco.com) is the document shepherd.
Send notices to: abfab-chairs@tools.ietf.org, draft-ietf-abfab-usecases@tools.ietf.org

ABFAB                                                      R. Smith, Ed.
Internet-Draft                                        Cardiff University
Intended status: Informational                        September 25, 2012
Expires: March 29, 2013

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

Abstract

   Federated identity is typically associated with Web-based services at
   present, but there is growing interest in its application in non Web-
   based contexts.  The goal of this document is to document a selection
   of the wide variety of these 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 March 29, 2013.

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 March 29, 2013                 [Page 1]
Internet-Draft               ABFAB Use Cases              September 2012

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Context of Use Cases . . . . . . . . . . . . . . . . . . . . .  3
   3.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     3.1.  Cloud Services . . . . . . . . . . . . . . . . . . . . . .  4
       3.1.1.  Cloud-based Application Services . . . . . . . . . . .  4
       3.1.2.  Cloud-based Infrastructure Services  . . . . . . . . .  5
     3.2.  High Performance Computing . . . . . . . . . . . . . . . .  6
     3.3.  Grid Infrastructure  . . . . . . . . . . . . . . . . . . .  7
     3.4.  Databases and Directories  . . . . . . . . . . . . . . . .  8
     3.5.  Media Streaming  . . . . . . . . . . . . . . . . . . . . .  8
     3.6.  Printing . . . . . . . . . . . . . . . . . . . . . . . . .  9
     3.7.  Accessing Applications from Devices on a Telecoms
           Infrastructure . . . . . . . . . . . . . . . . . . . . . .  9
     3.8.  Enhanced Security Services for S/MIME  . . . . . . . . . . 10
     3.9.  Smart Objects  . . . . . . . . . . . . . . . . . . . . . . 11
   4.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
   5.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 12
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 12
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 12

Smith                    Expires March 29, 2013                 [Page 2]
Internet-Draft               ABFAB Use Cases              September 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 the
   administrative overhead for the organizations involved and improving
   the usability of systems 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 organizations may include
   authentication state and identity information that can be used for

[include full document text]