Presentation on theme: "Building Consensus on Middleware for Digital Video"— Presentation transcript:
1Building Consensus on Middleware for Digital Video VidMidBuilding Consensus on Middleware for Digital VideoMary Fran Yafchak,Southeastern Universities Research Association
2Getting Started Once upon an I2 meeting room in Washington DC…. Attendees: I2 MW, ViDe (with ANU, Gatech, SURA, SURFNet, UAB, UNC, UT), GSUMeeting purpose: Compare notes, share project ideas & approaches, decide if there is more to be done
3An Initiative is Born “Vidmid” - Middleware for Digital Video Goals: Identify needs (MW for near term DV)Develop/prioritize usage scenariosExamine approaches for design/developmentDiscussions so far: Naming the group (!), DoD & ENUM, related activities, project scoping
4Current Members (5/9/01) Ken Klingenstein (U-Colorado/I2) Acting Chair Ben Chinowsky (I2) ScribeEgon Verharen (SURFNet)Ivana Belgers (SURFNet)David Pokorney (U-Florida)Mary Trauner (GaTech)Mike Staman (Macon State)Bob Riddle (I2)Michael Gettes (Georgetown)Art Vandenberg (GSU)Ted Hanss (I2)Amy Philipson (ResearchChannel)Keith Hazelton (U-Wisconsin)Pat Jackson (Va Tech)Bob Morgan (U-Washington)Tyler Johnson (UNC)Bob Dixon (OSU)Larry Amiot (ANL/NWU/I2)Renee Frost (I2)Markus Buchhorn (ANU)Mark Poepping (CMU)Dan McCarriar (CMU)Ellen Vaughan (I2)Keith Portis (U-Nebraska)Jill Gemmill (UAB)Mairead Martin (UT)John McNair (UT)David Kuhlman (UT)Phil Galanter (NYU)Mary Fran Yafchak (SURA)Orit Levin (RADVision)
5Middleware - An Early View A “Ted Talk” from SeptTechnology Scope of Middleware:QoSDigital video/audioSecurityCollaborationDirectoriesMulticastFile systemsMeasurementRemote instrumentsIMSTransaction systemsMeta-computingManagementIP telephonyAccounting/billingE-commerceObject brokersSearch mechanismsPrinting
7And now: DV MiddlewareDV middleware - the middleware necessary to support scaleable useful DV usage scenariosVoice/Video/Data “call” scenariosStreaming & On-demand scenariosDV-to-Directory Services scenarios
8Scenarios: Directory Services Examples (from Art Vandenberg/GSU):User can look up person information in a directory. Search interface is simple, “intuitive” and provides contact details. Directory details include attributes specific to supporting videoconference connection (IP address, type of equipment, local time zone info, bandwidth…?).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.
9Scenarios: Directory Services More examples: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’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..
11*A.K.A “Related Activities & Initiatives” One Big Happy Mess*I2 Middleware - Early Harvest/Adopters, MACE (eduPerson, DoDHE, Shibboleth)Standards makers - ITU, IETF, DMTF, Others?“Development Communities” - ViDe, TERENA, the I2 Commons, Federal PKI, CREN, PKI & ICS, CSG, Grid Community, Others?*A.K.A “Related Activities & Initiatives”
12Today’s Bonus: MFY Working Group Prayer Interested in More?Today’s Bonus: MFY Working Group Prayer“May we be big enough to be inclusive yet small enough to get things done!”For all interested - the Vidmid Web site:To join the group, contact any vidmidderKnow someone else who ought to know about vidmid? Pass it along!