[abfab] RFC 7831 on Application Bridging for Federated Access Beyond Web (ABFAB) Architecture

rfc-editor@rfc-editor.org Wed, 11 May 2016 23:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: abfab@ietfa.amsl.com
Delivered-To: abfab@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D2C6212D18F; Wed, 11 May 2016 16:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id XuIsRafl-MBw; Wed, 11 May 2016 16:20:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB2B812D706; Wed, 11 May 2016 16:20:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CAFEA180003; Wed, 11 May 2016 16:19:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160511231904.CAFEA180003@rfc-editor.org>
Date: Wed, 11 May 2016 16:19:04 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/abfab/wSLELwEg8-7em1sXkpO_2yher4I>
Cc: drafts-update-ref@iana.org, abfab@ietf.org, rfc-editor@rfc-editor.org
Subject: [abfab] RFC 7831 on Application Bridging for Federated Access Beyond Web (ABFAB) Architecture
X-BeenThere: abfab@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Application Bridging, Federated Authentication Beyond \(the web\)" <abfab.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abfab>, <mailto:abfab-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/abfab/>
List-Post: <mailto:abfab@ietf.org>
List-Help: <mailto:abfab-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abfab>, <mailto:abfab-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 23:20:04 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7831

        Title:      Application Bridging for Federated Access 
                    Beyond Web (ABFAB) Architecture 
        Author:     J. Howlett, S. Hartman,
                    H. Tschofenig, J. Schaad
        Status:     Informational
        Stream:     IETF
        Date:       May 2016
        Mailbox:    josh.howlett@ja.net, 
        Pages:      46
        Characters: 114076
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-abfab-arch-13.txt

        URL:        https://www.rfc-editor.org/info/rfc7831

        DOI:        http://dx.doi.org/10.17487/RFC7831

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 access and web-based access.
However, the solutions to these use cases that have been proposed and
deployed tend to have few 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), the Generic Security Service
Application Program Interface (GSS-API), 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.

This document is a product of the Application Bridging for Federated Access Beyond web Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC