ViDe.Net - Schedule

LDAP Schema (CommObject)
1. DefinitionITU-T H.350 (done or completed by end of May)
  1. h323Identity ITU-T H.350.1
  2. h235Identity ITU-T H.350.2
  3. h320Identity ITU-T H.350.3
  4. sipIdentity ITU-T H.350.4
  5. commIdentity ITU_T H.350.5 <NEW>
2. Standardization
  1. ITU-T meeting ratification (May) (tyler, nadim)
  2. SIPPING group (Samir - April?)
  3. VidMid-VC meeting April 21
3. Definition of Shibboleth-compatible Annex E profile proposed in the context of some real application like Emergency Network; Description of KX.509 style certificates passed to commObject via PKCS11 libraries and use of not-yet-existent credentials translator (Version 1 - October 2003 – tyler, nadim, jill, egon)

Directory-Enabled Gatekeeper
1. Gatekeeper (RADVISION)

commObject enabled Gatekeeper (RADVISION – June 15, 2003)
Testbed experience with Cisco/RADIUS support using special OpenH323 Gatekeeper (Egon – May 2003)
Annex D using commObject (RADVISION – June 15, 2003)
Annex E using commObject (Q1 2004)

Management web interface (UNC)
1. The UNC code will be distributed as is to testbed sites; don’t need to use zone administrator parts at testbed sites. (UNC – May 2003)

TestBed/Video Middleware Cookbook (Jason, Jill)

Technical description of object classes – from ITU docs – May 2003
Installation and Configuration of inetOrgperson/eduPerson and commObject directories

iPlanet (done)
OpenLDAP (Jason)

Discuss architectural options & advantages/disadvantages. Document configuration options (relations of person and commObject directories) ) (May 2003)

All in one directory approach (Two LDAP trees, one LDAP server)
Northwestern/UAB approaches (use enterprise directory, commObject stand-alone)
ViDeNet Public Zone – where is it? Document setting it up, or how to use it?
Document how to register you directory with ViDeNet DoD

General approaches to Security: (July 2003)
1. In the network – VPN
2. Between network and application – SSL/TLS (TCP/IP only)
3. In application
ECS w. commObject (July 2003)
1. Document setup/config
2. Install 3-4 at testbed sites ( July 2003 UAB, UNC, SURFNet, NWU?, Teitelbaum group?)

Document CISCO RADIUS approach – Egon – June 2003

Interoperability:
1. SIP-SIP (started – March 2003)
2. Gateways
  1. Document VRVS use for H.323-AG gateway
  2. Test/Document VRVS use for SIP/AG/H.323 gateway
  3. SIP-H323
  4. w. security : SIP-H323

EndPoints
1. CGU SIP user agent distribution (CGU)
  1. commObject enabled white pages lookup (done)
  2. authentication with Digest MD5 to internal database (done)
  3. Web page on videnet for distribution (April 2003)
  4. FAQ (April 2003)
  5. Complete Phase I - ie get password from sipIdentity and pass to UserAgent; do full configure from sipIdentity if possible – June 2003
  6. Phase II – with SAML/inter-realm – October 2003
  7. Reference Source Code from CGU
    1. Phase I – June 2003
    2. Phase II – October 2003
2. RADVISION
  1. endpoint Annex D using commObject
  2. endpoint Annex E using commObject
  3. Reference Source Code from RADVISION

Video White Pages - SURFnet

Set up TIO DoD server – SURFnet (Summer 2003)
Some decisions need to be made about what attributes to index (May 2003)
We may want to add the address of the ldap server to the zone record.

Evaluation of Shibboleth Architecture
1. Document flows and policy decision points for SIP (Samir - done)
2. Document flows and policy decision points for H323 (Jill - done)
3. (Annex E profile) (Jill and who? )
4. Setup Shibboleth components (UAB, CGU – May 2003)

Coordination with AG
1. Discuss accessgridIdentity (done)
2. Bob Olson at VidMid VC and ViDe meetings (done)
3. XML schema for commObject (Jill – August 2003)

Questions and Comments: Jason L. W. Lynn
last updated Tuesday, April 6, 2004 13:30