<?xml version='1.0'?>

<reference anchor='RFC2095'>

<front>
<title abbrev='IMAP/POP AUTHorize Extension'>IMAP/POP AUTHorize Extension for Simple Challenge/Response</title>
<author initials='J.' surname='Klensin' fullname='John C. Klensin'>
<organization>MCI Telecommunications</organization>
<address>
<postal>
<street>800 Boylston St</street>
<street>7th floor</street>
<city>Boston</city>
<region>MA</region>
<code>02199</code>
<country>US</country></postal>
<phone>+1 617 960 1011</phone>
<email>klensin@mci.net</email></address></author>
<author initials='R.' surname='Catoe' fullname='Randy Catoe'>
<organization>MCI Telecommunications</organization>
<address>
<postal>
<street>2100 Reston Parkway</street>
<city>Reston</city>
<region>VA</region>
<code>22091</code>
<country>US</country></postal>
<phone>+1 703 715 7366</phone>
<email>randy@mci.net</email></address></author>
<author initials='P.' surname='Krumviede' fullname='Paul Krumviede'>
<organization>MCI Telecommunications</organization>
<address>
<postal>
<street>2100 Reston Parkway</street>
<city>Reston</city>
<region>VA</region>
<code>22091</code>
<country>US</country></postal>
<phone>+1 703 715 7251</phone>
<email>paul@mci.net</email></address></author>
<date month='January' year='1997' />
<abstract>
<t>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.  Since it utilizes Keyed-MD5 digests and does not require that the secret be stored in the clear on the server, it may also constitute an improvement on APOP for POP3 use as specified in RFC 1734.</t></abstract></front>

<seriesInfo name='RFC' value='2095' />
</reference>
