[126] in Open-Software-Foundation-News
OSF-RFC 80.0
daemon@ATHENA.MIT.EDU (Walt Tuvell)
Fri Feb 24 15:11:55 1995
Resent-From: Bill Cattey <wdc@MIT.EDU>
Resent-To: osf-news-mtg@menelaus.LOCAL
From: Walt Tuvell <walt@osf.org>
Date: Fri, 24 Feb 95 13:38:35 -0500
To: sig-dce@osf.org, sig-security@osf.org, sig-dce-security@osf.org
*** OSF-RFC ANNOUNCEMENT ***
The following OSF-RFC has just been published:
=====================================================================
80.0 J. Wray, "DCE 1.2 Certification API -- Functional
Specification", February 1995,
Bytes: roff=44451, txt=35160, ps=130334; pages: txt=14, ps=12.
This document describes the DCE 1.2 certification API. This API
provides a distributed name to public-key service, supporting the
trust models of (at least) DCE hierarchical-cells and a PEM-like
model.
=====================================================================
/* Instructions for FTP access: "ftp grabbag.osf.org" (130.105.100.2),
user="dce-rfc", password="dce-rfc", "cd dce-rfc", usual ftp commands.
Instructions for Internet email access: "mail dce-rfc-archive@osf.org",
subject line null, body has two lines that look like this:
path <your-return-email-address>
send rfc <rfc-name>
where <rfc-name> has one of two forms:
rfc<M>.<m>.[roff|txt|ps]
rfc-index.[roff|txt|ps] <-- See this for list of all RFC's.
For full information about these and all other aspects of OSF-RFC's, see
the Introductory RFC 0.0 (rfc0.0.txt, which is considered REQUIRED
READING for all users of this series). Authors of OSF-RFC's must also
consult the Template and Style Guide RFC 0.1 (rfc0.1.roff).
HISTORICAL NOTE: OSF-RFC numbers < 62 are also known as "DCE-RFC's". */
- Walt Tuvell (OSF), OSF-RFC Editor, walt@osf.org, +1-617-621-8764
