Multi-party Security Contexts Within the GSS-API
draft-barton-gss-api-sec-party-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Daniel M. Barton | ||
| Last updated | 1996-02-22 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Generic Security Service Application Program Interface (GSS-API), as defined in RFC-1508 and subsequent Internet Draft documents, provides security services to callers (applications) in a generic fashion, supportable with a range of underlying mechanisms and technologies, allowing source-level portability of applications to different environments. Multi-party security contexts, where security context information is shared amongst more than two session peers, have received little consideration within the scope of the GSS-API. This document describes details of one approach for supporting multi-party security services within the GSS-API.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)