**MACE Call 22-November-2010**

 

**Attending**

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

Rodney McDuff, U. Queensland

Renee Shuey, Penn State U.

Ken Klingenstein, Internet2

Leif Johansson, SUNET/NORDUnet

Michael Gettes, independent

Jim Jokl, U. Virginia

Nate Klingenstein, Internet2

Keith Hazelton, U. Wisc. - Madison

Von Welch, independent

Steven Carmody, Brown U.

Scott Cantor, The Ohio State U.

Renee Frost, Internet2

Ann West, Internet2

Tom Barton, U. Chicago

Steve Olshansky, Internet2 (scribe)

 

NEXT CALL: 22-November-2010

 

*New Action Items**

[AI] (Ken) will coordinate a small working group with Heather to look into access control and IdM layer requirements for shared file services, calendaring, and web-conferencing in a federation-centric context.

 

[AI] (All) with suggestions for other foundations that the Shib Consortium could eventually be embedded in are encouraged to discuss them on the list.

 

[AI] (All) Volunteers for the ACAMP program committee are encouraged to contact Ann, TomB, or RL "Bob"

 

 

*Carryover Action Items*

[AI] (Ken) will convene a small subgroup of MACE to consider the seed cord issues in more depth and report back on a forthcoming call, soon.

[AI] (Ken) will invite Mike Conlin (U. Florida), the VIVO PI, to a forthcoming MACE call.

[AI] (Keith) will maintain an issues list to inform a potential new charter for MACE-DirNG, syncing it with the FedApps charter.

[AI] (RLBob, Scott, and SteveO) will proceed with the process of formalizing the FedApps working group, including setting up a list/wiki/website, and advertise it in the appropriate venues.

[AI] (Ken) will draft a one-pager about what MACE does and what questions it has, for review by MACE, as a discussion guide with Internet2 leadership.

[AI] (Ken) will distribute a draft requirements framework for VO support engagement

[AI] (David) will contact GSA for an update on the approval process for InCommon Silver.

[AI] (ReneeS) will revisit the list of potential new MACE members on the list.

[AI] (Ken) will revise the mission statement based upon feedback received on the call.

[AI] (Ken) will send out info on DHS secure online transactions

[AI] (Ken) will follow up on a MACE/AMSAC call.

[AI] (Ken) will follow up with Kuali/Rice about I2MI collaboration.

[AI] (Ken) will draft a catalyst doc, covering the key items to be addressed in advising VOs how to use our infrastructure.

[AI] (Leif) will contact Ken/Steven/Tom about potential overlaps between the SDCI proposal and projects in the EU.

[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.

 

 

**Upcoming Meetings**

https://spaces.internet2.edu/display/MACECalendar/MACE+Calendar

 

- EuroCAMP, Vienna

Nov 23-24, 2010

http://www.terena.org/activities/eurocamp/nov10/

Collaboration platforms will be the theme.

 

- CAMP/ACAMP 2011

ACAMP will be adjacent to the JASIG conference in Denver, and will be similar to past ACAMPs.

 

[AI] (All) Volunteers for the ACAMP program committee are encouraged to contact Ann, TomB, or RL "Bob"

 

- CSG

Jan 12-14, 2011, Durham NC (Duke)

http://www.stonesoup.org/meetings/1101/

 

- RSA

Feb 14-18, 2011, San Francisco CA

http://www.rsaconference.com/2011/usa/

 

TF-EMC2

Feb 14-15, 2011, Lyon France

http://www.terena.org/activities/tf-emc2/meetings/17/

 

- IETF 80 - Prague, CR

March 27-April 1, 2011

http://www.ietf.org/meeting/upcoming.html

 

- Spring 2011 Internet2 Member Meeting

April 18-20, 2011, Arlington, VA

http://events.internet2.edu/2011/spring-mm/

 

- IIW

Date TBD, Mountain View, CA

http://iiw.idcommons.net/

 

 

**Discussion**

- update on collab-management discussions - CMP metadata questions

 

Ken had a recent meeting with SURFnet. They are working on a killer app - FileSender, a flexible web-based file-sharing system based on HTML5 (not WebDav), with a running implementation in Australia: CloudStore. This might hold some promise as a component in COmanage.

http://www.assembla.com/wiki/show/file_sender

 

There is also an app with similar functionality developed at Duke.

 

BigBlueButton, a web conferencing approach with promise.

http://www.bigbluebutton.org/

 

- Foodle

A new version is able to do free/busy searches on remote calendars. Where would functionality live to get your calendar link into a consumable space? Would this be more than free/busy? Would CalConnect have a role?

 

Defining an attribute for a link to your calendar might be a useful approach near-term.

 

COmanage would seem to be the logical home for groups looking into these various collaboration tools, ongoing.

 

[AI] (Ken) will coordinate a small working group with Heather to look into access control and IdM layer requirements for shared file services, calendaring, and web-conferencing in a federation-centric context.

 

COIP, COIN, and COmanage

What metadata about these CMPs would be useful - whether human or machine-consumable? Being able to communicate to RPs what attributes are required to expose group info might be useful. However there may be namespace collision issues...

 

These issues may be the theme for a future MACE call.

 

- MACE-Dir status, identifier issues

There have been some recent discussions about future direction, and Keith will be taking a more active role. On the near-term horizon:

- identifiers - what to RPs/SPs mean by non-reassignable persistent identifier?

- Draft docs for edu* docs to clarify attribute exchange in the SAML context, and clarifying for the InCommon community that this is the venue for working on attribute-related issues.

- Working on deliverables and identifiers related to the new FedApps working group.

 

- Shibboleth consortium status

This is still coming together. There is a draft plan circulating, and they are working on an initial planning process. Current thinking is that the consortium would entail little practical change in the project operation, but would clarify the role of the 3 supporting organizations over the next ~2 years (Internet2, JISC, and SWITCH), and that eventually it might move into another umbrella...

 

[AI] (All) with suggestions for other foundations that the Shib Consortium could eventually be embedded in are encouraged to discuss them on the list.

 

- the ICAM whirl, privacy, assurance, international aspects

Recent issues have included privacy guidance materials, which have seemed somewhat onerous in the real world. There may be a summit in the next couple of months in an attempt to resolve differences...

 

It is unclear what the privacy policies will be in the EU, as it relates to higher-ed in the US, especially related to higher LoAs. In particular, assumptions about the independence of internal auditors may differ.

 

It was noted that many of the big science projects have historically only outsourced initial identity vetting. InC-Silver brings additional assurances that many projects are likely to find useful.

 

2-Factory authentication topics appear on the Educause IdM and Security lists -- should MACE participate more proactively to provide leadership in this discussion?

 

- Internet2 and middleware budget updates

This process is underway, stay tuned for more details as they are available.

 

- IETF keyassure/kidns

This has become a working group...

https://www.ietf.org/mailman/listinfo/keyassure

http://trac.tools.ietf.org/area/sec/trac/wiki/Keyassure

 

Questionable cert providers in the browser trust list have surfaced as a hot topic. Thus black- and white-listing CAs is being discussed.