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


	STD 11:
        RFC 1869:

        Title:      SMTP Service Extensions
        Author:     J. Klensin, N. Freed, M. Rose, E. Stefferud
                    & D. Crocker
        Date:       November 1995
        Mailbox:    klensin@mci.net, ned@innosoft.com,
                    mrose@dbc.mtview.ca.us, stef@nma.com,
                    dcrocker@mordor.stanford.edu   
        Pages:      11
        Characters: 23,299
        Obsoletes:  1651

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


This memo defines a framework for extending the SMTP service by
defining a means whereby a server SMTP can inform a client SMTP as to
the service extensions it supports.  Extensions to the SMTP service
are registered with the IANA. This framework does not require
modification of existing SMTP clients or servers unless the features
of the service extensions are to be requested or provided.  This RFC
is the product of the Internet Mail Extensions Working Group of the
IETF.

This is now a 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@CNRI.RESTON.VA.US.  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
USC/Information Sciences Institute