rfc585.txt

RFC 相关的技术文档

      c. The NIC should set up Network ident groups for Principal
         Investigators, Liaisons, Station Agents, Accounts
         Administrators, Consultants, etc., so that users can easily
         direct their comments, inquiries and mail to these groups.

      d. A Network Servers Group should be started, to coordinate the
         activities (to the extent possible) of the servers (a Server's
         Cartel?).  It would also provide a focus for user complaints
         and suggestions.

         (The group was originally dubbed the "Tobacco Institute".  The
         Tobacco Institute acts as a representative for the disparate
         Tobacco companies, and attempts to convince the public that
         smoking is good for them.)

         The point of the Servers Group -- rather than trying to
         convince the Network public that servers are good for them --
         would be for servers to help each other with common tasks (such
         as documentation) that are too big for each to handle alone.

            This eventually works in the users interest, because the
            servers (in the Network free-market economy) are dependent
            upon the users for their livelihood.




Crocker, et al.                  Users                          [Page 5]

RFC 585               USING Working Group Meeting          November 1973


         There should be cooperation between the Server Group and USING,
         but the groups would NOT be comprised of the same people.  They
         are on opposite sides of the product.

      e. Station Agents should supply users with information of a
         clerical nature such as names, phone numbers, titles,
         documentations, etc.  To be able to do this, the Agents must
         first HAVE this information.

   5. Messages to Users

      a. Messages to users, such as error messages or diagnostics,
         should be simple, clear, and meaningful to users.

      b. The user should have the ability to control notifications given
         to him, by being able to queue messages or refuse them.

      c. Users should be able to suppress diagnostics or to specify
         abbreviated or expanded versions.

   6. Tailoring of Resources for Users

      a. Interfaces to users should support different levels of user
         proficiency, without being a burden to the more proficient
         user.

         That is, a new user needs more prompting, etc.  A more
         experienced user does not need and DOES NOT WANT such
         prompting.  So the capabilities of the interface, which are not
         needed by a specific user, should be transparent.

      b. A method for work flow management that permits a user to set up
         a sequence of computer tasks that are contingent upon one
         another is needed.  The user should be able to describe this
         sequence interactively and then be able to detach and continue
         with other work while the sequence of tasks is being carried
         out.

   7. Personal Information Management System

      a. Users need a system for managing all types of machine-based
         contacts such as mail, links, journal items, etc.

         Such a system should `log' what has been received and allow the
         user to keep a copy, if desired.

         It should also provide the user with options for organizing his
         personal information.



Crocker, et al.                  Users                          [Page 6]

RFC 585               USING Working Group Meeting          November 1973


      b. A personal `calendar' or reminder system would be handy,
         especially if it allowed one to look ahead to coming events as
         well as to check events for the current day or week.

      c. A `return to sender' feature is needed in the Network-wide mail
         address system.

      d. (Discussion of the current work on the Mail Protocol indicated
         that some of these ideas are already being considered)

   8. Uniform Accounting Procedures and Online Status of Accounts

      a. This topic was covered in detail by sections of the Resource
         Sharing Workshop.  It is mentioned here only because it is a
         problem of real concern to users.

   9. Trial Usage and Browsing

      a. Ideally, users should be allowed some `free' sampling of
         systems and features available at each site.  Practically, this
         presents problems of space allocation, accounting, consulting,
         etc.  Although none of these problems are easy to solve
         equitably, an attempt should still be made to provide some free
         usage to everyone.
      b. Several types of trial usage should be considered, such as for
         those who will make an immediate commitment and those who wish
         merely to sample, without making any commitment.

   10.  Prelogon Facilities

      a. Some facilities should be available as prelogon facilities, so
         that any user can access them whether or not he has an account,
         directory, etc., at a given site.  Some sites will not be able
         to support many of these functions, so a required set must be
         kept to a minimum.

   11.  Remote User Facilitation

      a. Users not only need help with actual use of systems from a
         remote site, but they also need facilitation of administrative
         tasks.  Station Agents should be able to handle most of these
         problems or transfer the user to the proper person.  System
         access requirements, account and billing problems, and document
         acquisition need particular attention.







Crocker, et al.                  Users                          [Page 7]

RFC 585               USING Working Group Meeting          November 1973


      b. There should be a simple mechanism for users to acquire/update
         information in functional documents such as the Resource Note-
         book and in files such as identification files.  Publications
         or files of this sort should combine the collective input of
         all the users.

   12.  Transportability of Resources and Information

      a. Users should be able to easily transfer information, such as
         files, memos, mail, online documentation, (programs?!?) etc.,
         from one site to another.

   13.  Network Utilities

      a. Should distributed data banks and similar features be
         considered Network utilities that can be used by all?

         The idea of "Network Utilities" was recognized as an
         interesting one by the group, but there was little agreement as
         to what constitutes Network utilities or how they should be
         supported.

CURRENT PLANS

   1. Neigus, Crocker, and Iseli will draft the scope, objectives,
      goals, and priorities of USING and will submit their
      recommendations for approval by the members.

   2. MITRE will design a New User's Packet incorporating ideas from
      USING.

   3. Bowles, Hathaway, and Stoughton will write preliminary specs for a
      Network Common Command Language Protocol.  All members should
      suggest a list of commands for consideration.

   4. Padlipsky will produce specifications for a simple, standard
      editor (NETED) which could easily be implemented by server hosts.

   5. A general Users Group (NIC ident = USERS) will be formed, to allow
      any interested person to monitor user-oriented activities,
      especially those of USING.  Anyone interested in being in USERS
      should contact Dave Crocker (DHC).









Crocker, et al.                  Users                          [Page 8]

RFC 585               USING Working Group Meeting          November 1973


   6. Activities of the group will be reported in the ARPAnet News, and
      a user's forum column will be made available for user's comments.

   7. The group will meet again in the Fall of 1973 at the Network
      Information Center in Menlo Park, California.


          [ This RFC was put into machine readable form for entry ]
              [ into the online RFC archives by Via Genie 3/00 ]










































Crocker, et al.                  Users                          [Page 9]