ViDeNet Project Meeting August 5, 2002.
Attending: Jill Gemmill, Tyler Johnson, Nadim El-Khoury, John-Paul Robinson, Aditya Srinivasan, Karen Krivaa, Anatoli Levine, Samir Chatterjee, <Samir's student - please insert name here- I apologize for missing this>
Action Item Summary
[ Everyone ] - please state who will be attending the October in-person meeting; include students so we can get a head-count and see if there's room.
[Anatoli] will handle local arrangements, including reserving the room, providing transportation and hotel information. Anatoli will also check number of people who fit in the room: students' ability to be present will depend on room size.
[RADVISION] Can RADVISION supply (loan during testbed period, provide software for a campus server...) one or two SIP proxy servers for use in TestBed?
[Karen] will provide an example Marketing level requirements doc; this has apparently gone to Tyler, but would there be any problem if I got a copy as well?
[Samir's group] can have SIPIdentity object definition ready by end of this year
[Samir] will send info/papers, if available, on digital watermarking for audio/video.
[Samir] will investigate availability of SIMCOM gateway
[ Jill?] Set up meetings with VRVS and AG to begin Xidentity discussions
[Jill's group] will begin gathering information about who has implemented commObject, contact information,
[Jill] will investigate availability of Nortel SIP proxy
[Nadim] will organize a developers' meeting discussion to discuss PhP/Java language selection (may or may not have to pick one to use for everything). People to be included are: Nadim, Tyler, Aditya, John-Paul and Jill.
[Tyler] circulate a first draft of requirements, preferably in one week so we have time to consider before next meeting.
Discussion
(1) October 8,9 face-to-face meeting in Glen Rock, N.J. As stated in an earlier email by Tyler: "a conference room for 15 people for 2 days. The conference room should
have a white board, speakerphone and h.323 facilities to Internet2. We will pay for catering."
Jill adds - please remember that NSF funds cannot be used to pay for alcohol expenses - not that we'd be having any during the meeting!
(2) subcontracts status – no questions
(3) Grant deliverables review and status
LDAP schema (commObject) for H323Identity favorably received by SG 16; first ratification opportunity will be October 2002. ITU wants new OID's used. After October, we will have a ratified version *or* can selectively freeze a current version to deploy in the TestBed. H323Zone is in progress.
Videoconferencing 'White Pages' - Advanced search definitely needs improvement. Aditya gone mid-August to mid-Sept. but otherwise ready & willing to work on distributed search (he has circulated a little prototype already). Access to the existing search code base would be very useful.
Directory Enabled Gatekeeper - requirements document to be developed. We discussed:
-ECS authentication is end-point to Gatekeeper
-most customers today are thinking about authentication of endpoint; inter-realm is farther away
RADVISION plan for GK to GK authentication via SSL by end of 2003, at best.
-discussed some possible architectures for media encryption (how it could be done for MCU case w/o CPU bogging down; impact of VPN use on performance). We agree it would be useful to gather information about possible architectures & do performance comparison. Samir mentions digital watermarking for authentication as interest with group at JPL – .
TestBed - need to select a single version of the object class to deploy in initial, limited testbed.
H323/SIP gateway(s) would be important for testbed. RADVISION's is still prototype, not available.
A RADVISION SIP MCU will be available Q1 2003 on VIP 400 platform
Tyler noted Microsoft .NET SIP proxy/registrar in developer's pack; Karen followed up with information that this product is called RTC server and is scheduled for Spring 2003 release.
CookBook - will definitely be an on-going process and include a lot of "how to" and LDIF files, but may also include background summaries of types of authentication. Since there was a question about whether the latter is in scope, we can begin to develop the material & if it isn't deemed cookbook material will go in some other location.
Secure SIP - endpoints will be available in about 3 weeks, for very limited distribution.
Secure H323 Endpoint - requirements document to be developed.
(4) Requirements document - we may need two documents, (a) a Marketing level document describing high level features and functions, perhaps user scenarios and (b) a Developer's document, perhaps co-written by one of the developers, documenting the design and at more detail than the first. Target date to complete this document - end of September.
(5) Samir provided a summary of the current direction in VidMid AuthN/AuthZ flow diagrams.
(6) Repeating Tyler's proposed agenda for October meeting: There are 10 hours here, but we have actually scheduled two full days (let’s say 14 hours) so we can revise this agenda accordingly
Project Organization and Tools - 1 hour
Project Timeline and Milestones - 1 hour
Authentication - 3 hours
Status of VidMid AAA Architecture
SIP Client Development
H323 Client Development
Directory Services - 2 hours
commObject Standards Process (AVD-2199)
h323Zone Object Class
Gatekeeper Architecture - 1 hour
LDAP
User Interface / Zone Management Tools
Cookbook - 1 hour
Revised Timeline and Deliverables - 1 hour