rfc524.txt

来自「中、英文RFC文档大全打包下载完全版 .」· 文本 代码 · 共 1,976 行 · 第 1/5 页

            in the absence of an explicit SIGNATURE command, one
            identical to that for the previous quintuplet is assumed.

         DISPOSITION <disposition> <CA>

            The DISPOSITION command identifies the intent with which the
            Mail is Delivered to the Recipient by the Author(s), and may
            take any, all, or none of the following as arguments:

               RSVP

                  The Author(s) request a Reply from the Recipient.

               ACTION

                  The Author(s) expect some action on the part of the
                  Recipient.  If ACTION doesn't appear, then the Mail is
                  intended for the Recipient's information only.

               INTERRUPT

                  The Author(s) declare that examination of the Mail by
                  the Recipient is urgent.  In such cases, the
                  Recipient's Mail server process may, upon Delivery,
                  choose to interrupt the Recipient if he happens to be
                  logged in at a terminal.

            No specific action in response to the presence of any of
            these arguments is required; the server is free if he likes
            to treat DISPOSITION commands as NOPs.

            The absence of a DISPOSITION command implies one with no
            arguments (i.e., for the Recipient's information only, no
            Reply required, and not urgent).

   DYNAMIC ATTRIBUTES (of a piece of Recorded Mail)

      Those attributes of a piece of Recorded Mail -- Distribution List,
      Access List, and Catalog List -- which, though given initial
      values at Recording Time, can always be modified by an Individual
      with Controlling Access to the piece of Mail.

   FORWARDING (of Mail received for an Individual)

      The act of transferring that set of Mail which has been previously
      Delivered to but not Read by an Individual, to another Individual.



White                                                          [Page 15]

RFC 524                 A Proposed Mail Protocol            13 June 1973


      Users who are known at more than one host can cause their unRead
      Mailto be gathered in to a central location by performing the
      Forwarding function at each such host (both Individuals being, in
      this case, instances of the same User).  Mail which has been
      Forwarded is considered to have been Read at its source.

   FORWARDEE

      That Individual whose Delivered but UnRead Mail is to be
      Forwarded.

      A Forwardee is represented in the Protocol as an Individual List
      of type FORWARDEE and length 1.

   GENERAL DELIVERY (of a piece of Mail to an unrecognized Recipient)

      The act on the part of a server of accepting Delivery of a piece
      of Mail on behalf of an intended Recipient whose name the server
      doesn't recognize.  The server retains the Recipient's name, and
      makes it and the other information provided by the user process
      available to some competent person, who attempts to make sense of
      the Recipient's name.  If the Recipient is recognized, the Mail is
      'hand' delivered to the appropriate Individual.

      General Delivery of a piece of Mail to one of its intended
      Recipient(s) is performed only after the server informs the user
      process of its intent and receives the user process' consent.  If
      that consent is not given, or if the server doesn't implement
      General Delivery, the server rejects the Delivery attempt for that
      Recipient.

      Consent for General Delivery is represented in the Protocol by the
      command

         GENERALDELIVERY <CA>

   GREETING (for the Delivery of a piece of Mail to a Recipient)

      A short greeting to a Recipient of a piece of Mail. 'Dear Dave' is
      a valid and perhaps typical Greeting.

      A Greeting is represented in the Protocol by the command:

         GREETING <greeting> <CA>







White                                                          [Page 16]

RFC 524                 A Proposed Mail Protocol            13 June 1973


   ID (for an Individual)

      The password which an Individual may have to present to a Mail
      server process, to prove his identity.

      An Id is represented in the Protocol by the command:

         ID <id> <CA>

      Ids have nothing to do with accounting, and when required by a
      server, they're required only to protect that server from forgery
      or misrepresentation.

   INDIVIDUAL

      An instance of a User, identified by NIC Ident, or by the
      combination of host and Mailbox Name.

   INDIVIDUAL LIST (of type "t" and length "n")

      A set of Individuals.

      An Individual List is represented in the Protocol as a series of
      "n" command pairs (juxtaposed in the command stream), each pair
      consisting of a "t" command, followed immediately by an ID
      command.  Each pair corresponds to one Individual in the set.

      The ID command is given by the Mail user process at the option of
      the Mail server process; and whenever the server requires it, he
      must prompt for it with an appropriate reply to the preceding "t"
      command.  If no such prompt is given, the user process is not
      obliged to provide the ID command, but may if it chooses, in which
      case the server is obliged to treat it as if it had been prompted
      for and found correct.

      The ID command is a mechanism by which the server can assure
      himself that the user process is not acting without proper
      authorization from the Individual(s) involved, i.e., a mechanism
      by which a server can protect himself against forgery,
      misrepresentation, etc.

         "t" <individual> <CA>

         ID <id> <CA>







White                                                          [Page 17]

RFC 524                 A Proposed Mail Protocol            13 June 1973


   MAIL

      A body of text communicated from one set of Individual(s) to
      another, in less than (but ideally approaching) real time.

   MAILBOX NAME

      The name a User employs at a host to send and receive Mail.

   MONITOR (for a piece of Mail)

      The Individual who is the recipient for Acknowledgments and
      Progress Reports.

      A Monitor is represented in the Protocol as an Individual List of
      type MONITOR and length 1.

      Monitor defaults to the Clerk if not explicitly specified.

   PROGRESS REPORT (for a piece of Mail)

      A form of Unrecorded Mail, generated periodically during the
      distribution process by a Distribution Agent, whose Recipient is
      the Monitor for a previous piece of Mail, and whose Content is a
      list of the Recipient(s) and the current Delivery Status for each.
      A Progress Report bears the Serial Number of the Mail whose status
      it reports, as the Reference Serial Number.

   PROTOCOL

      The Mail Protocol (MP).

   READ (a piece of previously-Delivered Mail)

      The act, on the part of the User, of examining a piece of
      Delivered Mail.

   READ ACCESS (to a piece of Recorded Mail)

      The right of an Individual to retrieve the Content of a piece of
      Recorded Mail.

      Recording Agents permit an Individual to retrieve the Content of a
      piece of Recorded Mail if and only if he can properly identify
      himself as someone having Read Access to that Mail.  An Individual
      can retrieve the Citation (except Content) from the Recording
      Agent independently of whether or not he has Read Access to the
      Mail.



White                                                          [Page 18]

RFC 524                 A Proposed Mail Protocol            13 June 1973


   READ DATE (of a piece of Mail for one of its Recipient(s))

      The date and time, necessarily following Delivery, at which a
      piece of Mail is Read by a Recipient.  A multitude of Read Dates,
      one for each Recipient, are associated with each piece of Mail.

   RECIPIENT (of a piece of Mail)

      An Individual who has or is to receive Delivery of a piece of
      Mail.

   RECORDED MAIL

      A piece of Mail whose Citation is available on a long-term
      (indefinite) basis from a Recording Agent.

   RECORDING

      The service provided by a Recording Agent.

   RECORDING AGENT

      A Mail server process which accepts Mail, permanently Records its
      Citation, and assigns a pathname by which that information can at
      any time be retrieved by an Individual with appropriate access.

   RECORDING DATE

      The date and time at which a piece of Mail is presented to a
      Recording Agent for Recording.  A single Recording Date is
      associated with each piece of Recorded Mail.

   REFERENCE SERIAL NUMBER (for an Acknowledgment, Progress Report, or
      Reply)

      The Serial Number of the piece of Mail to which an Acknowledgment,
      Progress Report, or Reply refers.

      A Reference Serial Number is represented in the protocol by the
      command:

         REFERENCESERIAL <serialnumber> <CA>

      In the absence of an explicit REFERENCESERIAL command, no Serial
      Number is to be assumed.






White                                                          [Page 19]

RFC 524                 A Proposed Mail Protocol            13 June 1973


   REPLY (to a previous piece of Mail)

      A piece of Recorded or Unrecorded Mail whose Author(s) are
      Recipient(s) of a previous piece of Mail, and which replies or
      pertains to that same piece of Mail and bears its Serial Number,
      as the Reference Serial Number.

   REPORT INTERVAL (for a Progress Report)

      The interval between Progress Reports.

      A Report Interval is represented in the Protocol by the command:

         REPORTINTERVAL <interval> <CA>

      In the absence of an explicit REPORTINTERVAL command, one with an
      argument whose value is effectively infinite is to be assumed
      (i.e., no Progress Reports are to be made).

   REQUESTOR

      The Individual on whose behalf a Mail user process connects to and
      interacts with a Mail server process.

      A Requestor is represented in the Protocol as an Individual List
      of type REQUESTOR and length 1.

   SERIAL NUMBER (for a piece of Mail)

      A short-term identifier, assigned to a piece of Mail by the Clerk
      (or his system), which accompanies Acknowledgments, Progress
      Reports, and Replies, and is used to correlate the latter with the
      former.  The lifetime of a Serial Number is conceptually from its
      assignment by the Clerk until the Delivery of the Recipient(s)
      Reply(s) to the Author(s) (or until their decision to send no
      reply).

      A serial Number is represented in the Protocol by the command:

         SERIAL <serialnumber> <CA>

      In the absence of an explicit SERIAL command, no Serial Number is
      to be assumed.

   SIGNATURE (for the delivery of a piece of Mail to a Recipient)

      A human-readable indication of the Author(s) of a piece of Mail.
      The string 'Jim and Dick' is a valid Signature.



White                                                          [Page 20]

RFC 524                 A Proposed Mail Protocol            13 June 1973


      A Signature is represented in the Protocol by the command:

         SIGNATURE <signature> <CA>

   STATIC ATTRIBUTES (of a piece of Recorded Mail)

      Those attributes of a piece of Recorded Mail -- Content, Title,
      Comments, Author(s), Clerk, and Creation Date -- which are forever
      fixed at Recording Time, and hence can never be modified.

      Static Attributes can be independently specified with commands
      described elsewhere, or specified collectively by reference to an
      existing piece of Recorded Mail.  The command which follows
      assigns to the current piece of Mail the Static Attributes of the
      piece of Recorded Mail it references, and is exactly equivalent to
      an appropriate set of TITLE, COMMENTS, etc.  commands.

         LOCATION <fileaddr> <CA>

   TITLE (of a piece of Mail)

      A concise description of the Content of a piece of Mail.

      A Title is represented in the Protocol by the command:

         TITLE <title> <CA>

      In the absence of an explicit TITLE command, one with a null
      argument is to be assumed.

   UNRECORDED MAIL

      Mail which is never presented to a Recording Agent for permanent
      storage and cataloging, but which is simply Delivered to its
      Recipient(s) by a Delivery Agent.

   UPDATE REQUEST (to a Recording Agent for a piece of Recorded Mail)

      A request made of a Recording Agent to add, replace, or delete an
      Individual from the Access or Distribution List for a piece of
      Mail; or to add or delete a Catalog from the Catalog List.

      An Update Request is represented in the Protocol by the command:

         UPDATETYPE <updatetype> <CA>

      followed immediately in the command stream by an Access,
      Distribution or Catalog List.



White                                                          [Page 21]

RFC 524                 A Proposed Mail Protocol            13 June 1973


   USER

      A process or human who sends and/or receives Mail.

   USER VERIFICATION