miami-small.jpg (5872 bytes)

Network Client Program Group

Further information about the Program Group

Program Group area
(restricted to Program Group members)
Session Objectives
  • Continue the process of kick-starting this new Program
  • Inform participants on latest developments in the field
  • Review customer requirements from available sources
  • Build plan for submission of requirements to the Architecture Board

Agenda

Wednesday 22nd July 1998
09:00 Introductions and review of agenda  
09:15 Update on NC 2.0: The next iteration of the NC was discussed at the last meeting. Company review closes in June. Products are expected to emerge from suppliers between Q4'98 to Q1'99. There will be a quick overview and update on this and a review of issues relating to subsequent versions.  
10:00 Open discussion: Input from all present on the work of the NC Specification group and contributing activities  
10:30 Coffee Break  
11:00 Customer Input: The Mitre Corp. will discuss their requirements for Network Clients. This will include a presentation on US Airforce requirements (definitions and compliance). Bob Blaisdell, The Mitre Corp.
11:30 Joint session with Management PG and NC Management Group: At this point the Management PG will be in joint session. Mark Pozefsky was featured on last meeting's agenda. The Network Client PG requested further discussion to help Open Group participants understand the work of the NCMG and perhaps provide the group with some requirements input. This session is planned for Miami and we expect to have key members of the NCMG in attendance. Mark Pozefsky, NC Management Group
12:30 Lunch Break  
14:00 Mobile NC: A presentation and discussion of the requirements currently envisaged for mobile Network Clients. Jackson Wong, Mobile NC Group
15:30 Coffee Break  
15:00-
15:30
and 16:00-
17:00		 Network Client Requirements: The main work of the group is to produce requirement input to the Architecture Board. The following areas will be addressed:
  • General Roundup: a review of the requirements captured last time and decisions on which of these to focus on
  • Desktop Environment: how important is consistency in the features and functionality of the client interface?
    For example:
    • if there is a need to support terminal sessions do we care exactly such a session would be invoked?
    • if there need to be many windows on the screen does it matter how the user manages these?
    • if we need to require a net news reader what capabilities should be specified?

Previously collected priorities for the Program Group include:

  1. Classification of Clients
  2. Classification of Servers
  3. Business case for transition
  4. Need for Architectural Context
  5. Security - End User Authentication, including single sign-on
  6. Bandwidth Management
  7. Minimum Client Functionality
  8. Scoping what is meant by Network Computing
  9. Discovery
  10. Architecture
  11. Minimum Client Definition
  12. Quality of Service
  13. Interoperability of heterogeneous clients and servers
  14. User Mobility (access to personal preferences and applications regardless of where the user logs on)

These requirements should be clarified and from them the group should create an activity schedule. They may result in identifying needs for further information gathering or could lead to requirements specific enough to be passed to the Specification Working Group via the Architecture Board.

  
17:00 Wrap-up  

Please feel free to mail any further suggestions to the group's email alias ognetclient@opengroup.org or speak with Paul Tanner or Julie Surer.

© 1998