Subject: [abfab] RFC 7057 on Update to the Extensible Authentication Protocol (EAP) Applicability Statement for Application Bridging for Federated Access Beyond Web (ABFAB)

From: [email-masked]
Date: Tue, 31 Dec 2013 09:48:29 -0800 (PST)

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

        RFC 7057

        Title:      Update to the Extensible Authentication 
                    Protocol (EAP) Applicability Statement for Application 
                    Bridging for Federated Access Beyond Web 
                    (ABFAB) 
        Author:     S. Winter, J. Salowey
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2013
        Mailbox:    [email-masked], 
                    [email-masked]
        Pages:      7
        Characters: 16006
        Updates:    RFC 3748

        I-D Tag:    draft-ietf-abfab-eapapplicability-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7057.txt

This document updates the Extensible Authentication Protocol (EAP)
applicability statement from RFC 3748 to reflect recent usage of the
EAP protocol in the Application Bridging for Federated Access Beyond
web (ABFAB) architecture.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC