RFC 2195 on IMAP/POP AUTHorize Extension

RFC Editor <rfc-ed@isi.edu> Wed, 10 September 1997 23:17 UTC

Message-Id: <199709102315.AA13294@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC 2195 on IMAP/POP AUTHorize Extension
Cc: rfc-ed@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 10 Sep 1997 16:15:41 -0700
Sender: ietf-announce-request@ietf.org
From: RFC Editor <rfc-ed@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 2195:  

        Title:      IMAP/POP AUTHorize Extension for Simple
                    Challenge/Response
	Author:     J. Klensin, R. Catoe, P. Krumviede
        Category:   Proposed Standard
        Date:       September 1997
        Mailbox:    klensin@mci.net, randy@mci.net, paul@mci.net
        Pages:      5
        Characters: 10468
        Obsoletes:  2095


        URL:        ftp://ds.internic.net/rfc/rfc2195.txt


While IMAP4 supports a number of strong authentication mechanisms
as described in RFC 1731, it lacks any mechanism that neither passes
cleartext, reusable passwords across the network nor requires either a
significant security infrastructure or that the mail server update a
mail-system-wide user authentication file on each mail access.  This
specification provides a simple challenge-response authentication
protocol that is suitable for use with IMAP4.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

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 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
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.

ftp://ds.internic.net/rfc/rfc2195.txt"><ftp://ds.internic.net/rfc/rfc2195.txt>

RFC 2195 on IMAP/POP AUTHorize Extension RFC Editor