[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 RFC 2645

Internet Draft: On-Demand Mail Relay                         R. Gellens
Document: draft-gellens-on-demand-06.txt                       QUALCOMM
Expires: 30 September 1999                                31 March 1999


                      ON-DEMAND MAIL RELAY (ODMR)
                     SMTP with Dynamic IP Addresses


Status of this Memo:

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.

    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as
    Internet-Drafts.

    Internet-Drafts are draft documents valid for a maximum of six
    months and may be updated, replaced, or obsoleted by other documents
    at any time.  It is inappropriate to use Internet- Drafts as
    reference material or to cite them other than as "work in progress."

    The list of current Internet-Drafts can be accessed at
    <http://www.ietf.org/ietf/1id-abstracts.txt>

    The list of Internet-Draft Shadow Directories can be accessed at
    <http://www.ietf.org/shadow.html>.

    A version of this draft document is intended for submission to the
    RFC editor as a Proposed Standard for the Internet Community.
    Discussion and suggestions for improvement are requested.


Copyright Notice

    Copyright (C) The Internet Society 1999.  All Rights Reserved.

















Gellens                 Expires September 1999                 [Page 1]

Internet Draft              On-Demand Mail Relay              March 1999

Table of Contents

     1.  Abstract . . . . . . . . . . . . . . . . . . . . . . . . . .  2
     2.  Conventions Used in this Document . . . . . . . . . . . . . . 2
     3.  Comments . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     4.  Description . . . . . . . . . . . . . . . . . . . . . . . . . 3
     5.  States . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
       5.1.  Initial State . . . . . . . . . . . . . . . . . . . . . . 4
         5.1.1.  EHLO . . . . . . . . . . . . . . . . . . . . . . . .  4
         5.1.2.  AUTH  . . . . . . . . . . . . . . . . . . . . . . . . 4
         5.1.3.  QUIT . . . . . . . . . . . . . . . . . . . . . . . .  5
       5.2.  Authenticated State . . . . . . . . . . . . . . . . . . . 5
         5.2.1.  ATRN (Authenticated TURN)  . . . . . . . . . . . . .  5
       5.3.  Reversed State  . . . . . . . . . . . . . . . . . . . . . 6
       5.4.  Other Commands . . . . . . . . . . . . . . . . . . . . .  6
     6.  Example On-Demand Mail Relay Session: . . . . . . . . . . . . 6
     7.  Response Codes . . . . . . . . . . . . . . . . . . . . . . .  7
     8.  Security Considerations . . . . . . . . . . . . . . . . . . . 7
     9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . .  7
    10.  References  . . . . . . . . . . . . . . . . . . . . . . . . . 7
    11.  Full Copyright Statement . . . . . . . . . . . . . . . . . .  8
    12.  Author's Address  . . . . . . . . . . . . . . . . . . . . . . 9


1.  Abstract

    With the spread of low-cost computer systems and Internet
    connectivity, the demand for local mail servers has been rising.
    Many people now want to operate a mail server on a system which has
    only an intermittent connection to a service provider.  If the
    system has a static IP address, the ESMTP ETRN command [ETRN] can be
    used.  However, systems with dynamic IP addresses (which are very
    common with low-cost connections) have no widely-deployed solution.

    This memo proposes a new service, On-Demand Mail Relay (ODMR), which
    is a profile of SMTP [SMTP, ESMTP], providing for a secure,
    extensible, easy to implement approach to the problem.


2.  Conventions Used in this Document

    Because the client and server roles reverse during the session, to
    avoid confusion, the terms "customer" and "provider" will be used in
    place of "client" and "server", although of course this protocol may
    be useful in cases other than commercial service providers and
    customers.

    In examples, "P:" is used to indicate lines sent by the provider,
    and "C:" indicates those sent by the customer.  Line breaks within a
    command are for editorial purposes only.




Gellens                 Expires September 1999                 [Page 2]

Internet Draft              On-Demand Mail Relay              March 1999

    The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY"
    in this document are to be interpreted as defined in [KEYWORDS].

    Examples use 'example.net' as the provider, and 'example.org' and
    'example.com' as the customers.


3.  Comments

    Private comments should be sent to the author.  Public comments may
    be sent to the IETF Disconnected SMTP mailing list,
    <ietf-disconn-smtp@imc.org>.  To subscribe, send a message to
    <ietf-disconn-smtp-request@imc.org> containing the word SUBSCRIBE as
    the body.


4.  Description

    On-Demand Mail Relay is a restricted profile of SMTP [SMTP, ESMTP].
    Port 366 is reserved for On-Demand Mail Relay.  The initial client
    and server roles are short-lived, as the point is to allow the
    intermittently-connected host to request mail held for it by a
    service provider.

    The customer initiates a connection to the provider, authenticates,
    and requests its mail.  The roles of client and server then reverse,
    and normal SMTP [SMTP, ESMTP] proceeds.

    The provider has an On-Demand Mail Relay process listening for
    connections on the ODMR port.  This process does not need to be a
    full SMTP server.  It does need to be an SMTP client with access to
    the outgoing mail queues, and as a server implement the EHLO, AUTH,
    ATRN, and QUIT commands.

    An MTA normally has a mail client component which processes the
    outgoing mail queues, attempting to send mail for particular
    domains, based on time or event (such as new mail being placed in
    the queue, or receipt of an ETRN command by the SMTP server
    component).  The On-Demand Mail Relay service processes the outgoing
    queue not on a timer or new mail creation, but on request.

    The provider side has normal SMTP server responsibilities [SMTP],
    including generation of delivery failure notices, etc. as needed.











Gellens                 Expires September 1999                 [Page 3]

Internet Draft              On-Demand Mail Relay              March 1999

5.  States

    The On-Demand Mail Relay service has three states: an initial state,
    an authenticated state, and a reversed state.  The state progression
    is illustrated in the following diagram:

---------------------------
!      initial state      !
---------------------------
  !             !
QUIT           AUTH
  !             !
  !             V
  !      -----------------------
  !      ! authenticated state !
  !      -----------------------
  !       !            !
  !      QUIT         ATRN
  !       !            !
  !       !            V
  !       !      ------------------
  !       !      ! reversed state !
  !       !      ------------------
  !       !         !
  !       !        QUIT
  !       !         !
  V       V         V
  ---------------------
  !    termination    !
  ---------------------


5.1.  Initial State

    In the initial state, the provider is the server and the customer is
    the client.  Three commands are valid:  EHLO, AUTH, and QUIT.


5.1.1.  EHLO

    The EHLO command is the same as in [ESMTP].  The response MUST
    include AUTH and ATRN.


5.1.2.  AUTH

    The AUTH command is specified in [AUTH].  The AUTH command uses a
    [SASL] mechanism to authenticate the session.  The session is not
    considered authenticated until a success response to AUTH has been
    sent.




Gellens                 Expires September 1999                 [Page 4]

Internet Draft              On-Demand Mail Relay              March 1999

    For interoperability, implementations MUST support the CRAM-MD5
    mechanism [CRAM].  Other SASL mechanisms may be supported.  A site
    MAY disable CRAM-MD5 support if it uses more secure methods.  The
    EXTERNAL mechanism [SASL] might be useful in some cases, for
    example, if the provider has already authenticated the client, such
    as during a PPP connection.


5.1.3.  QUIT

    The QUIT command is the same as in [SMTP].


5.2.  Authenticated State

    The authenticated state is entered after a successful AUTH command.
    Two commands are valid in the authenticated state:  ATRN and QUIT.


5.2.1.  ATRN (Authenticated TURN)

    Unlike the TURN command in [SMTP], the ATRN command optionally takes
    one or more domains as a parameter.  The ATRN command MUST be
    rejected if the session has not been authenticated.  Response code
    530 [AUTH] should be used for this.

    The timeout for this command MUST be at least 10 minutes to allow
    the provider time to process its mail queue.

    An ATRN command sent with no domains is equivalent to an ATRN
    command specifying all domains to which the customer has access.

    If the authentication used by the customer does not provide access
    to all of the domains specified in ATRN, the provider MUST NOT send
    mail for any domains to the customer; the provider MUST reject the
    ATRN command with a 450 code.

    If the customer does have access to all of the specified domains,
    but none of them have any queued mail, the provider normally rejects
    the ATRN command with response code 453.  The provider MAY use
    response code 450, to avoid disclosing information to unauthorized
    parties regarding the domains for which it provides ODMR service.
    Or, the provider MAY issue a 250 success code, and after the roles
    are reversed, send a QUIT following the EHLO.

    The provider MAY also reject the ATRN command with a 450 response to
    indicate refusal to accept multiple requests issued within a
    particular time interval.

    If the customer has access to all of the specified domains and mail
    exists in at least one of them, the provider issues a 250 success
    code.


Gellens                 Expires September 1999                 [Page 5]

Internet Draft              On-Demand Mail Relay              March 1999

    If the server is unable to verify access to the requested domains
    (for example, a mapping database is temporarily unavailable),
    response code 451 is sent.

    [ABNF] for ATRN:

    atrn          = "ATRN" [domain *("," domain)]

    domain        = sub-domain 1*("." sub-domain)

    sub-domain    = (ALPHA / DIGIT) *(ldh-str)

    ldh-str       = *(ALPHA / DIGIT / "-") (ALPHA / DIGIT)


5.3.  Reversed State

    After the provider has sent a success reply to the ATRN command, the
    roles reverse, and the customer becomes the server, and the provider
    becomes the client.

    After receiving the success response to ATRN, the customer sends a
    standard SMTP initial greeting line.  At this point normal SMTP
    [SMTP, ESMTP] commands are used.  Typically the provider sends EHLO
    after seeing the customer's greeting, to be followed by MAIL FROM
    and so on.


5.4.  Other Commands

    The provider MAY reject all commands other than EHLO, AUTH, ATRN,
    and QUIT with response code 502.


6.  Example On-Demand Mail Relay Session:
      P:  220 EXAMPLE.NET on-demand mail relay server ready
      C:  EHLO example.org
      P:  250-EXAMPLE.NET
      P:  250-AUTH CRAM-MD5 EXTERNAL
      P:  250 ATRN
      C:  AUTH CRAM-MD5
      P:  334 MTg5Ni42OTcxNzA5NTJASVNQLkNPTQo=
      C:  Zm9vYmFyLm5ldCBiOTEzYTYwMmM3ZWRhN2E0OTViNGU2ZTczMzRkMzg5MAo=
      P:  235 now authenticated as example.org
      C:  ATRN example.org, example.com
      P:  250 OK now reversing the connection
      C:  220 example.org ready to receive email
      P:  EHLO EXAMPLE.NET
      C:  250-example.org
      C:  250 SIZE
      P:  MAIL FROM: <Lester.Tester@dot.foo.bar>
      C:  250 OK


Gellens                 Expires September 1999                 [Page 6]

Internet Draft              On-Demand Mail Relay              March 1999

      P:  RCPT TO: <l.eva.msg@example.com>
      C:  250 OK, recipient accepted
      ...
      P:  QUIT
      C:  221 example.org closing connection


7.  Response Codes

    The response codes used in this document are:

    250  Requested mail action okay, completed
    450  ATRN request refused
    451  Unable to process ATRN request now
    453  You have no mail
    502  Command not implemented
    530  Authentication required [AUTH]


8.  Security Considerations

    Because access to the On-Demand Mail Relay server is only useful
    with a prior arrangement between the parties (so the provider is the
    target of MX records for the customer's domains and thus has mail to
    relay), it may be useful for the provider to restrict access to the
    On-Demand Mail Relay port.  For example, the ODMR server could be
    configurable, or a TCP wrapper or firewall could be used, to block
    access to port 366 except within the provider's network.  This might
    be useful when the provider is the customer's ISP.  Use of such
    mechanisms does not reduce the need for the AUTH command, however,
    but can increase the security it provides.

    Use of SASL in the AUTH command allows for substitution of more
    secure authentication mechanisms in the future.

    See sections 5.1.2 and 5.2.1 for additional security details.


9.  Acknowledgments

    This draft has been developed in part based on comments and
    discussions which took place on and off the IETF-disconn-smtp
    mailing list.  Special thanks to Chris Newman and Ned Freed for
    their comments.


10.  References

    [ABNF] Crocker, Overell, "Augmented BNF for Syntax Specifications:
    ABNF", RFC 2234, Internet Mail Consortium, Demon Internet Ltd.,
    November 1997. <ftp://ftp.isi.edu/in-notes/rfc2234.txt>



Gellens                 Expires September 1999                 [Page 7]

Internet Draft              On-Demand Mail Relay              March 1999

    [AUTH] Myers, J., "SMTP Service Extension for Authentication", RFC
    2554, Netscape Communications, March 1999.
    <ftp://ftp.isi.edu/in-notes/rfc2554.txt>

    [CODES-EXTENSION] Freed, N., "SMTP Service Extension for Returning
    Enhanced Error Codes", RFC 2034, October 1996,
    <ftp://ftp.isi.edu/in-notes/rfc2034.txt>

    [CRAM] Klensin, Catoe, Krumviede, "IMAP/POP AUTHorize Extension for
    Simple Challenge/Response", RFC 2195, September 1997,
    <ftp://ftp.isi.edu/in-notes/rfc2195.txt>

    [ESMTP] Klensin, Freed, Rose, Stefferud, and Crocker, "SMTP Service
    Extensions", RFC 1869, STD 10, November 1995,
    <ftp://ftp.isi.edu/in-notes/rfc1869.txt>

    [ETRN] De Winter, J., "SMTP Service Extension for Remote Message
    Queue Starting", RFC 1985, August 1996,
    <ftp://ftp.isi.edu/in-notes/rfc1985.txt>

    [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
    Requirement Levels", RFC 2119, March 1997,
    <ftp://ftp.isi.edu/in-notes/rfc2119.txt>

    [SASL] Myers, J., "Simple Authentication and Security Layer (SASL)",
    RFC 2222, October 1997, <ftp://ftp.isi.edu/in-notes/rfc2222.txt>

    [SMTP-CODES] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC
    1893, January 1996, <ftp://ftp.isi.edu/in-notes/rfc1893.txt>

    [SMTP] Postel, J., "Simple Mail Transfer Protocol", RFC 821, STD 10,
    August 1982, <ftp://ftp.isi.edu/in-notes/rfc821.txt>


11.  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
    Internet 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.



Gellens                 Expires September 1999                 [Page 8]

Internet Draft              On-Demand Mail Relay              March 1999

    The limited permissions granted above are perpetual and will not be
    revoked by the Internet Society or its successors or assigns.

    This document and the information contained herein 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.


12.  Author's Address

    Randall Gellens                    +1.619.651.5115
    QUALCOMM Incorporated              randy@qualcomm.com
    6455 Lusk Blvd.
    San Diego, CA  92121-2779
    U.S.A.




































Gellens                 Expires September 1999                 [Page 9]

Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/