Enterprise Network Computer Product Standard
Copyright© 1999 The Open Group

Frontmatter

Copyright © January 1999 The Open Group. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners.

Motif^®, OSF/1^®, and UNIX^® are registered trademarks, and the IT DialTone^tm, The Open Group^tm, and the "X Device"^tm are trademarks, of The Open Group.

Any comments relating to the material contained in this document may be submitted to The Open Group at:

The Open Group
Apex Plaza
Forbury Road
Reading
Berkshire, RG1 1AX
United Kingdom

or by electronic mail to:

OGSpecs@opengroup.org

Contents

Contents

1.   Definition
1.1.   Name
1.2.   Label for Logo
1.3.   Description

2.   Conformance Requirements
2.1.   Human-Computer Interface
2.2.   Portability Interface
2.3.   Programming Language Environment
2.4.   Interoperability

3.   Operational Environment

4.   Portability Environment

5.   Overriding Standards

6.   Indicators of Compliance

7.   Migration

1. Definition

1.1. Name

Enterprise Network Computer

1.2. Label for Logo

Enterprise Network Computer

1.3. Description

This Enterprise Network Computer Product Standard is based upon the following document:

Technical Standard: Network Computing Client, Document Number C801, October 1998

The Enterprise Network Computer is platform-independent. Any product that meets the conformance requirements described in this document can be registered as conformant. A conformant product consists of a particular combination of hardware and software, and the specific product must therefore be uniquely identified in a Conformance Statement.

A single configuration of the product shall meet all the mandatory conformance requirements defined in this document. In addition to the mandatory requirements, conformant products may implement any additional services defined in the Network Computing Client Technical Standard, as long as those services are implemented in a conformant manner.

Conformant products may also provide additional standards-based or proprietary services, as long as the mandatory conformance requirements continue to be met, or an environment in which these requirements are met can be configured by a user.

Unlike existing conformance definitions for the Open Brand, this Product Standard does not rely solely upon specifications published by The Open Group or Standards issued by formal standards bodies. While all references in this document are to the Network Computing Client Technical Standard, that Technical Standard in turn references specifications that are widely recognized in the industry as being de facto standards. The majority of these have been developed by the Internet Engineering Task Force (IETF). Others were developed by Sun Microsystems.

2. Conformance Requirements

2.1. Human-Computer Interface

• Hardware Configuration
  A conforming implementation shall provide at least the following physical interface:
  • A display screen with a resolution of at least 640 x 480, or equivalent (including NTSC, PAL, and SECAM television display resolutions) supporting at least 256 colors.
  • Pointing capability.
  • Text input capability.
  • Audio output capability.
  • A network connection over which Internet Protocol information can be sent and received.
• User Interface
  As defined in the Network Computing Client Technical Standard: Providing a User Environment.
• Rendition Requirements
  As defined in the Network Computing Client Technical Standard: Rendition Requirements.
• User Configuration View and Modification
  As defined in the Network Computing Client Technical Standard: User Configuration View and Modification.

2.2. Portability Interface

• Java support as defined in the Network Computing Client Technical Standard: Executing Java Bytecode, including file system support.
• HyperText Markup Language support as defined in the Network Computing Client Technical Standard: Processing and Presentation of Resources - text/html.
• If the product supports ECMAScript, it shall do so as defined in the Network Computing Client Technical Standard: Processing of Encapsulated Resources, subsection ECMAScript Scripts.
• If the product supports the Virtual Reality Modeling Language, it shall do so as defined in the Network Computing Client Technical Standard: Processing and Presentation of Resources - x-world/x-vrml.
• If the product supports a distributed object environment, it shall do so as defined in the Network Computing Client Technical Standard: Distributed Object Environment.

2.3. Programming Language Environment

That of the chosen Portability Environment.

2.4. Interoperability

• Startup Protocols
  If the product is Permanently Connected to the network, it shall start up as defined in the Network Computing Client Technical Standard: Starting the Implementation, subsection Permanently Connected Systems.
  If the product is Occasionally Connected to the network, it shall start up as defined in the Network Computing Client Technical Standard: Starting the Implementation, subsection Occasionally Connected Systems.
• User Authentication Protocols
  The product shall authenticate users as defined in the Network Computing Client Technical Standard: User Authentication.
• Data Interchange Formats
  None.
• Communications Interfaces and Protocols
  • Transmission Control Protocol (TCP) as defined in the Network Computing Client Technical Standard: Transmission Control Protocol.
  • User datagram protocol (UDP) as defined in the Network Computing Client Technical Standard: User Datagram Protocol.
  • Internet Protocol (IP) as defined in the Network Computing Client Technical Standard: Internet Protocol.
  • Secure Sockets Layer (SSL) as defined in the Network Computing Client Technical Standard: Secure Sockets Layer supporting at least the SSL_DHE_EXPORT_WITH_DES40_CBC_SHA cipher suite. Support for additional cipher suites is implementation-defined.
  • HyperText Transfer Protocol (HTTP) as defined in the Network Computing Client Technical Standard: Transmitting Resource Requests.
  • Network File System
    If the product supports remote file access, it shall do so as defined in the Network Computing Client Technical Standard: Providing a File System.
  • Line Printer Daemon Protocol as defined in the Network Computing Client Technical Standard: Selecting a Printer.
  • Simple Network Management Protocol (SNMP) as defined in the Network Computing Client Technical Standard: Answering SNMP Queries.
• Processing and Presentation of Resources
  • Character Set Encoding
    as defined in the Network Computing Client Technical Standard: Processing and Presentation of Resources.
  • Content type recognition/presentation
    text/plain, text/html, image/gif. image/jpeg, image/png, audio/basic, audio/x-wav, application/pdf, and multipart/mixed, each as defined in the Network Computing Client Technical Standard: Processing and Presentation of Resources.
  • Virtual Reality Modeling Language
    If the product supports the content type x-world/x-vrml, it shall do so as defined in the Network Computing Client Technical Standard: Processing and Presentation of Resources, subsection x-world/x-vrml.
  • Encapsulated Resources
    As defined in the Network Computing Client Technical Standard: Processing of Encapsulated Resources, subsections Java Applets, In-line Images, and Background Images.
• Hypertext Protocol Transfer Services
  • Processing Uniform Resource Locators (URLs)
    As defined in the Network Computing Client Technical Standard: Processing Uniform Resource Locators.
  • Transmit Resource Requests
    As defined in the Network Computing Client Technical Standard: Transmit Resource Requests.
• Mail Services
  • Sending Electronic Mail
    As defined in the Network Computing Client Technical Standard: Sending Electronic Mail.
  • Viewing Electronic Mail
    As defined in the Network Computing Client Technical Standard: Viewing Electronic Mail.
• Selecting and Retrieving Files
  As defined in the Network Computing Client Technical Standard: Selecting and Retrieving Files.
• Establish and Conduct Virtual Terminal Sessions
  • If Telnet Terminal Sessions are supported, they shall be implemented as defined in the Network Computing Client Technical Standard: Establish and Conduct Virtual Terminal Sessions, subsection Telnet Terminal Sessions.
  • If TN3270 Terminal Sessions are supported, they shall be implemented as defined in the Network Computing Client Technical Standard: Establish and Conduct Virtual Terminal Sessions, subsection TN3270 Terminal Sessions.

3. Operational Environment

Refer to Conformance Requirements

4. Portability Environment

There are no dependencies on Operating System interfaces.

For languages, only Java Bytecode and HTML support are required. Support for the Virtual Reality Modeling Language and for ECMAScript is optional. See Portability Interface.

5. Overriding Standards

All formal standards included within the Network Computing Client Technical Standard are specified by direct reference to the formal standard document itself.

6. Indicators of Compliance

The Open Group will develop a Test Suite for this Product Standard. The Test Suite will be a mandatory indicator of compliance when it is available. Information on the availability of this Test Suite may be obtained from The Open Group's Client Test Technology links from its Network Computing public Web page, or from the address specified at the beginning of this document.

The indicator of compliance for the execution of Java Bytecode is one of the following:

• A test report from The Open Group's Java Conformance Test Suite
• Self-certification that the requirements of Sun Microsystems' Java Conformance for JDK 1.1 have been satisfied.

7. Migration

This Product Standard is fully compatible with the Network Computer: Foundation Product Standard.