|
DCE Futures Rankings - Based on voting at San Diego Member's Meeting |
The purpose of this session was to have an interactive discussion on how we can advance DCE. Participants in the meeting we asked two questions and then broke up into smaller groups to discuss responses. All responses were collected and voted on by everyone attending.
1) What, if any, additional features/services do you want added to DCE Secure Core (that realistically could be included by Q1 '99)?
Each attendee was asked to vote for their top 5 choices. Responses and their ranking follow.
- (15) LDAP
- Directory consistency with industry direction
- Support of LDAP in DCE
- CDS PI support by LDAP
- Consistent ACLs - consistent access control with standards
- (15) DCE integration w/PKI
- (13) CDSA support
- (11) Single Sign-on
- (7) Scalability: increasing general performance when you increase processors (RCP over TCP)
- (7) Documented & supported CDS replication protocols and services
- (7) Directory services: robustness & reliability
- (6) Cross-cell trust using public key
- (5) Federated naming (LDAP, NDS,Notes, NIS+, ...)
- (4) Better interoperability with other architectures, esp. NT and Macintosh
- (3) Understandable & useable audit subsystem - for message (it's there today, but very unusable)
- (2) Better authentication services (such as countersigning)
- (2) Asynchronous message support - message queues
- (1) Directory services - provide an address book (propagated to various platforms)
- (0) Directory service: single global hierarchical naming model
2) What would be important to have on top of the DCE Secure Core?
Participants were asked to vote for their top 4.
- (19) Actual tools to manage environment
- (10) Simplified standard library to access core services
- (9) Making applications DCE-aware (esp. vendor apps)
- (7) Firewall proxy support
- (7) ORB (CORBA) support
- (6) Improved/expanded development environment (i.e. visual basic)
- (5) Reinstitute IFEST
- (3) Asynchronous queing
- (3) Workflow management
- (3) Extending JADE to include beans
- (0) CORBA naming sercie API to be used on top of CDS
- (0) Dynamic locator services
