Action Items
[AI] {Ben} will develop overview statement soliciting requirements for the SIP demonstration at I2 Fall Members Meeting.
[AI] {Ben} will invite Jill, Tyler, Nadim and Jamey to attend the UT call discussing the SIP demo.
[AI] {Bill} will report results of UT call to group via the list or on the next call.

*Attendees*
Paul Hill, Massachusetts Institute of Technology
Jamey Hicks, Hewlett Packard:
Joe Rork, Ford Motor Company
Mike LaHaye, Internet2
Ben Teitelbaum, Internet2
Lisa Hogeboom, Internet2
Steve Olshansky, Internet2
Terrie Clark, Internet2

*Discussion*
All communications and work of Internet2 WG’s are subject to the Internet2 Intellectual Property Framework http://members.internet2.edu/intellectualproperty.html, please review this page.

The VidMid-VC WG will hold a BoF session during the previously scheduled Internet2 Fall Member Meeting, September 27 – 30, 2004 in Austin, Texas. http://events.internet2.edu/2004/fall-mm/. This is an open working group session for the VidMid-VC group. The goal of this session is to gain consensus on the best way to achieve Federated Secure Internet Conferencing and to further the discussions on developing a "security agent" operating outside of any multimedia protocols.

PIC Demonstration Discussion - The group would like to demonstrate auto-configuration of clients thus eliminating username/password entry and menu navigating for multi-media applications at the I2 Fall Members Meeting. Ideally, this would be implemented through an H.350 enabled directory. Previous demonstration tools have left users confused with configuring soft clients. Since we are authenticating a WIFI environment, then why not leverage the WIFI authentication to auto-configure the SIP soft client? This can be accomplished by the UT-Austin systems group on the UT production WIFI and wired authentication infrastructure. The group will develop a list of questions to ask the UT systems organization about databases, access, client requirements etc. Currently, the only form of credentials is a user address from dhcp lease. The UT infrastructure is proprietary and has no LDAP. A distributed database may be necessary to support the demo. Or, a MySQL database including MAC addresses of individuals registered to use wireless LAN could be required. This could provide details about credentials including where are they stored and how to access them. A server could be reconfigured for the demo. Attendee registration information would be stored in one database and the UT authentication system would function independently. Clear text username/passwords could be extracted from the system and populated into an LDAP-like directory. An LDAP directory can be populated from the attendee registration database. However, it my not be the best solution for individuals registering on-site during the meeting.

The next call will be Monday, August 9, 2004 at 11:00AM ET.