Network mail meeting summary
RFC 469

Document Type RFC - Unknown (March 1973; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 469 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
NWG/RFC#469                             Michael D. Kudlick MDK (SRI-ARC)
NIC 14798                               8-MAR-73

                      Network Mail Meeting Summary


   The purpose of this RFC is to briefly summarize, from the NIC's
   viewpoint, the principal conclusions reached at the Network Mail
   Meeting held Friday, February 23 1973, at SRI-ARC.

      Please refer to RFC #475 (NIC 14919) for Abhay Bhushan's
      comprehensive summary of the issues discussed at the meeting.

      There is no major disagreement between the present RFC and RFC

      RFC #453 (NIC 14317) contains background information on the

      RFC #479 (NIC 14948) describes what the NIC would like to see
      included in the File Transfer Protocol for Network Mail purposes,
      and also describes briefly how the NIC would use the information.

   The present RFC is organized as follows:



   Additional FTP mail requirements were decided upon.  These would be
   implemented as a new mail command, with the following subcommands:


         This field is explicitly allowed to contain multiple
         addressees, with a standard syntax:  user@host.


         This field provides a return-address for notification of
         undeliverable mail, as well as a clearcut identification of the
         sender for the recipient's information..

                                                                [Page 1]
NIC 14798                                       MDK 8-MAR-73 17:24 14798


         This field denotes the author of the mail.  There may be
         multiple authors

         The "title" (i.e. subject) of the mail is to be terminated by
         period carriage return.

      ACKNOWLEDEGMENT  success / failure (time out) / normal

         For use by the intermediate host, probably the NIC in most
         cases, to tell the sender what happened to his attempt to send
         mail.  (Note:  "normal" wasn't defined.)

      RECORDED  jnumber / null

         Note: "jnumber" is the pre-assigned accession number (NIC
         number), to be used when known.

         The "RECORDED" subcommand provides for the option of having the
         mail recorded.  Information given with this subcommand would be
         recognized at the NIC. Options are:

            to be recorded (in NIC journal) only,
            to be recorded and distributed,
            to be distributed only.

         This field would also be used to inform the recipient that the
         mail has been recorded.

            (In retrospect, it may be preferable to have a separate
            command to inform the recipient of this fact, but no
            decision on this was made at the 23-Feb-73 meeting.)

      TYPE  long / urgent / ordinary

         This allows the recipient site to take whatever action it
         thinks appropriate in storing the mail.



            This field is for the text of the mail message.

                                                                [Page 2]
NIC 14798                                       MDK 8-MAR-73 17:24 14798


         The purpose of the field is unclear to me.  Does it contain a
         machine readable pointer to the file that the sender wishes the
         recipient to read?


         This field is a person-readable pointer to the file that the
         sender wishes the recipient to read.  When the citation command
         is used, no mail is sent other than the citation.



      The key aspects in the solution are:

         1) It is based on FTP.

         2) It uses the NIC without requiring direct use of NLS.

         3) There is a mechanism for uniformity in the use of
         user identifications.

         4) There is a mechanism for recording the mail for
         later reference.

      These issues are covered in the discussion that follows.

New FTP Mail Subcommands


      Addressee Format

         The standard form of the address is:  user@host

         "User" may be an individual's last name; or it may be whatever
         other identification the recipient has chosen AND has made
         known to the rest of the network.

            If the intended host doesn't recognize the intended
            recipient's identification, then it sends back an
            "undeliverable" mail message to the sender's host.  It is up
            to the individual to keep the NIC informed of his wherabouts
            [sic]; otherwise, he may not get his mail on time.

                                                                [Page 3]
NIC 14798                                       MDK 8-MAR-73 17:24 14798

      NIC Role

         The NIC need have no role at all for mail sent from point A to
         point B, whenever that mail is not to be recorded at the NIC.
Show full document text