Application Bridging for Federated Access Beyond Web (ABFAB) Architecture
draft-ietf-abfab-arch-03

The information below is for an old version of the document
Document Type Active Internet-Draft (abfab WG)
Last updated 2012-07-09
Replaces draft-lear-abfab-arch
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                                                         J. Howlett
Internet-Draft                                                 JANET(UK)
Intended status: Informational                                S. Hartman
Expires: January 10, 2013                              Painless Security
                                                           H. Tschofenig
                                                  Nokia Siemens Networks
                                                                 E. Lear
                                                      Cisco Systems GmbH
                                                               J. Schaad
                                                 Soaring Hawk Consulting
                                                            July 9, 2012

      Application Bridging for Federated Access Beyond Web (ABFAB)
                              Architecture
                      draft-ietf-abfab-arch-03.txt

Abstract

   Over the last decade a substantial amount of work has occurred in the
   space of federated access management.  Most of this effort has
   focused on two use-cases: network and web-based access.  However, the
   solutions to these use-cases that have been proposed and deployed
   tend to have few common building blocks in common.

   This memo describes an architecture that makes use of extensions to
   the commonly used security mechanisms for both federated and non-
   federated access management, including the Remote Authentication Dial
   In User Service (RADIUS) and the Diameter protocol, the Generic
   Security Service (GSS), the GS2 family, the Extensible Authentication
   Protocol (EAP) and the Security Assertion Markup Language (SAML).
   The architecture addresses the problem of federated access management
   to primarily non-web-based services, in a manner that will scale to
   large numbers of identity providers, relying parties, and
   federations.

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

Howlett, et al.         Expires January 10, 2013                [Page 1]
Internet-Draft             ABFAB Architecture                  July 2012

   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 January 10, 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
   described in the Simplified BSD License.

Howlett, et al.         Expires January 10, 2013                [Page 2]
Internet-Draft             ABFAB Architecture                  July 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5
     1.2.  An Overview of Federation  . . . . . . . . . . . . . . . .  6
     1.3.  Challenges to Contemporary Federation  . . . . . . . . . .  9
     1.4.  An Overview of ABFAB-based Federation  . . . . . . . . . .  9
     1.5.  Design Goals . . . . . . . . . . . . . . . . . . . . . . . 12
     1.6.  Use of AAA . . . . . . . . . . . . . . . . . . . . . . . . 13
     1.7.  Use of GSS-API . . . . . . . . . . . . . . . . . . . . . . 14
   2.  Architecture . . . . . . . . . . . . . . . . . . . . . . . . . 15
     2.1.  Relying Party to Identity Provider . . . . . . . . . . . . 16
       2.1.1.  AAA, RADIUS and Diameter . . . . . . . . . . . . . . . 17
       2.1.2.  Discovery and Rules Determination  . . . . . . . . . . 18
       2.1.3.  Routing and Technical Trust  . . . . . . . . . . . . . 19
       2.1.4.  SAML Assertions  . . . . . . . . . . . . . . . . . . . 20
     2.2.  Client To Identity Provider  . . . . . . . . . . . . . . . 22
       2.2.1.  Extensible Authentication Protocol (EAP) . . . . . . . 22
Show full document text