Generic Security Service Application Programming Interface (GSS-API) Naming Extensions (RFC6680)
Original Publication Date: 2012-Aug-01
Included in the Prior Art Database: 2012-Aug-30
Internet Society Requests For Comment (RFCs)
N. Williams: AUTHOR [+4]
As described in [RFC4768], the GSS-API's naming architecture suffers from certain limitations. This document attempts to overcome these limitations.
Internet Engineering Task Force (IETF) N. Williams Request for Comments: 6680 Cryptonector, LLC Category: Standards Track L. Johansson ISSN: 2070-1721 SUNET S. Hartman Painless Security S. Josefsson SJD AB August 2012
Generic Security Service Application Programming Interface (GSS-API) Naming Extensions
The Generic Security Service Application Programming Interface (GSS-API) provides a simple naming architecture that supports name- based authorization. This document introduces new APIs that extend the GSS-API naming model to support name attribute transfer between GSS-API peers.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6680.
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
al. Standards Track [Page 1]
RFC 6680 GSS-API Naming Extensions August 2012