6 Thank you (Acknowledgments)
ABISOURCE's Eric W. Sink is the original author of the previous version of this specification.
Other authors who have contributed to this specification through discussion methods:
Peter J. Churchyard, Ned Freed and David M. Kristol.
JIM GetTys and Larry Masinter have done the last update to this document.
7 Reference Bibliography (References)
[1] Berners-Lee, T., Fielding, R. And H. Frystyk, "Hypertext
Transfer Protocol - HTTP / 1.0 ", RFC 1945, May 1996.
[2] FIELDING, R., GetTys, J., Mogul, J., Frysyk, H., Masinter, L.,
Leach, P. And T. Berners-Lee, "Hypertext Transfer Protocol -
HTTP / 1.1 ", RFC 2616, June 1999.
[3] Rivest, R., "THE MD5 Message-Digest Algorithm", RFC 1321, APRIL
The 1992.
[4] FREED, N. And N. Borenstein. "Multipurpose Internet Mail
Extensions (MIME) Part ONE: FORMAT of Internet Message Bodies,
RFC 2045, NOVEMBER 1996.
[5] Dierks, T. And C. Allen "The TLS Protocol, Version 1.0", RFC
2246, January 1999.
[6] Franks, J., Hallam-Baker, P., Hostetler, J., Leach, P.,
Luotonen, A., Sink, E. and L. Stewart, "An Extension TO HTTP:
Digest Access Authentication, RFC 2069, January 1997.
[7] Berners Lee, T, Fielding, R. And L. Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax, RFC 2396, August 1998.
[8] Kaliski, B., Robshaw, M., "Message Authentication with MD5",
Cryptobytes, SPING 1995, RSA Inc,
(http://www.rsa.com/rsalabs/pubs/cryptobytes/spring95/md5.htm)
[9] Klensin, J., Catoe, R. and P. Krumviede, "IMAP / POP Authorize
Extension for Simple Challenge / Response ", RFC 2195, September
1997.
[10] Morgan, B., Alvestrand, H., Hodges, J., Wahl, M.,
"Authentication Methods for LDAP", Work in Progress.
Franks, et al. Standards TRACK [Page 31]
8 author address (Authors' Addresses) John Franks
Professor of Mathematics
Department of Mathematics
Northwestern University
Evanston, IL 60208-2730, USA
Email: john@math.nwu.edu
Phillip M. Hallam-Baker
Principal Consultant
VeriSign Inc.
301 Edgewater Place
Suite 210
Wakefield MA 01880, USA
Email: pbaker@verignign.com
Jeffery L. Hostetler
Software craftsman
Abisource, Inc.
6 Dunlap Court
Savoy, IL 61874
Email: jeff@abisource.com
Scott D. Lawrence
Agranat Systems, Inc.
5 Clocktower Place, Suite 400
Maynard, MA 01754, USA
Email: lawrence@agranat.com
Paul J. Leach
Microsoft Corporation
1 Microsoft Way
Redmond, WA 98052, USA
Email: paulle@microsoft.com
Franks, et al. Standards TRACK [Page 32]
Ari Luotonen
Member of Technical Staff
Netscape Communications Corporation
501 East Middlefield Road
Mountain view, CA 94043, USA
Lawrence C. STEWART
Open Market, Inc.
215 FIRST Street
Cambridge, MA 02142, USA
Email: Stewart@openmarket.com
Franks, et al. Standards TRACK [Page 33]
9. Complete Copyright Statement (Full Copyright Statement)
Copyright (c) The Internet Society (1999). All Rights Reserved.
THIS Document And Translations of It May Be Copied and Furnished To
Others, And DeriVative Works That Comment On or OtherWise Explain IT
OR Assist in ITS Implementation May Be Prepared, Copied, Published
And Distributed, in Whole or in Part, WITHOUT RESTRICTION OF ANY
Kind, Provided That The Above Copyright Notice and this Paragraph Are
Included on All Such Copies and DeriVative Works. However, this
Document Itself May Not Be Modified in Any Way, Such as by Removing
The Copyright Notice Or References To The Internet Society or Other Interinternet Organizations, Except As Needed for the Purpose of
Developing Internet Standards in Which Case the Procedures for
Copyrights Defined in The Internet Standards Process Must Be
Followed, or as required to translate it inTo languages Other Than
ENGLISH.
THE LIMITED Permissions Grand Above Are Perpetual and Will Not Be
REVOKED by the Internet society or its surcessors or associgns.
This Document and the information contained here0 is provided on an
"As IS" Basis and the Internet Society and the Internet Engineering
Task Force Disclaims All Warranties, Express or Implied, Including
But not limited to any warranty That The Use of the information
Herein Will Not Infringe Any Rights or Any Implied Warranties of
Merchantability or fitness for a particular purpose.
Thanks (Acknowledgement)
RFC Author Fund provided by the Internet community.
Franks, et al. STANDARDS TRACK [Page 34]
Translator statement:
This document is translated by chifire (chifire@263.net).
This document maintains consistent with the original RFC documentation as much as possible in the typographic format.
Since I have limited level, some places may be insufficient enough, or even mistakes, or some terminology translation is wrong, please invite God to forgive, and write criticism.
