"Generic Security Service API Version 2 : Java Bindings Update", Mayan Upadhyay, Seema Malkani, 16-Feb-09. ( bytes)

The Generic Security Services Application Program Interface (GSS-API)offers application programmers uniform access to security services atop a variety of underlying cryptographic mechanisms. This document updates the Java bindings for the GSS-API that are specified in "Generic Security Service API version 2 : Java Bindings" (RFC2853). This document obsoletes RFC 2853 by making specific and incremental clarifications and corrections to it in response to identification of transcription errors and implementation experience. The GSS-API is described at a language independent conceptual level in "Generic Security Service Application Program Interface Version 2, Update 1" (RFC2743). The GSS-API allows a caller application to authenticate a principal identity, to delegate rights to a peer, and to apply security services such as confidentiality and integrity on a per-message basis. Examples of security mechanisms defined for GSS- API are "The Simple Public-Key GSS-API Mechanism" (RFC2025) and "The Kerberos Version 5 GSS-API Mechanism (RFC4121).

"Namespace Considerations and Registries for GSS-API Extensions", Nicolas Williams, 1-Apr-09. ( bytes)

This document describes the ways in which the GSS-API may be extended and directs the creation of an IANA registry for various GSS-API namespaces.

"GSS-API Naming Extensions", Nicolas Williams, Leif Johansson, 30-Jul-09. ( bytes)

The Generic Security Services API (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.

Return to Internet-Draft directory.

Return to IETF home page.