VidMid Directory Scenarios for a Videoconferencing User (DRAFT)
- User can look up person information. Search interface is simple, "intuitive" and provides contact details. Directory details include attributes specific to supporting videoconference connection (cf. IP address, type of equipment, local time zone info, bandwidth...?).
- User can register and maintain their directory entry. User's initial default data may be displayed based on expected common data or through "auto-discovery" by directory tool. User can link their directory profile to a source (directory or other data source) that will automatically synchronize and propagate changes.
- User's video conferencing software provides an LDAP interface to the directory information user has set up. The result of a lookup can be used to initiate a conference connection ("click to connect") and the software can use the configuration details in the directory to negotiate the connection.
- User's results are returned quickly and any connections are initiated with minimum delay. Results should conform to the expectation for looking up someone's number, dialing the number, and hearing the ring.
- Added feature of user's directory is that user can index video datasets or other objects that they wish to access during conference. Convenient interface permits them to organize folders, assign sharing access, etc.
- User should be able to rely on the "authority" of the directory. This may require that initial entry into the directory is screened or verified to ensure that services will be delivered correctly. For instance, the name, address, phone info may be confirmed via call back; the configuration info may be confirmed by test conference; etc. Authority of the directory includes accuracy of information, timeliness of entry updates, and audit trail of changes.
- User's directory information is stored in a standard objectClass that enables the information to be discovered easily, promoting interoperability.
- User is not expected to know details of directory infrastructure. Directory transparently masks any distributed integration required for deployment, performance, or synchronization.
Above scenarios based on March 7, 2001 discussion items:
- How do you define successful search in a large domain?
- Role-based attributes, cf. calendaring, are important.
- MACE-Dir and affiliated directories
- Where is the Community of Science <http://www.cos.com/>?
- Space Physics & Aeronomy Research Collaboration (SPARC) <http://intel.si.umich.edu/sparc/>
- GRID and eduPerson - cf. Global Grid Forum <http://www.gridforum.org/>
- Directory-of-Directories
- Shibboleth - authenticate locally, act globally
- Advanced Internet Technology University of Tennessee has some middleware folded in.
- Video Access Working Group - <http://gtel.gatech.edu/vide/videoaccess/> "expand access... promote preservation and management... through the use of shared, standards-based video metadata and search and retrieval technologies."
- Keep video datasets secure
- ViDeNet <http://www.cavner.org/videnet/> Voice over IP; 57 sites, 40% international. Simple number lookup; communities; directory as general repository, multiple services (owners want to avoid overhead of maintaining multiple directories).
- Voice over IP gateways can enable conferencing, but need to be secure.
- Can directory services be effective real-time service? (Dialing gets an immediate ring.)
- ViDe objectClass for IP-based performance attributes
- Australian Academic and Research Network (AARNET) <http://www.aarnet.edu.au/services/index.html> Voice over IP initiative, infrastructure 2 months away, authentication not...
- Middleware doesn't cross boundaries well. Cf. eduPerson is U.S., not international, object