[abfab] RFC 7056 on Name Attributes for the GSS-API Extensible Authentication Protocol (EAP) Mechanism
rfc-editor@rfc-editor.org Tue, 31 December 2013 17:48 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: abfab@ietfa.amsl.com
Delivered-To: abfab@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AEF31AE369; Tue, 31 Dec 2013 09:48:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ceB4H-bQY-44; Tue, 31 Dec 2013 09:48:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 22AF51AE3B1; Tue, 31 Dec 2013 09:48:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F37EB7FC3A1; Tue, 31 Dec 2013 09:48:05 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20131231174805.F37EB7FC3A1@rfc-editor.org>
Date: Tue, 31 Dec 2013 09:48:05 -0800
Cc: drafts-update-ref@iana.org, abfab@ietf.org, rfc-editor@rfc-editor.org
Subject: [abfab] RFC 7056 on Name Attributes for the GSS-API Extensible Authentication Protocol (EAP) Mechanism
X-BeenThere: abfab@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 31 Dec 2013 17:48:18 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7056 Title: Name Attributes for the GSS-API Extensible Authentication Protocol (EAP) Mechanism Author: S. Hartman, J. Howlett Status: Standards Track Stream: IETF Date: December 2013 Mailbox: hartmans-ietf@mit.edu, josh.howlett@ja.net Pages: 11 Characters: 24622 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-abfab-gss-eap-naming-07.txt URL: http://www.rfc-editor.org/rfc/rfc7056.txt The naming extensions to the Generic Security Service Application Programming Interface (GSS-API) provide a mechanism for applications to discover authorization and personalization information associated with GSS-API names. The Extensible Authentication Protocol GSS-API mechanism allows an Authentication, Authorization, and Accounting (AAA) peer to provide authorization attributes alongside an authentication response. It also supplies mechanisms to process Security Assertion Markup Language (SAML) messages provided in the AAA response. This document describes how to use the Naming Extensions API to access that information. 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 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