RFC 2645 on On-Demand Mail Relay

RFC Editor <rfc-ed@ISI.EDU> Wed, 04 August 1999 23:32 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27641; Wed, 4 Aug 1999 19:32:50 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA06324 for ietf-123-outbound.10@ietf.org; Wed, 4 Aug 1999 19:35:03 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA06235 for <all-ietf@loki.ietf.org>; Wed, 4 Aug 1999 19:27:59 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27218 for <all-ietf@ietf.org>; Wed, 4 Aug 1999 19:23:06 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA10312; Wed, 4 Aug 1999 16:23:07 -0700 (PDT)
Message-Id: <199908042323.QAA10312@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2645 on On-Demand Mail Relay
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 04 Aug 1999 16:23:07 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


       RFC 2645:

        Title:	    ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP
                    Addresses
        Author(s):  R. Gellens
        Status:     Proposed Standard
	Date:       August 1999
        Mailbox:    randy@qualcomm.com
        Pages:      9
        Characters: 16302
	Updates:    
        I-D Tag:    draft-gellens-on-demand-07.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2645.txt


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.

This document is a product of the IETF Working Group.

This is now a Proposed Standard.

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@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
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://ftp.isi.edu/in-notes/rfc2645.txt"><ftp://ftp.isi.edu/in-notes/rfc2645.txt>