API tools faq
paste
Advertisement
Guest User

ARPANET

a guest
Jun 24th, 2017
2,087
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 172.96 KB | None | 0 0
raw download clone embed print report
  2. NIC 50003
  3.  
  4.  
  5.  
  6.  
  8. NIC 50003
  9.  
  10.  
  11.  
  12.  
  13.  
  14.  
  15.  
  16.  
  17.  
  18.  
  19.  
  20.  
  21.  
  22.  
  23.  
  24.  
  25.  
  26.  
  27.  
  28.  
  29. ARPANET INFORMATION BROCHURE
  30.  
  31.  
  32.  
  33. DECEMBER 1985
  34.  
  35.  
  36.  
  37.  
  38.  
  39.  
  40.  
  41.  
  42.  
  43.  
  44.  
  45.  
  46.  
  47.  
  48.  
  49.  
  50.  
  51.  
  52.  
  53. ARPANET INFORMATION BROCHURE
  54.  
  55.  
  56.  
  57.  
  58. DECEMBER 1985
  59.  
  60.  
  61.  
  62. Editor:
  63. Stephen C. Dennett
  64. Elizabeth J. Feinler
  65. Francine Perillo
  66.  
  67.  
  68.  
  69.  
  70.  
  71.  
  72.  
  73. Additional copies of this document may be obtained from the DDN Network
  74. Information Center, SRI International, 333 Ravenswood Avenue, Room EJ291,
  75. Menlo Park, CA 94025, or from the Defense Technical Information Center
  76. (DTIC), Cameron Station, Alexandria, VA 22314.
  77.  
  78.  
  79.  
  80.  
  81.  
  82.  
  83.  
  84.  
  85.  
  86.  
  87.  
  88.  
  89.  
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100. ---------------------------------------------------------------------------
  101. UNIX is a registered trademark of AT&T Bell Laboratories. TELENET is a
  102. registered trademark of GTE. TYMNET is a registered trademark of TYMNET
  103. Inc., a subsidiary of McDonnell Douglas Corporation.
  104. ---------------------------------------------------------------------------
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111. ARPANET Information Brochure. Printed and bound in the United States of
  112. America. Published by the DDN Network Information Center, SRI
  113. International, Menlo Park, CA 94025.
  114.  
  115.  
  116.  
  117. Date: December 1985
  118.  
  119. TABLE OF CONTENTS
  120.  
  121.  
  122.  
  123.  
  124.  
  125. ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . III
  126.  
  127. ABSTRACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V
  128.  
  129. SECTION 1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 1
  130. 1.1. How To Use This Document . . . . . . . . . . . . . . 1
  131.  
  132. SECTION 2. ARPANET MANAGEMENT AND POLICIES . . . . . . . . . . . . 3
  133. 2.1. What is the ARPANET? . . . . . . . . . . . . . . . . 3
  134. 2.2. Management of the ARPANET . . . . . . . . . . . . . 3
  135. 2.2.1. DARPA/IPTO . . . . . . . . . . . . . . . . . . . . 3
  136. 2.2.2. DDN PMO Responsibilities . . . . . . . . . . . . . 3
  137. 2.2.3. IAB Responsibilities . . . . . . . . . . . . . . . 3
  138. 2.3. ARPANET Access and Use Policies . . . . . . . . . . 4
  139. 2.3.1. Host Access Controls . . . . . . . . . . . . . . . 4
  140. 2.3.2. TAC Access Controls . . . . . . . . . . . . . . . 4
  141.  
  142. SECTION 3. SUBSCRIBER ACCESS PROCEDURES . . . . . . . . . . . . . . 5
  143. 3.1. Process Overview . . . . . . . . . . . . . . . . . . 5
  144. 3.1.1. Feeder TSRs . . . . . . . . . . . . . . . . . . . 6
  145. 3.2. Backbone Hardware Requirements . . . . . . . . . . . 6
  146. 3.2.1. Types of Service . . . . . . . . . . . . . . . . . 6
  147. 3.2.2. Equipment Procurement and Costs . . . . . . . . . 6
  148. 3.2.3. PSN Port Assignment . . . . . . . . . . . . . . . 7
  149. 3.3. TAC Connection . . . . . . . . . . . . . . . . . . . 7
  150. 3.4. Registration Procedures . . . . . . . . . . . . . . 7
  151. 3.4.1. Host Registration . . . . . . . . . . . . . . . . 7
  152. 3.4.2. Host Addresses and Domains . . . . . . . . . . . . 7
  153. 3.4.3. LAN and Gateway Registration . . . . . . . . . . . 7
  154. 3.4.4. User Registration . . . . . . . . . . . . . . . . 7
  155. 3.4.4.1. NIC Registration Template . . . . . . . . . . . 7
  156. 3.4.4.2. NIC REGISTER Program . . . . . . . . . . . . . . 8
  157. 3.4.5. ARPANET TAC Access Registration . . . . . . . . . 8
  158.  
  159. SECTION 4. ARPANET PROTOCOLS . . . . . . . . . . . . . . . . . . . 9
  160. 4.1. DDN Protocol Handbook . . . . . . . . . . . . . . . 9
  161. 4.2. TCP/IP Implementations and Vendors Guide . . . . . . 9
  162. 4.3. RFCs . . . . . . . . . . . . . . . . . . . . . . . . 9
  163.  
  164. SECTION 5. HARDWARE AND SOFTWARE MODIFICATIONS . . . . . . . . . . 11
  165. 5.1. Subscriber Software and Hardware Modification
  166. Requests 11
  167. 5.2. ARPANET Software/Node Modification Procedures . . . 11
  168.  
  169. SECTION 6. NETWORK INFORMATION SERVICES . . . . . . . . . . . . . . 13
  170. 6.1. DDN Network Information Center . . . . . . . . . . . 13
  171. 6.1.1. User Assistance Service . . . . . . . . . . . . . 13
  172. 6.1.2. NIC Contacts . . . . . . . . . . . . . . . . . . . 14
  173. 6.1.3. Online Servers . . . . . . . . . . . . . . . . . . 14
  174. 6.1.3.1. TACNEWS . . . . . . . . . . . . . . . . . . . . 14
  175. 6.1.3.2. WHOIS/NICNAME . . . . . . . . . . . . . . . . . 14
  176. 6.1.3.3. Host Name Server . . . . . . . . . . . . . . . . 14
  177. 6.1.4. Documents . . . . . . . . . . . . . . . . . . . . 14
  178. 6.1.5. Online Files . . . . . . . . . . . . . . . . . . . 15
  179. 6.2. ARPANET Network Monitoring Center . . . . . . . . . 15
  180. 6.2.1. AMC Contacts . . . . . . . . . . . . . . . . . . . 15
  181. 6.3. Complaint Center/Unsatisfactory Service Reports . . 15
  182.  
  183. SECTION 7. KEY CONTACTS . . . . . . . . . . . . . . . . . . . . . . 17
  184. 7.1. DDN PMO Contacts . . . . . . . . . . . . . . . . . . 17
  185. 7.2. DARPA Contacts . . . . . . . . . . . . . . . . . . . 17
  186. 7.3. Contacts for Specific Services . . . . . . . . . . . 17
  187.  
  188. SECTION 8. REFERENCES . . . . . . . . . . . . . . . . . . . . . . . 19
  189. 8.1. Cited References . . . . . . . . . . . . . . . . . . 19
  190. 8.2. Additional References . . . . . . . . . . . . . . . 19
  191.  
  192. SECTION 9. GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . 21
  193.  
  194. APPENDIX. SITE PERSONNEL DUTIES . . . . . . . . . . . . . . . . . 23
  195.  
  196. List of Figures
  197.  
  198. Figure 2-1: Hardware and Configuration of the DDN 3
  199. Figure 2-2: Management of the ARPANET 3
  200. Figure 3-1: ARPANET New Subscriber Request Flow 5
  201. Figure 3-2: Sample Feeder TSR Template 6
  202. Figure 3-3: Host Data 7
  203. Figure 3-4: Host Administrator Data 7
  204. Figure 3-5: Sample User Registration Template 7
  205. Figure 5-1: Modification Request Procedure 11
  206.  
  207. ACKNOWLEDGEMENTS
  208.  
  209. The ARPANET Information Brochure was prepared by the DDN Network
  210. Information Center (NIC) for the Defense Advanced Research Projects Agency
  211. and the Defense Data Network Program Management Office of the Defense
  212. Communications Agency under contract number DCA-200-83-C-0025.
  213.  
  214. The NIC wishes to acknowledge the valuable assistance of Lt. Col. Bob
  215. E. Baker of the Defense Advanced Research Projects Agency, Andrew Hogan of
  216. the Defense Data Network Program Management Office, and Alan Hill of BBN
  217. Communications Corporation in the preparation of this document.
  218.  
  219.  
  220. ABSTRACT
  221.  
  222.  
  223. The ARPANET is an unclassified, packet-switched data network originally
  224. built by the Defense Advanced Research Projects Agency (DARPA) and used for
  225. Department of Defense computer science and networking research. It is now
  226. one of the subnetworks of the Defense Data Network (DDN) and, as such, is
  227. managed by the Defense Data Network Program Management Office (DDN PMO).
  228. Policy for the ARPANET is established by DARPA and they also decide who may
  229. become subscribers. Subscribers are required to follow certain technical
  230. and administrative procedures to connect host computers or other equipment
  231. to the DDN. This document describes these procedures as they apply to the
  232. ARPANET, provides background and technical information on the ARPANET, and
  233. suggests sources of further information on protocol implementations and
  234. interface equipment.
  235.  
  236.  
  237. SECTION 1. INTRODUCTION
  238.  
  239. The Defense Advanced Research Projects Agency (DARPA) may require its
  240. contractors or associated researchers to become ARPANET "subscribers"
  241. (sites which have host computers or other equipment connected to the
  242. network). In such cases DARPA requests authorization from the Defense Data
  243. Network Program Management Office (DDN PMO) to add the required equipment
  244. to the network.
  245.  
  246. This document describes the steps necessary for potential subscribers to
  247. attach host computers or other equipment to the ARPANET. Administrative
  248. and technical procedures are included. References to documents and
  249. services, which will be helpful during the process of connecting equipment
  250. to the network, are also included and are designated by the number of the
  251. reference in brackets, e.g. [1].
  252.  
  253.  
  254. 1.1 How To Use This Document
  255.  
  256. Section 1, the Introduction, explains how this document is organized.
  257.  
  258. Section 2 provides background on the ARPANET, describes the current
  259. management structure, and states the criteria for becoming a subscriber.
  260.  
  261. Section 3 presents the administrative and technical procedures necessary to
  262. bring a host onto the ARPANET. Different types of network connections and
  263. associated costs are described.
  264.  
  265. Section 4 discusses the protocols used on the ARPANET and the DDN, and
  266. tells how protocol implementations and documentation may be obtained.
  267.  
  268. Section 5 describes the administrative procedures required for requesting
  269. modifications of network software or hardware.
  270.  
  271. Sections 6 and 7 describe the services and personnel available to help with
  272. the process of connecting equipment to the ARPANET and with using the
  273. network.
  274.  
  275. Section 8, References, contains citations and sources for publications
  276. which provide further useful information. This section explains how to
  277. obtain both hardcopy and online documents.
  278.  
  279. Finally, the Appendix contains important information on the duties assigned
  280. to local network representatives.
  281. Comments or suggestions for improvements to the document are welcome. Send
  282. these by U.S. mail using the Comments Form at the end of the document or
  283. through network mail to: SUGGESTIONS@SRI-NIC.ARPA.
  284.  
  285.  
  286. SECTION 2. ARPANET MANAGEMENT AND POLICIES
  287.  
  288. This section presents background on how the ARPANET evolved into what it is
  289. today, and how it is currently managed.
  290.  
  291.  
  292. 2.1 What is the ARPANET?
  293.  
  294. The ARPANET began as an experimental packet-switched host-to-host network
  295. in late 1969. It was funded through a research and development program
  296. sponsored by DARPA. The goal of the program was to advance the
  297. state-of-the-art in computer networking. The resultant network
  298. successfully provided efficient communications between heterogeneous
  299. computers, allowing convenient sharing of hardware, software, and data
  300. resources among a varied community of geographically-dispersed users.
  301.  
  302.  
  303.  
  304.  
  305.  
  306.  
  307.  
  308.  
  309.  
  310.  
  311.  
  312.  
  313.  
  314.  
  315.  
  316.  
  317.  
  318.  
  319.  
  320.  
  321.  
  322.  
  323.  
  324.  
  325.  
  326.  
  327.  
  328.  
  329.  
  330.  
  331.  
  332. Figure 2-1: Hardware and Configuration of the DDN
  333.  
  334. In 1982 the DDN was created. The DDN uses ARPANET technology to link
  335. existing and planned Department of Defense (DoD) networks. It is composed
  336. of several operational, resource sharing, host-to-host networks which are
  337. linked by controlled gateways, and which serve DoD facilities and non-DoD
  338. research centers in the United States, Pacific, and European areas. All of
  339. the networks that make up the DDN share the same "backbone" of node
  340. computers. (See Figure 2-1 for a pictorial overview of the network
  341. hardware and configuration). Node computers are interconnected through a
  342. set of communications protocols referred to as the DoD Internet Protocol
  343. Suite.
  344.  
  345. In 1983, the existing ARPANET was administratively divided into two
  346. unclassified networks, ARPANET and MILNET, to meet the growing need for an
  347. unclassified operational military network as well as the need for a
  348. research and development network. The physical split into separate
  349. networks was completed in September 1984. Each network now has its own
  350. backbone, and is interconnected through controlled gateways to the other.
  351. The ARPANET serves primarily as an experimental research and development
  352. network, while the MILNET functions as an operational military network for
  353. non-classified traffic. Communication and resource sharing between them
  354. continue, but are subject to administrative restrictions.
  355.  
  356.  
  357. 2.2 Management of the ARPANET
  358.  
  359. The DDN, including ARPANET, is operated for the DoD by the Defense
  360. Communications Agency DDN PMO. For an overview of the management structure
  361. for ARPANET, see Figure 2-2.
  362.  
  363.  
  364.  
  365.  
  366.  
  367.  
  368.  
  369. DoD
  370. ________________|________________
  371. | |
  372. DCA DARPA
  373. | |
  374. DDN PMO IPTO
  375. | |
  376. (operational management) (administration, policy)
  377. (security) (configuration, access)
  378. |________________ ________________|
  379. |
  380. ARPANET
  381.  
  382.  
  383.  
  384. Figure 2-2: Management of the ARPANET
  385.  
  386.  
  387. 2.2.1 DARPA/IPTO
  388.  
  389. DARPA's Information Processing Techniques Office (IPTO) is dedicated to
  390. developing advanced information processing and computer communications
  391. technologies for critical military and national security applications. The
  392. building of the ARPANET and development of its protocols was an IPTO
  393. program, which has evolved into what is now known as the Internet Research
  394. Program.
  395.  
  396. Through IPTO, DARPA sets policy for, and manages use of, the ARPANET. This
  397. is done within broad guidelines established for all DDN networks by the DDN
  398. PMO. It also funds the ARPANET, and funds research carried out on the
  399. ARPANET. Since there have been recent changes, it is important to
  400. reiterate that the DDN PMO operates and manages the ARPANET, including the
  401. node software and hardware, while DARPA pays the backbone operating costs,
  402. sets policy for the ARPANET, and approves access for DARPA-sponsored
  403. subscribers.
  404.  
  405.  
  406. 2.2.2 DDN PMO Responsibilities
  407.  
  408. The DDN PMO is responsible for overall management, operations, and policy
  409. guidelines for the entire DDN. It assists new subscribers in connecting
  410. hosts and related equipment to the DDN, and manages the ARPANET on behalf
  411. of DARPA. The DDN PMO provides many services to network users and
  412. potential network subscribers, including:
  413.  
  414. - Keeping the network up and running
  415.  
  416. - Providing users with assistance
  417.  
  418. - Planning for growth
  419.  
  420. - Providing configuration management and control
  421.  
  422. - Assisting with protocol implementation and testing
  423.  
  424. - Advising subscribers on the selection of interface equipment and
  425. software
  426.  
  427. - Managing access control and security for the network backbone
  428.  
  429. - Designating local host and node representatives
  430.  
  431. - Arranging for all equipment required to establish a network
  432. connection
  433.  
  434. - Providing technical management of contracts for services,
  435. equipment, and software obtained from outside corporations and
  436. vendors.
  437.  
  438. The Data Operations Division, Code B650, of the DDN PMO manages all DDN
  439. networks, including the ARPANET. For each DDN network, a PMO staff member
  440. has been designated as the primary "point of contact" (POC). All
  441. operational questions should be referred to this POC. (See Section 7 for
  442. the phone number and mailbox of the ARPANET POC). The Data Operations
  443. Division is also responsible for coordinating operational matters within
  444. the DDN PMO itself, as well as with other branches and divisions of the DCA
  445. and with DARPA.
  446.  
  447.  
  448. 2.2.3 IAB Responsibilities
  449.  
  450. The DARPA Internet Research Program is directed by DARPA IPTO with the
  451. assistance of an Internet Advisory Board (IAB) and a set of IPTO-appointed
  452. Task Forces (technical working committees). The IAB consists of the
  453. chairmen of the Task Forces, the DARPA Program Manager, the Chairman of the
  454. IAB (the Internet Architect), the Deputy Chairman, and the Secretary of the
  455. IAB.
  456.  
  457. The IAB guides and reviews the work of the Task Forces, and ensures proper
  458. cross communication among them. The IAB may from time to time create new,
  459. or disband existing, Task Forces.
  460.  
  461. The Task Forces are expected to generate and develop new ideas, to monitor
  462. the technical work of the Internet program, and to recommend additional
  463. research activity. The role of the Task Forces is seminal and advisory,
  464. and very important to the advancement of the research goals of the Internet
  465. program.
  466.  
  467. Members of each Task Force are chosen by its chairman, and they are
  468. expected to make a moderate commitment of time to the work of the Task
  469. Force. Most Task Forces also have mailing lists for persons interested in
  470. following the work of a given Task Force. Current Task Forces and chairmen
  471. are:
  472.  
  473. Task Force Chairman Organization (See Glossary)
  474. Applications Bob Thomas BBNCC
  475. Gateway Algorithms
  476. and Data Structures Dave Mills M/A-COM
  477. Interoperability
  478. and Autonomous Systems Robert Cole UCL
  479. New End to End Services Bob Braden UCLA
  480. Privacy Steve Kent BBNCC
  481. Robustness and Survivability Jim Mathis SRI
  482. Security Ray McFarland DOD
  483. Tactical Internetting David Hartmann MITRE
  484. Testing Ed Cain DCEC
  485. IAB officers are:
  486.  
  487. Position Occupant Organization
  488. Internet Architect Dave Clark MIT
  489. Deputy Internet Architect Jon Postel ISI
  490. DARPA Program Manager Dennis Perry DARPA
  491. IAB Secretary Chris Perry MITRE
  492.  
  493. Phone numbers for IAB members are available through DARPA.
  494.  
  495.  
  496. 2.3 ARPANET Access and Use Policies
  497.  
  498. DARPA and the DDN PMO have set broad guidelines for ARPANET access and use,
  499. administered locally by volunteer site personnel called Host
  500. Administrators. Legitimate ARPANET users must be engaged in U.S.
  501. government business or research, or directly involved in providing
  502. operations or system support for government-owned or government-sponsored
  503. computer communications equipment. The network is not available for use by
  504. the general public, nor is it intended to compete with comparable
  505. commercial network services.
  506.  
  507. The purpose of the ARPANET is to provide a facility for advanced
  508. packet-switched communications technologies research and experimental
  509. communication support of government-sponsored university computer science
  510. research. Consequently, access to, and use of, ARPANET will not be
  511. authorized to support operational (as opposed to experimental)
  512. communication requirements. Such operational facilities are provided for
  513. DoD users by the DDN, and for others by public and private packet-switched
  514. networks (such as TYMNET or TELENET).
  515.  
  516. Users of ARPANET may only use the network to conduct the official business
  517. for which their access was authorized. They must not violate privacy or
  518. any other applicable laws, and must not use the network for private gain or
  519. for commercial purposes, such as advertising or recruiting. ARPANET users
  520. may connect to other DDN networks only when approved by the DDN PMO on a
  521. host-by-host basis.
  522.  
  523. Host site personnel are responsible for developing and enforcing specific
  524. policies to ensure that these guidelines are followed. (See the Appendix
  525. for a formal statement of site personnel responsibilities). The Host
  526. Administrator is given the authority to disallow access to the ARPANET by
  527. users who use the network irresponsibly or for unauthorized purposes. The
  528. DDN PMO assumes this authority only in an emergency, or if administration
  529. at the local level is not functioning.
  530.  
  531.  
  532. 2.3.1 Host Access Controls
  533.  
  534. Subscribers and sponsors are responsible for letting only authorized users
  535. have network privileges. All non-government users should be associated
  536. with a valid contract number, or have explicit permission to use the
  537. ARPANET. Additionally, host sites must maintain these controls:
  538.  
  539. - Procedures that allow only valid users to obtain accounts on
  540. government-owned computers or to obtain access to the ARPANET
  541. backbone from the host
  542.  
  543. - Login Name/Password so that only valid users can access the host
  544.  
  545. - Periodic Reviews of users so that persons who no longer need
  546. ARPANET access are denied such access and unused accounts are
  547. closed.
  548.  
  549. Any attempts to break into a system from the network should be reported by
  550. the Host Administrator to the DDN PMO and DARPA by telephone or U.S. mail.
  551.  
  552. When violations of the above policies are observed, DCA will notify the
  553. site personnel. If the problem is not corrected within a reasonable time,
  554. DCA may exercise the option of disconnecting the host or terminal from the
  555. network.
  556.  
  557.  
  558. 2.3.2 TAC Access Controls
  559.  
  560. A Terminal Access Controller (TAC) is a computer system attached directly
  561. to the DDN that lets a user at a terminal connect to hosts on the network
  562. without first going through a local host. (See Section 3.3 for a
  563. description of a TAC connection).
  564.  
  565. ARPANET users must be authorized for network TAC access by a
  566. DARPA-appointed network contact known as a "Responsible Person" (RP). An
  567. RP is a person in a position of authority within each organization
  568. authorized to use the ARPANET. The RP is responsible for ensuring that TAC
  569. access to the ARPANET is only allowed for those members of his organization
  570. with a valid requirement for such access. The RP, or his delegate, sees
  571. that TAC users are entered into the ARPANET TAC User Database (UDB)
  572. accessible through the network. The RP uses the UDB to generate a "USER
  573. ID" and an "ACCESS CODE" for each user.
  574.  
  575. The User Database is downloaded regularly to several "login hosts"
  576. throughout the ARPANET. These hosts verify authorized use at the time a
  577. user logs in to a TAC. When an ARPANET TAC user tries to open a connection
  578. to a host from a TAC, the TAC requests a USER ID and ACCESS CODE, then
  579. interacts with a login host to validate the user. If the login host
  580. reports that the USER ID/ACCESS CODE is invalid, the TAC prints an error
  581. message and refuses to open a connection. Access is thus restricted to
  582. users whose names have been entered into the user database.
  583.  
  584. MILNET, the DoD's operational military network which shares the DDN
  585. backbone with ARPANET, also contains TACs and has a system of registering
  586. MILNET TAC users. Although these registration systems serve the same
  587. purpose, they are different in operation, and are physically and
  588. administratively completely independent from each other. A user authorized
  589. for access through both MILNET and ARPANET TACs must register twice, once
  590. in each system. Note that the login procedure itself is identical whether
  591. the user logs in from ARPANET or MILNET. Only the user registration
  592. procedures are different.
  593.  
  594. Lack of local ARPANET TAC resources is not considered sufficient reason to
  595. provide ARPANET users with MILNET TAC access and vice versa. MILNET TACs
  596. are provided to assist authorized users in carrying out DDN operational
  597. tasks. Contact the DARPA POC (see Section 7.2) if you are an authorized
  598. ARPANET user and there is no ARPANET TAC available in your area.
  599.  
  600.  
  601. SECTION 3. SUBSCRIBER ACCESS PROCEDURES
  602.  
  603. This section describes how a potential ARPANET subscriber can apply for
  604. access to the network. It compares the different types of connections
  605. available, and describes how terminals can access hosts through the network
  606. TACS.
  607.  
  608. NOTE: The entire process from application to completion may require
  609. over a year if installation of phone lines or node equipment is
  610. required. It is important to plan ahead and let DARPA and the DDN PMO
  611. know what your anticipated needs are.
  612.  
  613. The process of becoming a subscriber involves several steps. It must first
  614. be determined that the potential subscriber has a legitimate need to access
  615. the network and has authorization from DARPA to use the network. Paperwork
  616. must be submitted to authorize the DDN PMO to begin the process of ordering
  617. all equipment required to establish a network connection.
  618.  
  619. Site personnel must arrange to lease or purchase a host computer (if one is
  620. not already available), and to implement or procure implementations of
  621. network protocols that will run on it. They must also arrange for the
  622. installation and testing of site hardware. The sections that follow
  623. describe these procedures in greater detail.
  624.  
  625.  
  626. 3.1 Process Overview
  627.  
  628. All ARPANET host connections are managed by the Packet Switching Operations
  629. Branch, Code B652, of the DDN PMO. The procedures for getting a host
  630. connected to ARPANET are outlined below.
  631.  
  632. a. Contact Code B641 of the DDN PMO, who determines whether the
  633. requirement qualifies for ARPANET or MILNET connection.
  634.  
  635. b. Contact the ARPANET Coordinator in the Information Processing
  636. Techniques Office (IPTO) at DARPA, who will verify government
  637. sponsorship and will provide the required Feeder
  638. Telecommunications Service Request (TSR), Host Approved Form
  639. (HAF) and, when necessary, the Internet Protocol Network Number
  640. Request Form.
  641.  
  642. c. Submit the filled-in Telecommunications Service Request (TSR)
  643. forms to DARPA for approval and subsequent forwarding to Code
  644. B643 and Code B652 of the DDN PMO.
  645.  
  646. d. The TSR is issued by the DDN PMO. The requester receives a
  647. hardcopy confirmation via Mailgram, TELEX or AUTODIN message.
  648.  
  649. e. Requester also receives a Telecommunications Service Order (TSO)
  650. delivered via the same means.
  651.  
  652. f. The Installation Branch, Code B642, generates a Network Change
  653. Request (NCR) from host data provided by Code B652.
  654.  
  655. g. The NCR is approved by Code B652 of the PMO and becomes a
  656. Network Change Directive (NCD). Host data is added to the NIC
  657. host table, the ARPANET Monitoring Center (AMC) activates the
  658. host port, and the requester receives electronic mail
  659. confirmation of the NCD.
  660.  
  661. h. When the host is installed, the requester receives a completion
  662. report by the same means as the original TSR.
  663.  
  664. NOTE: The TSR and TSO indicate the assigned network address, and
  665. therefore, the network node through which service will be provided.
  666. Each node has a Node Site Coordinator (NSC) (See Appendix ), whom the
  667. host requester may wish to contact concerning cabling or other
  668. connection mechanisms between the host and node locations. If a new
  669. node must be installed at the site before hosts can be connected to
  670. the network, an NSC will have to be appointed, who should be prepared
  671. to assist DDN PMO field representatives with node equipment
  672. installation.
  673.  
  674.  
  675.  
  676.  
  677. New Subscriber Request
  678. |
  679. DCA Code B641
  680. |
  681. ARPANET Coordinator, DARPA
  682. |
  683. Feeder TSR and HAF
  684. |
  685. DARPA IPTO Approval
  686. |
  687. DCA Code B652 Approval
  688. |
  689. DCA Code B643
  690. |
  691. Requester <------- TSR Issued
  692. Notified TSO Issued --------> DECCO
  693. |
  694. DCA Code B652
  695. Provides Host Data
  696. |
  697. DCA Code B642
  698. |
  699. NCR
  700. |
  701. DCA Code B652
  702. Approval
  703. |
  704. NCD
  705. |
  706. ______________________|______________________
  707. | | |
  708. SRI NIC Requester AMC
  709. | Notified |
  710. Host Table Change NCAN
  711. |
  712. DCA Code B652
  713.  
  714.  
  715. AMC: ARPANET Monitoring Center NCD: Network Change Directive
  716. DECCO: Defense Commercial Comm. Office NCR: Network Change Request
  717. HAF: Host Approved Form SRI NIC: Network Information Ctr.
  718. IPTO: Info. Process. Techniques Office TSO: Telecomm. Service Order
  719. NCAN: Network Change Ack. Notice TSR: Telecomm. Service Request
  720.  
  721.  
  722. Figure 3-1: ARPANET New Subscriber Request Flow
  723.  
  724.  
  725. 3.1.1 Feeder TSRs
  726.  
  727. The Feeder TSR provides information for assessing the applicant's need for
  728. network access, and is a preliminary request for service leading to the
  729. issuance of a full TSR by the DDN PMO. To submit a Feeder TSR for ARPANET
  730. service, the template shown in Figure 3-2 must be completed.
  731.  
  732. The parts of the Feeder TSR are:
  733.  
  734. (1) TSR ITEM NUMBER - the number for each entry.
  735.  
  736. (2) INFORMATION - data provided by the applicant; on the sample
  737. template (Figure 3-2) a description is provided of the
  738. information required for each item.
  739.  
  740. (3) TYPE OF ACTION - indicates whether applicant must complete an
  741. item, contingent upon choice indicated in Item 103.
  742.  
  743. For example, if you are starting service, write "start" on line 103 in the
  744. information column. You must then fill in information for all lines where
  745. there is an "X" in the "START" column under "Type of Action". If you have
  746. questions about the template, contact the ARPANET Coordinator at DARPA or
  747. the ARPANET POC at the DDN PMO.
  748.  
  749.  
  750. FEEDER TSR TEMPLATE (Sample)
  751.  
  752. (1) (2) (3)
  753.  
  754. TSR INFORMATION TYPE OF ACTION
  755. ITEM NO. START AMEND REHOME CANCEL
  756. --- ----------- ----------------------------
  757.  
  758. 101 LEAVE BLANK
  759. 103 TYPE OF ACTION (Start, Change,
  760. Discontinue, Amendment, Rehome)
  761. 104 Fill in the words "LEASED EQUIPMENT/
  762. SERVICE CONTRACT" if leased modems
  763. and maintenance is required to be
  764. provided by the government
  765. 105 Fill in the word "DEDICATED" if
  766. ARPANET and "DDN" if MILNET
  767. 106 State the requested service date
  768. by day, Greenwich Mean Time, Month,
  769. and Year. e.g. 141200Z JUL 84.
  770. NOTE: A minimum of 150 days is required
  771. for circuits.
  772. 110 FULL DUPLEX
  773. 111 Enter the data rate (2.4KB, 1.2KB,
  774. 4.8KB, 9.6KB, 50KB, 56KB, 100KB) of
  775. the requested service.
  776. 112 FULL PERIOD
  777. 115 NO SIGNALLING X X
  778. 116 Enter the words "NEW LEASE" if this
  779. is a new requirement, or enter the
  780. Commercial Communications Service
  781. Authorization Number (CSA) if this is
  782. an amendment, rehome, disconnect, or
  783. change to an existing requirement.
  784. If no circuit is required, omit this
  785. item.
  786. 117 LEAVE BLANK
  787. 118 LEAVE BLANK
  788. 120A The end user location requiring
  789. ARPANET/MILNET Access (Geographical
  790. location, e.g. city, base, camp, post
  791. or station that is applicable)
  792. 121A State of the end user location
  793. 123A CPV
  794. 124A The building number where the user's
  795. terminal or host is located that will
  796. be connected to the ARPANET/MILNET
  797. 125A The room number where the user's
  798. terminal or host is located that will
  799. be connected to the ARPANET/MILNET
  800. 126A The type of terminal or host equipment
  801. that will be connected.
  802. 128A The user interface that will be
  803. connected up to the circuit (RS-232C,
  804. RS-449, Synchronous, Asynchronous,
  805. MIL-STD 188-114, Leased Modem)
  806. 130A Provide the name, telephone number
  807. and office code or symbol of a primary
  808. and alternate person at the user's
  809. terminal end that is familiar with the
  810. details and requirements of this request
  811. 131A Provide the complete mailing address
  812. of the primary person identified in
  813. 130A, including the agency, street
  814. address, building number, city, state
  815. and zip code.
  816. 120B TO BE DETERMINED BY DCA
  817. 353 Fill in "ARPANET" or "MILNET"
  818. 354 If this requirement is for a terminal
  819. connection and not a host, enter the
  820. data link protocol (e.g. asynchronous)
  821. 357 If this requirement is to connect a
  822. host, enter the software and hardware
  823. interface requirements (e.g. RS232/
  824. V.35/MIL-188-114/Bell 303/cable only
  825. and HDH/X.25/DH/DH with ECU's
  826. 361 If this requirement is for a terminal
  827. connection and not a host, enter
  828. "ASCII"
  829. 401 State the exact requirement of this
  830. request, e.g. The purpose of this
  831. request is to request leased modems
  832. and circuit between end points.
  833. 407A If this request is to provide leased
  834. modems, state so here, and if the
  835. modem is to be a stand alone or rack
  836. mounted in a cabinet. If additional
  837. equipment is to be leased, state so
  838. (e.g. 1-ea 72 inch modem cabinet,
  839. 2-ea 25 ft RS-232 M/F connection
  840. cable). All equipment to be provided
  841. by the government should be listed
  842. here.
  843. 409 The individual at the user site who
  844. will accept service.
  845. 417 If this requirement is to connect up
  846. a host, please list the host name
  847. along with any narrative remarks which
  848. will help to clarify this requirement.
  849. e.g. statement that user is providing
  850. circuit and modems if that is the
  851. case, statement that no circuit is
  852. required due to it being a local
  853. connection if that is the case,
  854. desired/recommended PSN for connection.
  855. In all cases, the electronic mail
  856. address for the person shown in 130A
  857. should be indicated here.
  858. 419 DECCO SCOTT AFB
  859. 430 Estimated length of service requirement
  860. (12, 24, 36, 48, or 72 months)
  861. 431 "N" if ARPANET, "D" if MILNET
  862. 437A YES OWM
  863. 438A "NONE" if no leased equipment is
  864. required or "BOTH" if this request
  865. includes both circuit and associated
  866. leased equipment.
  867. 501 Justification for the service being
  868. requested, e.g. To provide UCLA
  869. connection to the ARPANET for testing
  870. host interfaces.
  871. 510 LEAVE BLANK
  872.  
  873.  
  874.  
  875. Figure 3-2: Sample Feeder TSR Template
  876.  
  877.  
  878.  
  879. Submit the feeder TSR templates for ARPANET service to DARPA:
  880. U.S. Mail Address
  881.  
  882. Defense Advanced Research Projects Agency
  883. Information Processing Techniques Office
  884. Attn: ARPANET COORDINATOR
  885. 1400 Wilson Boulevard, 7th Floor
  886. Arlington, Virginia 22209
  887.  
  888. Telephone
  889.  
  890. Phone: (202) 694-5921
  891.  
  892. Network Mailbox
  893.  
  894. BOWERS@USC-ISI.ARPA
  895.  
  896.  
  897.  
  898. 3.2 Backbone Hardware Requirements
  899.  
  900.  
  901. 3.2.1 Types of Service
  902.  
  903. The network interface can be either full service (supporting all DDN
  904. protocols) or limited service. A full-service interface is recommended
  905. whenever possible, as it provides the most functionality for users.
  906.  
  907. Limited service may be provided by a terminal emulation interface, or an
  908. interface supported by vendor-specific protocols. Either type may be used
  909. temporarily while awaiting a full-service interface. Permanent
  910. installation of limited-service interfaces should be restricted to terminal
  911. emulation interfaces, and to systems where the cost of a full-service
  912. interface would be prohibitive.
  913.  
  914. For complete information on types of service available on the DDN, see the
  915. DDN Subscriber Interface Guide [1].
  916.  
  917.  
  918. 3.2.2 Equipment Procurement and Costs
  919.  
  920. Costs for connection to the ARPANET are not fixed, but are arranged on an
  921. individual basis. Generally, DARPA pays backbone costs and the contractor
  922. pays all other costs (including Error Correction Units and interface units,
  923. when required). For detailed information, contact the ARPANET POC (see
  924. Section 7.2).
  925.  
  926.  
  927. 3.2.3 PSN Port Assignment
  928.  
  929. The initial Packet Switch Node (PSN, formerly called Interface Message
  930. Processor or IMP) port assignment is sent to the subscriber as part of the
  931. TSR/TSO process (described in Section 3.1.1). Subscribers must not change
  932. PSN ports or switch equipment on PSN ports without approval through the
  933. TSR/TSO process.
  934.  
  935. Note that PSN port changes must have proper authorization and will not
  936. happen instantaneously. Also, if a host is changed to a different PSN
  937. port, its host address will change (see Section 3.4.1). Contact the
  938. ARPANET POC or the NIC for assistance in obtaining a PSN port change or if
  939. problems with host names or addresses arise.
  940.  
  941.  
  942. 3.3 TAC Connection
  943.  
  944. ARPANET users may access a network host via a TAC, which is a special
  945. terminal access node. TACs let a terminal connect directly to the network,
  946. i.e., without going through another host. Terminals may be either
  947. hard-wired to the TAC or connected by a dial-up modem. A user
  948. geographically remote from a given host can dial up a nearby TAC, log in,
  949. open a connection to the distant host, and work as if he were connected
  950. locally. Thus, the TAC lets the user reach his host through the network,
  951. rather than through a direct long distance telephone call to the host.
  952.  
  953. Current TAC locations and phone numbers are available from the NIC. If
  954. installation of a TAC appears to be necessary for your area or user
  955. population, contact the DARPA POC and describe the need for the
  956. installation of a TAC at the designated location. DARPA will evaluate the
  957. request and, if the request is warranted, will place an order for TAC
  958. installation with the DDN PMO.
  959.  
  960.  
  961. 3.4 Registration Procedures
  962.  
  963. The following sections discuss the administrative steps a potential
  964. subscriber should take to register a host, and the procedures required to
  965. register users once the host is connected to the net. Figure 3-1 gives an
  966. overview of the process.
  967.  
  968.  
  969. 3.4.1 Host Registration
  970.  
  971. Each host on the DDN is identified by a unique host name and host address.
  972. To register a host, information must be supplied to DCA Code B652, the
  973. Packet Switching Operations Branch, as shown in the following examples
  974. (Figures 3-3, 3-4). Send completed forms online or by U.S. mail to the
  975. ARPANET Coordinator at DARPA.
  976.  
  977.  
  978. Host Data (Sample)
  979.  
  980. HOSTNAME: DDN1
  981. NETWORK ADDRESS: 10.1.0.25
  982. LOCATION: Bolt Beranek and Newman Inc.
  983. 1300 North 17th Street
  984. Suite 400
  985. Arlington, Virginia 22206
  986. CPUTYPE: BBN-C/70
  987. OPERATING SYSTEM: UNIX
  988. NICKNAME: DDN-1
  989. SPONSORING AGENCY: DCA
  990. HOST TYPE: DH
  991. PROTOCOLS: TCP/TELNET,TCP/FTP,TCP/SMTP
  992.  
  993.  
  994. Figure 3-3: Host Data
  995.  
  996.  
  997.  
  998.  
  999. Host Administrator Data (Sample)
  1000.  
  1001. NAME: Chipman, Steven G.
  1002. U.S. MAIL ADDRESS: Bolt Beranek and Newman Inc.
  1003. 10 Moulton Street
  1004. Cambridge, Massachusetts 02238
  1005. TELEPHONE: (617) 497-3505 (now 873-3505, May 89)
  1006. NETWORK MAILBOX: chipman@BBNF.ARPA
  1007.  
  1008.  
  1009. Figure 3-4: Host Administrator Data
  1010.  
  1011.  
  1012.  
  1013. 3.4.2 Host Addresses and Domains
  1014.  
  1015. The host address contains four decimal numbers, each separated by a period.
  1016. Each part represents one octet of a 32-bit address. The meaning of each
  1017. octet depends upon which class of network it describes. There are three
  1018. classes of networks (Class A, Class B, and Class C), based upon the
  1019. network's size and function.
  1020.  
  1021. On Class A networks, which are large, long-haul networks such as ARPANET
  1022. and MILNET, the first octet indicates the network number. The second octet
  1023. refers to the host port number on the PSN; the third octet is reserved, and
  1024. is usually zero; and the last octet is the number of the PSN to which the
  1025. host is connected.
  1026.  
  1027. For Class B networks, the first two octets indicate the network portion of
  1028. the number; for Class C networks the first three octets are used to
  1029. indicate the network number. For more information on address mappings, see
  1030. RFC 796 [2].
  1031.  
  1032. The DDN Network Information Center maintains the official DoD Internet Host
  1033. Table and is the network Hostmaster for names and addresses of hosts,
  1034. networks, nodes and domains. Hosts should arrange to regularly update
  1035. their local tables by retrieving all or part of the master table from the
  1036. NIC Host Name Server. For information about the DoD Internet Host Table
  1037. specification, see RFC 952 [3].
  1038.  
  1039. In the near future, all DARPA hosts will be required to either join an
  1040. existing "domain" or to administer a domain of their own. Domains are
  1041. administrative entities that provide decentralized host naming and
  1042. addressing management. Their purpose is to distribute the task of naming
  1043. and addressing.
  1044.  
  1045. Under the domain-naming scheme, information is stored in a distributed,
  1046. hierarchical database. Responsibility for naming domains (or sub-nodes of
  1047. the hierarchical naming tree) can then be delegated to different
  1048. organizations, each with responsibility for maintaining host-related
  1049. information for their domain. Information about hosts and domains is
  1050. disseminated through the network via Name Servers. For more information on
  1051. domains, see RFC 920 [4] and RFC 921 [5].
  1052.  
  1053. The domain system on ARPANET is experimental. The MILNET has not yet
  1054. implemented the domain system. The NIC name server translates between the
  1055. two systems and continues to provide a "flat" domainless host table for use
  1056. by MILNET hosts while serving as registrar for domain names for the
  1057. Internet.
  1058.  
  1059.  
  1060. 3.4.3 LAN and Gateway Registration
  1061.  
  1062. Subscribers wishing to connect a local area network (LAN) or other non-DDN
  1063. network to the ARPANET must first obtain DARPA and DCA approval. Such
  1064. networks are connected to the DDN through a "gateway" computer which
  1065. manages communication between the LAN or non-DDN net and the ARPANET.
  1066. DARPA treats gateways as regular hosts, so the procedure for registering a
  1067. gateway is the same as for hosts.
  1068.  
  1069. The subscriber must obtain a network number for each LAN from the NIC.
  1070. Within such a "private network", subscribers can assign their own host
  1071. names and addresses as long as they follow the internet network addressing
  1072. convention [2]. For more information on registering non-DDN networks,
  1073. contact HOSTMASTER@SRI-NIC.ARPA online or call (800) 235-3155.
  1074.  
  1075.  
  1076. 3.4.4 User Registration
  1077.  
  1078. The DDN PMO and DARPA have authorized the NIC to register all ARPANET
  1079. users, and to maintain this information in the NIC WHOIS database. This
  1080. database serves as an online "white pages" service for ARPANET users [6].
  1081.  
  1082. The Host Administrator for each host is responsible for registering the
  1083. users of his or her host with the NIC. This is done electronically over
  1084. the network, so the Host Administrator is required to have a network
  1085. mailbox.
  1086.  
  1087. Users may be registered either by sending filled-in templates to the NIC
  1088. through electronic mail, or by using the NIC REGISTER system. This section
  1089. describes the procedures a Host Administrator should follow to register
  1090. users.
  1091.  
  1092.  
  1093. 3.4.4.1 NIC Registration Template
  1094.  
  1095. To register by electronic mail, FTP a copy of the registration template
  1096. (pathname NETINFO:USER-TEMPLATE.TXT, see Figure 3-5) from SRI-NIC
  1097. (10.0.0.51). Complete one template for each individual and separate the
  1098. templates by a blank line. Fill in all the relevant fields as shown below.
  1099. Instructions for completing the template are included in the template file.
  1100. It is important that you use the NIC template and adhere to the same
  1101. data-entry style shown. This will allow automatic input of the data into
  1102. the WHOIS database. The NIC will not accept data that is not in the
  1103. specified template format.
  1104.  
  1105.  
  1106. FULL NAME: Coleman, Jr., Arthur F.
  1107. U.S. MAIL ADDRESS: SRI International
  1108. 333 Ravenswood Avenue
  1109. Menlo Park, CA 94025
  1110. PHONE: (415) 859-0000
  1111. AUTHORIZING HOST: SRI-NIC
  1112. PRIMARY LOGIN NAME: Coleman
  1113. PRIMARY NETWORK MAILBOX: coleman@SRI-NIC.ARPA
  1114. ALTERNATE NETWORK MAILBOXES (if any): acoleman@SRI-TSC.ARPA
  1115.  
  1116.  
  1117. Figure 3-5: Sample User Registration Template
  1118.  
  1119.  
  1120.  
  1121. The Host Administrator may send his users blank templates to fill out.
  1122. Users should return the completed templates to the Host Administrator who
  1123. will accumulate them in a single file. He will review the lists (as he is
  1124. responsible for the authorization of registered users on his hosts), and
  1125. send the files as online messages to REGISTRAR@SRI-NIC.ARPA.
  1126.  
  1127. If the list is too long for a given mail system to process, the Host
  1128. Administrator may break the lists arbitrarily (between templates) and send
  1129. them as a set of messages. If the lists are broken up, the subject field
  1130. of each message should specify this, e.g., Part 1 of 4, Part 2 of 4, etc.
  1131. To assure that the NIC mail system will be able to process the message,
  1132. never send a message of over 50,000 characters (100 templates). Full
  1133. instructions for registering users may be obtained from the NIC.
  1134.  
  1135. NOTE: Registering ARPANET users with the NIC for the WHOIS database
  1136. is a separate process from registering users for ARPANET TAC access.
  1137.  
  1138.  
  1139. 3.4.4.2 NIC REGISTER Program
  1140.  
  1141. REGISTER is a program running on SRI-NIC that will allow users to
  1142. interactively register themselves in the WHOIS database. Contact the NIC
  1143. for details on using this program.
  1144.  
  1145.  
  1146. 3.4.5 ARPANET TAC Access Registration
  1147.  
  1148. ARPANET TAC users must be authorized for network access by the "Responsible
  1149. Person" (RP) in their organization. Once users have been given permission
  1150. by the RP to use an ARPANET TAC, the RP or his delegate, or the user
  1151. himself may enter user registration data into the ARPANET TAC User Database
  1152. (UDB), using the User Database Tool located at host USC-ISI. The database
  1153. is downloaded regularly to several "login hosts" throughout the net. For
  1154. information on using the database tool, the RP or the user should obtain
  1155. and read ARPANET Access Control, User Manual for the User Database Tool [7]
  1156. available in hardcopy or online from the NIC.
  1157.  
  1158. NOTE: ARPANET TAC usernames and passwords must be changed every 6
  1159. months as they will be invalid after that time. The user may make
  1160. this change himself, once he has been given permission to be a TAC
  1161. user. However, the change must be made within the 6 month time period
  1162. or permission to be a TAC user will again need to be assigned by an
  1163. RP.
  1164.  
  1165.  
  1166. SECTION 4. ARPANET PROTOCOLS
  1167.  
  1168. A special set of DoD Internet protocols has been developed and implemented
  1169. on the ARPANET. The most important of these are the Transmission Control
  1170. Protocol (TCP) and the Internet Protocol (IP). These protocols govern the
  1171. handling of internet communication, and must be implemented on each host or
  1172. host interface before connecting to the network.
  1173.  
  1174. Each site has the choice of implementing its own version of the protocols,
  1175. adapting a public domain version of the protocols, or purchasing an
  1176. implementation from a commercial vendor. This section discusses some aids
  1177. to help subscribers choose the best approach based upon their needs.
  1178.  
  1179. NOTE: Protocols approved for use on the DDN are issued as official
  1180. DoD Military Standards (MIL STDs). The ARPANET is an experimental
  1181. network and may choose to implement experimental ARPANET protocols.
  1182. These may be ARPANET standards, i.e., required on the ARPANET, but may
  1183. not be MIL STDs or official DoD protocols.
  1184.  
  1185.  
  1186. 4.1 DDN Protocol Handbook
  1187.  
  1188. The 1985 DDN Protocol Handbook [8] describes specifications for MIL STD
  1189. communication protocols, ARPANET standard protocols, experimental
  1190. protocols, and de facto protocols in use on the DDN and the DARPA Internet.
  1191. It also includes background information, policy information, implementation
  1192. guidelines, and instructions on how to obtain other protocol information of
  1193. interest.
  1194.  
  1195. The primary purpose of the Handbook is to serve as a reference guide for
  1196. those planning to implement the DoD suite of protocols on various computers
  1197. to be attached to the ARPANET or the DDN. It is an essential reference
  1198. tool for sites bringing hosts onto the network. The Handbook is a
  1199. multi-volume set published by the NIC and is available from the NIC for
  1200. $110.00 prepaid, or from the Defense Technical Information Center (DTIC).
  1201.  
  1202.  
  1203. 4.2 TCP/IP Implementations and Vendors Guide
  1204.  
  1205. The TCP/IP Implementations and Vendors Guide [9] is a guide to commercially
  1206. available implementations of the TCP/IP protocols, including public domain
  1207. implementations. It is published for informational purposes only by the
  1208. DDN Network Information Center at SRI International on behalf of the DDN
  1209. PMO and in no way endorses or officially recommends any implementation or
  1210. product on the part of DCA, DARPA, the DoD, or the NIC. The Guide is
  1211. useful for finding out what public domain and commercial implementations of
  1212. protocols are available.
  1213.  
  1214.  
  1215. 4.3 RFCs
  1216.  
  1217. Before a proposed protocol is accepted for use on the DARPA Internet, it is
  1218. discussed, reviewed, and often revised by members of the Internet Advisory
  1219. Board, its Task Force members and other interested parties. This dialog is
  1220. captured in a set of technical notes known as Requests For Comments, or
  1221. RFCs.
  1222.  
  1223. Individuals who wish to be added to the online RFC notification list should
  1224. send a message to NIC@SRI-NIC.ARPA requesting that their names be added to
  1225. the distribution list.
  1226.  
  1227. RFCs can also be FTPed from SRI-NIC, using the pathname RFC:RFCnnn.TXT,
  1228. where "nnn" is the RFC number; also available is the file
  1229. RFC:RFC-INDEX.TXT, an index to RFCs. See Section 6.1.4 for information on
  1230. ordering hardcopies of RFCs.
  1231.  
  1232.  
  1233. SECTION 5. HARDWARE AND SOFTWARE MODIFICATIONS
  1234.  
  1235. As the ARPANET is an experimental network, there may be occasions when site
  1236. researchers or representatives wish to make temporary or permanent changes
  1237. in the host or node software or hardware. Host software may be modified
  1238. without DDN PMO approval; node software may not. Node equipment is owned
  1239. and managed by the DDN. Any changes require proper paperwork and
  1240. sufficient time to transact.
  1241.  
  1242. NOTE: PSN hardware and software may not be modified without DDN and
  1243. DARPA approval. Requests for such changes must be made through the
  1244. proper administrative channels.
  1245.  
  1246.  
  1247. 5.1 Subscriber Software and Hardware Modification Requests
  1248.  
  1249. Requests for node or backbone software modifications or bug fixes should be
  1250. sent to the ARPANET Monitoring Center (AMC) at BBN Communications
  1251. Corporation (BBNCC; see Section 6.2). BBNCC, acting on behalf of DARPA,
  1252. will prepare a Patch Note and submit it to the DDN Configuration Control
  1253. Group (CCG) for approval. The CCG will evaluate the request, and if
  1254. approved, will forward it to DCA Code B643 for implementation. (See Figure
  1255. 5-1).
  1256.  
  1257.  
  1258.  
  1259.  
  1260.  
  1261.  
  1262.  
  1263. DARPA (info copy)
  1264. /
  1265. User or DARPA Request >--> BBNCC >--> DDN CCG >--> Implementation
  1266.  
  1267.  
  1268. Figure 5-1: Modification Request Procedure
  1269.  
  1270.  
  1271.  
  1272.  
  1273. 5.2 ARPANET Software/Node Modification Procedures
  1274.  
  1275. From time to time patches to, or new versions of, node software are
  1276. released by the DDN PMO. Occasionally these require adjustments to the
  1277. protocol implementations at the host end. In general, official backbone
  1278. program changes that may affect hosts or users will be announced through a
  1279. DDN Management Bulletin (an official online mail notification issued by the
  1280. NIC on behalf of the DDN PMO), and coordinated with site personnel prior to
  1281. implementation by the DDN.
  1282.  
  1283.  
  1284. SECTION 6. NETWORK INFORMATION SERVICES
  1285.  
  1286.  
  1287. 6.1 DDN Network Information Center
  1288.  
  1289. The DDN Network Information Center, located at SRI International, Menlo
  1290. Park, CA, is funded by the DDN PMO to provide general user assistance and
  1291. information services to DDN and ARPANET subscribers and new users.
  1292.  
  1293. NIC personnel work closely with DARPA, DDN, BBNCC, network site
  1294. representatives, network protocol groups, vendors, contractors, government
  1295. agencies, and military sponsors to provide potential subscribers and new
  1296. users with pertinent network information. The NIC also serves as the DDN
  1297. Protocol Repository. Listed below are some of the services provided by the
  1298. NIC that may be of interest to new subscribers.
  1299.  
  1300.  
  1301. 6.1.1 User Assistance Service
  1302.  
  1303. The NIC provides user assistance services by telephone, U.S. mail, and
  1304. electronic mail. NIC staff can answer subscriber questions related to
  1305. connecting a host to the net, or general questions about using the net, and
  1306. can make referrals to the appropriate network representative for
  1307. administrative and technical questions. Additionally, the NIC is the
  1308. source for official ARPANET protocol documents (other than MIL STDs), and
  1309. is the network repository for RFCs and other technical documents.
  1310.  
  1311. The NIC User Assistance "hotline" telephone service is available Monday -
  1312. Friday, 7 am to 4 pm, Pacific time. The number is:
  1313.  
  1314. (800) 235-3155
  1315.  
  1316.  
  1317. 6.1.2 NIC Contacts
  1318.  
  1319. Correspondence may be sent by electronic or U.S. mail to:
  1320.  
  1321. Title Network Mailbox
  1322.  
  1323. User Assistance NIC@SRI-NIC.ARPA
  1324. User Registration, MILNET TAC Access REGISTRAR@SRI-NIC.ARPA
  1325. Network Naming and Addressing HOSTMASTER@SRI-NIC.ARPA
  1326. Feedback SUGGESTIONS@SRI-NIC.ARPA
  1327. Manager, NIC (415) 859-6287 FEINLER@SRI-NIC.ARPA
  1328.  
  1329. U.S. Mail Address
  1330. DDN Network Information Center
  1331. SRI International, Room EJ291
  1332. 333 Ravenswood Avenue
  1333. Menlo Park, CA 94025
  1334.  
  1335.  
  1336. 6.1.3 Online Servers
  1337.  
  1338.  
  1339. 6.1.3.1 TACNEWS
  1340.  
  1341. TACNEWS is a NIC online service that offers login help to TAC users,
  1342. includes the current list of ARPANET and MILNET TAC phone numbers, and
  1343. provides a mechanism for reading the DDN Newsletters and the DDN Management
  1344. Bulletins. Users should read these publications regularly to stay current
  1345. on DDN policies, announcements, and network news items. Access TACNEWS by
  1346. logging into a TAC and typing "@n<Return>" or by using the TELNET service
  1347. to connect to host
  1348. SRI-NIC (10.0.0.51) and typing "tacnews<Return>".
  1349.  
  1350.  
  1351. 6.1.3.2 WHOIS/NICNAME
  1352.  
  1353. WHOIS/NICNAME is a NIC program that provides an electronic "white pages" of
  1354. network users. It lists the name, network mailbox, U.S. mail address,
  1355. telephone number, and host for all registered users.
  1356.  
  1357. This program is available on the SRI-NIC host (10.0.0.51) and can be
  1358. reached by opening a TELNET connection and then by typing "whois<Return>".
  1359.  
  1360. WHOIS/NICNAME may also be run from a local host. WHOIS/NICNAME user
  1361. programs for several operating systems are available from the NIC. Contact
  1362. the NIC for copies and see RFC 954 [6] for details. Note that on most UNIX
  1363. systems the service is invoked by typing "nicname <Return>."
  1364.  
  1365.  
  1366. 6.1.3.3 Host Name Server
  1367.  
  1368. The NIC provides an internet Host Name Server on SRI-NIC (10.0.0.51) port
  1369. 101 decimal. This server delivers machine-translatable host
  1370. name/address/attribute information describing networks, gateways, and hosts
  1371. within the DDN. The server can deliver a single response or the entire
  1372. host table, depending upon the type of query sent. The server provides the
  1373. information outlined in RFC 952 [3] and is itself described in RFC 953
  1374. [10]. For further information on using the Host Name Server, make a TELNET
  1375. connection to SRI-NIC port 101 and type "help<Return>".
  1376.  
  1377.  
  1378. 6.1.4 Documents
  1379.  
  1380. The NIC edits, publishes, and distributes several documents useful to
  1381. ARPANET site representatives and users. Listed here are those of interest
  1382. to new or potential subscribers and users. (See Section 8 for additional
  1383. references.)
  1384.  
  1385. Documents of interest to subscribers:
  1386.  
  1387. DDN PROTOCOL HANDBOOK
  1388.  
  1389. The DDN Protocol Handbook [8] is a three-volume reference set of
  1390. experimental ARPANET and official DoD network protocols together with
  1391. implementation details and related background information. It can be
  1392. ordered prepaid from the NIC for $110.00, or from DTIC.
  1393.  
  1394. NOTE: The NIC publishes the DDN Protocol Handbook as a source
  1395. book for the convenience of implementers and network researchers.
  1396. Individual DoD military standards (MIL STDs) for protocols in
  1397. use on the DDN are officially issued by, and also are available
  1398. from, the Naval Publications and Forms Center, Code 3015, 5801
  1399. Tabor Ave., Philadelphia, PA 19120, (215) 697-3321.
  1400.  
  1401. TCP/IP IMPLEMENTATIONS AND VENDORS GUIDE
  1402.  
  1403. The Vendors Guide lists software and hardware implementations of the
  1404. DDN protocols, based upon information supplied by vendors. It is
  1405. available at no charge from the NIC for information purposes only.
  1406. Entry on this list does not imply endorsement.
  1407.  
  1408. RFCs (hardcopies)
  1409.  
  1410. Requests for Comments or RFCs are a set of network technical notes.
  1411. Hardcopies of RFCs can be ordered from the NIC. There is a $5.00
  1412. copying charge for each RFC under 100 pages, and a $10.00 copying
  1413. charge for each RFC over 100 pages. Orders should be prepaid to the
  1414. NIC.
  1415. Documents of interest to both subscribers and users:
  1416.  
  1417. DDN NEW USER GUIDE
  1418.  
  1419. The DDN New User Guide [12] is a brief guide to DDN network tools and
  1420. services designed to introduce users to the network. Available from
  1421. the NIC or DTIC.
  1422.  
  1423. DDN DIRECTORY
  1424.  
  1425. The DDN Directory [11] is a directory of users and hosts on the
  1426. network. It includes the name, address, network mailbox, and
  1427. telephone number for each registered network user (as of 1984).
  1428. Available for $10.00 prepaid to SRI International, DDN Network
  1429. Information Center, Room EJ291, Menlo Park, CA 94025, or from the
  1430. Defense Technical Information Center (DTIC).
  1431.  
  1432.  
  1433. 6.1.5 Online Files
  1434.  
  1435. The NIC maintains a number of online files which are available to network
  1436. subscribers via the ARPANET. These files contain information about
  1437. protocols, site personnel, hosts, and other subjects relevant to network
  1438. users. For more information on available public-access files, see the DDN
  1439. New User Guide [12], or contact the NIC User Assistance service.
  1440.  
  1441.  
  1442. 6.2 ARPANET Network Monitoring Center
  1443.  
  1444. The ARPANET Network Monitoring Center (AMC) is located within the Network
  1445. Operations Situation Room at BBN Communications Corporation (BBNCC) in
  1446. Cambridge, MA. AMC staff provide operations support for the ARPANET. The
  1447. AMC concentrates on real-time network management of the ARPANET by
  1448. maximizing the network operating efficiency. It provides:
  1449.  
  1450. - Operations and technical support
  1451.  
  1452. - Configuration management and software maintenance and enhancement
  1453.  
  1454. - Hardware maintenance
  1455.  
  1456. - Hardware requirements
  1457.  
  1458. - Network experiments.
  1459.  
  1460. AMC services include remote status monitoring, coordination of network
  1461. outage troubleshooting efforts, and 24-hour-per-day/7-day-per-week
  1462. technical assistance for network users. The AMC typically works on
  1463. backbone-related outages consisting of node and circuit problems, and
  1464. provides help in determining whether or not host connectivity problems are
  1465. network-related.
  1466.  
  1467. Contact the AMC for all network hardware problems, for hardware field
  1468. service, problems with host interfaces, or suspected node software
  1469. problems. Inform the AMC of any extended outages at your site, especially
  1470. those that may affect the PSN, and consult with them before carrying out
  1471. any experiment that may affect the network.
  1472.  
  1473. Users are encouraged to telephone the AMC rather than send electronic mail,
  1474. as this assures that the AMC will get all the necessary information, and
  1475. usually produces a faster response. (Note, however, that all orders for
  1476. backbone service must originate from the PMO.)
  1477.  
  1478. NOTE: The AMC will accept collect calls to (617) 661-0100.
  1479.  
  1480.  
  1481. 6.2.1 AMC Contacts
  1482.  
  1483. Title Telephone Network Mailbox
  1484.  
  1485. Network Monitoring Center (617) 661-0100 CONTROL@BBN-UNIX.ARPA
  1486. (617) 497-3571*
  1487. New Subscriber Liaison (617) 497-2633* DIPANFILO@BBN-UNIX.ARPA
  1488. Manager, NOC (617) 497-3117* JBURKE@BBN-UNIX.ARPA
  1489. * Now exchange 873 (May 89)
  1490.  
  1491.  
  1492. 6.3 Complaint Center/Unsatisfactory Service Reports
  1493.  
  1494. A complaint center terminal is maintained at the AMC to monitor messages
  1495. from users reporting problems or seeking assistance. (Send electronic mail
  1496. to GRIPES@BBN-UNIX.ARPA.) An additional channel for reporting
  1497. unsatisfactory service is the ARPANET Unsatisfactory Service Report (USR),
  1498. which is the formal mechanism for reporting operational deficiencies in the
  1499. ARPANET backbone. Problems or complaints which cannot be resolved through
  1500. normal channels should be reported by means of the USR. This may include
  1501. (but is not limited to) the following:
  1502.  
  1503. - Excessive response time
  1504.  
  1505. - Inadequate restoral procedures
  1506.  
  1507. - Unsatisfactory maintenance support.
  1508.  
  1509. The Subscriber must decide when service has reached an unsatisfactory
  1510. point, and must initiate the USR if the problem cannot be resolved. Send
  1511. the report online or by U.S. mail (see 7.1 for address) to DCA Code B652,
  1512. with information copies to the AMC (BBNCC) and any other activity deemed
  1513. appropriate by the originator.
  1514.  
  1515.  
  1516. SECTION 7. KEY CONTACTS
  1517.  
  1518.  
  1519. 7.1 DDN PMO Contacts
  1520.  
  1521. Code Title Telephone* Network Mailbox
  1522.  
  1523. B652 ARPANET POC 285-5233 ARPANETMGR@DDN1.ARPA
  1524. B600 Program Manager 285-5010 DCAB600@DDN1.ARPA
  1525. B641 Subscriber Requirements &
  1526. Integration Branch 285-5027 DCAB641@DDN1.ARPA
  1527. B602B Data Base and
  1528. Configuration Mgt. Branch 285-5017 DCAB602B@DDN1.ARPA
  1529. B652 Packet Switch Operations Branch 285-5225 DCAB652@DDN1.ARPA
  1530.  
  1531. [* Area Code (703), Autovon 356-xxxx]
  1532.  
  1533. Postal Mail: Defense Communications Agency
  1534. B652, Packet Switch Operations Branch
  1535. Washington, DC 20305
  1536. 7.2 DARPA Contacts
  1537.  
  1538. Title Telephone Network Mailbox
  1539.  
  1540. ARPANET COORDINATOR (202) 694-5921 BOWERS@USC-ISI.ARPA
  1541. DARPA POC (202) 694-3049 BAKER@USC-ISI.ARPA
  1542. Internet Advisory Board (202) 694-4002 PERRY@IPTO.ARPA
  1543. (617) 253-6003 DCLARK@MIT-MULTICS.ARPA
  1544. (213) 822-1511 POSTEL@USC-ISIF.ARPA
  1545. (703) 883-6000 CPERRY@MITRE.ARPA
  1546.  
  1547. Postal Mail: Defense Advanced Research Projects Agency
  1548. Information Processing Techniques Office
  1549. Attn: Lt. Col. Bob E. Baker
  1550. 1400 Wilson Boulevard
  1551. Arlington, VA 22209-2389
  1552.  
  1553. 7.3 Contacts for Specific Services
  1554.  
  1555. Telephone Network Mailbox
  1556.  
  1557. ARPANET Access Authorization (202) 694-3049 BAKER@USC-ISI.ARPA
  1558. ARPANET TAC Access Administration (202) 694-3049 BAKER@USC-ISI.ARPA
  1559. ARPANET New TAC Requests (202) 694-3049 BAKER@USC-ISI.ARPA
  1560. ARPANET Policy and Administration (202) 694-5050 KIGGENS@IPTO.ARPA
  1561. Backbone Equipment Information (617) 497-2633* DIPANFILO@BBN-UNIX.ARPA
  1562. Backbone Installation Schedule (703) 285-5231 ARPANETMGR@DDN1.ARPA
  1563. ARPANET Service Requests (202) 694-5921 BOWERS@USC-ISI.ARPA
  1564. General ARPANET Mgt. Information (703) 285-5233 ARPANETMGR@DDN1.ARPA
  1565. General ARPANET Information (800) 235-3155 NIC@SRI-NIC.ARPA
  1566. Node Problems (617) 661-0100 CONTROL@BBN-UNIX.ARPA
  1567. 8 Now 873-2633 (May 89)
  1568.  
  1569. SECTION 8. REFERENCES
  1570.  
  1571. Below is a bibliography of manuals and documents that are mentioned in this
  1572. document and are helpful in understanding the ARPANET and DDN. The
  1573. ordering number is given, when known, for items that may be ordered from
  1574. the Defense Technical Information Center (DTIC).
  1575.  
  1576. Documents marked (NIC) are available in hardcopy from the NIC; documents
  1577. marked (PMO) are available from the DDN PMO. Files available online at the
  1578. NIC (host SRI-NIC, 10.0.0.51) are indicated by giving the pathname in the
  1579. form [DIRECTORY:FILENAME.EXTENSION]. These files may be copied across the
  1580. network by using the File Transfer Protocol program (FTP). Call the NIC if
  1581. you need assistance with FTP.
  1582.  
  1583.  
  1584.  
  1585. 8.1 Cited References
  1586.  
  1587. [1] DDN Subscriber Interface Guide. Defense Data Network, Program
  1588. Management Office, Defense Communications Agency, Washington, DC,
  1589. 1983. (NIC) [AD-A132 877/2]
  1590.  
  1591. [2] RFC 796, Address Mappings. University of Southern California,
  1592. Information Sciences Institute, Marina del Rey, CA, September 1981.
  1593. (NIC) [RFC:RFC796.TXT]
  1594.  
  1595. [3] RFC 952, DoD Internet Host Table. SRI International, Menlo Park, CA,
  1596. October 1985. (NIC) [RFC:RFC952.TXT]
  1597.  
  1598. [4] RFC 920, Domain Requirements. University of Southern California,
  1599. Information Sciences Institute, Marina del Rey, CA, October 1984.
  1600. (NIC) [RFC:RFC920.TXT]
  1601.  
  1602. [5] RFC 921, Domain Name System Implementation Schedule - Revised.
  1603. University of Southern California, Information Sciences Institute,
  1604. Marina del Rey, CA, October 1984. (NIC) [RFC:RFC921.TXT]
  1605.  
  1606. [6] RFC 954, NICNAME/WHOIS. SRI International, Menlo Park, CA, October
  1607. 1985. (NIC) [RFC:RFC954.TXT]
  1608.  
  1609. [7] ARPANET Access Control, User Manual for the User Database Tool.
  1610. Defense Advanced Research Projects Agency, Arlington, VA, July 1984.
  1611. (NIC) [NETINFO:ARPA-TACACS.MAN]
  1612.  
  1613. [8] DDN Protocol Handbook. DDN Network Information Center, SRI
  1614. International, Menlo Park, CA, November 1985. (NIC, $110.00 domestic,
  1615. $130.00 overseas, prepaid)
  1616.  
  1617. [9] TCP/IP Implementations and Vendors Guide. DDN Network Information
  1618. Center, SRI International, Menlo Park, CA, 1985. (NIC) [NETINFO:TCP-
  1619. IP-IMPLEMENTATIONS.TXT]
  1620.  
  1621. [10] RFC 953, Hostnames Server. SRI International, Menlo Park, CA, October
  1622. 1985. (NIC) [RFC:RFC953.TXT]
  1623.  
  1624. [11] DDN Directory. DDN Network Information Center, SRI International,
  1625. Menlo Park, CA, 1984. (NIC, $10.00 prepaid) [AD-A148 213]
  1626.  
  1627. [12] DDN New User Guide. DDN Network Information Center, SRI
  1628. International, Menlo Park, CA, 1985. (NIC)
  1629.  
  1630.  
  1631.  
  1632. 8.2 Additional References
  1633.  
  1634. ARPANET Access Control, User Guide for the User Database Tool. Defense
  1635. Advanced Research Projects Agency, Arlington, VA, July 1984. (NIC)
  1636. [NETINFO:ARPA-TACACS.GUIDE]
  1637.  
  1638. Assigned Numbers, Information Sciences Institute, University of Southern
  1639. California, Marina del Rey, CA. (NIC) [RFC:ASSIGNED-NUMBERS.TXT]
  1640.  
  1641. DDN Defense Data Network Brochure. Defense Data Network, Program
  1642. Management Office, Defense Communications Agency, Washington, DC, 1984.
  1643. (NIC) (PMO)
  1644.  
  1645. DDN Subscriber Security Guide. Defense Data Network, Program Management
  1646. Office, Defense Communications Agency, Washington, DC, 1983. (NIC)
  1647. [AD-A152 524]
  1648.  
  1649. DDN User's Planning Guide. Defense Data Network, Program Management
  1650. Office, Defense Communications Agency, Washington, DC, 1985. (PMO)
  1651.  
  1652. DDN X.25 Host Interface Specification. Defense Data Network, Program
  1653. Management Office, Defense Communications Agency, Washington, DC, 1983.
  1654. (NIC) [NETINFO:X25.DOC] [AD-A137 427]
  1655.  
  1656. A HISTORY OF THE ARPANET: THE FIRST DECADE, Report No. 4799. Bolt Beranek
  1657. and Newman Inc., Cambridge, MA, 1981. [AD-A115-440]
  1658.  
  1659. Instructions for Network User Registration Drive (MILNET). DDN Network
  1660. Information Center, SRI International, Menlo Park, CA, October 1983. (NIC)
  1661. [NETINFO:MIL-TACACS-INSTRUCTIONS.TXT]
  1662.  
  1663. Submission of Telecommunications Service Requests, DCA Circular 310-130-1.
  1664. Defense Communications Agency, Washington, DC, 1983. (PMO)
  1665.  
  1666. TAC Users' Guide, Report No. 4780. Bolt Beranek and Newman Inc.,
  1667. Cambridge, MA, 1982. (NIC) [NETINFO:TAC-USER.DOC] [AD-A147 366]
  1668.  
  1669.  
  1670. SECTION 9. GLOSSARY
  1671.  
  1672.  
  1673. Listed here are terms and acronyms used in this document. Definitions are
  1674. given for terms, whereas organizational acronyms are generally just
  1675. expanded to their full length.
  1676.  
  1677. AMC ARPANET Network Monitoring Center, located at BBNCC,
  1678. Cambridge, MA.
  1679.  
  1680. ARPA see DARPA.
  1681.  
  1682. ARPANET DARPA's packet-switched host-to-host digital
  1683. communications network which links a wide variety of
  1684. DoD-sponsored computers at research centers around the
  1685. world.
  1686.  
  1687. BBNCC Bolt Beranek and Newman Communications Corporation; the
  1688. company that provides network node hardware, software and
  1689. field servicing, and manages the ARPANET Network
  1690. Monitoring Center. Early contributor to the development
  1691. of the DDN.
  1692.  
  1693. backbone The nodes (see below) and the leased telephone lines and
  1694. satellites connecting them, which form the core of the
  1695. DDN.
  1696.  
  1697. CCG DCA Configuration Control Group, the group which screens
  1698. and approves changes to the backbone configuration as
  1699. needed.
  1700.  
  1701. DARPA Defense Advanced Research Projects Agency.
  1702.  
  1703. DCA Defense Communications Agency.
  1704.  
  1705. DCEC Defense Communications Engineering Center.
  1706.  
  1707. DDN Defense Data Network; the DoD's host-to-host, packet-
  1708. switched data communications network. The DDN
  1709. interconnects several military networks, one of which is
  1710. the ARPANET.
  1711.  
  1712. DDN PMO Defense Data Network Program Management Office; the
  1713. office within the DCA responsible for management of the
  1714. DDN.
  1715.  
  1716. DECCO Defense Commercial Communications Office.
  1717.  
  1718. DoD Department of Defense.
  1719.  
  1720. Feeder TSR Preliminary Telecommunications Service Request (TSR) used
  1721. by DARPA to request ARPANET service from the DDN PMO.
  1722.  
  1723. FTP File Transfer Protocol; the network protocol that allows
  1724. host-to-host file transfer across the network without
  1725. disrupting the format of the file being transferred.
  1726.  
  1727. gateway A special computer which interconnects two networks,
  1728. performs any needed protocol conversion or address
  1729. translation, and administers access control between them.
  1730.  
  1731. HAdmin Host Administrator; see Appendix for a list of Host
  1732. Administrator duties.
  1733.  
  1734. HAF Host Approved Form provided by DARPA IPTO.
  1735.  
  1736. host Computer directly connected to a PSN port on the DDN.
  1737.  
  1738. HOSTMASTER Mailbox at the NIC for host registration, name, address,
  1739. and other changes to information in the DDN host table.
  1740.  
  1741. hostname Name which officially identifies a host computer attached
  1742. to the DDN.
  1743.  
  1744. IMP Interface Message Processor; now called Packet Switch
  1745. Node or PSN, which see.
  1746.  
  1747. INCO INstallation Check Out kits; containers of node spare
  1748. parts.
  1749.  
  1750. Internet Protocol Standard that allows Internet networks running different
  1751. protocols to connect and communicate with each other.
  1752.  
  1753. IPTO Information Processing Techniques Office; the DARPA
  1754. office that administers and sets policy for the ARPANET.
  1755.  
  1756. ISI University of Southern California Information Sciences
  1757. Institute.
  1758.  
  1759. LAN Local Area Network; a private network that connects data
  1760. processing equipment in a limited geographic area (e.g.
  1761. an office, building, or complex of buildings).
  1762.  
  1763. M/A-COM M/A-COM Linkabit, Incorporated.
  1764.  
  1765. MIT Massachusetts Institute of Technology.
  1766.  
  1767. MIL-STD Military Standard; the specification for a standard
  1768. (including network protocols) that is to be implemented
  1769. for a military system or as a product used by the DoD.
  1770.  
  1771. MILNET Unclassified operational MILitary NETwork, which is part
  1772. of the DDN.
  1773.  
  1774. MITRE MITRE Corporation.
  1775.  
  1776. NCAN Network Change Acknowledgement Notice.
  1777.  
  1778. NCD Network Change Directive.
  1779.  
  1780. NCR Network Change Request.
  1781.  
  1782. NIC Network Information Center located at SRI International,
  1783. Menlo Park, CA, under contract to the DDN PMO.
  1784.  
  1785. node Packet switch; a PSN, TAC, mail bridge, or combination of
  1786. these.
  1787.  
  1788. NSC Node Site Coordinator; local DDN representative assigned
  1789. to a TAC or PSN who is responsible for access control and
  1790. accountability for all DDN-owned hardware, software and
  1791. circuits located at the node site. (See Appendix for a
  1792. list of NSC duties).
  1793.  
  1794. OSD Office of the Secretary of Defense.
  1795.  
  1796. PDC Program Designator Code; code used to identify the
  1797. funding activity responsible for reimbursing the cost of
  1798. backbone charges.
  1799.  
  1800. PMO Program Management Office of the DDN.
  1801.  
  1802. POC Point Of Contact.
  1803.  
  1804. PSN Packet Switch Node; a store-and-forward packet switch to
  1805. which several host computers can be connected.
  1806.  
  1807. REGISTRAR Mailbox at the NIC for user registration, name, address,
  1808. and other changes to information in the registration
  1809. (WHOIS) database.
  1810.  
  1811. RFC Requests For Comments; a set of technical notes
  1812. describing networking research carried out by the DARPA
  1813. network community (available from the NIC).
  1814.  
  1815. RP Responsible Person; person appointed by DARPA to register
  1816. ARPANET TAC users in a particular organization.
  1817.  
  1818. site Organization or facility where host or node equipment is
  1819. located.
  1820.  
  1821. SMTP Simple Mail Transfer Protocol; the official DoD mail
  1822. protocol.
  1823.  
  1824. socket Logical address of a port providing access to a specific
  1825. device or service on a host.
  1826.  
  1827. SRI-NIC The DDN Network Information Center host computer, located
  1828. at SRI International, Menlo Park, CA. This host is
  1829. multi-homed on both the ARPANET and the MILNET, and
  1830. provides information services to both.
  1831.  
  1832. SRI SRI International; location of the DDN Network
  1833. Information Center and early contributor to the
  1834. development of the ARPANET and the DDN.
  1835.  
  1836. subscriber A system connected to the ARPANET, and the individuals
  1837. responsible for that system.
  1838.  
  1839. TAC Terminal Access Controller; a special host attached to a
  1840. PSN that lets terminals connect directly to the DDN.
  1841.  
  1842. TAC Access Code Password assigned to TAC users for TAC login.
  1843.  
  1844. TAC USER ID Alphanumeric character string that identifies a TAC user
  1845. upon TAC login.
  1846.  
  1847. TCP/IP Transmission Control Protocol/Internet Protocol; two of
  1848. the DoD standard network protocols.
  1849.  
  1850. TELCO Telephone company.
  1851.  
  1852. TELNET DoD protocol for opening a transparent (virtual terminal)
  1853. connection from one host to another. Also refers to the
  1854. program implementation that provides this service.
  1855.  
  1856. TIP Terminal Interface Processor; predecessor of the TAC,
  1857. serving a similar function.
  1858.  
  1859. TSO Telecommunications Service Order; DCA authorization to
  1860. start, change, or discontinue circuits or trunks.
  1861.  
  1862. TSR Telecommunications Service Request; a valid, approved and
  1863. funded telecommunications service requirement submitted
  1864. by DCA through DECCO to the telephone companies.
  1865.  
  1866. UCL University College London, England.
  1867.  
  1868. UCLA University of California, Los Angeles.
  1869.  
  1870. UDB User Database Tool for registering ARPANET users for TAC
  1871. Access.
  1872.  
  1873. USR Unsatisfactory Service Report; report sent to the DDN PMO
  1874. by a network subscriber to report unsatisfactory network
  1875. service.
  1876.  
  1877.  
  1878. APPENDIX. SITE PERSONNEL DUTIES
  1879.  
  1880. This appendix describes the duties of ARPANET personnel at host and node
  1881. locations.
  1882.  
  1883. 1. Responsible Person
  1884.  
  1885. The person in a particular organization appointed by DARPA who has
  1886. authority to give ARPANET users permission for TAC access is called a
  1887. Responsible Person (RP). RP's are representatives of organizations
  1888. involved in DARPA research programs.
  1889.  
  1890. Responsibilities:
  1891.  
  1892. a. For ARPANET TAC Access, a \Responsible Person" has been
  1893. identified in each government and contractor organization whose
  1894. members need to use ARPANET TACs. The Responsible Person grants
  1895. permission to use an APRANET TAC to members of his or her
  1896. organization by updating the ARPANET user database (which is
  1897. different from the NIC User Registration database). A \User
  1898. Database Tool" is used by the Responsible Persons or their
  1899. designated alternates to add, delete, and change information
  1900. describing authorized ARPANET TAC users.
  1901.  
  1902. b. The motivation for the organization-oriented approach to
  1903. authorization of TAC usage is to put the authorization in the
  1904. hands of the people best able to validate the requirement for
  1905. access. The \Responsible Persons" must make sure that TAC
  1906. access is granted only to people who are authorized to use the
  1907. ARPANET, and that such access conforms to guidelines on the
  1908. purpose of the ARPANET and the proper use of ARPANET TACs.
  1909.  
  1910. 2. Host Administrator
  1911.  
  1912. The Host Administrator (HAdmin) has administrative responsibility for the
  1913. policies, practices, and concerns of a host or hosts connected to the DDN,
  1914. including responsibility for that host's DDN users.
  1915.  
  1916. Responsibilities:
  1917.  
  1918. a. Assists the DDN PMO by ensuring that network policies and
  1919. procedures are observed by the users. Ensures that all of his
  1920. or her host users, who are using the network or the network
  1921. TACs, have been authorized for ARPANET access and are registered
  1922. in the NIC User Registration database.
  1923.  
  1924. b. Manages the network access control procedures and password
  1925. system, and is responsible for reporting network-related host
  1926. break-ins and assisting with investigative effort as needed.
  1927.  
  1928. c. Coordinates with the DDN PMO on installation and removal of
  1929. hosts on the DDN; and also coordinates installation of, or
  1930. changes to, host software that has direct or indirect impact on
  1931. the DDN. The HAdmin provides the DDN PMO and the NIC with
  1932. required descriptive information for each new host addition or
  1933. host change, and coordinates the host certification procedure
  1934. with the DDN PMO prior to passing traffic on the network. The
  1935. HAdmin is responsible for the proper implementation and
  1936. maintenance of DDN protocols at the host level.
  1937.  
  1938. d. Serves as local point of contact for his or her respective hosts
  1939. and local users and coordinates suspected network-related
  1940. problems directly with the network monitoring center.
  1941.  
  1942. e. Provides network information to the NIC, and assists local users
  1943. and other interested personnel with network-related matters.
  1944.  
  1945. 3. Node Site Coordinator
  1946.  
  1947. The Node Site Coordinator is designated as having site access control, DDN
  1948. hardware and software accountability, and coordination responsibility for
  1949. the DDN circuits and equipment located at the DDN Node Site.
  1950.  
  1951. Responsibilities:
  1952.  
  1953. a. Directly interacts with DDN management channels and the network
  1954. monitoring center on network communications operational matters.
  1955.  
  1956. b. Provides the node site's single point of contact for network
  1957. backbone matters. (Delegation of responsibilities to
  1958. individuals within the node site is the NSC's prerogative,
  1959. however, the NSC is still that node site's single point of
  1960. contact for network backbone matters).
  1961.  
  1962. c. Accountable for DDN node hardware and software (cassette tapes).
  1963.  
  1964. d. Authorizes and ensures personnel access to the node site.
  1965.  
  1966. e. Supervises, assists, coordinates or monitors the installation
  1967. and implementation of node hardware, software, and circuits.
  1968.  
  1969. f. Performs administrative functions, as required.
  1970.  
  1971. g. Ensures the node site has a single place of contact for the DDN
  1972. or its representatives to obtain local site assistance on a
  1973. 24-hour, 7-day a week basis, when required. (In the isolated
  1974. case that the node site is located in a facility that is not
  1975. manned on a 24-hour, 7-day a week basis, the NSC ensures that
  1976. someone at the place of contact can obtain local site assistance
  1977. within two hours).
  1978.  
  1979. h. Provides for accountability and access control of the PSN/TAC
  1980. system cassette tapes (IMPLOD and SYSTEM).
  1981.  
  1982. i. Provides for custodial care of the on-site container(s) of node
  1983. spare parts, known as INCO (INstallation Check Out) kits.
  1984. (Normally, these kits are located at selected overseas sites).
  1985.  
  1986. j. Provides site coordination and authorizes personnel with site
  1987. access for installation, removal, and modifications to DDN
  1988. hardware or circuits, for emergency or scheduled preventive
  1989. maintenance, as directed by DCA or the designated network
  1990. monitoring center.
  1991.  
  1992. k. Ensures that local site assistance is provided, when required by
  1993. the network monitoring center, for corrective actions during
  1994. node hardware or circuit degradation or outages, which are
  1995. beyond the capability of the network monitoring center to
  1996. correct. For instance, on instruction from the network
  1997. monitoring center due to PSN or circuit failure, the local site
  1998. representative may be requested to press reset buttons on the
  1999. back of PSN/TAC chassis, observe status lights, insert/remove
  2000. the tape cassette (normally always in reader), switch cables,
  2001. loop modems (normally on TAC connections), loop modems on
  2002. covered circuits in selected locations or coordinate restoration
  2003. actions with local field-site communications
  2004. technicians/organizations.
  2005.  
  2006. l. Ensures that DDN hardware, software, or circuits are not
  2007. altered, moved or tampered with, without proper authorization.
  2008.  
  2009. m. Monitors investigative reports related to DDN hardware and
  2010. software located at the node site.
  2011.  
  2012. n. Performs limited administrative functions such as: (1)
  2013. maintaining and being aware of operating instructions issued by
  2014. DCA, the Network Information Center (NIC) on behalf of the DDN
  2015. PMO, and the network monitoring center; (2) maintaining a
  2016. contact list of telephone numbers for the local TELCO service
  2017. office or DCS technical control, network monitoring center, and
  2018. the Host Administrator for each host connected to the DDN PSN(s)
  2019. at that node site; (3) maintaining a \Node Site Access Roster,"
  2020. which lists all personnel authorized to have access to the node
  2021. site and associated equipment.
  2022.  
  2023. INDEX
  2024.  
  2025. Access controls
  2026. host 4
  2027. TAC 4
  2028. AMC 15
  2029. ARPANET
  2030. access and use 4
  2031. description 3
  2032. ARPANET Network Monitoring Center
  2033. collect calls 15
  2034. description 15
  2035. telephone numbers 15
  2036.  
  2037. Bug fixes 11
  2038.  
  2039. CCG 11, 21
  2040. Complaints
  2041. Unsatisfactory Service Reports
  2042. 15
  2043. Configuration Control Group 11
  2044. Costs 6
  2045.  
  2046. DARPA
  2047. addresses and phone numbers
  2048. 17
  2049. mailing address 6
  2050. DARPA IPTO
  2051. mission 3
  2052. responsibilities 3
  2053. DCA
  2054. description 3
  2055. DDN PMO 3
  2056. responsibilities 3
  2057. DDN 3
  2058. Directory 15
  2059. Network Information Center
  2060. 13
  2061. New User Guide 15
  2062. Protocol Handbook 14
  2063. DDN Network Information Center
  2064. 13
  2065. toll free number 13
  2066. DDN PMO
  2067. contacts 17
  2068. mailing address 6
  2069. Defense Communications Agency 3
  2070. Domains 7
  2071.  
  2072. Feeder TSR 6
  2073.  
  2074. Gateway registration 7
  2075.  
  2076. HAF 5
  2077. Host address 7
  2078. Host Administrator
  2079. duties 23
  2080. Host Name Server 14
  2081. function 7
  2082. Host table
  2083. updating 7
  2084.  
  2085. IAB
  2086. responsibilities 3
  2087. task forces 3
  2088. Information Processing Techniques
  2089. Office
  2090. see also IPTO 3
  2091. Internet Research Program
  2092. 3
  2093. IPTO
  2094. mission 3
  2095. responsibilities 3, 5
  2096.  
  2097. Local Area Networks 7
  2098.  
  2099. MIL STD 9
  2100. MILNET 3
  2101.  
  2102. Naming domains 7
  2103. NCD
  2104. 5
  2105. confirmation 5
  2106. NCR
  2107. generation of 5
  2108. Network Monitoring Center 15
  2109. Network Operations Center
  2110. telephone numbers 15
  2111. NIC
  2112. getting Host tables from 7
  2113. Node
  2114. installation 5
  2115. problems 15
  2116. software modifications 11
  2117. Node Site Coordinator
  2118. duties 23
  2119. requirement for 5
  2120. NSC
  2121. requirement for 5
  2122.  
  2123. Protocols
  2124. ARPANET 9
  2125. documentation 9
  2126. Internet 9
  2127. vendors 9
  2128. PSN
  2129. modifications 11
  2130. port assignment 7
  2131. port changes 7
  2132. relation to network number 7
  2133.  
  2134. REGISTER 8
  2135. Registration template
  2136. user 7
  2137. Registration 7
  2138. host 7
  2139. TAC access 8
  2140. user 7
  2141. user - REGISTER 8
  2142. user - template 7
  2143. Registration template
  2144. host 7
  2145. Host Administrator 7
  2146. Registration template,
  2147. user 7
  2148. Request For Comments 9
  2149. Responsible Person 4
  2150. duties 23
  2151. RFC
  2152. hardcopies 14
  2153.  
  2154. Software modifications 11
  2155. Subscriber access
  2156. time required 5
  2157. Subscriber access procedures 5
  2158.  
  2159. TAC 4
  2160. TACNEWS 14
  2161. TCP/IP
  2162. Implementations and Vendors
  2163. Guide 14
  2164. Telephone numbers 17
  2165. Terminal connection 7
  2166. TSO
  2167. function 5
  2168. receipt of 5
  2169. TSR
  2170. function 5
  2171. obtaining 5
  2172. submission 5
  2173.  
  2174. UDB
  2175. registration 8
  2176. Unsatisfactory Service Reports
  2177. 15
  2178. User Data Base
  2179. ARPANET 4
  2180. User Data Base
  2181. registration 8
  2182.  
  2183. Vendors Guide
  2184. TCP/IP 14
  2185.  
  2186. WHOIS/NICNAME 14P
  2187.  
  2188.  
  2189.  
  2190.  
  2191.  
  2192.  
  2193.  
  2194.  
  2195.  
  2196.  
  2197.  
  2198.  
  2199.  
  2200.  
  2201.  
  2202. ARPANET INFORMATION BROCHURE
  2203.  
  2204.  
  2205.  
  2206. DECEMBER 1985
  2207.  
  2208.  
  2209.  
  2210.  
  2211.  
  2212.  
  2213.  
  2214.  
  2215.  
  2216.  
  2217.  
  2218.  
  2219.  
  2220.  
  2221.  
  2222.  
  2223.  
  2224.  
  2225.  
  2226. ARPANET INFORMATION BROCHURE
  2227.  
  2228.  
  2229.  
  2230.  
  2231. DECEMBER 1985
  2232.  
  2233.  
  2234.  
  2235. Editor:
  2236. Stephen C. Dennett
  2237. Elizabeth J. Feinler
  2238. Francine Perillo
  2239.  
  2240.  
  2241.  
  2242.  
  2243.  
  2244.  
  2245.  
  2246. Additional copies of this document may be obtained from the DDN Network
  2247. Information Center, SRI International, 333 Ravenswood Avenue, Room EJ291,
  2248. Menlo Park, CA 94025, or from the Defense Technical Information Center
  2249. (DTIC), Cameron Station, Alexandria, VA 22314.
  2250.  
  2251.  
  2252.  
  2253.  
  2254.  
  2255.  
  2256.  
  2257.  
  2258.  
  2259.  
  2260.  
  2261.  
  2262.  
  2263.  
  2264.  
  2265.  
  2266.  
  2267.  
  2268.  
  2269.  
  2270.  
  2271.  
  2272.  
  2273. ---------------------------------------------------------------------------
  2274. UNIX is a registered trademark of AT&T Bell Laboratories. TELENET is a
  2275. registered trademark of GTE. TYMNET is a registered trademark of TYMNET
  2276. Inc., a subsidiary of McDonnell Douglas Corporation.
  2277. ---------------------------------------------------------------------------
  2278.  
  2279.  
  2280.  
  2281.  
  2282.  
  2283.  
  2284. ARPANET Information Brochure. Printed and bound in the United States of
  2285. America. Published by the DDN Network Information Center, SRI
  2286. International, Menlo Park, CA 94025.
  2287.  
  2288.  
  2289.  
  2290. Date: December 1985
  2291.  
  2292. TABLE OF CONTENTS
  2293.  
  2294.  
  2295.  
  2296.  
  2297.  
  2298. ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . III
  2299.  
  2300. ABSTRACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V
  2301.  
  2302. SECTION 1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 1
  2303. 1.1. How To Use This Document . . . . . . . . . . . . . . 1
  2304.  
  2305. SECTION 2. ARPANET MANAGEMENT AND POLICIES . . . . . . . . . . . . 3
  2306. 2.1. What is the ARPANET? . . . . . . . . . . . . . . . . 3
  2307. 2.2. Management of the ARPANET . . . . . . . . . . . . . 3
  2308. 2.2.1. DARPA/IPTO . . . . . . . . . . . . . . . . . . . . 3
  2309. 2.2.2. DDN PMO Responsibilities . . . . . . . . . . . . . 3
  2310. 2.2.3. IAB Responsibilities . . . . . . . . . . . . . . . 3
  2311. 2.3. ARPANET Access and Use Policies . . . . . . . . . . 4
  2312. 2.3.1. Host Access Controls . . . . . . . . . . . . . . . 4
  2313. 2.3.2. TAC Access Controls . . . . . . . . . . . . . . . 4
  2314.  
  2315. SECTION 3. SUBSCRIBER ACCESS PROCEDURES . . . . . . . . . . . . . . 5
  2316. 3.1. Process Overview . . . . . . . . . . . . . . . . . . 5
  2317. 3.1.1. Feeder TSRs . . . . . . . . . . . . . . . . . . . 6
  2318. 3.2. Backbone Hardware Requirements . . . . . . . . . . . 6
  2319. 3.2.1. Types of Service . . . . . . . . . . . . . . . . . 6
  2320. 3.2.2. Equipment Procurement and Costs . . . . . . . . . 6
  2321. 3.2.3. PSN Port Assignment . . . . . . . . . . . . . . . 7
  2322. 3.3. TAC Connection . . . . . . . . . . . . . . . . . . . 7
  2323. 3.4. Registration Procedures . . . . . . . . . . . . . . 7
  2324. 3.4.1. Host Registration . . . . . . . . . . . . . . . . 7
  2325. 3.4.2. Host Addresses and Domains . . . . . . . . . . . . 7
  2326. 3.4.3. LAN and Gateway Registration . . . . . . . . . . . 7
  2327. 3.4.4. User Registration . . . . . . . . . . . . . . . . 7
  2328. 3.4.4.1. NIC Registration Template . . . . . . . . . . . 7
  2329. 3.4.4.2. NIC REGISTER Program . . . . . . . . . . . . . . 8
  2330. 3.4.5. ARPANET TAC Access Registration . . . . . . . . . 8
  2331.  
  2332. SECTION 4. ARPANET PROTOCOLS . . . . . . . . . . . . . . . . . . . 9
  2333. 4.1. DDN Protocol Handbook . . . . . . . . . . . . . . . 9
  2334. 4.2. TCP/IP Implementations and Vendors Guide . . . . . . 9
  2335. 4.3. RFCs . . . . . . . . . . . . . . . . . . . . . . . . 9
  2336.  
  2337. SECTION 5. HARDWARE AND SOFTWARE MODIFICATIONS . . . . . . . . . . 11
  2338. 5.1. Subscriber Software and Hardware Modification
  2339. Requests 11
  2340. 5.2. ARPANET Software/Node Modification Procedures . . . 11
  2341.  
  2342. SECTION 6. NETWORK INFORMATION SERVICES . . . . . . . . . . . . . . 13
  2343. 6.1. DDN Network Information Center . . . . . . . . . . . 13
  2344. 6.1.1. User Assistance Service . . . . . . . . . . . . . 13
  2345. 6.1.2. NIC Contacts . . . . . . . . . . . . . . . . . . . 14
  2346. 6.1.3. Online Servers . . . . . . . . . . . . . . . . . . 14
  2347. 6.1.3.1. TACNEWS . . . . . . . . . . . . . . . . . . . . 14
  2348. 6.1.3.2. WHOIS/NICNAME . . . . . . . . . . . . . . . . . 14
  2349. 6.1.3.3. Host Name Server . . . . . . . . . . . . . . . . 14
  2350. 6.1.4. Documents . . . . . . . . . . . . . . . . . . . . 14
  2351. 6.1.5. Online Files . . . . . . . . . . . . . . . . . . . 15
  2352. 6.2. ARPANET Network Monitoring Center . . . . . . . . . 15
  2353. 6.2.1. AMC Contacts . . . . . . . . . . . . . . . . . . . 15
  2354. 6.3. Complaint Center/Unsatisfactory Service Reports . . 15
  2355.  
  2356. SECTION 7. KEY CONTACTS . . . . . . . . . . . . . . . . . . . . . . 17
  2357. 7.1. DDN PMO Contacts . . . . . . . . . . . . . . . . . . 17
  2358. 7.2. DARPA Contacts . . . . . . . . . . . . . . . . . . . 17
  2359. 7.3. Contacts for Specific Services . . . . . . . . . . . 17
  2360.  
  2361. SECTION 8. REFERENCES . . . . . . . . . . . . . . . . . . . . . . . 19
  2362. 8.1. Cited References . . . . . . . . . . . . . . . . . . 19
  2363. 8.2. Additional References . . . . . . . . . . . . . . . 19
  2364.  
  2365. SECTION 9. GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . 21
  2366.  
  2367. APPENDIX. SITE PERSONNEL DUTIES . . . . . . . . . . . . . . . . . 23
  2368.  
  2369. List of Figures
  2370.  
  2371. Figure 2-1: Hardware and Configuration of the DDN 3
  2372. Figure 2-2: Management of the ARPANET 3
  2373. Figure 3-1: ARPANET New Subscriber Request Flow 5
  2374. Figure 3-2: Sample Feeder TSR Template 6
  2375. Figure 3-3: Host Data 7
  2376. Figure 3-4: Host Administrator Data 7
  2377. Figure 3-5: Sample User Registration Template 7
  2378. Figure 5-1: Modification Request Procedure 11
  2379.  
  2380. ACKNOWLEDGEMENTS
  2381.  
  2382. The ARPANET Information Brochure was prepared by the DDN Network
  2383. Information Center (NIC) for the Defense Advanced Research Projects Agency
  2384. and the Defense Data Network Program Management Office of the Defense
  2385. Communications Agency under contract number DCA-200-83-C-0025.
  2386.  
  2387. The NIC wishes to acknowledge the valuable assistance of Lt. Col. Bob
  2388. E. Baker of the Defense Advanced Research Projects Agency, Andrew Hogan of
  2389. the Defense Data Network Program Management Office, and Alan Hill of BBN
  2390. Communications Corporation in the preparation of this document.
  2391.  
  2392.  
  2393. ABSTRACT
  2394.  
  2395.  
  2396. The ARPANET is an unclassified, packet-switched data network originally
  2397. built by the Defense Advanced Research Projects Agency (DARPA) and used for
  2398. Department of Defense computer science and networking research. It is now
  2399. one of the subnetworks of the Defense Data Network (DDN) and, as such, is
  2400. managed by the Defense Data Network Program Management Office (DDN PMO).
  2401. Policy for the ARPANET is established by DARPA and they also decide who may
  2402. become subscribers. Subscribers are required to follow certain technical
  2403. and administrative procedures to connect host computers or other equipment
  2404. to the DDN. This document describes these procedures as they apply to the
  2405. ARPANET, provides background and technical information on the ARPANET, and
  2406. suggests sources of further information on protocol implementations and
  2407. interface equipment.
  2408.  
  2409.  
  2410. SECTION 1. INTRODUCTION
  2411.  
  2412. The Defense Advanced Research Projects Agency (DARPA) may require its
  2413. contractors or associated researchers to become ARPANET "subscribers"
  2414. (sites which have host computers or other equipment connected to the
  2415. network). In such cases DARPA requests authorization from the Defense Data
  2416. Network Program Management Office (DDN PMO) to add the required equipment
  2417. to the network.
  2418.  
  2419. This document describes the steps necessary for potential subscribers to
  2420. attach host computers or other equipment to the ARPANET. Administrative
  2421. and technical procedures are included. References to documents and
  2422. services, which will be helpful during the process of connecting equipment
  2423. to the network, are also included and are designated by the number of the
  2424. reference in brackets, e.g. [1].
  2425.  
  2426.  
  2427. 1.1 How To Use This Document
  2428.  
  2429. Section 1, the Introduction, explains how this document is organized.
  2430.  
  2431. Section 2 provides background on the ARPANET, describes the current
  2432. management structure, and states the criteria for becoming a subscriber.
  2433.  
  2434. Section 3 presents the administrative and technical procedures necessary to
  2435. bring a host onto the ARPANET. Different types of network connections and
  2436. associated costs are described.
  2437.  
  2438. Section 4 discusses the protocols used on the ARPANET and the DDN, and
  2439. tells how protocol implementations and documentation may be obtained.
  2440.  
  2441. Section 5 describes the administrative procedures required for requesting
  2442. modifications of network software or hardware.
  2443.  
  2444. Sections 6 and 7 describe the services and personnel available to help with
  2445. the process of connecting equipment to the ARPANET and with using the
  2446. network.
  2447.  
  2448. Section 8, References, contains citations and sources for publications
  2449. which provide further useful information. This section explains how to
  2450. obtain both hardcopy and online documents.
  2451.  
  2452. Finally, the Appendix contains important information on the duties assigned
  2453. to local network representatives.
  2454. Comments or suggestions for improvements to the document are welcome. Send
  2455. these by U.S. mail using the Comments Form at the end of the document or
  2456. through network mail to: SUGGESTIONS@SRI-NIC.ARPA.
  2457.  
  2458.  
  2459. SECTION 2. ARPANET MANAGEMENT AND POLICIES
  2460.  
  2461. This section presents background on how the ARPANET evolved into what it is
  2462. today, and how it is currently managed.
  2463.  
  2464.  
  2465. 2.1 What is the ARPANET?
  2466.  
  2467. The ARPANET began as an experimental packet-switched host-to-host network
  2468. in late 1969. It was funded through a research and development program
  2469. sponsored by DARPA. The goal of the program was to advance the
  2470. state-of-the-art in computer networking. The resultant network
  2471. successfully provided efficient communications between heterogeneous
  2472. computers, allowing convenient sharing of hardware, software, and data
  2473. resources among a varied community of geographically-dispersed users.
  2474.  
  2475.  
  2476.  
  2477.  
  2478.  
  2479.  
  2480.  
  2481.  
  2482.  
  2483.  
  2484.  
  2485.  
  2486.  
  2487.  
  2488.  
  2489.  
  2490.  
  2491.  
  2492.  
  2493.  
  2494.  
  2495.  
  2496.  
  2497.  
  2498.  
  2499.  
  2500.  
  2501.  
  2502.  
  2503.  
  2504.  
  2505. Figure 2-1: Hardware and Configuration of the DDN
  2506.  
  2507. In 1982 the DDN was created. The DDN uses ARPANET technology to link
  2508. existing and planned Department of Defense (DoD) networks. It is composed
  2509. of several operational, resource sharing, host-to-host networks which are
  2510. linked by controlled gateways, and which serve DoD facilities and non-DoD
  2511. research centers in the United States, Pacific, and European areas. All of
  2512. the networks that make up the DDN share the same "backbone" of node
  2513. computers. (See Figure 2-1 for a pictorial overview of the network
  2514. hardware and configuration). Node computers are interconnected through a
  2515. set of communications protocols referred to as the DoD Internet Protocol
  2516. Suite.
  2517.  
  2518. In 1983, the existing ARPANET was administratively divided into two
  2519. unclassified networks, ARPANET and MILNET, to meet the growing need for an
  2520. unclassified operational military network as well as the need for a
  2521. research and development network. The physical split into separate
  2522. networks was completed in September 1984. Each network now has its own
  2523. backbone, and is interconnected through controlled gateways to the other.
  2524. The ARPANET serves primarily as an experimental research and development
  2525. network, while the MILNET functions as an operational military network for
  2526. non-classified traffic. Communication and resource sharing between them
  2527. continue, but are subject to administrative restrictions.
  2528.  
  2529.  
  2530. 2.2 Management of the ARPANET
  2531.  
  2532. The DDN, including ARPANET, is operated for the DoD by the Defense
  2533. Communications Agency DDN PMO. For an overview of the management structure
  2534. for ARPANET, see Figure 2-2.
  2535.  
  2536.  
  2537.  
  2538.  
  2539.  
  2540.  
  2541.  
  2542. DoD
  2543. ________________|________________
  2544. | |
  2545. DCA DARPA
  2546. | |
  2547. DDN PMO IPTO
  2548. | |
  2549. (operational management) (administration, policy)
  2550. (security) (configuration, access)
  2551. |________________ ________________|
  2552. |
  2553. ARPANET
  2554.  
  2555.  
  2556.  
  2557. Figure 2-2: Management of the ARPANET
  2558.  
  2559.  
  2560. 2.2.1 DARPA/IPTO
  2561.  
  2562. DARPA's Information Processing Techniques Office (IPTO) is dedicated to
  2563. developing advanced information processing and computer communications
  2564. technologies for critical military and national security applications. The
  2565. building of the ARPANET and development of its protocols was an IPTO
  2566. program, which has evolved into what is now known as the Internet Research
  2567. Program.
  2568.  
  2569. Through IPTO, DARPA sets policy for, and manages use of, the ARPANET. This
  2570. is done within broad guidelines established for all DDN networks by the DDN
  2571. PMO. It also funds the ARPANET, and funds research carried out on the
  2572. ARPANET. Since there have been recent changes, it is important to
  2573. reiterate that the DDN PMO operates and manages the ARPANET, including the
  2574. node software and hardware, while DARPA pays the backbone operating costs,
  2575. sets policy for the ARPANET, and approves access for DARPA-sponsored
  2576. subscribers.
  2577.  
  2578.  
  2579. 2.2.2 DDN PMO Responsibilities
  2580.  
  2581. The DDN PMO is responsible for overall management, operations, and policy
  2582. guidelines for the entire DDN. It assists new subscribers in connecting
  2583. hosts and related equipment to the DDN, and manages the ARPANET on behalf
  2584. of DARPA. The DDN PMO provides many services to network users and
  2585. potential network subscribers, including:
  2586.  
  2587. - Keeping the network up and running
  2588.  
  2589. - Providing users with assistance
  2590.  
  2591. - Planning for growth
  2592.  
  2593. - Providing configuration management and control
  2594.  
  2595. - Assisting with protocol implementation and testing
  2596.  
  2597. - Advising subscribers on the selection of interface equipment and
  2598. software
  2599.  
  2600. - Managing access control and security for the network backbone
  2601.  
  2602. - Designating local host and node representatives
  2603.  
  2604. - Arranging for all equipment required to establish a network
  2605. connection
  2606.  
  2607. - Providing technical management of contracts for services,
  2608. equipment, and software obtained from outside corporations and
  2609. vendors.
  2610.  
  2611. The Data Operations Division, Code B650, of the DDN PMO manages all DDN
  2612. networks, including the ARPANET. For each DDN network, a PMO staff member
  2613. has been designated as the primary "point of contact" (POC). All
  2614. operational questions should be referred to this POC. (See Section 7 for
  2615. the phone number and mailbox of the ARPANET POC). The Data Operations
  2616. Division is also responsible for coordinating operational matters within
  2617. the DDN PMO itself, as well as with other branches and divisions of the DCA
  2618. and with DARPA.
  2619.  
  2620.  
  2621. 2.2.3 IAB Responsibilities
  2622.  
  2623. The DARPA Internet Research Program is directed by DARPA IPTO with the
  2624. assistance of an Internet Advisory Board (IAB) and a set of IPTO-appointed
  2625. Task Forces (technical working committees). The IAB consists of the
  2626. chairmen of the Task Forces, the DARPA Program Manager, the Chairman of the
  2627. IAB (the Internet Architect), the Deputy Chairman, and the Secretary of the
  2628. IAB.
  2629.  
  2630. The IAB guides and reviews the work of the Task Forces, and ensures proper
  2631. cross communication among them. The IAB may from time to time create new,
  2632. or disband existing, Task Forces.
  2633.  
  2634. The Task Forces are expected to generate and develop new ideas, to monitor
  2635. the technical work of the Internet program, and to recommend additional
  2636. research activity. The role of the Task Forces is seminal and advisory,
  2637. and very important to the advancement of the research goals of the Internet
  2638. program.
  2639.  
  2640. Members of each Task Force are chosen by its chairman, and they are
  2641. expected to make a moderate commitment of time to the work of the Task
  2642. Force. Most Task Forces also have mailing lists for persons interested in
  2643. following the work of a given Task Force. Current Task Forces and chairmen
  2644. are:
  2645.  
  2646. Task Force Chairman Organization (See Glossary)
  2647. Applications Bob Thomas BBNCC
  2648. Gateway Algorithms
  2649. and Data Structures Dave Mills M/A-COM
  2650. Interoperability
  2651. and Autonomous Systems Robert Cole UCL
  2652. New End to End Services Bob Braden UCLA
  2653. Privacy Steve Kent BBNCC
  2654. Robustness and Survivability Jim Mathis SRI
  2655. Security Ray McFarland DOD
  2656. Tactical Internetting David Hartmann MITRE
  2657. Testing Ed Cain DCEC
  2658. IAB officers are:
  2659.  
  2660. Position Occupant Organization
  2661. Internet Architect Dave Clark MIT
  2662. Deputy Internet Architect Jon Postel ISI
  2663. DARPA Program Manager Dennis Perry DARPA
  2664. IAB Secretary Chris Perry MITRE
  2665.  
  2666. Phone numbers for IAB members are available through DARPA.
  2667.  
  2668.  
  2669. 2.3 ARPANET Access and Use Policies
  2670.  
  2671. DARPA and the DDN PMO have set broad guidelines for ARPANET access and use,
  2672. administered locally by volunteer site personnel called Host
  2673. Administrators. Legitimate ARPANET users must be engaged in U.S.
  2674. government business or research, or directly involved in providing
  2675. operations or system support for government-owned or government-sponsored
  2676. computer communications equipment. The network is not available for use by
  2677. the general public, nor is it intended to compete with comparable
  2678. commercial network services.
  2679.  
  2680. The purpose of the ARPANET is to provide a facility for advanced
  2681. packet-switched communications technologies research and experimental
  2682. communication support of government-sponsored university computer science
  2683. research. Consequently, access to, and use of, ARPANET will not be
  2684. authorized to support operational (as opposed to experimental)
  2685. communication requirements. Such operational facilities are provided for
  2686. DoD users by the DDN, and for others by public and private packet-switched
  2687. networks (such as TYMNET or TELENET).
  2688.  
  2689. Users of ARPANET may only use the network to conduct the official business
  2690. for which their access was authorized. They must not violate privacy or
  2691. any other applicable laws, and must not use the network for private gain or
  2692. for commercial purposes, such as advertising or recruiting. ARPANET users
  2693. may connect to other DDN networks only when approved by the DDN PMO on a
  2694. host-by-host basis.
  2695.  
  2696. Host site personnel are responsible for developing and enforcing specific
  2697. policies to ensure that these guidelines are followed. (See the Appendix
  2698. for a formal statement of site personnel responsibilities). The Host
  2699. Administrator is given the authority to disallow access to the ARPANET by
  2700. users who use the network irresponsibly or for unauthorized purposes. The
  2701. DDN PMO assumes this authority only in an emergency, or if administration
  2702. at the local level is not functioning.
  2703.  
  2704.  
  2705. 2.3.1 Host Access Controls
  2706.  
  2707. Subscribers and sponsors are responsible for letting only authorized users
  2708. have network privileges. All non-government users should be associated
  2709. with a valid contract number, or have explicit permission to use the
  2710. ARPANET. Additionally, host sites must maintain these controls:
  2711.  
  2712. - Procedures that allow only valid users to obtain accounts on
  2713. government-owned computers or to obtain access to the ARPANET
  2714. backbone from the host
  2715.  
  2716. - Login Name/Password so that only valid users can access the host
  2717.  
  2718. - Periodic Reviews of users so that persons who no longer need
  2719. ARPANET access are denied such access and unused accounts are
  2720. closed.
  2721.  
  2722. Any attempts to break into a system from the network should be reported by
  2723. the Host Administrator to the DDN PMO and DARPA by telephone or U.S. mail.
  2724.  
  2725. When violations of the above policies are observed, DCA will notify the
  2726. site personnel. If the problem is not corrected within a reasonable time,
  2727. DCA may exercise the option of disconnecting the host or terminal from the
  2728. network.
  2729.  
  2730.  
  2731. 2.3.2 TAC Access Controls
  2732.  
  2733. A Terminal Access Controller (TAC) is a computer system attached directly
  2734. to the DDN that lets a user at a terminal connect to hosts on the network
  2735. without first going through a local host. (See Section 3.3 for a
  2736. description of a TAC connection).
  2737.  
  2738. ARPANET users must be authorized for network TAC access by a
  2739. DARPA-appointed network contact known as a "Responsible Person" (RP). An
  2740. RP is a person in a position of authority within each organization
  2741. authorized to use the ARPANET. The RP is responsible for ensuring that TAC
  2742. access to the ARPANET is only allowed for those members of his organization
  2743. with a valid requirement for such access. The RP, or his delegate, sees
  2744. that TAC users are entered into the ARPANET TAC User Database (UDB)
  2745. accessible through the network. The RP uses the UDB to generate a "USER
  2746. ID" and an "ACCESS CODE" for each user.
  2747.  
  2748. The User Database is downloaded regularly to several "login hosts"
  2749. throughout the ARPANET. These hosts verify authorized use at the time a
  2750. user logs in to a TAC. When an ARPANET TAC user tries to open a connection
  2751. to a host from a TAC, the TAC requests a USER ID and ACCESS CODE, then
  2752. interacts with a login host to validate the user. If the login host
  2753. reports that the USER ID/ACCESS CODE is invalid, the TAC prints an error
  2754. message and refuses to open a connection. Access is thus restricted to
  2755. users whose names have been entered into the user database.
  2756.  
  2757. MILNET, the DoD's operational military network which shares the DDN
  2758. backbone with ARPANET, also contains TACs and has a system of registering
  2759. MILNET TAC users. Although these registration systems serve the same
  2760. purpose, they are different in operation, and are physically and
  2761. administratively completely independent from each other. A user authorized
  2762. for access through both MILNET and ARPANET TACs must register twice, once
  2763. in each system. Note that the login procedure itself is identical whether
  2764. the user logs in from ARPANET or MILNET. Only the user registration
  2765. procedures are different.
  2766.  
  2767. Lack of local ARPANET TAC resources is not considered sufficient reason to
  2768. provide ARPANET users with MILNET TAC access and vice versa. MILNET TACs
  2769. are provided to assist authorized users in carrying out DDN operational
  2770. tasks. Contact the DARPA POC (see Section 7.2) if you are an authorized
  2771. ARPANET user and there is no ARPANET TAC available in your area.
  2772.  
  2773.  
  2774. SECTION 3. SUBSCRIBER ACCESS PROCEDURES
  2775.  
  2776. This section describes how a potential ARPANET subscriber can apply for
  2777. access to the network. It compares the different types of connections
  2778. available, and describes how terminals can access hosts through the network
  2779. TACS.
  2780.  
  2781. NOTE: The entire process from application to completion may require
  2782. over a year if installation of phone lines or node equipment is
  2783. required. It is important to plan ahead and let DARPA and the DDN PMO
  2784. know what your anticipated needs are.
  2785.  
  2786. The process of becoming a subscriber involves several steps. It must first
  2787. be determined that the potential subscriber has a legitimate need to access
  2788. the network and has authorization from DARPA to use the network. Paperwork
  2789. must be submitted to authorize the DDN PMO to begin the process of ordering
  2790. all equipment required to establish a network connection.
  2791.  
  2792. Site personnel must arrange to lease or purchase a host computer (if one is
  2793. not already available), and to implement or procure implementations of
  2794. network protocols that will run on it. They must also arrange for the
  2795. installation and testing of site hardware. The sections that follow
  2796. describe these procedures in greater detail.
  2797.  
  2798.  
  2799. 3.1 Process Overview
  2800.  
  2801. All ARPANET host connections are managed by the Packet Switching Operations
  2802. Branch, Code B652, of the DDN PMO. The procedures for getting a host
  2803. connected to ARPANET are outlined below.
  2804.  
  2805. a. Contact Code B641 of the DDN PMO, who determines whether the
  2806. requirement qualifies for ARPANET or MILNET connection.
  2807.  
  2808. b. Contact the ARPANET Coordinator in the Information Processing
  2809. Techniques Office (IPTO) at DARPA, who will verify government
  2810. sponsorship and will provide the required Feeder
  2811. Telecommunications Service Request (TSR), Host Approved Form
  2812. (HAF) and, when necessary, the Internet Protocol Network Number
  2813. Request Form.
  2814.  
  2815. c. Submit the filled-in Telecommunications Service Request (TSR)
  2816. forms to DARPA for approval and subsequent forwarding to Code
  2817. B643 and Code B652 of the DDN PMO.
  2818.  
  2819. d. The TSR is issued by the DDN PMO. The requester receives a
  2820. hardcopy confirmation via Mailgram, TELEX or AUTODIN message.
  2821.  
  2822. e. Requester also receives a Telecommunications Service Order (TSO)
  2823. delivered via the same means.
  2824.  
  2825. f. The Installation Branch, Code B642, generates a Network Change
  2826. Request (NCR) from host data provided by Code B652.
  2827.  
  2828. g. The NCR is approved by Code B652 of the PMO and becomes a
  2829. Network Change Directive (NCD). Host data is added to the NIC
  2830. host table, the ARPANET Monitoring Center (AMC) activates the
  2831. host port, and the requester receives electronic mail
  2832. confirmation of the NCD.
  2833.  
  2834. h. When the host is installed, the requester receives a completion
  2835. report by the same means as the original TSR.
  2836.  
  2837. NOTE: The TSR and TSO indicate the assigned network address, and
  2838. therefore, the network node through which service will be provided.
  2839. Each node has a Node Site Coordinator (NSC) (See Appendix ), whom the
  2840. host requester may wish to contact concerning cabling or other
  2841. connection mechanisms between the host and node locations. If a new
  2842. node must be installed at the site before hosts can be connected to
  2843. the network, an NSC will have to be appointed, who should be prepared
  2844. to assist DDN PMO field representatives with node equipment
  2845. installation.
  2846.  
  2847.  
  2848.  
  2849.  
  2850. New Subscriber Request
  2851. |
  2852. DCA Code B641
  2853. |
  2854. ARPANET Coordinator, DARPA
  2855. |
  2856. Feeder TSR and HAF
  2857. |
  2858. DARPA IPTO Approval
  2859. |
  2860. DCA Code B652 Approval
  2861. |
  2862. DCA Code B643
  2863. |
  2864. Requester <------- TSR Issued
  2865. Notified TSO Issued --------> DECCO
  2866. |
  2867. DCA Code B652
  2868. Provides Host Data
  2869. |
  2870. DCA Code B642
  2871. |
  2872. NCR
  2873. |
  2874. DCA Code B652
  2875. Approval
  2876. |
  2877. NCD
  2878. |
  2879. ______________________|______________________
  2880. | | |
  2881. SRI NIC Requester AMC
  2882. | Notified |
  2883. Host Table Change NCAN
  2884. |
  2885. DCA Code B652
  2886.  
  2887.  
  2888. AMC: ARPANET Monitoring Center NCD: Network Change Directive
  2889. DECCO: Defense Commercial Comm. Office NCR: Network Change Request
  2890. HAF: Host Approved Form SRI NIC: Network Information Ctr.
  2891. IPTO: Info. Process. Techniques Office TSO: Telecomm. Service Order
  2892. NCAN: Network Change Ack. Notice TSR: Telecomm. Service Request
  2893.  
  2894.  
  2895. Figure 3-1: ARPANET New Subscriber Request Flow
  2896.  
  2897.  
  2898. 3.1.1 Feeder TSRs
  2899.  
  2900. The Feeder TSR provides information for assessing the applicant's need for
  2901. network access, and is a preliminary request for service leading to the
  2902. issuance of a full TSR by the DDN PMO. To submit a Feeder TSR for ARPANET
  2903. service, the template shown in Figure 3-2 must be completed.
  2904.  
  2905. The parts of the Feeder TSR are:
  2906.  
  2907. (1) TSR ITEM NUMBER - the number for each entry.
  2908.  
  2909. (2) INFORMATION - data provided by the applicant; on the sample
  2910. template (Figure 3-2) a description is provided of the
  2911. information required for each item.
  2912.  
  2913. (3) TYPE OF ACTION - indicates whether applicant must complete an
  2914. item, contingent upon choice indicated in Item 103.
  2915.  
  2916. For example, if you are starting service, write "start" on line 103 in the
  2917. information column. You must then fill in information for all lines where
  2918. there is an "X" in the "START" column under "Type of Action". If you have
  2919. questions about the template, contact the ARPANET Coordinator at DARPA or
  2920. the ARPANET POC at the DDN PMO.
  2921.  
  2922.  
  2923. FEEDER TSR TEMPLATE (Sample)
  2924.  
  2925. (1) (2) (3)
  2926.  
  2927. TSR INFORMATION TYPE OF ACTION
  2928. ITEM NO. START AMEND REHOME CANCEL
  2929. --- ----------- ----------------------------
  2930.  
  2931. 101 LEAVE BLANK
  2932. 103 TYPE OF ACTION (Start, Change,
  2933. Discontinue, Amendment, Rehome)
  2934. 104 Fill in the words "LEASED EQUIPMENT/
  2935. SERVICE CONTRACT" if leased modems
  2936. and maintenance is required to be
  2937. provided by the government
  2938. 105 Fill in the word "DEDICATED" if
  2939. ARPANET and "DDN" if MILNET
  2940. 106 State the requested service date
  2941. by day, Greenwich Mean Time, Month,
  2942. and Year. e.g. 141200Z JUL 84.
  2943. NOTE: A minimum of 150 days is required
  2944. for circuits.
  2945. 110 FULL DUPLEX
  2946. 111 Enter the data rate (2.4KB, 1.2KB,
  2947. 4.8KB, 9.6KB, 50KB, 56KB, 100KB) of
  2948. the requested service.
  2949. 112 FULL PERIOD
  2950. 115 NO SIGNALLING X X
  2951. 116 Enter the words "NEW LEASE" if this
  2952. is a new requirement, or enter the
  2953. Commercial Communications Service
  2954. Authorization Number (CSA) if this is
  2955. an amendment, rehome, disconnect, or
  2956. change to an existing requirement.
  2957. If no circuit is required, omit this
  2958. item.
  2959. 117 LEAVE BLANK
  2960. 118 LEAVE BLANK
  2961. 120A The end user location requiring
  2962. ARPANET/MILNET Access (Geographical
  2963. location, e.g. city, base, camp, post
  2964. or station that is applicable)
  2965. 121A State of the end user location
  2966. 123A CPV
  2967. 124A The building number where the user's
  2968. terminal or host is located that will
  2969. be connected to the ARPANET/MILNET
  2970. 125A The room number where the user's
  2971. terminal or host is located that will
  2972. be connected to the ARPANET/MILNET
  2973. 126A The type of terminal or host equipment
  2974. that will be connected.
  2975. 128A The user interface that will be
  2976. connected up to the circuit (RS-232C,
  2977. RS-449, Synchronous, Asynchronous,
  2978. MIL-STD 188-114, Leased Modem)
  2979. 130A Provide the name, telephone number
  2980. and office code or symbol of a primary
  2981. and alternate person at the user's
  2982. terminal end that is familiar with the
  2983. details and requirements of this request
  2984. 131A Provide the complete mailing address
  2985. of the primary person identified in
  2986. 130A, including the agency, street
  2987. address, building number, city, state
  2988. and zip code.
  2989. 120B TO BE DETERMINED BY DCA
  2990. 353 Fill in "ARPANET" or "MILNET"
  2991. 354 If this requirement is for a terminal
  2992. connection and not a host, enter the
  2993. data link protocol (e.g. asynchronous)
  2994. 357 If this requirement is to connect a
  2995. host, enter the software and hardware
  2996. interface requirements (e.g. RS232/
  2997. V.35/MIL-188-114/Bell 303/cable only
  2998. and HDH/X.25/DH/DH with ECU's
  2999. 361 If this requirement is for a terminal
  3000. connection and not a host, enter
  3001. "ASCII"
  3002. 401 State the exact requirement of this
  3003. request, e.g. The purpose of this
  3004. request is to request leased modems
  3005. and circuit between end points.
  3006. 407A If this request is to provide leased
  3007. modems, state so here, and if the
  3008. modem is to be a stand alone or rack
  3009. mounted in a cabinet. If additional
  3010. equipment is to be leased, state so
  3011. (e.g. 1-ea 72 inch modem cabinet,
  3012. 2-ea 25 ft RS-232 M/F connection
  3013. cable). All equipment to be provided
  3014. by the government should be listed
  3015. here.
  3016. 409 The individual at the user site who
  3017. will accept service.
  3018. 417 If this requirement is to connect up
  3019. a host, please list the host name
  3020. along with any narrative remarks which
  3021. will help to clarify this requirement.
  3022. e.g. statement that user is providing
  3023. circuit and modems if that is the
  3024. case, statement that no circuit is
  3025. required due to it being a local
  3026. connection if that is the case,
  3027. desired/recommended PSN for connection.
  3028. In all cases, the electronic mail
  3029. address for the person shown in 130A
  3030. should be indicated here.
  3031. 419 DECCO SCOTT AFB
  3032. 430 Estimated length of service requirement
  3033. (12, 24, 36, 48, or 72 months)
  3034. 431 "N" if ARPANET, "D" if MILNET
  3035. 437A YES OWM
  3036. 438A "NONE" if no leased equipment is
  3037. required or "BOTH" if this request
  3038. includes both circuit and associated
  3039. leased equipment.
  3040. 501 Justification for the service being
  3041. requested, e.g. To provide UCLA
  3042. connection to the ARPANET for testing
  3043. host interfaces.
  3044. 510 LEAVE BLANK
  3045.  
  3046.  
  3047.  
  3048. Figure 3-2: Sample Feeder TSR Template
  3049.  
  3050.  
  3051.  
  3052. Submit the feeder TSR templates for ARPANET service to DARPA:
  3053. U.S. Mail Address
  3054.  
  3055. Defense Advanced Research Projects Agency
  3056. Information Processing Techniques Office
  3057. Attn: ARPANET COORDINATOR
  3058. 1400 Wilson Boulevard, 7th Floor
  3059. Arlington, Virginia 22209
  3060.  
  3061. Telephone
  3062.  
  3063. Phone: (202) 694-5921
  3064.  
  3065. Network Mailbox
  3066.  
  3067. BOWERS@USC-ISI.ARPA
  3068.  
  3069.  
  3070.  
  3071. 3.2 Backbone Hardware Requirements
  3072.  
  3073.  
  3074. 3.2.1 Types of Service
  3075.  
  3076. The network interface can be either full service (supporting all DDN
  3077. protocols) or limited service. A full-service interface is recommended
  3078. whenever possible, as it provides the most functionality for users.
  3079.  
  3080. Limited service may be provided by a terminal emulation interface, or an
  3081. interface supported by vendor-specific protocols. Either type may be used
  3082. temporarily while awaiting a full-service interface. Permanent
  3083. installation of limited-service interfaces should be restricted to terminal
  3084. emulation interfaces, and to systems where the cost of a full-service
  3085. interface would be prohibitive.
  3086.  
  3087. For complete information on types of service available on the DDN, see the
  3088. DDN Subscriber Interface Guide [1].
  3089.  
  3090.  
  3091. 3.2.2 Equipment Procurement and Costs
  3092.  
  3093. Costs for connection to the ARPANET are not fixed, but are arranged on an
  3094. individual basis. Generally, DARPA pays backbone costs and the contractor
  3095. pays all other costs (including Error Correction Units and interface units,
  3096. when required). For detailed information, contact the ARPANET POC (see
  3097. Section 7.2).
  3098.  
  3099.  
  3100. 3.2.3 PSN Port Assignment
  3101.  
  3102. The initial Packet Switch Node (PSN, formerly called Interface Message
  3103. Processor or IMP) port assignment is sent to the subscriber as part of the
  3104. TSR/TSO process (described in Section 3.1.1). Subscribers must not change
  3105. PSN ports or switch equipment on PSN ports without approval through the
  3106. TSR/TSO process.
  3107.  
  3108. Note that PSN port changes must have proper authorization and will not
  3109. happen instantaneously. Also, if a host is changed to a different PSN
  3110. port, its host address will change (see Section 3.4.1). Contact the
  3111. ARPANET POC or the NIC for assistance in obtaining a PSN port change or if
  3112. problems with host names or addresses arise.
  3113.  
  3114.  
  3115. 3.3 TAC Connection
  3116.  
  3117. ARPANET users may access a network host via a TAC, which is a special
  3118. terminal access node. TACs let a terminal connect directly to the network,
  3119. i.e., without going through another host. Terminals may be either
  3120. hard-wired to the TAC or connected by a dial-up modem. A user
  3121. geographically remote from a given host can dial up a nearby TAC, log in,
  3122. open a connection to the distant host, and work as if he were connected
  3123. locally. Thus, the TAC lets the user reach his host through the network,
  3124. rather than through a direct long distance telephone call to the host.
  3125.  
  3126. Current TAC locations and phone numbers are available from the NIC. If
  3127. installation of a TAC appears to be necessary for your area or user
  3128. population, contact the DARPA POC and describe the need for the
  3129. installation of a TAC at the designated location. DARPA will evaluate the
  3130. request and, if the request is warranted, will place an order for TAC
  3131. installation with the DDN PMO.
  3132.  
  3133.  
  3134. 3.4 Registration Procedures
  3135.  
  3136. The following sections discuss the administrative steps a potential
  3137. subscriber should take to register a host, and the procedures required to
  3138. register users once the host is connected to the net. Figure 3-1 gives an
  3139. overview of the process.
  3140.  
  3141.  
  3142. 3.4.1 Host Registration
  3143.  
  3144. Each host on the DDN is identified by a unique host name and host address.
  3145. To register a host, information must be supplied to DCA Code B652, the
  3146. Packet Switching Operations Branch, as shown in the following examples
  3147. (Figures 3-3, 3-4). Send completed forms online or by U.S. mail to the
  3148. ARPANET Coordinator at DARPA.
  3149.  
  3150.  
  3151. Host Data (Sample)
  3152.  
  3153. HOSTNAME: DDN1
  3154. NETWORK ADDRESS: 10.1.0.25
  3155. LOCATION: Bolt Beranek and Newman Inc.
  3156. 1300 North 17th Street
  3157. Suite 400
  3158. Arlington, Virginia 22206
  3159. CPUTYPE: BBN-C/70
  3160. OPERATING SYSTEM: UNIX
  3161. NICKNAME: DDN-1
  3162. SPONSORING AGENCY: DCA
  3163. HOST TYPE: DH
  3164. PROTOCOLS: TCP/TELNET,TCP/FTP,TCP/SMTP
  3165.  
  3166.  
  3167. Figure 3-3: Host Data
  3168.  
  3169.  
  3170.  
  3171.  
  3172. Host Administrator Data (Sample)
  3173.  
  3174. NAME: Chipman, Steven G.
  3175. U.S. MAIL ADDRESS: Bolt Beranek and Newman Inc.
  3176. 10 Moulton Street
  3177. Cambridge, Massachusetts 02238
  3178. TELEPHONE: (617) 497-3505 (now 873-3505, May 89)
  3179. NETWORK MAILBOX: chipman@BBNF.ARPA
  3180.  
  3181.  
  3182. Figure 3-4: Host Administrator Data
  3183.  
  3184.  
  3185.  
  3186. 3.4.2 Host Addresses and Domains
  3187.  
  3188. The host address contains four decimal numbers, each separated by a period.
  3189. Each part represents one octet of a 32-bit address. The meaning of each
  3190. octet depends upon which class of network it describes. There are three
  3191. classes of networks (Class A, Class B, and Class C), based upon the
  3192. network's size and function.
  3193.  
  3194. On Class A networks, which are large, long-haul networks such as ARPANET
  3195. and MILNET, the first octet indicates the network number. The second octet
  3196. refers to the host port number on the PSN; the third octet is reserved, and
  3197. is usually zero; and the last octet is the number of the PSN to which the
  3198. host is connected.
  3199.  
  3200. For Class B networks, the first two octets indicate the network portion of
  3201. the number; for Class C networks the first three octets are used to
  3202. indicate the network number. For more information on address mappings, see
  3203. RFC 796 [2].
  3204.  
  3205. The DDN Network Information Center maintains the official DoD Internet Host
  3206. Table and is the network Hostmaster for names and addresses of hosts,
  3207. networks, nodes and domains. Hosts should arrange to regularly update
  3208. their local tables by retrieving all or part of the master table from the
  3209. NIC Host Name Server. For information about the DoD Internet Host Table
  3210. specification, see RFC 952 [3].
  3211.  
  3212. In the near future, all DARPA hosts will be required to either join an
  3213. existing "domain" or to administer a domain of their own. Domains are
  3214. administrative entities that provide decentralized host naming and
  3215. addressing management. Their purpose is to distribute the task of naming
  3216. and addressing.
  3217.  
  3218. Under the domain-naming scheme, information is stored in a distributed,
  3219. hierarchical database. Responsibility for naming domains (or sub-nodes of
  3220. the hierarchical naming tree) can then be delegated to different
  3221. organizations, each with responsibility for maintaining host-related
  3222. information for their domain. Information about hosts and domains is
  3223. disseminated through the network via Name Servers. For more information on
  3224. domains, see RFC 920 [4] and RFC 921 [5].
  3225.  
  3226. The domain system on ARPANET is experimental. The MILNET has not yet
  3227. implemented the domain system. The NIC name server translates between the
  3228. two systems and continues to provide a "flat" domainless host table for use
  3229. by MILNET hosts while serving as registrar for domain names for the
  3230. Internet.
  3231.  
  3232.  
  3233. 3.4.3 LAN and Gateway Registration
  3234.  
  3235. Subscribers wishing to connect a local area network (LAN) or other non-DDN
  3236. network to the ARPANET must first obtain DARPA and DCA approval. Such
  3237. networks are connected to the DDN through a "gateway" computer which
  3238. manages communication between the LAN or non-DDN net and the ARPANET.
  3239. DARPA treats gateways as regular hosts, so the procedure for registering a
  3240. gateway is the same as for hosts.
  3241.  
  3242. The subscriber must obtain a network number for each LAN from the NIC.
  3243. Within such a "private network", subscribers can assign their own host
  3244. names and addresses as long as they follow the internet network addressing
  3245. convention [2]. For more information on registering non-DDN networks,
  3246. contact HOSTMASTER@SRI-NIC.ARPA online or call (800) 235-3155.
  3247.  
  3248.  
  3249. 3.4.4 User Registration
  3250.  
  3251. The DDN PMO and DARPA have authorized the NIC to register all ARPANET
  3252. users, and to maintain this information in the NIC WHOIS database. This
  3253. database serves as an online "white pages" service for ARPANET users [6].
  3254.  
  3255. The Host Administrator for each host is responsible for registering the
  3256. users of his or her host with the NIC. This is done electronically over
  3257. the network, so the Host Administrator is required to have a network
  3258. mailbox.
  3259.  
  3260. Users may be registered either by sending filled-in templates to the NIC
  3261. through electronic mail, or by using the NIC REGISTER system. This section
  3262. describes the procedures a Host Administrator should follow to register
  3263. users.
  3264.  
  3265.  
  3266. 3.4.4.1 NIC Registration Template
  3267.  
  3268. To register by electronic mail, FTP a copy of the registration template
  3269. (pathname NETINFO:USER-TEMPLATE.TXT, see Figure 3-5) from SRI-NIC
  3270. (10.0.0.51). Complete one template for each individual and separate the
  3271. templates by a blank line. Fill in all the relevant fields as shown below.
  3272. Instructions for completing the template are included in the template file.
  3273. It is important that you use the NIC template and adhere to the same
  3274. data-entry style shown. This will allow automatic input of the data into
  3275. the WHOIS database. The NIC will not accept data that is not in the
  3276. specified template format.
  3277.  
  3278.  
  3279. FULL NAME: Coleman, Jr., Arthur F.
  3280. U.S. MAIL ADDRESS: SRI International
  3281. 333 Ravenswood Avenue
  3282. Menlo Park, CA 94025
  3283. PHONE: (415) 859-0000
  3284. AUTHORIZING HOST: SRI-NIC
  3285. PRIMARY LOGIN NAME: Coleman
  3286. PRIMARY NETWORK MAILBOX: coleman@SRI-NIC.ARPA
  3287. ALTERNATE NETWORK MAILBOXES (if any): acoleman@SRI-TSC.ARPA
  3288.  
  3289.  
  3290. Figure 3-5: Sample User Registration Template
  3291.  
  3292.  
  3293.  
  3294. The Host Administrator may send his users blank templates to fill out.
  3295. Users should return the completed templates to the Host Administrator who
  3296. will accumulate them in a single file. He will review the lists (as he is
  3297. responsible for the authorization of registered users on his hosts), and
  3298. send the files as online messages to REGISTRAR@SRI-NIC.ARPA.
  3299.  
  3300. If the list is too long for a given mail system to process, the Host
  3301. Administrator may break the lists arbitrarily (between templates) and send
  3302. them as a set of messages. If the lists are broken up, the subject field
  3303. of each message should specify this, e.g., Part 1 of 4, Part 2 of 4, etc.
  3304. To assure that the NIC mail system will be able to process the message,
  3305. never send a message of over 50,000 characters (100 templates). Full
  3306. instructions for registering users may be obtained from the NIC.
  3307.  
  3308. NOTE: Registering ARPANET users with the NIC for the WHOIS database
  3309. is a separate process from registering users for ARPANET TAC access.
  3310.  
  3311.  
  3312. 3.4.4.2 NIC REGISTER Program
  3313.  
  3314. REGISTER is a program running on SRI-NIC that will allow users to
  3315. interactively register themselves in the WHOIS database. Contact the NIC
  3316. for details on using this program.
  3317.  
  3318.  
  3319. 3.4.5 ARPANET TAC Access Registration
  3320.  
  3321. ARPANET TAC users must be authorized for network access by the "Responsible
  3322. Person" (RP) in their organization. Once users have been given permission
  3323. by the RP to use an ARPANET TAC, the RP or his delegate, or the user
  3324. himself may enter user registration data into the ARPANET TAC User Database
  3325. (UDB), using the User Database Tool located at host USC-ISI. The database
  3326. is downloaded regularly to several "login hosts" throughout the net. For
  3327. information on using the database tool, the RP or the user should obtain
  3328. and read ARPANET Access Control, User Manual for the User Database Tool [7]
  3329. available in hardcopy or online from the NIC.
  3330.  
  3331. NOTE: ARPANET TAC usernames and passwords must be changed every 6
  3332. months as they will be invalid after that time. The user may make
  3333. this change himself, once he has been given permission to be a TAC
  3334. user. However, the change must be made within the 6 month time period
  3335. or permission to be a TAC user will again need to be assigned by an
  3336. RP.
  3337.  
  3338.  
  3339. SECTION 4. ARPANET PROTOCOLS
  3340.  
  3341. A special set of DoD Internet protocols has been developed and implemented
  3342. on the ARPANET. The most important of these are the Transmission Control
  3343. Protocol (TCP) and the Internet Protocol (IP). These protocols govern the
  3344. handling of internet communication, and must be implemented on each host or
  3345. host interface before connecting to the network.
  3346.  
  3347. Each site has the choice of implementing its own version of the protocols,
  3348. adapting a public domain version of the protocols, or purchasing an
  3349. implementation from a commercial vendor. This section discusses some aids
  3350. to help subscribers choose the best approach based upon their needs.
  3351.  
  3352. NOTE: Protocols approved for use on the DDN are issued as official
  3353. DoD Military Standards (MIL STDs). The ARPANET is an experimental
  3354. network and may choose to implement experimental ARPANET protocols.
  3355. These may be ARPANET standards, i.e., required on the ARPANET, but may
  3356. not be MIL STDs or official DoD protocols.
  3357.  
  3358.  
  3359. 4.1 DDN Protocol Handbook
  3360.  
  3361. The 1985 DDN Protocol Handbook [8] describes specifications for MIL STD
  3362. communication protocols, ARPANET standard protocols, experimental
  3363. protocols, and de facto protocols in use on the DDN and the DARPA Internet.
  3364. It also includes background information, policy information, implementation
  3365. guidelines, and instructions on how to obtain other protocol information of
  3366. interest.
  3367.  
  3368. The primary purpose of the Handbook is to serve as a reference guide for
  3369. those planning to implement the DoD suite of protocols on various computers
  3370. to be attached to the ARPANET or the DDN. It is an essential reference
  3371. tool for sites bringing hosts onto the network. The Handbook is a
  3372. multi-volume set published by the NIC and is available from the NIC for
  3373. $110.00 prepaid, or from the Defense Technical Information Center (DTIC).
  3374.  
  3375.  
  3376. 4.2 TCP/IP Implementations and Vendors Guide
  3377.  
  3378. The TCP/IP Implementations and Vendors Guide [9] is a guide to commercially
  3379. available implementations of the TCP/IP protocols, including public domain
  3380. implementations. It is published for informational purposes only by the
  3381. DDN Network Information Center at SRI International on behalf of the DDN
  3382. PMO and in no way endorses or officially recommends any implementation or
  3383. product on the part of DCA, DARPA, the DoD, or the NIC. The Guide is
  3384. useful for finding out what public domain and commercial implementations of
  3385. protocols are available.
  3386.  
  3387.  
  3388. 4.3 RFCs
  3389.  
  3390. Before a proposed protocol is accepted for use on the DARPA Internet, it is
  3391. discussed, reviewed, and often revised by members of the Internet Advisory
  3392. Board, its Task Force members and other interested parties. This dialog is
  3393. captured in a set of technical notes known as Requests For Comments, or
  3394. RFCs.
  3395.  
  3396. Individuals who wish to be added to the online RFC notification list should
  3397. send a message to NIC@SRI-NIC.ARPA requesting that their names be added to
  3398. the distribution list.
  3399.  
  3400. RFCs can also be FTPed from SRI-NIC, using the pathname RFC:RFCnnn.TXT,
  3401. where "nnn" is the RFC number; also available is the file
  3402. RFC:RFC-INDEX.TXT, an index to RFCs. See Section 6.1.4 for information on
  3403. ordering hardcopies of RFCs.
  3404.  
  3405.  
  3406. SECTION 5. HARDWARE AND SOFTWARE MODIFICATIONS
  3407.  
  3408. As the ARPANET is an experimental network, there may be occasions when site
  3409. researchers or representatives wish to make temporary or permanent changes
  3410. in the host or node software or hardware. Host software may be modified
  3411. without DDN PMO approval; node software may not. Node equipment is owned
  3412. and managed by the DDN. Any changes require proper paperwork and
  3413. sufficient time to transact.
  3414.  
  3415. NOTE: PSN hardware and software may not be modified without DDN and
  3416. DARPA approval. Requests for such changes must be made through the
  3417. proper administrative channels.
  3418.  
  3419.  
  3420. 5.1 Subscriber Software and Hardware Modification Requests
  3421.  
  3422. Requests for node or backbone software modifications or bug fixes should be
  3423. sent to the ARPANET Monitoring Center (AMC) at BBN Communications
  3424. Corporation (BBNCC; see Section 6.2). BBNCC, acting on behalf of DARPA,
  3425. will prepare a Patch Note and submit it to the DDN Configuration Control
  3426. Group (CCG) for approval. The CCG will evaluate the request, and if
  3427. approved, will forward it to DCA Code B643 for implementation. (See Figure
  3428. 5-1).
  3429.  
  3430.  
  3431.  
  3432.  
  3433.  
  3434.  
  3435.  
  3436. DARPA (info copy)
  3437. /
  3438. User or DARPA Request >--> BBNCC >--> DDN CCG >--> Implementation
  3439.  
  3440.  
  3441. Figure 5-1: Modification Request Procedure
  3442.  
  3443.  
  3444.  
  3445.  
  3446. 5.2 ARPANET Software/Node Modification Procedures
  3447.  
  3448. From time to time patches to, or new versions of, node software are
  3449. released by the DDN PMO. Occasionally these require adjustments to the
  3450. protocol implementations at the host end. In general, official backbone
  3451. program changes that may affect hosts or users will be announced through a
  3452. DDN Management Bulletin (an official online mail notification issued by the
  3453. NIC on behalf of the DDN PMO), and coordinated with site personnel prior to
  3454. implementation by the DDN.
  3455.  
  3456.  
  3457. SECTION 6. NETWORK INFORMATION SERVICES
  3458.  
  3459.  
  3460. 6.1 DDN Network Information Center
  3461.  
  3462. The DDN Network Information Center, located at SRI International, Menlo
  3463. Park, CA, is funded by the DDN PMO to provide general user assistance and
  3464. information services to DDN and ARPANET subscribers and new users.
  3465.  
  3466. NIC personnel work closely with DARPA, DDN, BBNCC, network site
  3467. representatives, network protocol groups, vendors, contractors, government
  3468. agencies, and military sponsors to provide potential subscribers and new
  3469. users with pertinent network information. The NIC also serves as the DDN
  3470. Protocol Repository. Listed below are some of the services provided by the
  3471. NIC that may be of interest to new subscribers.
  3472.  
  3473.  
  3474. 6.1.1 User Assistance Service
  3475.  
  3476. The NIC provides user assistance services by telephone, U.S. mail, and
  3477. electronic mail. NIC staff can answer subscriber questions related to
  3478. connecting a host to the net, or general questions about using the net, and
  3479. can make referrals to the appropriate network representative for
  3480. administrative and technical questions. Additionally, the NIC is the
  3481. source for official ARPANET protocol documents (other than MIL STDs), and
  3482. is the network repository for RFCs and other technical documents.
  3483.  
  3484. The NIC User Assistance "hotline" telephone service is available Monday -
  3485. Friday, 7 am to 4 pm, Pacific time. The number is:
  3486.  
  3487. (800) 235-3155
  3488.  
  3489.  
  3490. 6.1.2 NIC Contacts
  3491.  
  3492. Correspondence may be sent by electronic or U.S. mail to:
  3493.  
  3494. Title Network Mailbox
  3495.  
  3496. User Assistance NIC@SRI-NIC.ARPA
  3497. User Registration, MILNET TAC Access REGISTRAR@SRI-NIC.ARPA
  3498. Network Naming and Addressing HOSTMASTER@SRI-NIC.ARPA
  3499. Feedback SUGGESTIONS@SRI-NIC.ARPA
  3500. Manager, NIC (415) 859-6287 FEINLER@SRI-NIC.ARPA
  3501.  
  3502. U.S. Mail Address
  3503. DDN Network Information Center
  3504. SRI International, Room EJ291
  3505. 333 Ravenswood Avenue
  3506. Menlo Park, CA 94025
  3507.  
  3508.  
  3509. 6.1.3 Online Servers
  3510.  
  3511.  
  3512. 6.1.3.1 TACNEWS
  3513.  
  3514. TACNEWS is a NIC online service that offers login help to TAC users,
  3515. includes the current list of ARPANET and MILNET TAC phone numbers, and
  3516. provides a mechanism for reading the DDN Newsletters and the DDN Management
  3517. Bulletins. Users should read these publications regularly to stay current
  3518. on DDN policies, announcements, and network news items. Access TACNEWS by
  3519. logging into a TAC and typing "@n<Return>" or by using the TELNET service
  3520. to connect to host
  3521. SRI-NIC (10.0.0.51) and typing "tacnews<Return>".
  3522.  
  3523.  
  3524. 6.1.3.2 WHOIS/NICNAME
  3525.  
  3526. WHOIS/NICNAME is a NIC program that provides an electronic "white pages" of
  3527. network users. It lists the name, network mailbox, U.S. mail address,
  3528. telephone number, and host for all registered users.
  3529.  
  3530. This program is available on the SRI-NIC host (10.0.0.51) and can be
  3531. reached by opening a TELNET connection and then by typing "whois<Return>".
  3532.  
  3533. WHOIS/NICNAME may also be run from a local host. WHOIS/NICNAME user
  3534. programs for several operating systems are available from the NIC. Contact
  3535. the NIC for copies and see RFC 954 [6] for details. Note that on most UNIX
  3536. systems the service is invoked by typing "nicname <Return>."
  3537.  
  3538.  
  3539. 6.1.3.3 Host Name Server
  3540.  
  3541. The NIC provides an internet Host Name Server on SRI-NIC (10.0.0.51) port
  3542. 101 decimal. This server delivers machine-translatable host
  3543. name/address/attribute information describing networks, gateways, and hosts
  3544. within the DDN. The server can deliver a single response or the entire
  3545. host table, depending upon the type of query sent. The server provides the
  3546. information outlined in RFC 952 [3] and is itself described in RFC 953
  3547. [10]. For further information on using the Host Name Server, make a TELNET
  3548. connection to SRI-NIC port 101 and type "help<Return>".
  3549.  
  3550.  
  3551. 6.1.4 Documents
  3552.  
  3553. The NIC edits, publishes, and distributes several documents useful to
  3554. ARPANET site representatives and users. Listed here are those of interest
  3555. to new or potential subscribers and users. (See Section 8 for additional
  3556. references.)
  3557.  
  3558. Documents of interest to subscribers:
  3559.  
  3560. DDN PROTOCOL HANDBOOK
  3561.  
  3562. The DDN Protocol Handbook [8] is a three-volume reference set of
  3563. experimental ARPANET and official DoD network protocols together with
  3564. implementation details and related background information. It can be
  3565. ordered prepaid from the NIC for $110.00, or from DTIC.
  3566.  
  3567. NOTE: The NIC publishes the DDN Protocol Handbook as a source
  3568. book for the convenience of implementers and network researchers.
  3569. Individual DoD military standards (MIL STDs) for protocols in
  3570. use on the DDN are officially issued by, and also are available
  3571. from, the Naval Publications and Forms Center, Code 3015, 5801
  3572. Tabor Ave., Philadelphia, PA 19120, (215) 697-3321.
  3573.  
  3574. TCP/IP IMPLEMENTATIONS AND VENDORS GUIDE
  3575.  
  3576. The Vendors Guide lists software and hardware implementations of the
  3577. DDN protocols, based upon information supplied by vendors. It is
  3578. available at no charge from the NIC for information purposes only.
  3579. Entry on this list does not imply endorsement.
  3580.  
  3581. RFCs (hardcopies)
  3582.  
  3583. Requests for Comments or RFCs are a set of network technical notes.
  3584. Hardcopies of RFCs can be ordered from the NIC. There is a $5.00
  3585. copying charge for each RFC under 100 pages, and a $10.00 copying
  3586. charge for each RFC over 100 pages. Orders should be prepaid to the
  3587. NIC.
  3588. Documents of interest to both subscribers and users:
  3589.  
  3590. DDN NEW USER GUIDE
  3591.  
  3592. The DDN New User Guide [12] is a brief guide to DDN network tools and
  3593. services designed to introduce users to the network. Available from
  3594. the NIC or DTIC.
  3595.  
  3596. DDN DIRECTORY
  3597.  
  3598. The DDN Directory [11] is a directory of users and hosts on the
  3599. network. It includes the name, address, network mailbox, and
  3600. telephone number for each registered network user (as of 1984).
  3601. Available for $10.00 prepaid to SRI International, DDN Network
  3602. Information Center, Room EJ291, Menlo Park, CA 94025, or from the
  3603. Defense Technical Information Center (DTIC).
  3604.  
  3605.  
  3606. 6.1.5 Online Files
  3607.  
  3608. The NIC maintains a number of online files which are available to network
  3609. subscribers via the ARPANET. These files contain information about
  3610. protocols, site personnel, hosts, and other subjects relevant to network
  3611. users. For more information on available public-access files, see the DDN
  3612. New User Guide [12], or contact the NIC User Assistance service.
  3613.  
  3614.  
  3615. 6.2 ARPANET Network Monitoring Center
  3616.  
  3617. The ARPANET Network Monitoring Center (AMC) is located within the Network
  3618. Operations Situation Room at BBN Communications Corporation (BBNCC) in
  3619. Cambridge, MA. AMC staff provide operations support for the ARPANET. The
  3620. AMC concentrates on real-time network management of the ARPANET by
  3621. maximizing the network operating efficiency. It provides:
  3622.  
  3623. - Operations and technical support
  3624.  
  3625. - Configuration management and software maintenance and enhancement
  3626.  
  3627. - Hardware maintenance
  3628.  
  3629. - Hardware requirements
  3630.  
  3631. - Network experiments.
  3632.  
  3633. AMC services include remote status monitoring, coordination of network
  3634. outage troubleshooting efforts, and 24-hour-per-day/7-day-per-week
  3635. technical assistance for network users. The AMC typically works on
  3636. backbone-related outages consisting of node and circuit problems, and
  3637. provides help in determining whether or not host connectivity problems are
  3638. network-related.
  3639.  
  3640. Contact the AMC for all network hardware problems, for hardware field
  3641. service, problems with host interfaces, or suspected node software
  3642. problems. Inform the AMC of any extended outages at your site, especially
  3643. those that may affect the PSN, and consult with them before carrying out
  3644. any experiment that may affect the network.
  3645.  
  3646. Users are encouraged to telephone the AMC rather than send electronic mail,
  3647. as this assures that the AMC will get all the necessary information, and
  3648. usually produces a faster response. (Note, however, that all orders for
  3649. backbone service must originate from the PMO.)
  3650.  
  3651. NOTE: The AMC will accept collect calls to (617) 661-0100.
  3652.  
  3653.  
  3654. 6.2.1 AMC Contacts
  3655.  
  3656. Title Telephone Network Mailbox
  3657.  
  3658. Network Monitoring Center (617) 661-0100 CONTROL@BBN-UNIX.ARPA
  3659. (617) 497-3571*
  3660. New Subscriber Liaison (617) 497-2633* DIPANFILO@BBN-UNIX.ARPA
  3661. Manager, NOC (617) 497-3117* JBURKE@BBN-UNIX.ARPA
  3662. * Now exchange 873 (May 89)
  3663.  
  3664.  
  3665. 6.3 Complaint Center/Unsatisfactory Service Reports
  3666.  
  3667. A complaint center terminal is maintained at the AMC to monitor messages
  3668. from users reporting problems or seeking assistance. (Send electronic mail
  3669. to GRIPES@BBN-UNIX.ARPA.) An additional channel for reporting
  3670. unsatisfactory service is the ARPANET Unsatisfactory Service Report (USR),
  3671. which is the formal mechanism for reporting operational deficiencies in the
  3672. ARPANET backbone. Problems or complaints which cannot be resolved through
  3673. normal channels should be reported by means of the USR. This may include
  3674. (but is not limited to) the following:
  3675.  
  3676. - Excessive response time
  3677.  
  3678. - Inadequate restoral procedures
  3679.  
  3680. - Unsatisfactory maintenance support.
  3681.  
  3682. The Subscriber must decide when service has reached an unsatisfactory
  3683. point, and must initiate the USR if the problem cannot be resolved. Send
  3684. the report online or by U.S. mail (see 7.1 for address) to DCA Code B652,
  3685. with information copies to the AMC (BBNCC) and any other activity deemed
  3686. appropriate by the originator.
  3687.  
  3688.  
  3689. SECTION 7. KEY CONTACTS
  3690.  
  3691.  
  3692. 7.1 DDN PMO Contacts
  3693.  
  3694. Code Title Telephone* Network Mailbox
  3695.  
  3696. B652 ARPANET POC 285-5233 ARPANETMGR@DDN1.ARPA
  3697. B600 Program Manager 285-5010 DCAB600@DDN1.ARPA
  3698. B641 Subscriber Requirements &
  3699. Integration Branch 285-5027 DCAB641@DDN1.ARPA
  3700. B602B Data Base and
  3701. Configuration Mgt. Branch 285-5017 DCAB602B@DDN1.ARPA
  3702. B652 Packet Switch Operations Branch 285-5225 DCAB652@DDN1.ARPA
  3703.  
  3704. [* Area Code (703), Autovon 356-xxxx]
  3705.  
  3706. Postal Mail: Defense Communications Agency
  3707. B652, Packet Switch Operations Branch
  3708. Washington, DC 20305
  3709. 7.2 DARPA Contacts
  3710.  
  3711. Title Telephone Network Mailbox
  3712.  
  3713. ARPANET COORDINATOR (202) 694-5921 BOWERS@USC-ISI.ARPA
  3714. DARPA POC (202) 694-3049 BAKER@USC-ISI.ARPA
  3715. Internet Advisory Board (202) 694-4002 PERRY@IPTO.ARPA
  3716. (617) 253-6003 DCLARK@MIT-MULTICS.ARPA
  3717. (213) 822-1511 POSTEL@USC-ISIF.ARPA
  3718. (703) 883-6000 CPERRY@MITRE.ARPA
  3719.  
  3720. Postal Mail: Defense Advanced Research Projects Agency
  3721. Information Processing Techniques Office
  3722. Attn: Lt. Col. Bob E. Baker
  3723. 1400 Wilson Boulevard
  3724. Arlington, VA 22209-2389
  3725.  
  3726. 7.3 Contacts for Specific Services
  3727.  
  3728. Telephone Network Mailbox
  3729.  
  3730. ARPANET Access Authorization (202) 694-3049 BAKER@USC-ISI.ARPA
  3731. ARPANET TAC Access Administration (202) 694-3049 BAKER@USC-ISI.ARPA
  3732. ARPANET New TAC Requests (202) 694-3049 BAKER@USC-ISI.ARPA
  3733. ARPANET Policy and Administration (202) 694-5050 KIGGENS@IPTO.ARPA
  3734. Backbone Equipment Information (617) 497-2633* DIPANFILO@BBN-UNIX.ARPA
  3735. Backbone Installation Schedule (703) 285-5231 ARPANETMGR@DDN1.ARPA
  3736. ARPANET Service Requests (202) 694-5921 BOWERS@USC-ISI.ARPA
  3737. General ARPANET Mgt. Information (703) 285-5233 ARPANETMGR@DDN1.ARPA
  3738. General ARPANET Information (800) 235-3155 NIC@SRI-NIC.ARPA
  3739. Node Problems (617) 661-0100 CONTROL@BBN-UNIX.ARPA
  3740. 8 Now 873-2633 (May 89)
  3741.  
  3742. SECTION 8. REFERENCES
  3743.  
  3744. Below is a bibliography of manuals and documents that are mentioned in this
  3745. document and are helpful in understanding the ARPANET and DDN. The
  3746. ordering number is given, when known, for items that may be ordered from
  3747. the Defense Technical Information Center (DTIC).
  3748.  
  3749. Documents marked (NIC) are available in hardcopy from the NIC; documents
  3750. marked (PMO) are available from the DDN PMO. Files available online at the
  3751. NIC (host SRI-NIC, 10.0.0.51) are indicated by giving the pathname in the
  3752. form [DIRECTORY:FILENAME.EXTENSION]. These files may be copied across the
  3753. network by using the File Transfer Protocol program (FTP). Call the NIC if
  3754. you need assistance with FTP.
  3755.  
  3756.  
  3757.  
  3758. 8.1 Cited References
  3759.  
  3760. [1] DDN Subscriber Interface Guide. Defense Data Network, Program
  3761. Management Office, Defense Communications Agency, Washington, DC,
  3762. 1983. (NIC) [AD-A132 877/2]
  3763.  
  3764. [2] RFC 796, Address Mappings. University of Southern California,
  3765. Information Sciences Institute, Marina del Rey, CA, September 1981.
  3766. (NIC) [RFC:RFC796.TXT]
  3767.  
  3768. [3] RFC 952, DoD Internet Host Table. SRI International, Menlo Park, CA,
  3769. October 1985. (NIC) [RFC:RFC952.TXT]
  3770.  
  3771. [4] RFC 920, Domain Requirements. University of Southern California,
  3772. Information Sciences Institute, Marina del Rey, CA, October 1984.
  3773. (NIC) [RFC:RFC920.TXT]
  3774.  
  3775. [5] RFC 921, Domain Name System Implementation Schedule - Revised.
  3776. University of Southern California, Information Sciences Institute,
  3777. Marina del Rey, CA, October 1984. (NIC) [RFC:RFC921.TXT]
  3778.  
  3779. [6] RFC 954, NICNAME/WHOIS. SRI International, Menlo Park, CA, October
  3780. 1985. (NIC) [RFC:RFC954.TXT]
  3781.  
  3782. [7] ARPANET Access Control, User Manual for the User Database Tool.
  3783. Defense Advanced Research Projects Agency, Arlington, VA, July 1984.
  3784. (NIC) [NETINFO:ARPA-TACACS.MAN]
  3785.  
  3786. [8] DDN Protocol Handbook. DDN Network Information Center, SRI
  3787. International, Menlo Park, CA, November 1985. (NIC, $110.00 domestic,
  3788. $130.00 overseas, prepaid)
  3789.  
  3790. [9] TCP/IP Implementations and Vendors Guide. DDN Network Information
  3791. Center, SRI International, Menlo Park, CA, 1985. (NIC) [NETINFO:TCP-
  3792. IP-IMPLEMENTATIONS.TXT]
  3793.  
  3794. [10] RFC 953, Hostnames Server. SRI International, Menlo Park, CA, October
  3795. 1985. (NIC) [RFC:RFC953.TXT]
  3796.  
  3797. [11] DDN Directory. DDN Network Information Center, SRI International,
  3798. Menlo Park, CA, 1984. (NIC, $10.00 prepaid) [AD-A148 213]
  3799.  
  3800. [12] DDN New User Guide. DDN Network Information Center, SRI
  3801. International, Menlo Park, CA, 1985. (NIC)
  3802.  
  3803.  
  3804.  
  3805. 8.2 Additional References
  3806.  
  3807. ARPANET Access Control, User Guide for the User Database Tool. Defense
  3808. Advanced Research Projects Agency, Arlington, VA, July 1984. (NIC)
  3809. [NETINFO:ARPA-TACACS.GUIDE]
  3810.  
  3811. Assigned Numbers, Information Sciences Institute, University of Southern
  3812. California, Marina del Rey, CA. (NIC) [RFC:ASSIGNED-NUMBERS.TXT]
  3813.  
  3814. DDN Defense Data Network Brochure. Defense Data Network, Program
  3815. Management Office, Defense Communications Agency, Washington, DC, 1984.
  3816. (NIC) (PMO)
  3817.  
  3818. DDN Subscriber Security Guide. Defense Data Network, Program Management
  3819. Office, Defense Communications Agency, Washington, DC, 1983. (NIC)
  3820. [AD-A152 524]
  3821.  
  3822. DDN User's Planning Guide. Defense Data Network, Program Management
  3823. Office, Defense Communications Agency, Washington, DC, 1985. (PMO)
  3824.  
  3825. DDN X.25 Host Interface Specification. Defense Data Network, Program
  3826. Management Office, Defense Communications Agency, Washington, DC, 1983.
  3827. (NIC) [NETINFO:X25.DOC] [AD-A137 427]
  3828.  
  3829. A HISTORY OF THE ARPANET: THE FIRST DECADE, Report No. 4799. Bolt Beranek
  3830. and Newman Inc., Cambridge, MA, 1981. [AD-A115-440]
  3831.  
  3832. Instructions for Network User Registration Drive (MILNET). DDN Network
  3833. Information Center, SRI International, Menlo Park, CA, October 1983. (NIC)
  3834. [NETINFO:MIL-TACACS-INSTRUCTIONS.TXT]
  3835.  
  3836. Submission of Telecommunications Service Requests, DCA Circular 310-130-1.
  3837. Defense Communications Agency, Washington, DC, 1983. (PMO)
  3838.  
  3839. TAC Users' Guide, Report No. 4780. Bolt Beranek and Newman Inc.,
  3840. Cambridge, MA, 1982. (NIC) [NETINFO:TAC-USER.DOC] [AD-A147 366]
  3841.  
  3842.  
  3843. SECTION 9. GLOSSARY
  3844.  
  3845.  
  3846. Listed here are terms and acronyms used in this document. Definitions are
  3847. given for terms, whereas organizational acronyms are generally just
  3848. expanded to their full length.
  3849.  
  3850. AMC ARPANET Network Monitoring Center, located at BBNCC,
  3851. Cambridge, MA.
  3852.  
  3853. ARPA see DARPA.
  3854.  
  3855. ARPANET DARPA's packet-switched host-to-host digital
  3856. communications network which links a wide variety of
  3857. DoD-sponsored computers at research centers around the
  3858. world.
  3859.  
  3860. BBNCC Bolt Beranek and Newman Communications Corporation; the
  3861. company that provides network node hardware, software and
  3862. field servicing, and manages the ARPANET Network
  3863. Monitoring Center. Early contributor to the development
  3864. of the DDN.
  3865.  
  3866. backbone The nodes (see below) and the leased telephone lines and
  3867. satellites connecting them, which form the core of the
  3868. DDN.
  3869.  
  3870. CCG DCA Configuration Control Group, the group which screens
  3871. and approves changes to the backbone configuration as
  3872. needed.
  3873.  
  3874. DARPA Defense Advanced Research Projects Agency.
  3875.  
  3876. DCA Defense Communications Agency.
  3877.  
  3878. DCEC Defense Communications Engineering Center.
  3879.  
  3880. DDN Defense Data Network; the DoD's host-to-host, packet-
  3881. switched data communications network. The DDN
  3882. interconnects several military networks, one of which is
  3883. the ARPANET.
  3884.  
  3885. DDN PMO Defense Data Network Program Management Office; the
  3886. office within the DCA responsible for management of the
  3887. DDN.
  3888.  
  3889. DECCO Defense Commercial Communications Office.
  3890.  
  3891. DoD Department of Defense.
  3892.  
  3893. Feeder TSR Preliminary Telecommunications Service Request (TSR) used
  3894. by DARPA to request ARPANET service from the DDN PMO.
  3895.  
  3896. FTP File Transfer Protocol; the network protocol that allows
  3897. host-to-host file transfer across the network without
  3898. disrupting the format of the file being transferred.
  3899.  
  3900. gateway A special computer which interconnects two networks,
  3901. performs any needed protocol conversion or address
  3902. translation, and administers access control between them.
  3903.  
  3904. HAdmin Host Administrator; see Appendix for a list of Host
  3905. Administrator duties.
  3906.  
  3907. HAF Host Approved Form provided by DARPA IPTO.
  3908.  
  3909. host Computer directly connected to a PSN port on the DDN.
  3910.  
  3911. HOSTMASTER Mailbox at the NIC for host registration, name, address,
  3912. and other changes to information in the DDN host table.
  3913.  
  3914. hostname Name which officially identifies a host computer attached
  3915. to the DDN.
  3916.  
  3917. IMP Interface Message Processor; now called Packet Switch
  3918. Node or PSN, which see.
  3919.  
  3920. INCO INstallation Check Out kits; containers of node spare
  3921. parts.
  3922.  
  3923. Internet Protocol Standard that allows Internet networks running different
  3924. protocols to connect and communicate with each other.
  3925.  
  3926. IPTO Information Processing Techniques Office; the DARPA
  3927. office that administers and sets policy for the ARPANET.
  3928.  
  3929. ISI University of Southern California Information Sciences
  3930. Institute.
  3931.  
  3932. LAN Local Area Network; a private network that connects data
  3933. processing equipment in a limited geographic area (e.g.
  3934. an office, building, or complex of buildings).
  3935.  
  3936. M/A-COM M/A-COM Linkabit, Incorporated.
  3937.  
  3938. MIT Massachusetts Institute of Technology.
  3939.  
  3940. MIL-STD Military Standard; the specification for a standard
  3941. (including network protocols) that is to be implemented
  3942. for a military system or as a product used by the DoD.
  3943.  
  3944. MILNET Unclassified operational MILitary NETwork, which is part
  3945. of the DDN.
  3946.  
  3947. MITRE MITRE Corporation.
  3948.  
  3949. NCAN Network Change Acknowledgement Notice.
  3950.  
  3951. NCD Network Change Directive.
  3952.  
  3953. NCR Network Change Request.
  3954.  
  3955. NIC Network Information Center located at SRI International,
  3956. Menlo Park, CA, under contract to the DDN PMO.
  3957.  
  3958. node Packet switch; a PSN, TAC, mail bridge, or combination of
  3959. these.
  3960.  
  3961. NSC Node Site Coordinator; local DDN representative assigned
  3962. to a TAC or PSN who is responsible for access control and
  3963. accountability for all DDN-owned hardware, software and
  3964. circuits located at the node site. (See Appendix for a
  3965. list of NSC duties).
  3966.  
  3967. OSD Office of the Secretary of Defense.
  3968.  
  3969. PDC Program Designator Code; code used to identify the
  3970. funding activity responsible for reimbursing the cost of
  3971. backbone charges.
  3972.  
  3973. PMO Program Management Office of the DDN.
  3974.  
  3975. POC Point Of Contact.
  3976.  
  3977. PSN Packet Switch Node; a store-and-forward packet switch to
  3978. which several host computers can be connected.
  3979.  
  3980. REGISTRAR Mailbox at the NIC for user registration, name, address,
  3981. and other changes to information in the registration
  3982. (WHOIS) database.
  3983.  
  3984. RFC Requests For Comments; a set of technical notes
  3985. describing networking research carried out by the DARPA
  3986. network community (available from the NIC).
  3987.  
  3988. RP Responsible Person; person appointed by DARPA to register
  3989. ARPANET TAC users in a particular organization.
  3990.  
  3991. site Organization or facility where host or node equipment is
  3992. located.
  3993.  
  3994. SMTP Simple Mail Transfer Protocol; the official DoD mail
  3995. protocol.
  3996.  
  3997. socket Logical address of a port providing access to a specific
  3998. device or service on a host.
  3999.  
  4000. SRI-NIC The DDN Network Information Center host computer, located
  4001. at SRI International, Menlo Park, CA. This host is
  4002. multi-homed on both the ARPANET and the MILNET, and
  4003. provides information services to both.
  4004.  
  4005. SRI SRI International; location of the DDN Network
  4006. Information Center and early contributor to the
  4007. development of the ARPANET and the DDN.
  4008.  
  4009. subscriber A system connected to the ARPANET, and the individuals
  4010. responsible for that system.
  4011.  
  4012. TAC Terminal Access Controller; a special host attached to a
  4013. PSN that lets terminals connect directly to the DDN.
  4014.  
  4015. TAC Access Code Password assigned to TAC users for TAC login.
  4016.  
  4017. TAC USER ID Alphanumeric character string that identifies a TAC user
  4018. upon TAC login.
  4019.  
  4020. TCP/IP Transmission Control Protocol/Internet Protocol; two of
  4021. the DoD standard network protocols.
  4022.  
  4023. TELCO Telephone company.
  4024.  
  4025. TELNET DoD protocol for opening a transparent (virtual terminal)
  4026. connection from one host to another. Also refers to the
  4027. program implementation that provides this service.
  4028.  
  4029. TIP Terminal Interface Processor; predecessor of the TAC,
  4030. serving a similar function.
  4031.  
  4032. TSO Telecommunications Service Order; DCA authorization to
  4033. start, change, or discontinue circuits or trunks.
  4034.  
  4035. TSR Telecommunications Service Request; a valid, approved and
  4036. funded telecommunications service requirement submitted
  4037. by DCA through DECCO to the telephone companies.
  4038.  
  4039. UCL University College London, England.
  4040.  
  4041. UCLA University of California, Los Angeles.
  4042.  
  4043. UDB User Database Tool for registering ARPANET users for TAC
  4044. Access.
  4045.  
  4046. USR Unsatisfactory Service Report; report sent to the DDN PMO
  4047. by a network subscriber to report unsatisfactory network
  4048. service.
  4049.  
  4050.  
  4051. APPENDIX. SITE PERSONNEL DUTIES
  4052.  
  4053. This appendix describes the duties of ARPANET personnel at host and node
  4054. locations.
  4055.  
  4056. 1. Responsible Person
  4057.  
  4058. The person in a particular organization appointed by DARPA who has
  4059. authority to give ARPANET users permission for TAC access is called a
  4060. Responsible Person (RP). RP's are representatives of organizations
  4061. involved in DARPA research programs.
  4062.  
  4063. Responsibilities:
  4064.  
  4065. a. For ARPANET TAC Access, a \Responsible Person" has been
  4066. identified in each government and contractor organization whose
  4067. members need to use ARPANET TACs. The Responsible Person grants
  4068. permission to use an APRANET TAC to members of his or her
  4069. organization by updating the ARPANET user database (which is
  4070. different from the NIC User Registration database). A \User
  4071. Database Tool" is used by the Responsible Persons or their
  4072. designated alternates to add, delete, and change information
  4073. describing authorized ARPANET TAC users.
  4074.  
  4075. b. The motivation for the organization-oriented approach to
  4076. authorization of TAC usage is to put the authorization in the
  4077. hands of the people best able to validate the requirement for
  4078. access. The \Responsible Persons" must make sure that TAC
  4079. access is granted only to people who are authorized to use the
  4080. ARPANET, and that such access conforms to guidelines on the
  4081. purpose of the ARPANET and the proper use of ARPANET TACs.
  4082.  
  4083. 2. Host Administrator
  4084.  
  4085. The Host Administrator (HAdmin) has administrative responsibility for the
  4086. policies, practices, and concerns of a host or hosts connected to the DDN,
  4087. including responsibility for that host's DDN users.
  4088.  
  4089. Responsibilities:
  4090.  
  4091. a. Assists the DDN PMO by ensuring that network policies and
  4092. procedures are observed by the users. Ensures that all of his
  4093. or her host users, who are using the network or the network
  4094. TACs, have been authorized for ARPANET access and are registered
  4095. in the NIC User Registration database.
  4096.  
  4097. b. Manages the network access control procedures and password
  4098. system, and is responsible for reporting network-related host
  4099. break-ins and assisting with investigative effort as needed.
  4100.  
  4101. c. Coordinates with the DDN PMO on installation and removal of
  4102. hosts on the DDN; and also coordinates installation of, or
  4103. changes to, host software that has direct or indirect impact on
  4104. the DDN. The HAdmin provides the DDN PMO and the NIC with
  4105. required descriptive information for each new host addition or
  4106. host change, and coordinates the host certification procedure
  4107. with the DDN PMO prior to passing traffic on the network. The
  4108. HAdmin is responsible for the proper implementation and
  4109. maintenance of DDN protocols at the host level.
  4110.  
  4111. d. Serves as local point of contact for his or her respective hosts
  4112. and local users and coordinates suspected network-related
  4113. problems directly with the network monitoring center.
  4114.  
  4115. e. Provides network information to the NIC, and assists local users
  4116. and other interested personnel with network-related matters.
  4117.  
  4118. 3. Node Site Coordinator
  4119.  
  4120. The Node Site Coordinator is designated as having site access control, DDN
  4121. hardware and software accountability, and coordination responsibility for
  4122. the DDN circuits and equipment located at the DDN Node Site.
  4123.  
  4124. Responsibilities:
  4125.  
  4126. a. Directly interacts with DDN management channels and the network
  4127. monitoring center on network communications operational matters.
  4128.  
  4129. b. Provides the node site's single point of contact for network
  4130. backbone matters. (Delegation of responsibilities to
  4131. individuals within the node site is the NSC's prerogative,
  4132. however, the NSC is still that node site's single point of
  4133. contact for network backbone matters).
  4134.  
  4135. c. Accountable for DDN node hardware and software (cassette tapes).
  4136.  
  4137. d. Authorizes and ensures personnel access to the node site.
  4138.  
  4139. e. Supervises, assists, coordinates or monitors the installation
  4140. and implementation of node hardware, software, and circuits.
  4141.  
  4142. f. Performs administrative functions, as required.
  4143.  
  4144. g. Ensures the node site has a single place of contact for the DDN
  4145. or its representatives to obtain local site assistance on a
  4146. 24-hour, 7-day a week basis, when required. (In the isolated
  4147. case that the node site is located in a facility that is not
  4148. manned on a 24-hour, 7-day a week basis, the NSC ensures that
  4149. someone at the place of contact can obtain local site assistance
  4150. within two hours).
  4151.  
  4152. h. Provides for accountability and access control of the PSN/TAC
  4153. system cassette tapes (IMPLOD and SYSTEM).
  4154.  
  4155. i. Provides for custodial care of the on-site container(s) of node
  4156. spare parts, known as INCO (INstallation Check Out) kits.
  4157. (Normally, these kits are located at selected overseas sites).
  4158.  
  4159. j. Provides site coordination and authorizes personnel with site
  4160. access for installation, removal, and modifications to DDN
  4161. hardware or circuits, for emergency or scheduled preventive
  4162. maintenance, as directed by DCA or the designated network
  4163. monitoring center.
  4164.  
  4165. k. Ensures that local site assistance is provided, when required by
  4166. the network monitoring center, for corrective actions during
  4167. node hardware or circuit degradation or outages, which are
  4168. beyond the capability of the network monitoring center to
  4169. correct. For instance, on instruction from the network
  4170. monitoring center due to PSN or circuit failure, the local site
  4171. representative may be requested to press reset buttons on the
  4172. back of PSN/TAC chassis, observe status lights, insert/remove
  4173. the tape cassette (normally always in reader), switch cables,
  4174. loop modems (normally on TAC connections), loop modems on
  4175. covered circuits in selected locations or coordinate restoration
  4176. actions with local field-site communications
  4177. technicians/organizations.
  4178.  
  4179. l. Ensures that DDN hardware, software, or circuits are not
  4180. altered, moved or tampered with, without proper authorization.
  4181.  
  4182. m. Monitors investigative reports related to DDN hardware and
  4183. software located at the node site.
  4184.  
  4185. n. Performs limited administrative functions such as: (1)
  4186. maintaining and being aware of operating instructions issued by
  4187. DCA, the Network Information Center (NIC) on behalf of the DDN
  4188. PMO, and the network monitoring center; (2) maintaining a
  4189. contact list of telephone numbers for the local TELCO service
  4190. office or DCS technical control, network monitoring center, and
  4191. the Host Administrator for each host connected to the DDN PSN(s)
  4192. at that node site; (3) maintaining a \Node Site Access Roster,"
  4193. which lists all personnel authorized to have access to the node
  4194. site and associated equipment.
  4195.  
  4196. INDEX
  4197.  
  4198. Access controls
  4199. host 4
  4200. TAC 4
  4201. AMC 15
  4202. ARPANET
  4203. access and use 4
  4204. description 3
  4205. ARPANET Network Monitoring Center
  4206. collect calls 15
  4207. description 15
  4208. telephone numbers 15
  4209.  
  4210. Bug fixes 11
  4211.  
  4212. CCG 11, 21
  4213. Complaints
  4214. Unsatisfactory Service Reports
  4215. 15
  4216. Configuration Control Group 11
  4217. Costs 6
  4218.  
  4219. DARPA
  4220. addresses and phone numbers
  4221. 17
  4222. mailing address 6
  4223. DARPA IPTO
  4224. mission 3
  4225. responsibilities 3
  4226. DCA
  4227. description 3
  4228. DDN PMO 3
  4229. responsibilities 3
  4230. DDN 3
  4231. Directory 15
  4232. Network Information Center
  4233. 13
  4234. New User Guide 15
  4235. Protocol Handbook 14
  4236. DDN Network Information Center
  4237. 13
  4238. toll free number 13
  4239. DDN PMO
  4240. contacts 17
  4241. mailing address 6
  4242. Defense Communications Agency 3
  4243. Domains 7
  4244.  
  4245. Feeder TSR 6
  4246.  
  4247. Gateway registration 7
  4248.  
  4249. HAF 5
  4250. Host address 7
  4251. Host Administrator
  4252. duties 23
  4253. Host Name Server 14
  4254. function 7
  4255. Host table
  4256. updating 7
  4257.  
  4258. IAB
  4259. responsibilities 3
  4260. task forces 3
  4261. Information Processing Techniques
  4262. Office
  4263. see also IPTO 3
  4264. Internet Research Program
  4265. 3
  4266. IPTO
  4267. mission 3
  4268. responsibilities 3, 5
  4269.  
  4270. Local Area Networks 7
  4271.  
  4272. MIL STD 9
  4273. MILNET 3
  4274.  
  4275. Naming domains 7
  4276. NCD
  4277. 5
  4278. confirmation 5
  4279. NCR
  4280. generation of 5
  4281. Network Monitoring Center 15
  4282. Network Operations Center
  4283. telephone numbers 15
  4284. NIC
  4285. getting Host tables from 7
  4286. Node
  4287. installation 5
  4288. problems 15
  4289. software modifications 11
  4290. Node Site Coordinator
  4291. duties 23
  4292. requirement for 5
  4293. NSC
  4294. requirement for 5
  4295.  
  4296. Protocols
  4297. ARPANET 9
  4298. documentation 9
  4299. Internet 9
  4300. vendors 9
  4301. PSN
  4302. modifications 11
  4303. port assignment 7
  4304. port changes 7
  4305. relation to network number 7
  4306.  
  4307. REGISTER 8
  4308. Registration template
  4309. user 7
  4310. Registration 7
  4311. host 7
  4312. TAC access 8
  4313. user 7
  4314. user - REGISTER 8
  4315. user - template 7
  4316. Registration template
  4317. host 7
  4318. Host Administrator 7
  4319. Registration template,
  4320. user 7
  4321. Request For Comments 9
  4322. Responsible Person 4
  4323. duties 23
  4324. RFC
  4325. hardcopies 14
  4326.  
  4327. Software modifications 11
  4328. Subscriber access
  4329. time required 5
  4330. Subscriber access procedures 5
  4331.  
  4332. TAC 4
  4333. TACNEWS 14
  4334. TCP/IP
  4335. Implementations and Vendors
  4336. Guide 14
  4337. Telephone numbers 17
  4338. Terminal connection 7
  4339. TSO
  4340. function 5
  4341. receipt of 5
  4342. TSR
  4343. function 5
  4344. obtaining 5
  4345. submission 5
  4346.  
  4347. UDB
  4348. registration 8
  4349. Unsatisfactory Service Reports
  4350. 15
  4351. User Data Base
  4352. ARPANET 4
  4353. User Data Base
  4354. registration 8
  4355.  
  4356. Vendors Guide
  4357. TCP/IP 14
  4358.  
  4359. WHOIS/NICNAME 14
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!