26-Apr-83 03:54:06-PDT,15000;000000000001
Return-path: <NIC@SRI-NIC>
Mail-From: SMTP created at 26-Apr-83 03:51:38
Received: FROM SRI-NIC BY USC-ISIF.ARPA WITH TCP ; 26 Apr 83 03:51:43 PDT
Date: 25 Apr 1983 2002-PDT
From: NIC at SRI-NIC
Subject: DDN Newsletter No. 25
To: DDN-NEWS-DIST: ;
===============================================================================
DDN-NEWS 25 NETWORK INFO CENTER for
15 April 1983 DCA DDN Program Mgmt Office
(NIC@SRI-NIC)
(415) 859-3695
DEFENSE DATA NETWORK NEWSLETTER
(Maximum Distribution Requested. The DDN Newsletter is published by the
Network Information Center under DCA contract. For subscription, contact
NIC@SRI-NIC. Back issues obtainable by FTP from the directory <DDN-NEWS>
at SRI-NIC [10.0.0.73].)
==============================================================================
Section I. OFFICIAL
Topic: - New Format for Newsletter
- Subscriptions Wanted.
- New TAC Inventory Report Requirement
Section II. UNOFFICIAL
Topic: - DDN-DIGEST
-----------------------------------------------------------------------------
******OFFICIAL******
NEW FORMAT FOR NEWSLETTER.
With this issue, the DoD NETWORK NEWSLETTER becomes the DEFENSE DATA NETWORK
NEWSLETTER, marking the official beginning of the DDN in April 1983. Though
directed primarily at the numerous subnets making up the DDN, the DDN
Newsletter, for the foreseeable future, will continue to serve as a source of
information for users of the ARPANET as well. This, and future editions of the
DDN Newsletter will be published in a new format, with different sections for
OFFICIAL and UNOFFICIAL articles. Articles in the OFFICIAL section will
contain policy announcements and other general information which is being
disseminated for review, adherence, and possible response. Articles in the
UNOFFICIAL Section will contain general information items which do not
necessarily represent official policy or practice. As space permits, this
section may include items submitted by users. Such items should be as brief
as possible, and should be forwarded to NIC@SRI-NIC for consideration. All
articles for the UNOFFICIAL section should be signed and provide the
organizational affiliation of the contributor.
----------
SUBSCRIPTIONS WANTED.
Along with the change in name and format, the DDN Newsletter gains a greatly
expanded role as the official means by which the DDN Program Management Office
communicates with DDN and ARPANET users. To this end, a significant increase
in circulation is sought. Two means of accomplishing this are feasible.
The first means of increasing circulation is by remailing at the host level.
This clearly is the more efficient method, and avoids building the mailing list
at the NIC into something unmanageable. Host Administrators and Technical
Liaison personnel are therefore requested, where feasible, to remail the DDN
Newsletter to all account holders on their host. Remailing is particularly
solicited for this edition of the DDN-NEWS.
The second means is by direct mailing from the NIC. Although not the desired
approach, an increase in size of the NIC mailing list is feasible within
limits. Users with accounts at hosts which cannot provide remailing of the
newsletter may, therefore, obtain a copy directly from the NIC by submitting a
request for subscription directly to NIC@SRI-NIC.
----------
NEW TAC INVENTORY REPORT REQUIREMENT
In Newsletter 22, the March submission of the Tac Inventory Report
was deferred pending reevaluation and revision of the requirements and format
for the report. That process having been completed, the new requirements and
format are as follows.
Who: The Tac Inventory Report is submitted by the Technical Liaison
for each TAC. Reports are required for all TACs,
whether on the MILNET or ARPANET. TAC users, especially of
hard-wired terminal ports, are requested to assist the TAC Liaison
in gathering the information for this report.
What: See format below.
When: The first report is required not later than 27 May 1983.
Subsequent reports are required by the end of each quarter
thereafter beginning with the September submission.
Where: Submit reports via electronic mail to the mailbox
TACSTATRPT@SRI-NIC.
How: The complete report must be submitted each time and must
be complete and accurate. Incomplete reports will require
resubmission.
Why: During the next year, we will be engaged in a massive rehoming
effort to relocate MILNET users to MILNET TACs and ARPANET users
to ARPANET TACs. We need the information requested in this report
in order to accomplish this task with least disruption to the
users affected. Your assistance in providing us with this data
in the manner and timeliness requested will be a major
contribution in the effort to accomplish this. The importance
of this first submission of the revised TAC Inventory Report
cannot (repeat) cannot be overemphasized. This data will
provide the basis for exhaustive analysis which is vital
to successful network partitioning. Failure to provide
complete and timely information will result in denial of service
to TAC users.
----------------------------------------------------------------------------
TAC PORT INVENTORY REPORT
ITEM:
-----
1. TAC Name and Net Address:
2. Date of Report:
3. TAC Liaison Information
a. Name:
b. U. S. Mail Address:
c. Net Mail Address:
d. Telephone -
Commercial:
AUTOVON:
4. PORT INVENTORY - PART I.
1. 2. 3. 4. 5.
PORT TYPE MODEM ID TELCO ID USER ID
---- ---- -------------- ------------------ ----------------------------
See See See Note 3. See Note 4. See Note 5.
Note Note
1. 2.
NOTE 1. Enter the port number for every port on the TAC, whether or not that
port is in use. For ports which are not in use, enter the statement:
"Port not in use" following the port number. For hardwired ports
connected to a multiplexor or comparible device, enter "See Part II". For
other ports, enter the information in Columns 2 - 5 as requested.
NOTE 2. Enter D for dial-up ports or H for Hard-wired ports.
NOTE 3. Enter Baud Rate, Manufacturer, and Model of the modem in that
order, on separate lines as shown. Modems which will accept more than one
speed should enter both speeds separated by a slash.
NOTE 4. For Dial-up ports, enter the telephone number, including area
code. For Hardwired ports, enter the word "Local" if no telephone circuit
is involved; or the circuit number and vendor if a circuit is leased
from the telephone company.
NOTE 5. For dial-up ports, enter N/A for not applicable. For Hard-wired
ports, enter the following information on separate lines as shown in the
sample entries for Part I.
Name of responsible user:
Organization of user and
U.S. Mail Address:
Netmail address:
Telephone (commercial
and AUTOVON):
Net Alignment:
Terminal location:
SAMPLE ENTRIES - PART I.
1. 2. 3. 4. 5.
PORT TYPE MODEM ID TELCO ID USER ID
---- ---- -------------- ------------------ ----------------------------
01. Port not in use.
02. Port not in use.
03. Port not in use.
04. D 300/1200 (123)777-XXXX N/A
Prentice
212A
05. D 300/1200 (123)456-7890 N/A
Prentice
212A
06. H None Local Dr J. W. Sears
Armstrong Univ, C.S. Dept.
4400 University Blvd
Bethany, VA 22047
Smith@Armstrong
(703)437-XXXX
ARPANET
TERMINAL LOCATION:
Room 357, C.S. Bldg, Armstrong University.
07. H 1200 37FD3501 Dr. Dee Colvett
Bell Armstrong Univ, Math Dept.
202T 4400 University Blvd
Bethany, VA 22047
Colvett@Armstrong
(703)437-YYYY
ARPANET
TERMINAL LOCATION:
Room 314, Ganus Hall, Armstrong U.
08. H 1200 37FD3501 Col Jerry Jones
Bell C&P Telco HQ DCA, Code 1234
202T Wash, D. C. 20305
JJones@DDN-1
(202)692-XXXX
AV 222-XXXX
MILNET
TERMINAL LOCATION:
Room 5602, 8th and Courthouse Rd., Arlington, VA.
09. See Part II.
10. Port not in use.
11. See Part II.
12. See Part II.
13. Port not in use.
14. See Part II.
5. PORT INVENTORY - PART II.
1. 2. 3. 4. 5.
PORT MODEM MUX MODEM USER ID
---- -------------- -------------- -------------- --------------------------
See See Note 7. See Note 8. See Note 9. See Note 5. Above.
Note
6.
NOTE 6. Enter TAC port number from PART I. Port numbers connected
to the same multiplexor should be grouped together even if not in sequence.
NOTE 7. Enter MUX channel, baud rate of modem connection to TAC, Manufacturer,
and Model in that order.
NOTE 8. Enter Baud rate, Manufacturer, and Model of the multiplexor;
and Telco circuit number and vendor.
NOTE 9. For all entries, enter MUX channel, baud rate of modem on terminal
side, manufacturer, and model in that order. For users who are local to the
MUX, add the word "local". For users who are connected via hard-wired phone
line, add circuit number and vendor. For MUX channels which terminate in
dial-up equipment, add the dial-in telephone number and enter N/A in column 5.
SAMPLE ENTRIES - PART II.
1. 2. 3. 4. 5.
PORT MODEM MUX MODEM USER ID
---- -------------- -------------- -------------- --------------------------
09 Cnl 1 4800 Cnl 1 Major Don Berryhill
1200 MICOM 1200 3040 Comm SQ/CC
RIXON 800 RIXON Searcy AFS, AR 72941
C212A 41FDDM15873 C212A Berryhill@SAR-1
AT&T Local (501)474-XXXX
AV777-XXXX
MILNET
TERMINAL LOCATION:
Rm 4, Bldg 1962, Searcy AFS, AR.
11 Cnl 2 Same as 09 Cnl 2 Capt Joe Pryor
1200 1200 3040 Comm Sq/DO
RIXON RIXON Searcy AFS, AR 72941
C212A C212A (501)474-YYYY
AV777-YYYY
MILNET
TERMINAL LOCATION:
Rm 201, Benson Bldg, Searcy AFS, AR.
12 Cnl 3 Same as 09 Cnl 3 N/A
300/1200 300/1200
Bell Bell
212A 212A
(501)474-ZZZZ
14 Cnl 4 Same as 09 Cnl 4
Not in use
6. Other Comments: (Use this section to appraise us of any other information
pertaining to your TAC users which you believe we should be aware of):
-----------------------------------------------------------------------------
In most cases, providing this information will require direct contact between
the Liaison and the user. It is extremely important that all of the
information requested be provided. Without it, we will be unable to
rehome users to their appropriate net, and this will result in denial of
service to those hard-wired TAC users who remain connected to the wrong net.
Question pertaining to this report may be directed to Major Parker at
(703)285-5133 or AV 356-5133, or by netmail to GPARK@BBNC.
----------
******UNOFFICIAL******
DDN-DIGEST.
Our thanks to Steve Nelson and Pete Vayda for their timely and excellent
suggestion that we begin a DDN-DIGEST, similar to the TCP-IP Digest published
by Mike Muuss, to keep you, the users, informed about the DDN and to get
feedback from you as well. To this end, we have established the mailbox
DDN-NEWS@SRI-NIC to receive questions, comments, and the like which you want
to send us. These we will incorporate in the UNOFFICIAL section of the
Newsletter (allowing for duplication) along with an answer from an appropriate
person. More on this in future Newsletters, but in the meanwhile, the mailbox
is there and ready for your use.
DARRYL HENRY
DCA Code B627
DDN-PMO System Development Branch
-------
