Network journal submission and delivery
RFC 543

Document Type RFC - Unknown (July 1973; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 543 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           D. Meyer
Request for Comments: 543                                        SRI-ARC
NIC: 17777                                                  31 July 1973

                Network Journal Submission and Delivery

Augmentation Research Center

Stanford Research Center
Menlo Park, California 94025

   The on-line documentation will be maintained as (userguides.
   journal-netsub,).  Hard copies are available from Marcia Keeney.

   The first implementation of a Network Journal Submission and Delivery
   system is now experimentally up.  This system allows use of the NIC's
   NLS Journal System without entering NLS.  Network users may submit
   text files written on their host systems using their mail subsystems
   (e.g. SNDMSG, FTP, TELNET).  The mail will then be converted at SRI-
   ARC into NLS files, journalized, and sent to the specified recipients
   according to their preset Journal delivery options.  A newly added
   option permits the user to receive automatic Journal delivery (of
   citations to journalized documents) at his host via the Network mail
   protocol.

Overview

   Network mail sent to SRI-ARC (NIC) will be entered into the NIC
   Journal system if a slash appears in the user-name.  To get the mail
   to the NIC, you may use either the FTP, TELNET, or mail subsystem
   provided by your local system.

   The author's NIC Ident(s) are assumed to appear before the slash; the
   recipients' NIC Ident(s) after it.  Idents should be separated by
   spaces.  (See scenarios in branch 3)
   (e.g. jew / mdk dhc)

Meyer                                                           [Page 1]
RFC 543         Network Journal Submission and Delivery     13 July 1973

   When this format is detected by the NIC, the Network Journal system
   will be invoked.  At SRI-ARC the mail will be transformed into an NLS
   file, assigned a unique catalog number, stored permanently under that
   number, and a notice of it will be sent to all the listed recipients.
   If the slash is not found, the mail will be handled in the normal
   way.

   Delivery of Journal citations may now be obtained via the Network (as
   well as to an NLS file at SRI-ARC and in hard copy).  If you wish to
   receive your Journal mail at you host computer, contact the NIC (see
   RFC510 -- 16400,).

   A more detailed description follows.

NETWORK JOURNAL SUBMISSION

   The remote user prepares the text of his Journal article in his host
   using whatever tools he has available to him.  He may wish to prepare
   long articles beforehand using his text editor (e.g. TECO if he's a
   TENEX user).  For short messages, he may be content with the basic
   editing features (such as backspace character and line delete)
   provided by his submission subsystem.

Connecting to the NIC

   To get the mail to the SRI-ARC FTP server, you must either:

      1) via FTP and TELNET mail subsystems, connect to SRI-ARC's FTP
         server process, then issue the FTP mail command, or

      2) use the mail subsystem provided by your local system.

         For TENEX SNDMSG mail: put "@nic" at the end of the "User:"
         field.
            (e.g. jew / mdk dhc@nic)

         If you wish to send the mail as a SNDMSG message to  some
         people as well as submit it to the Journal, you may treat the
         Journal form as one name, follow it with a comma, and then list
         other names of which SNDMSG is aware, separated by commas.
            (e.g. jew/mdk dhc@nic, meyer, white)

Specifying Authors and Recipients

   The user invokes Network Journal submission via his mail subsystem.
   Network Journal Submission is invoked by a user-name field of the
   following format:

Meyer                                                           [Page 2]
RFC 543         Network Journal Submission and Delivery     13 July 1973

      author $(SP author) [SP] / [SP] recipient $ (SP recipient) [SP]
      [ ; conversion algorithm]

         "$(..)" means "any number of occurrences, possibly
                 zero, of what's inside the parentheses"
         "SP" means "space"
         "[..]" mean "the contents of the brackets are optional"

   i.e., author(s), slash, recipient(s), optional semicolon and
   conversion-algorithm

      e.g., jew/mdk rww   cr    dcs rww jcn / sri-arc ;h

   'Author' is the NIC Ident of (one of) the user(s) submitting the
   article, and 'recipient' the Ident of (one of) its intended
   recipient(s).  An Ident, as usual, may designate either a "group" or
   an "individual".  SRI-ARC will verify the idents.  If it finds them
   correct, it will accept the mail.  An invalid Ident will cause the
   mail to be rejected; the user will get an error message and have to
   start over.  The first author Ident will be taken to be the clerk.

   If the SRI-ARC mail subsystem finds the slash in the user-name field,
   the Network Journal Submission system will be invoked; otherwise, the
Show full document text