ves@MITRE-BEDFORD.ARPA (Sovinsky) (04/01/88)
Introductory Note:
The Standard System Center is preparing an Air Force-wide acquisition
of LAN interface software (ULANA compatible) and PC security
hardware/software.
The equipment performance specification which follows this
introductory note is provided for comments and suggestions. This is
an informal medium, and the Standard Systems Center will not be held
accountable for the disposition of the comments received. This is
provided as a courtesy to the vendor community and provides them a
chance to point out any errors we may have made. The Standard Systems
Center in no way has to provide any response to the vendor about the
comments received.
The suspense date for comments is April 7, 1988. Your prompt action
will be appreciated. You may direct your comments to the following
two points of contact:
Technical Issues: Lt Robinson, 205-279-4555
Contracting Issues: Dwynell Streeter 205-279-5520
You may also contact the following staff at MITRE:
Stan Ames 617-271-3182
Vivian Sovinsky 617-271-7780
We apologize for attaching to this message the complete draft
specification which is about ten pages in length.
---------------------------------------------------------------------
HQ SSC/SSMC EPS-88-001
Gunter AFS, AL 36114 08 Mar 1988
DRAFT EQUIPMENT PERFORMANCE SPECIFICATION
FOR
LAN SOFTWARE AND SECURITY MODULE CONTRACT
1.0. SCOPE.
1.1. Intent. This aquisition is for disk operating system (DOS) hosts
with integral ULANA host attachments. This Equipment Performance
Specification (EPS) defines the requirement to obtain local area network
(LAN) software and a microcomputer security module through an indefinite
delivery, indefinite quantity requirements contract. This shall be a
procurement of commercial off-the-shelf (COTS) products. In order to be
considered COTS, not more than 10 percent of the original code may be
changed or added. (For example, if the original program consisted of
10,000 lines of code, not more than 1,000 lines can be changed or added.)
1.2. Documents. Supporting documentation for the operation of the
packages shall be delivered in accordance with paragraph 3.3.
2.0. APPLICABLE DOCUMENTS.
2.1. Government Documents. The following documents of the exact issue
shown (or successors where indicated) form a part of this specification to
the extent specified elsewhere in this specification. In the event of a
conflict between the documents referenced below and the contents of this
specification, the information in this document shall be considered
superseding requirements.
2.1.1. Military Standards.
MIL-STD-1777, 12 Aug 83, Internet Protocol (IP).
MIL-STD-1778, 12 Aug 83, Transmission Control Protocol (TCP).
MIL-STD-1780, 10 May 84, File Transfer Protocol (FTP).
MIL-STD-1781, 10 May 84, Simple Mail Transfer Protocol (SMTP).
MIL-STD-1782, 10 May 84, TELNET Protocol.
MIL-STD-129J, 25 Nov 86, Marking for Shipment and Storage.
2.1.2. Requests for Comment (RFC).
RFC 904 (or successor), Apr 87, Exterior Gateway Protocols.
RFC 1001, 1002, Feb 87, NETBIOS.
RFC 960 (or successor), Dec 85, Assigned Numbers.
RFC 768, Aug 80, User Datagram Protocol.
RFC 792, Sep 81, Internet Control Message Protocol.
RFC 821, Aug 82, Simple Mail Transfer Protocol.
2.1.3. Government Specifications.
System Specification for the Air Force Unified Local Area Network
Architecture (ULANA I), 17 Apr 87.
EPS-88-001
08 Mar 1988
System Specification for the Standard Multiuser Small Computer
Requirements Contract (SMSCRC), 20 Feb 87.
2.1.4. Other Standards.
Institute of Electrical and Electronics Engineers Standard 802.3 (IEEE
802.3), 1985.
2.2. Availability of Applicable Documents. The specifications,
standards, and other documents cited herein that are not provided as a
part of the solicitation and are not readily obtainable may be examined at
HQ SSC/PKB, Bldg 1011, Gunter AFS AL 36114.
3.0. REQUIREMENTS.
3.1. General. The LAN software shall allow users in various locations to
communicate with one another, share data and executable files, and share
peripherals via the ULANA network. The security module shall prevent
unauthorized access to workstations. The government shall have the right
to make working backup copies of each software package purchased for its
use. Copy protected software is not acceptable. The backup copies must
execute in the same manner as the originally shipped disks.
3.2. Operational Concept. The contractor(s) shall provide software and
documentation as described in the following paragraphs for use at
worldwide government locations. The software shall be orderable on both 3
1/2-inch and 5 1/4-inch media.
3.2.1. Overall Operational Criteria - LAN Software. The contractor
provided LAN software shall fully support the following functionally
described minimum characteristics and requirements:
3.2.1.1. The required software shall operate and be
completely compatible with the Zenith Z-150, Zenith Z-200T, Zenith Z-248,
Sperry PC, and IBM PC XT/AT or compatibles running MS-DOS 3.1 and later
with ULANA host attachments. The LAN software shall not interfere with,
degrade the performance of, or prevent the proper operation of the ULANA
host attachments.
3.2.1.2. The software shall provide the functions necessary
to support the following client-server architectures:
3.2.1.2.1 Non-dedicated LAN server - the software shall
allow two or more PCs to function as servers in a non-dedicated mode. The
software shall not use more than 256 KB of base memory. The software
running in a client machine may use but not require extended memory
which is
available from Zenith Data Systems for the Zenith microcomputers. The
available extended memory on the Zenith microcomputers is between 512 KB
and 2.5 MB. The software shall be limited to the use of 256 KB of
extended memory for server and slave operation. A PC shall have the
capability to act as a server and a client on the network at the same time.
EPS-88-001
08 Mar 1988
3.2.1.2.2. Dedicated LAN server - the software shall allow
two or more PCs to function as servers in a dedicated mode. If the
dedicated server requires a different operating system (other than DOS 3.1
and later) it must be included with the LAN software.
3.2.1.2.3. Client workstation - The software shall not use
more than 128 KB of base memory when installed and configured as a client.
The software running in the client machine may use but does not require
extended memory which is available from Zenith Data Systems for the
Zenith microcomputers. The available extended memory on the Zenith
microcomputers is between 512 KB and 2.5 MB. The software shall be
limited to the use of 256 KB of extended memory for server and slave
operation. A PC shall have the capability to act as a server and a client
on the network at the same time.
3.2.1.2.4. SMB Server Interoperability - The software shall
interoperate with an SMB server that conforms with NETBIOS as per RFCs
1001 and 1002.
3.2.1.3. Each micro-computer listed in 3.2.1.1 that must run
the local area network application software provided under this contract
will be provided with an installed ULANA host attachment. A NETBIOS
service level interface that conforms to RFCs 1001-1002 will be provided
as part of this host attachment. The LAN Application software shall
utilize this service level interface to communicate with other
micro-computers across the LAN. While running the local area network
software it shall be possible to execute TELNET, FTP, and other DOS-based
applications provided under the ULANA contract.
3.2.1.4. The software shall be icon-driven, menu driven and
command driven at the users option (2 out of the 3 options).
3.2.1.5. The software shall provide the capability of
switching between the network and the operating system. It shall
accomplish this through use of options available in 3.2.1.4..
3.2.1.6. For all machines listed in 3.2.1.1., the
software shall support a minimum of 16 concurrent users per server.
3.2.1.6.1 For all machines listed in 3.2.1.1., the software
shall support a minimum of 100 users per server.
3.2.1.7. The software shall support the following input
devices:
Device Zenith Data Systems Part No
------ ---------------------------
Z-150/200
Keyboard 181-6894
TEMPEST Kurta Tablet AFP-11-T
EPS-88-001
08 Mar 1988
Z-248
Keyboard HE-163-24
Summagraphics Summasketch Input Device SI-1201
Logitech Mouse LG-7
Tempest Kurta Tablet AFP-11-T
3.2.1.8 The software shall allow the sharing of output
devices, to include as a minimum:
Device Zenith Data Systems Part No
------ ---------------------------
Z-150/200
Z-150 CGA Color Monitor ZVM-133-T
Z-150 Monochrome Monitor ZVM-122-T
Dataproducts DP55Q Letter Quality Printer TT-5155
Dataproducts TCG200 Dot Matrix Color Printer AFP-4-T
DMP-29T Plotter DMP-29-TM
Z-248
Monochrome Monitor ZMM-1470-G
EGA Color Monitor ZVM-1380
ALPS P2000G Dot Matrix AL-2000
Diablo TC150 Ink Jet Printer AFP-8-T
Western Graphtec MP 2300 Plotter, 8 Pen Self Capping WG-2300
CTS 2424 Dial Up Modem ZM-2424
Zenith Modem (Hayes 2400 baud) ZM-2401
Xerox 4020 Ink Jet Printer DS-200
Asynchronous 9600 Baud Voice/Data Modem ZM-192
MPI Printmate 350 Dot Matrix Printer MPI-350-B1
Primage 90 Letter Quality Daisy Wheel Printer PP-252
Genicom 3184 Dot Matrix Printer AFP-6-TG
Diablo 630 Daisy Wheel Printer
Okidata 83A Dot Matrix Printer
MPI Printmate 180 FT Dot Matrix Printer
Diablo Advantage 80 Daisy Wheel Printer
DMP-29 Plotter, 8 Pens
HP HGL Output Devices
Postscript Output Devices
3.2.1.9 The software shall provide a backup capability for
shared network files utilizing the users choice of the following:
Irwin 20 MB Tape Backup System Z-427-20
Interdyne 20 MB Tape Backup System ID-6025
Scorpion 60 MB Internal Tape Backup Drive ZD-60
Shall back up 20 MB in less than 20 minutes and have unlimited capacity.
3.2.1.10 The software shall allow the user to run the
following application programs when stored on the server from the standard
small computer requirements contracts and their NETBIOS compatible LAN
versions when they become available:
EPS-88-001
08 Mar 1988
Package Version Contract
------- ------- --------
Wordstar Professional 3.31 and later Z-248 (F19630-86-D-0002)
Multimate 3.3 and later Z-248 (F19630-86-D-0002)
dBASE II 2.43 and later Z-248 (F19630-86-D-0002)
dBASE III 1.1 and later Z-248 (F19630-86-D-0002)
Condor III 2.11 and later Z-248 (F19639-86-D-0002)
Microstat 4.0 and later Z-248 (F19630-86-D-0002)
Supercalc 3 2.1 and later Z-248 (F19630-86-D-0002)
Graftalk 3.27 and later Z-248 (F19630-86-D-0002)
4-Point Composition Graphics 1.57 and later Z-248 (F19630-84-D-0009)
Cad Key 2.0 and later Z-248 (F19630-86-D-0002)
Timeline 2.0 and later Z-248 (F19630-86-D-0002)
Enable 1.15 and later Z-248 (F19630-86-D-0002)
Microsoft Windows 1.01 and later Z-248 (F19630-86-D-0002)
3.2.1.11. The software shall provide windowing and
multitasking capability. It shall allow the capability to create a
minimum of eight windows allowing the concurrent viewing of eight tasks.
One application selected by the user will execute, and the others will be
suspended until selected. The tasks may consist of eight different
applications or eight separate executions of a single application.
3.2.1.12. The software shall provide network administration
functions to allow for installation and maintenance of the network
software. These functions shall include adding users, deleting users,
changing passwords, adding shared peripherals, and diagnostics and
statistics tools to identify network load and problems. The information
provided by the diagnostics and statistics tools shall be more than raw
data--it shall help the user to interpret the data. This shall not be a
separate software package.
3.2.1.13. The software shall allow a password for each user
identification with different levels of access (i.e.: read only, read
write, etc). Passwords shall be initially assigned by the network
administrator. User shall have the ability to change their password.
3.2.1.14. The software shall provide full file sharing
capabilities that allow the user to:
3.2.1.14.1. Grant, remove, and change access to their files
on the LAN.
3.2.1.14.2. Grant file access to a single user, multiple
users, and all users on the LAN using options available in 3.2.1.4.
3.2.1.14.3. Specify type of access granted to other users
to include: none, read only, write only, execute, and read-write.
3.2.1.14.4. Grant access to a single file, a group of
files, an entire subdirectory, and an entire drive.
EPS-88-001
08 Mar 1988
3.2.1.14.5. Place a password on files to which the user has
granted access to others so that the other user must use that password to
access the files.
3.2.1.14.6. Display a listing of all files to which the
user has granted access to other users and the type of access they have.
3.2.1.14.7. Display a listing of all the files to which
others have granted the user access and the type of access they have.
3.2.1.15. While running the LAN software, the user shall be
able to invoke all DOS application programs.
3.2.1.16. The software shall provide options available in
3.2.1.4 for the installation procedure.
3.2.1.17. The software shall allow workstations to link to
any shared peripheral on the network.
3.2.1.18. The software shall provide print spooling with
the capability to reorder print queues, delete print files and queues, and
move print files and queues to other printers.
3.2.1.19. The software shall provide context sensitive help
facility accessible from all workstations.
3.2.1.20. The software shall provide error messages that
correctly identify the error and explain how to correct it.
3.2.1.21. The software shall provide remote dial-in
capability that allows access to all network resources and capabilities.
It shall support user selectable data transmission speeds ranging from 300
BPS to 19.2K BPS (300, 1200, 2400, 9600, 19,200).
3.2.1.22. As a late deliverable, the contractor shall
provide a version of the software that will run with the SMSCRC operating
system that is functionally conformable with the System V Interface
Definition (SVID). This version shall provide a user interface as similar
to that of the PC version as possible.
3.2.1.23. Additional consideration shall be given to those
contractors who offer a version of the software to be installed and
configured on the Zenith Z-100 computer to enable it to operate as a
client node on a network. This version of the software must operate the
same as and provide a user interface identical to that of the software for
the machines cited in 3.2.1.1.
3.2.1.24. The software shall provide electronic mail
facilities. It shall support a minimum of 100 mailboxes, which shall be
established by the network administrator. It shall support both text and
non-text (8-bit ASCII). The maximum size of electronic mail messages
shall be limited only by the amount of storage space the user has
available.
EPS-88-001
08 Mar 1988
3.2.1.24.1. The capabilities shall include:
3.2.1.24.1.1. Choose and read a message.
3.2.1.24.1.2. Create a message with an editor supplied
by the vendor.
3.2.1.24.1.3. Send a message. Retain a copy of the
message if desired.
3.2.1.24.1.4. Reply to a message.
3.2.1.24.1.5. Forward a message and/or series of
messages.
3.2.1.24.1.6. Delete a message and/or series of
messages.
3.2.1.24.1.7. Send a courtesy copy (cc) of a message to
addresses upon transmission. Shall allow for the creation, storage, and
use of distribution lists.
3.2.1.24.1.8. Copy a message and/or series of messages
into a file.
3.2.1.24.1.9. Insert files into the body of a message
and include as attachments to a message. (minimum of 10 files)
3.2.1.24.1.10. Display headers including: Date,
Subject, Return address, Read and unread, Answered and Unanswered, Flagged
and Unflagged.
3.2.1.24.1.11. The user should be able to send and
receive electronic mail using this electronic mail facility to and from
other hosts on the network that only utilize the SMTP protocol for
electronic mail exchange from a host supported by ULANA using SMTP
protocol.
3.2.1.24.1.12. Shall provide positive confirmation of
addressee receipt of message.
3.2.1.24.1.13. Notify user upon log-in that he has new
mail.
3.2.1.24.1.14. Save mail to a file of user's choice.
3.2.1.24.2. The message shall include the following fields
in data area:
3.2.1.24.2.1. Subject.
EPS-88-001
08 Mar 1988
3.2.1.24.2.2. Comments (on forwarded or resent
messages).
3.2.1.24.2.3. Return path (explicit series of
forwarding hosts/gateways).
3.2.1.24.2.4. Return address.
3.2.1.24.2.5. Date.
3.2.1.25. The software shall have a network calendaring
capability with the following functions:
3.2.1.25.1. It shall allow creation and use of a minimum of
100 calendars per server.
3.2.1.25.2. It shall provide for public and private
calendars that shall cover a minimum of 12 previous months and 12
subsequent months to the current month.
3.2.1.25.3. It shall display a planning calendar by day,
week, or month at the users option. As a minimum, the daily calendar
shall allow 80 characters per entry; the weekly calendar 40 characters per
entry; and the monthly calendar 20 characters per entry.
3.2.1.25.4. It shall allow the user to print a hard copy of
daily, weekly, and monthly calendars.
3.2.1.25.5. It shall allow the user the capability to
designate other users who will have access to view and modify his calendar.
3.2.1.25.6. It shall allow the user to input information to
his own calendar and to calendars to which he has access.
3.2.1.25.7. It shall have appointment scheduling
capabilities such that a user may specify individuals whose calendars
should be checked for open time (during a specified day or week). When a
common time is found, it shall reserve the time slot on each attendees
calendar. It shall also check the availability of meeting rooms and
equipment for the meeting and schedule them as well. In case of multiple
openings, the utility shall query the user scheduling the appointment as
to the desired time.
3.2.1.25.8. It shall allow the user to delete a scheduled
event from multiple calendars with a single action.
3.2.1.25.9 It shall provide a calendar "scratch pad"
function which allows any user to propose calendar updates to any other
users' "scratch pad", plus a calendar update utility which allows each
user to review his scratch entries off-net and accept or reject proposed
updates to their actual calendar file.
EPS-88-001
08 Mar 1988
3.2.2. Operational Concept - Security Module. The
contractor-provided security module shall, through the use of a software
and hardware combination and without affecting the normal operation of the
PC, fully support the following functionally described minimum
characteristics and requirements:
3.2.2.1. Shall be completely compatible with the Zenith Z-248
model computers manufactured by Zenith Data Systems running MS-DOS 3.1 or
later.
3.2.2.2. Shall have a password for each user identification with
different types of access (disk, directory, and files). This password
shall be user modifiable.
3.2.2.3. Shall keep an audit trail of user accesses both
successful and unsuccessful. After a given number of unsuccessful log-on
attempts (as determined by the network administrator), shall record the
access attempts and the time in the audit trail and shall lock out the
unauthorized user by disabling the keyboard or CPU.
3.2.2.4. When a successful access is completed, shall provide an
audit trail report showing all access attempts made and what functions
were done during each access. This report shall cover the previous 24,
48, or 72 hours at the users option. At the end of the user specified
period, the audit trail data will be deleted. (For example, if the user
specifies a 24 hour audit trail, at the end of the 24th hour, the data for
hour 1 is deleted to make room for the data for hour 25.)
3.2.2.5. Shall prevent unauthorized users from booting system
(including booting from the floppy drive).
3.2.2.6. Additional consideration shall be given to those
contractors who offer a security module package to be installed and
configured on the Zenith Z-100 computer. This version of the security
module must operate the same as and provide a user interface identical to
that of the software for the Z-248.
Note: If meeting these requirements requires the use of an internal
board, that board shall fit into an available PC slot in the Z-248 and an
available slot in the Z-100 (if offered). Different boards will be
permitted for each model of computer. This board, if offered, shall not
interfere with the normal operation of the system in which it is installed.
3.3. Documentation.
3.3.1. Contractor(s) shall provide comprehensive
documentation to accompany each software package. Proposals should be
made for documentation as a separately orderable item and as bundled with
the software. When bundled with the software, the price of the
documentation will be included in the price of the software. This
documentation shall contain
EPS-88-001
08 Mar 1988
explanations of each capability and how to perform it, an error message
key to provide further explanations of error messages described in
3.2.1.19., and a glossary of applicable terms. It shall be aimed at the
novice user so that even a beginner can use the software with minimal
assistance.
3.3.2. The contractor(s) shall furnish the government any
changes to documentation within 60 days after notification of errors in
the original documentation or of discrepancies in the software that render
the documentation incorrect.
3.3.3. The contractor(s) shall furnish an installation
manual with each file server package. This volume shall describe, in
detail, the software installation process and procedures, and how to set
up the network.
3.4. Delivery of Orders.
3.4.1. The first delivery of each CLIN/SLIN shall be delivered to
Gunter AFS Alabama 6 work days after receipt by contractor of a delivery
order. Subsequent deliveries shall be made to the "ship to" address
indicated on each delivery order.
3.4.2. The contractor(s) shall ship orders within 21 days of
arrival of the delivery order at the contractor's location.
3.5. Warranties.
3.5.1. All software and hardware components purchased through this
contract shall be warranted against all defects and failures for a period
of 1 year. All defective items that fail during the warranty period will
be returned to the contractor via a common carrier at government expense.
Replacements of defective items shall be made free of charge within 4
working days of contractor's receipt of the returned defective item.
Contractor shall pay the cost of shipping the replacement items.
3.5.2. For CONUS deliveries, the warranty period for a given
delivery order shall not begin until delivery of the items to the
specified destination or 15 days after government acceptance of the
delivery, whichever occurs first.
3.5.3. For OCONUS deliveries, the warranty period for a given
delivery order shall not begin until delivery of the order to the
specified location or 30 days after government acceptance of the delivery,
whichever occurs first.
3.6. Updates and Upgrades.
3.6.1. Updates.
3.6.1.1. An update shall be defined as: Corrections and/or
additions to existing versions of a product that cause the product to
operate as specified in this solicitation.
EPS-88-001
08 Mar 1988
3.6.1.2. Free updates and corrected documentation shall be
made available to Air Force users not more than 60 days after the
contractor(s) receives official notification by the government of a
problem, or within 30 days after commercial availability of the update.
When an update is necessary, users will send the contractor a letter
stating the serial numbers from their originally purchased packages and
the address to which the update should be mailed. The contractor shall
send updates on diskette and corrections to documentation in hardcopy
form. These items must be mailed to the user within 7 work days after
contractor received the letter from the user.
3.6.2. Upgrades.
3.6.2.1. An upgrade shall be defined as: A new version of
the product with corrections and enhancements not available in previous
versions.
3.6.2.2. If, after the contract is awarded, the
contractor(s) markets a new commercial version of the product, the added
features and enhancements of the new commercial version and updated
documentation shall be proposed to the government in the form of an
upgrade to the government version of the package. This proposal shall be
made within 30 days of the availability of the new commercial version.
The government may elect to modify the contract and, at its option, may
have the new version delivered in lieu of the originally specified
package. Upgrades shall be listed as a separate contract line item.
3.6.2.3. Method of distribution is negotiable prior to
contract award. Suggested method is to notify government users of the
update and have them send their original diskettes to the contractor who
in turn will return the upgraded version to the user. The user shall
receive the upgraded versions within 7 working days of contractor receipt
of the original diskettes.
3.6.2.4. The price of the upgrade will be proportional to
the price of the originally offered package. For instance, if the
original package was offered to the Air Force at 50 percent of its
commercial price, then the upgrade must also be offered to the Air Force
at 50 percent of its commercial price.
3.7. Support.
3.7.1. The contractor(s) shall furnish a point of contact for
questions/problems. This individual or individuals must be identified by
name, address, and toll-free telephone number. The toll-free number shall
be manned between 0800 and 1700 Central Time, Monday through Friday
(except Federal Holidays) for the life of the contract.
3.7.2. The contractor(s) shall be required to maintain a data base
providing the following information on one screen:
3.7.2.1. order acceptance date (date order received by
contractor)
3.7.2.2. ship date (expected and actual)
EPS-88-001
08 Mar 1988
3.7.2.3. ship-to address
3.7.2.4. list of items on order
Note: The government shall have access to this data base at any time
through the use of the contractor-supplied toll-free phone line described
in 3.7.1. above and a standard asynchronous telecommunications package
(such as HyperAccess or Enable). The data base shall be accessible by
delivery order number or by ship-to address at the users option.
3.8. Monthly Reports.
3.8.1. The contractor(s) shall provide monthly production and
delivery reports on the fifth work day of each month. These reports shall
contain the ordering status for the previous month (number ordered, number
delivered, number returned with defects) and the dollar amount associated
with these orders. In addition, the ordering status and dollar figures
for the total period of the contract up to the end of the previous month
are also required (number ordered-to-date, number delivered-to-date,
number returned-to-date, explanation of backorders).
3.8.2. The contractor(s) shall also furnish the Small Computer Office
Automation/Service Organization (SCOASO) at Gunter AFS a monthly report
synopsizing the calls received over the toll-free line described in 3.7.1.
above. This report shall specify the problem calls received and the
solutions given.
3.9. Training. The offered packages shall provide a computer aided
instruction module and interactive tutorial to provide an overview of the
products and aid the user in learning the capabilities of the products.
3.10. Preparation for Delivery.
3.10.1. Packaging.
3.10.1.1. The contractor(s) is responsible for the
preservation, packaging, and packing of all items to be delivered under
the terms of this contract in such a manner that adequate protection is
provided against corrosion, deterioration, and physical damage during
shipment and handling from source of supply to final destination. The
contractor's commercial packaging practice is acceptable in the event
these practices provide the required protection. The contractor(s) is
fully liable for any damage, deterioration, and losses incurred during
shipment and handling unless the damage, deterioration, and losses are the
fault or negligence of the government. Marking shall be in accordance
with MIL-STD-129J, 25 Sep 84, Marking for Shipment and Storage.
3.10.1.2. The government shall be responsible for the
preservation, packaging, and packing to the above standards of all items
returned to the contractor(s) for warranty service.
EPS-88-001
08 Mar 1988
3.10.2. Delivery. For deliveries to CONUS, Alaska and Hawaii
locations, deliverable items shall be F.O.B. destination. For overseas
deliveries, deliverable items shall be F.O.B. point of exportation (POE).
Examples of initial delivery points for POE shipments are as follows:
McChord AFB, WA (Japan and Korea)
Travis AFB, CA (Philippines and Guam)
Dover AFB, DE (Europe)
Charleston AFB, SC (Panama)
Patrick AFB, FL (Puerto Rico)
JBVB@AI.AI.MIT.EDU ("James B. VanBokkelen") (04/01/88)
1. Why no mention of RFCs 963 and 964, detailing the ways in which the descriptions of IP and TCP in MIL-STD 1777 and 1778 are wrong? The 1983 dates on the MIL-STDs lead me to believe that they haven't been revised to correct these problems. 2. Why no mention of RFC-950, "Internet Standard Subnetting Procedure"? This brings up another issue that has been on my mind recently: Is anyone working on a "Requirements for Internet Hosts" RFC, in the vein of RFC1009? I have recently encountered a number of very literal readings of the MIL-STDs into government procurement specifications, such that a PC is required to: a. Support 'Page Mode' in its FTP. b. Generate ICMP Time Exceeded messages, even though it has only one interface, and this represents discarding an otherwise perfectly acceptable packet (albeit one which barely got to me). c. Reply to ICMP Information Request messages, which appear to me to be intended for DDN use, and not for a broadcast LAN. I can't guess exactly why they might want this, but BOOTP seems to be much better suited. There is also the issue of whether a workstation should reply to this sort of thing at all (particularly if the request is broadcast). d. Support the IP option "Satnet stream ID", which I am informed is not relevant to any of the standard upper layer protocols (TCP, UDP, etc.). I can ignore it just fine, but I don't know if this is 'support'. I would be interested in working with anyone who is working on a host- oriented equivalent to RFC1009. I might even have time to start one myself. Of course, if I'm entirely wrong in my criticism above, I'm not the right person... James VanBokkelen FTP Software Inc.
CERF@A.ISI.EDU (04/01/88)
Ves and Stan, Two thoughts after a first pass scan of the performance specs: 1. Will the windows lawsuits between Apple and HP/Microsoft create problems for vendors trying to respond to the ULANA specs? 2. Should the electronic mail requirements include anything about interoperability with Internet Mail (perhaps it does so by inclusion of reference to SMTP ?), with any public mail service?, with name server capabilities? Vint
braden@VENERA.ISI.EDU (04/02/88)
Yes, there is a WG of the IETF doing exactly that. Your friend and mine JNC is supposedly holed up writing Good Words about the IP layer, even as I type. (Go, Go, Noel!). By the way, I seem to be the chair of this WG. If you want to devote time & energy to it, let me know. Bob Braden
braden@VENERA.ISI.EDU (04/02/88)
This brings up another issue that has been on my mind recently: Is anyone
working on a "Requirements for Internet Hosts" RFC, in the vein of RFC1009?
Yes, there is a WG of the IETF doing exactly that. Your friend and mine
JNC is supposedly holed up writing Good Words about the IP layer, even
as I type. (Go, Go, Noel!). By the way, I seem to be the chair of this
WG. If you can put time and energy to it, let me know!
Bob Braden
PS: To those who got an earlier, garbaged, copy of this message, I apologize
on behalf of a well-known Bay-Area university and a well-known Bay Area
workstation mfr, who were responsible for the mailer software I use.
RTBbraden@VENERA.ISI.EDU (04/02/88)
This brings up another issue that has been on my mind recently: Is anyone
working on a "Requirements for Internet Hosts" RFC, in the vein of RFC1009?
Yes, there is a WG of the IETF doing exactly that. Your friend and mine
JNC is supposedly holed up writing Good Words about the IP layer, even
as I type. (Go, Go, Noel!). By the way, I seem to be the chair of this
WG. If you can put time and energy to it, let me know!
Bob Braden
PS: To those who got an earlier, garbaged, copy of this message, I apologize
on behalf of a well-known Bay-Area university and a well-known Bay Area
workstation mfr, who were responsible for the mailer software I use.
RT