**MACE Call 1-February-2010**

**Attending**

RL "Bob" Morgan, U. Washington (chair)

Ken Klingenstein, Internet2

Michael Gettes, MIT

Paul Hill, MIT

Steven Carmody, Brown U.

Jens Haeusser, U. British Columbia

Jim Jokl, U. Virginia

Mark Poepping, CMU

Tom Barton, U. Chicago

Renee Frost, Internet2

Renee Shuey, Penn State

Scott Cantor, The Ohio State U.

Keith Hazelton, U. Wisconsin - Madison

Scotty Logan, Stanford

Ann West, Internet2

Nate Klingenstein, Internet2

Neal McBurnett, Internet2

Steve Olshansky, Internet2 (scribe)

*New Action Item*
[AI] (All) Suggest topics via the list, or directly to RL "Bob," for the next special call on 1-March.

*Carryover Action Items*

[AI] (All) attending EMC2/REfeds/Mobility, please contact Ken.

[AI] (Leif) will discuss the IDTrust meeting on the PKNG list, seeking feedback.

[AI] (Jens) will speak to an Eduroam rep about communicating with Educause.

[AI] (Ken) will draft and circulate a letter to Rice leadership, requesting input to roadmaps and use cases, and to ensure our projects with Kuali projects are aligned with their high-level strategic direction.

[AI] (Nate) will distribute information to the list about upcoming tactical issues facing MACE

[AI] (All) send Bamboo IAM comments to Tom ASAP for coordination.

[AI] (All) interested in participating in the international collaboration activity contact RL "Bob."

[AI] (RL "Bob") will contact a representative of Kuali Rice about coordinating a call.

[AI] (Ken and Mark) will distribute some information on trust anchors in the context of dynamic network configuration in GENI testbed, as well as for general access control.

[AI] (Ken) will circulate some meeting notes from the last TERENA/ REFEDS meetings.

**Discussion**

- MACE call strategy

MACE will from this point out alternate call formats, with every other call focused on a specific topic to be advertised in advance on the list (so that participants may prep). It was suggested that using the MACE calendaring tool in the wiki, and iCal events included with call announcements, would be helpful to keep track of the new call regime. SteveO will work with RL "Bob" to enable this ongoing...

Scheduling constraints among some would inhibit their ability to extend some calls beyond an hour, which is another proposal on the table. We will try extending the time on a trial basis for the special topic calls, when warranted.

- MACE relationship to Internet2/InCommon
(see MACE topic page for expansion)

There was a wide-ranging discussion on this topic. The substantial overlap in MACE and the InCommon TAC, both in people and topics being addressed, was noted as an example of cross-pollination.

It was noted that MACE is an independent body, with some operational support from Internet2. Some MACE participants are supported to some degree by Internet2, by means of a percentage release time from their respective institutions. MACE has a long-standing oversight role for the Internet2 Middleware Initiative (I2MI), but is not limited in its scope of activities to the I2MI.

The MACE agenda is really aligned with representing campus/higher-ed/R&E sector interests. Federation and LoA were cited as example topics that span both MACE and the InCommon TAC.

It was proposed that calls be setup in the near future between MACE and AMSAC, and between MACE and Kuali leadership, to discuss coordination and areas of common interest. More to come on this as it develops.