[55] in Open-Software-Foundation-News
OSF-RFC 64.0
daemon@ATHENA.MIT.EDU (Walt Tuvell)
Tue Oct 25 17:01:15 1994
Resent-From: Bill Cattey <wdc@MIT.EDU>
Resent-To: osf-news-mtg@menelaus.LOCAL
From: Walt Tuvell <walt@osf.org>
Date: Tue, 25 Oct 94 12:43:38 -0400
To: sig-dce@osf.org, sig-security@osf.org, sig-dce-security@osf.org
Cc: dce-tech@osf.org, dce-team@osf.org
*** OSF-RFC ANNOUNCEMENT ***
The following OSF-RFC has just been published:
=====================================================================
64.0 C. Blauner, J. Schindler, "Security SIG Strategy Document",
October 1994.
Bytes: roff=47855, txt=40742, ps=136402; pages: txt=16, ps=10.
This is, to some extent, a "historical" document. It is the product
of the OSF Security SIG, and was originally produced and presented to
OSF in October, 1992. This RFC version of the document is a
reproduction of the original document -- verbatim, except for minor
editing (reformatting, clarification, correction of typographical
errors), and the addition of this introductory paragraph and an
Acknowledgements section. In particular, this document has not been
substantively revised to take into account recent events, such as the
course of technological progress over the last two years, or the 1994
re-organization of OSF and the introduction of Pre-Structured
Technologies (PST's) into OSF's process model. It is anticipated,
however, that this RFC will now become a "living document", and that
such revisions will be undertaken in the future.
=====================================================================
/* 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 were known as "DCE-RFC's". */
- Walt Tuvell (OSF), OSF-RFC Editor, walt@osf.org, +1-617-621-8764
