Move developer documentation to doc/Development

[squirrelmail.git] / doc / Development / rfc_documents.txt

SquirrelMail "talks" several protocols.  To make sure that we are
standards-compatible, we need to refer to RFC documents.  Here's a list of
the ones we use a lot:

They are available from a wide variety of places on the net.
For instance, if you want RFC 822, you can jump directly to it at
    http://www.faqs.org/rfcs/rfc822.html
    http://www.rfc-editor.org/rfc/rfc822.txt
    http://www.imc.org/Searchable/rfc822

NUMBER     DESCRIPTION
-----------------------------------------------------------
RFC 822    Format of ARPA Internet text messages
RFC 1730   IMAP version 4 (obsoleted by 2060)
RFC 2045   MIME Part One: Format of Internet Message Bodies
RFC 2046   MIME Part Two: Media Types
RFC 2047   MIME Part Three: Message Header Extensions for Non-ASCII Text
RFC 2060   IMAP version 4rev1 (obsoleted by 3501)
RFC 2183   Content-Disposition MIME header
RFC 2195   IMAP/POP AUTHorize Extension for Simple Challenge/Response
RFC 2221   IMAP4 Login Referrals
RFC 2298   Details return receipts
RFC 2342   The IMAP4 NAMESPACE command
RFC 2369   The Use of URLs as Meta-Syntax for Core Mail List Commands and their
           Transport through Message Header Fields 
           (implemented in listcommands plugin)
RFC 2616   HTTP/1.1
RFC 2683   IMAP4 Implementation Recommendations
RFC 2822   Format of an email message (sendmail)
RFC 2831   Using Digest Authentication as a SASL Mechanism (digest-md5)
RFC 3501   IMAP version 4rev1