[9157] in cryptography@c2.net mail archive
RFC 3163 on ISO/IEC 9798-3 Authentication SASL Mechanism (fwd)
daemon@ATHENA.MIT.EDU (P.J. Ponder)
Fri Aug 24 15:00:25 2001
Date: Fri, 24 Aug 2001 14:56:30 -0400 (EDT)
From: "P.J. Ponder" <ponder@freenet.tlh.fl.us>
To: <cryptography@wasabisystems.com>
Message-ID: <Pine.OSF.4.31.0108241455160.103-120000@fn3.freenet.tlh.fl.us>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY=NextPart
Content-ID: <Pine.OSF.4.31.0108241455161.103@fn3.freenet.tlh.fl.us>
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--NextPart
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.OSF.4.31.0108241455162.103@fn3.freenet.tlh.fl.us>
for those not on RFC-Dist or IETF mailing lists:
---------- Forwarded message ----------
Date: Fri, 24 Aug 2001 09:44:24 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
To: rfc-dist@rfc-editor.org
Cc: rfc-ed@ISI.EDU
Subject: RFC 3163 on ISO/IEC 9798-3 Authentication SASL Mechanism
A new Request for Comments is now available in online RFC libraries.
RFC 3163
Title: ISO/IEC 9798-3 Authentication SASL Mechanism
Author(s): R. Zuccherato, M. Nystrom
Status: Experimental
Date: August 2001
Mailbox: robert.zuccherato@entrust.com,
magnus@rsasecurity.com
Pages: 17
Characters: 32498
Obsoletes/Updates/SeeAlso: None
I-D Tag: draft-zuccherato-9798-3-sasl-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3163.txt
This document defines a SASL (Simple Authentication and Security
Layer) authentication mechanism based on ISO/IEC 9798-3 and FIPS PUB
196 entity authentication.
This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind. Discussion and
suggestions for improvement are requested. 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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
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 RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
--NextPart
Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY=OtherAccess
Content-ID: <Pine.OSF.4.31.0108241455163.103@fn3.freenet.tlh.fl.us>
Content-Description:
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--OtherAccess
Content-Type: MESSAGE/EXTERNAL-BODY; ACCESS-TYPE=mail-server; SERVER="RFC-INFO@RFC-EDITOR.ORG"
Content-ID: <Pine.OSF.4.31.0108241455164.103@fn3.freenet.tlh.fl.us>
--OtherAccess
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="rfc3163.txt"; SITE="ftp.isi.edu"; ACCESS-TYPE=anon-ftp; DIRECTORY=in-notes
Content-ID: <Pine.OSF.4.31.0108241455165.103@fn3.freenet.tlh.fl.us>
--OtherAccess--
--NextPart--
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@wasabisystems.com
