*Attendees*
Jeff King, Wave Three Software
Jill Gemmill, UAB
Tyler Johnson, UNC
Art Vandenberg, GSU
Nadim El-Khoury, UNC
Samir Chatterjee, CGU
Tom Barton, U. Memphis
Doug Sicker, CU-Boulder
Egon Verharen, SURFnet
Ron Tipton, U. Tennessee
Tarun Abhichandani, CGU
Ken Klingenstein, Internet2
Jeanette Fielden, Internet2
Steve Olshansky, Internet2
Ann West, Educause/Internet2

*Discussion*
There are two VidMid VC sessions for Internet2 spring member meeting. The program is online at: http://events.internet2.edu/2003/spring-mm/. An update on what vendors will be able to participate should be available in a couple of days. The open session should focus on tools and a demo would be great for attendees who are not familiar with VidMid VC. Another topic for discussion could be the issue of bandwidth usage of clients for campus networks.

Client Update:
Samir said 8-10 people have downloaded the client and that there have been a few issues but they have worked with people to fix them. This raises the issue of support mechanisms for the client. Currently students support the users individually. There is a need for FAQ's, support lists and more documentation. Samir's group is assembling issues that need to be addressed.

Samir's group did extensive conference testing with Radvision and experimented with the real time communication server of Microsoft and the XP messenger client as well as a Siemens client. Many things did not interoperate though it is not yet clear why. For bandwidth Samir's client uses 61-89 Kilobits per second at15 frame per second though for some cameras it will be 30 frames per second. It currently supports two codecs, H.261 and H.263.

After discussion is was agreed that it would be very useful to have interoperability events similar to those in the SIP world that happen approximately every six months. Having documentation on how clients interoperate, or how they conflict would be extremely useful. Ken has a call with Ben Teitelbaum to talk about VoIP and will bring the subject up.

SIP Identity: There is a meeting this week to discuss SIP identity. The plan is to release it to this group on April 21st, 2003. Jill emphasized that people need to understand that the expected ratification of commObject in the ITU will include a SIP identity component and they're looking for comments during the one-month comment period prior to adoption. There is a need to explain the benefits of what's being done since there is consistent feedback that people don't fully understand. Any document should have an intro that says "putting these standardized objects in the directory is an operational/efficiency advantage."

Jeff King of Wave Three software (www.wave3software.com) talked about their products.
Their codecs are based on wavelet technology. There is some flexibility of frame rate and subjective quality parameters. For 15 frames per second you would want have at least 256K, if not 384K. Two codecs are available for sampling the video, 160x120 and 320x240. The display perspective is as small as 160x120 or as large as full screen. While the CPU may be affected the bandwidth needed isn't. Currently they support 11 audio codecs. G7-29 is not one but it's on the roadmap. Additional video codecs will be supported in June.

Jeff's primary role is systems and applications engineering and how Wave Three's products interoperate with other vendor solutions. Wave Three has a product called Session, which is a Windows 2000 and OSX, point-to-point video, voice and collaboration solution. The current version is 1.3, and is still point-to-point with some multipoint functionality planned for end of April. The key differentiator is that the video codec is based on wavelet technology. They plan to support 263 and possibly 261 in the July timeframe. Wave Three also has firewall and NAT traversal solutions they have worked on with several vendors. The product developed with Ridgeway is called IP Freedom. They have also worked with Ridgeway on a co-media spec for SIP for support of TCP streams and two data collaboration applications. One is called MediaSpace for whiteboarding of rich media and the other is an application-sharing product.

Wave Three is also working with various groups in the medical community so they are aware of HIPAA. Currently, there is no encryption per se built into the product. Subsequent product releases will support AES and encryption, which should largely satisfy the HIPAA requirements with regard to information security. They also plan on looking at other approaches for HIPAA compliance. Being a software only client, all of the coding and decoding is done in the software so there is a concern about processor load.

It would be nice to have an enterprise wide scheme where you don't have to have separate databases maintained for various services run within the campus/enterprise. They use a Digest authentication scheme built within the SIP standard. They want to be able to extend that to address enterprise wide solutions. IP Freedom works for voice, video and the data collaboration applications. The next release, which is not yet generally available yet, supports the co-media draft. For hardware solutions they have begun testing with Edgewater networks and it works there with video voice, and application sharing. They are addressing the media space with a co-media issue. The TCP streams are not yet completely co-media compliant. They are planning on supporting universal plug and play in the July timeframe release.

You can get a demo by filling out the request form on the www.wave3software.com site. Jeff volunteered to act as endpoint and walk people through the functionality of the demo.

There is a whole set of issues surrounding presence security and authentication. There will also be issues when federated authentication of presence happens. This represents a new horizon for this group to explore. Tyler will write a few sentences about presence and forward it to the list.

One topic for the next call is to talk about how to prepare for success. Shibboleth wasn't prepared fully and the desire is to be better prepared for video. Issues include, firewalls, authorization, and campus bandwidth.

Next call will be March 24, 2003.