Customer Council Requirements Journal
Index
Active Requirements

Rqt #

Original Statement of Requirement
1

DISA1_1: We need profiles of standards to enable true interoperability

2

DISA1_2: Directory Standards for Ent.Mgnt. - LDAP must be extended (or additional standards defined) to provide the level of interoperability required to enable enterprise management.

3

DISA1_3: Ubiquitous PKI - PKI certificate issuance and utilization is too complex for deployment in the community where it is required. PKI certificate issuance and utilization must be ubiquitous, virtually painless to the user, and manageable by mere mortals.
See also related DISA2_9 requirement (Rqt 11).

4

DISA1_4: Security services must be ubiquitous and abstract enough to be easily incorporated by application developers and administered by installations.

5

DISA1_6: Plug and Play infrastructure with assured QoS is essential - a standard that will provide the basis for enterprise services management. Users need help with exchange of information, perhaps using XML. Needs coordination and perhaps branding.

6

DISA2_1: Interoperable Network QoS

7

DISA2_2: Merger of X.500 and LDAP standards into one "best features of both" standard

8

DISA2_3: Major need for a management framework of APIs that provide a proven successor to the technology that SNMP gave to past management solutions, for network management of computing systems.

9

DISA2_4: Major need for a management framework of APIs for mobile computing

10

DISA2_5: Secure Wireless & Mobile Computing - need secure computing features to be available for users of mobile computing environments.
Combined with DISA 2.10 (require wireless PKI facility), DISA 2.11 (require secure wireless & mobile
computing facility), and Block 1.5 (architecture needed for mobile management, security, directory, etc.).

11

DISA2_9: Key PKI management services - PKI services require efficient management of keys information, so Key Management Services (KMS) are needed to provide efficient storage and access for PKI keys information.
This may be viewed as extending DISA1.3 (Rqt 3) to the API level.
12

DISA2_12: Need a common set of schemas for transaction processing and messaging using XML, so that XML data can be shared ubiquitously using a publicly available declared global registry of standard Document Type Definition (DTD) schemas.

13

CS1_1: Architecture is not used effectively by customers to vendors

14

CS1_2: Directory vendors seek to retain proprietary advantage over using available standards

15

 EMA1_1: A comprehensive Infrastructure for Electronic Business is required, to provide solutions for all the issues raised in a paper submitted to the DIF in July 2001.
25 EMA1_2: Need secure messaging capability - to enable organizations to exchange strongly encrypted email using a standards-based, vendor neutral architecture that does not require manual key exchange.
27 ALP_1: Need a formal industry-accepted process for assessment of risk management and reporting of security vulnerabilities in information systems that are used for e-Business.
Pending Requirements

16

DISA1_5: Run-time deconfliction is essential to minimize integration and total cost of ownership investments - need a single UNIX software installation & de-installation methodology, and a standard/brand that will assure the customer of plug-n-play run-time among commercial applications.

17

DISA1_7: Integrated Solutions - Customers need help with using existing and rapidly expanding numbers and types of technologies. We need integrated solutions that draw on the full range of products and services.

18

DISA2_6: Virtual collaboration workspaces for sharing data - there is a need for workspaces that enable users to draw out similar-format data (SQL, HTML, XML, UML, H.323, T.120, etc.) when working on any device, anywhere, irrespective of the geographical location of the source of the data, or of the device.

19

CS1_3: ARM and XSLM are not being taken-up by vendors

21

 CC_001: Criteria for when reference implementations are beneficial

22

 CC_002: Interoperability problems arising from technology-lead solutions

23

 CC_003: Facilitation of interoperability between software development teams
26 EMF-1: The Open Group should help train and interface users to Pegasus, by implementing a CIM object browser, then improving the browser with user feedback from training, i.e., a "virtuous circle". The  Customer Forum may want to encourage The Open Group to tie in training activity to The Open Group's participation.
Completed Requirements

24

CS1_4: Security vendors don't believe that customers understand security issues.