home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_a_c
/
draft-ietf-cat-dass-02.txt
< prev
next >
Wrap
Text File
|
1993-09-11
|
2KB
|
60 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1507:
Title: DASS - Distributed Authentication Security Service
Author: C. Kaufman
Mailbox: kaufman@zk3.dec.com
Pages: 119
Characters: 287,809
Updates/Obsoletes: none
Authentication is a security service. The goal of authentication is to
reliably learn the name of the originator of a message or request. The
classic way by which people authenticate to computers (and by which
computers authenticate to one another) is by supplying a password.
There are a number of problems with existing password based schemes
which DASS attempts to solve. The goal of DASS is to provide
authentication services in a distributed environment which are both
more secure (more difficult for a bad guy to impersonate a good guy)
and easier to use than existing mechanisms.
This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard. Discussion and suggestions
for improvement are requested. Please refer to the current edition of
the "Internet Official Protocol Standards" for the standardization
state and status of this protocol. Distribution of this memo is
unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body
"help: ways_to_get_rfcs". For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Joyce K. Reynolds
USC/Information Sciences Institute