Charter for ARPANET Users Interest Working Group
A working group formed to represent network users' interests
Iseli, J., Crocker, D., and N. Neigus, "Charter for ARPANET Users Interest Working Group", RFC 584, DOI 10.17487/RFC0584, November 1973, <https://www.rfc-editor.org/info/rfc584>.
@misc{rfc584,
series = {Request for Comments},
number = 584,
howpublished = {RFC 584},
publisher = {RFC Editor},
doi = {10.17487/RFC0584},
url = {https://www.rfc-editor.org/info/rfc584},
author = {J. Iseli and D. Crocker and N. Neigus},
title = {{Charter for ARPANET Users Interest Working Group}},
pagetotal = 3,
year = 1973,
month = nov,
} RFC text
Network Working Group J. Iseli (MITRE-TIP)
Request for Comments: 584 D. Crocker (UCLA-NMC)
NIC 19025 and 20049 N. Neigus (BBN-NET)
USING Note 6 6 November 1973
Categories: Users
Charter for Arpanet Users Interest Working Group
Background
The ARPANET Users Interest Working Group (NIC Ident = USING) was
formed at a meeting of 15 network people on May 23, 1973 in an
attempt to improve the Network user's working environment. USING will
attempt to represent the interests and needs of users in the Network
community, so as to increase awareness of user requirements and
encourage better provision of the neeed services. The group believes
that the network is moving beyond a concentration of resources in
self-perpetuating research and development; the Network is becoming a
service and its viability as such is dependent on user satisfaction.
A second group, the ARPANET Users Group (NIC Ident = USERS) is
organized as a forum for users to express their desires and
complaints. Acting as a steering committee and lobby for this group,
USING will forward their ideas to the appropriate centers.
Membership
Group membership, in USING, is open to individuals interested in
working to improve Network user support and able and willing to make
meaningful contributions to USING's activities.
Membership, in USERS, is open to any interested person.
Scope
USING has set as its scope those facets of Network activity that
affect the provision of services to users. This includes the
availability of resources, their reliability and ease of use.
Goals
USING's overall goal is to ensure that the ARPANET becomes a coherent
system in which users can regulate their own working environment
according to their level of experience and the degree of transparency
(of specific system idiosyncrasies) they desire. System resources
should be self-documenting, and all levels of assistance (on- and
NWG/RFC# 584 JI DHC NJN 5-NOV073 20:44 20049
off-line) should be available, again, to be regulated by the user.
Short Term Objectives, for the initial 6-12 months
1. Specification of a user-level Common Command Language (CCL);
2. Specification of a Network Editor for CCL;
3. Further definition and focusing of User Issues;
4. Encouraging establishment of a User's consulting service;
5. Publication of a New-Users Handbook.
Long Term Activities
1. Monitor and/or provide impetus for user-oriented Network
development efforts, including resource directories, tutorials
[static and dynamic], training courses and referral services;
2. Provide mechanisms to encourage, analyze, and respond to user
feedback;
3. Develop profile information relative to users' requirements,
types, usage attributes, and affiliations;
4. Stimulate mechanisms to facilitate entry of new users to the
ARPANET;
5. Sponsor user seminars and encourage formation of viable user
working groups where appropriate.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 10/99 ]
AI ELI5
On this page
§1Forming a User Advocacy Group
The ARPANET Users Interest Working Group (USING) was formed at a meeting on May 23, 1973, with 15 network people aiming to improve the network user's working environment. The group recognised that ARPANET was becoming a service, not just a research platform, and that its viability depended on user satisfaction. USING would represent the interests and needs of the Network community, making sure builders heard what users actually wanted.
Alongside USING, a broader group called USERS was created as a forum for any interested person to air complaints, exchange information and make proposals. USING served as a steering committee and lobby for USERS, forwarding ideas to the right people.
Network builders realised they needed to listen to the people who actually used the network, so they started a group called USING to speak up for users.
§2Scope and Membership
USING membership is open to individuals able and willing to make meaningful contributions to improving network user support. USING's scope covers all facets of Network activity that affect services to users: the availability of resources, their reliability and ease of use.
This includes everything from how friendly the system documentation is, to what commands users can type, to whether people are available to help when things go wrong.
USING focuses on all the things that make the network easy or hard to use: good guides, simple commands, and people ready to help.
§3Short-Term Objectives and Vision
USING's overall goal is to ensure ARPANET becomes a coherent system in which users can regulate their own working environment according to their experience level and desired transparency. System resources should be self-documenting, and assistance at all levels should be available and user-controlled.
For the first 6 to 12 months, the group set specific targets: specifying a user-level Common Command Language (so users didn't have to learn a different language at each site), designing a network editor, further defining user issues, encouraging user consulting services, and publishing a handbook for new users.
USING wanted the network to be easy for beginners but not annoying for experts, with all the help and tools built in.
§4Long-Term Vision
Beyond the immediate objectives, USING planned long-term activities including monitoring and spurring user-oriented development efforts like resource directories, tutorials, training courses and referral services. The group would create mechanisms to encourage and respond to user feedback, develop profiles of user requirements and usage patterns, and work to lower the barrier to entry for new users.
In the years ahead, they wanted to keep listening to users and keep making the network more friendly and educational for everyone.