SALSA-NetAuth - FWNA conference call August 11, 2005

*Attendees*
Kevin Miller, Duke U. (co-chair)
Philippe Hanset, U. Tennessee (co-chair)
Rich Cropp, Penn State
Roy Hockett, U. Michigan
Dennis Ward, U. Michigan
Chris Misra, U. Mass
Tony Genovese, ESnet
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)

New *Action Items*
[AI] {SteveO} will add a link for the FWNA wiki from the FWNA home page.

 [AI] {Philippe} will start a thread on the {SALSA - FWNA} list regarding service standards for eduroam.us.

Carry-over *Action Items*
[AI] {Group} will populate EAP and 802.1X information to the FWNA wiki. (27-Jul-05)

[AI] {Chris} will notify the {SALSA-FWNA} list once a date and time has been specified for the SALSA-NetAuth / FWNA combined BOF at the upcoming Fall Internet2 Member meeting in Philadelphia, PA (19/22-Sep-05). (14-Jul-05)

[AI] {Philippe} will draft a use case focusing on shared facilities between two institutions. (24-Mar-05)

*Discussion*
{Kevin} once again encouraged the Group to participate in the GWG-Eduroam development effort <http://lists.grangenet.net/mailman/listinfo/gwg-eduroam>. Global interoperability issues are being addressed in light of both technology and policy.

{Chris} and {Kevin} are working on the Secured Campus Wireless Architectures discussion at the Fall 2005 Internet2 Member Meeting <http://events.internet2.edu/2005/fall-mm/>. They are planning on presenting an update of FWNA and Eduroam, including general technologies, identifier security networks today – what are the options and tradeoffs? Discussion will fall at the network directory level, with a focus on Next Generation wireless security. Can we identify which things are needed to set that kind of network into motion?

As the experiment is getting underway, user feedback is extremely important in defining the next steps for FWNA. Vital issues include choosing the right AuthN strategy from the many available, as well as understanding how you authenticate to the network.

{Kevin} is still interested in feedback/edits for the wiki set up for the Operational “Goals” document <http://fwna.oit.duke.edu:2500/fwna>. The Group reviewed the posted documents in real-time, clarifying the language to distinguishing between root servers and top-level servers. The suggestion was made that the document should be written also for the lay perspective, such that newcomers can easily understand the terminology and concepts in general. A diagram may provide an additional way to communicate these concepts in a straightforward manner.

Additional documentation will be added, such as the Experimental Plan, Eduroam NGArchitecture, and Appendices. [AI] {SteveO} will add a link for the FWNA wiki from the FWNA home page.

Discussion will take place off-line to ensure that there is another top-level server in addition to U. Tennessee. It is necessary for the server to run at an operational level (equipment and deployment), and to be financially sustainable.

Both policy and technical provisioning are two issues that will shape restrictions placed on users and available support. Should a user be required to implement 802.1X or a web box with clear-type passwords? This will depend on what technology we are able to support. In the end, will FWNA benefit from setting restrictions, if not only temporarily - or will it bring limitations to the overall effort?

Even if technical provisioning is not a problem, questions will arise such as if there is a general policy towards running in the US. How is local and remote support to be handled, cost aside? From an experimental standpoint, we will need to think about how the idea of eduroam.us is addressed. [AI] {Philippe} will start a thread on the {SALSA - FWNA} list regarding service standards for eduroam.us.

The next SALSA-NetAuth – FWNA conference call will be on Thursday, August 25, 2005 at 11am ET.