[abfab] RFC 7832 on Application Bridging for Federated Access Beyond Web (ABFAB) Use Cases

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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E37C12D831; Wed, 11 May 2016 16:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IvaceBOL4y9P; Wed, 11 May 2016 16:20:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BB3212D82B; Wed, 11 May 2016 16:20:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AB692180204; Wed, 11 May 2016 16:19:16 -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: <20160511231916.AB692180204@rfc-editor.org>
Date: Wed, 11 May 2016 16:19:16 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/abfab/qL31e8yBmN3TmqKMbwbAhLquWSQ>
Cc: drafts-update-ref@iana.org, abfab@ietf.org, rfc-editor@rfc-editor.org
Subject: [abfab] RFC 7832 on Application Bridging for Federated Access Beyond Web (ABFAB) Use Cases
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:27 -0000

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

        
        RFC 7832

        Title:      Application Bridging for Federated Access 
                    Beyond Web (ABFAB) Use Cases 
        Author:     R. Smith, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       May 2016
        Mailbox:    rhys.smith@jisc.ac.uk
        Pages:      13
        Characters: 33640
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-abfab-usecases-05.txt

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

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

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 memo 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
Application Bridging for Federated Access Beyond web (ABFAB)
architecture and specifications.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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