SALSA-NetAuth - FWNA conference call July 13, 2006

*Attendees*
Chris Misra, U. Massachusetts (stand-in co-chair)
Kevin Miller, Duke U. (co-chair)
Walt Reynolds, U. Michigan
Richard Conto, Merit
Rich Cropp, Penn State U.
Mark Linton, Penn State U.
Renee Frost, Internet2
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)

New *Action Items*
[AI] {Mark and Rich} will contribute problem statement to address moving forward with FWNA.
[AI] {Group} will gather approaches for solving incident response aspects of guest access at various institutions, and will submit information to Chris.

Carry-over *Action Items*
[AI] Please contact {Mark} if you have ideas or scenarios to propose, <mashidaATmicrosoft.com>. (15-Jun-06)
[AI] {Kevin} will talk to {Mark} about continuing discussion on 802.1x implementation. (15-Jun-06)
[AI] {Klaas and John} will prepare slides, and {John} will approach the NEA Group with a proposal for a presentation on 802.1x at the next IETF meeting. (15-Jun-06)
[AI] {John} and {Chris} will work on a basic architecture page for a document on next steps w/802.1x, and {Group} will provide feedback. (18-May-06)
[AI] Please contact {Mark} if you have ideas or scenarios to propose, <mashidaATmicrosoft.com>. (15-Jun-06)
[AI] Philippe will approach Denmark to set up test connections. (15-Jun-06)
[AI] {Kevin} will connect the local RADIUS administration folks at Duke to the FWNA-Ops list. (23-Feb-06)

Future *Agenda Topics*
+ Group will continue discussion on certificate management. (15-Jun-06)
+ Group will discuss attributes and experimentation around a contact # attribute. (20-Apr-06)
+ Group will think of local site requirements for security, logging, and access to utilization of information in the context of Eduroam, where non-local users are involved. (3-Nov-05)

*Discussion*
The group discussed the short-, medium-, and long-term goals/project plan for the FWNA WG. While Philippe has demonstrated that FWNA works within the Eduroam infrastructure, the uptake is not widespread. What are the desired outcomes and where does the group plan to divide up their energies? Where is there current progress? What are the Lessons Learned? What are the next steps towards a policy-driven vs. technology-driven infrastructure.

How does FWNA fit into campus' needs to satisfy guest access issues? Can FWNA bring about a common solution to address the span of these issues? How can FWNA work towards a solution for authenticating not only people, but also remote devices?

{Rich} suggested a long-term goal of incorporating middleware operations, akin to InCommon. A more immediate item of interest includes improved logging. Specifically, {Rich and Mark} expressed key items that are missing from any logs they have access too, such as Who is authenticated, and When they authenticated. For example if a guest is a source of a virus, it would be necessary to find them so their computer could be fixed. [AI] {Mark and Rich} will contribute problem statement to address moving forward with FWNA. [AI] {Group} will gather approaches for solving incident response aspects of guest access at various institutions, and will submit information to Chris.

There were no new developments to report for the eduroam.us operations update.

The next SALSA-NetAuth - FWNA WG call will be held on Thursday, July 27 at 11am EDT.