[AI] (Brett) develop a more high level timeline for InCommon Steering
[AI] (Ann) consult with Internet2 Legal Dept. about the InCommon FOPP and InCommon Participation Agreement changes suggested for Baseline Expectations
[AI] (Brett) clarify who can contact InCommon support about a baseline expectations concern.
[AI] (Brett) move some of the details (regarding contacts/metadata and process to notify InCommon Community) to an operational appendix in the Draft Processes to Implement and Maintain Baseline Expectations (Brett started this)
[AI] (Brett) make additional updates to the Diagram, Community Dispute Resolution Process
[AI] (Tom) develop guiding principles for dispute resolution process
[AI] (Brett) develop thought piece for InCommon Steering regarding approach around supporting available profiles
[AI] (Emily) put reinstatement process (after metadata has been removed but then the issue is addressed) on a list for Ann and TomB to talk about with InCommon Ops
• Can the FM be modified to automatically check for metadata validity
• Once an entity has been modified in FM, can it be placed into the front of the maintenance process queue for checking contacts/URLs
Consultation for Baseline Expectations Implementation and Maintenance Plan - Closes Aug. 18 , 2017
IAM Online on Baseline Expectations - July 19, 2017
Slides and recording are linked at: https://www.incommon.org/iamonline/
There were over 70 participants on the IAM Online. It went well overall. Thanks to Kevin Morooney for the intro at the IAM online, setting the stage, explaining why Baseline Expectations is so important to the InC Federation .
Brett mentioned on the IAM Online the upcoming AAC recruitment and the community review board, emphasizing that we may pull in community members to help support the effort
Baseline Expectations and InCommon Steering
Brett presented the Baseline Expectations Package to InCommon Steering on July 10, 2017 as a preview. Sean Reynolds, Steering Chair, mentioned to Steering that the AAC is coming back to present more about Baseline Expectations at the August 10, 2017 Steering call. On July 10, Brett presented for about 25 minutes. It was a good conversation . Brett reminded Steering of the Baseline Expectations they approved in 2016 and explained that we are now presenting the plan to implement . It was emphasized we want to help the community get their metadata in order .
It was noted that consensus as presented in the Draft Processes to Implement and Maintain Baseline Expectations must be representative of entire community (not just R1 institutions) . Perhaps the AAC should expand to have a member from a small liberal arts college , or people with other perspectives (not only IT voices) from the participating institutions
Discussion on the AAC call: It is important to clarify to Steering what their role will be in Baseline Expectations Implementation and maintenance. One example: In the automated metadata checking process, if InCommon staff and the AAC can’t get attention and correction from an institution lacking the necessary metadata, the authority to go further must come from Steering. But we don’t want to have to approach Steering for each case. So the AAC may want a more categorical permission/ delegation from Steering. . However, it is possible we are not quite at that point yet of asking that permission/delegation from Steering.
Steering will likely want to know the impact on InC Operations staff from the process and enablement point of view. Also, Steering will want estimate on time needed from InCommon staff to set up and carry out the processes.
The Deep Dive discussions in 2016 led to the recent InCommon Fee increase that enabled new InCommon staffing. There was, included in the Deep Dive, a plan for another, 2nd, fee increase. That may cover some of the staff work for BE process.
Brett commented that he will be meeting soon with Erin Murtha, Internet project manager, to discuss BE project plan. This may help clarify how Steering will be involved in the process.
It was suggested to bring to Steering a proposal for updates to the AAC charter to spell out the new responsibilities for BE. A security expert and a privacy expert on the AAC could be helpful, to understand generally accepted security practices . It was also noted that we may be able to rely on our professional networks for some of that expertise .
It was suggested it would be good to understand FICAM issues before we rewrite the AAC charter .
InCommon Assurance program review
Tom reported that he has crafted a note to the InCommon Bronze certification holders that will go out tomorrow as part of the InCommon Assurance program review.
It was noted that we have little view into the sponsored partners in the InCommon Federation, we will need to be creative, perhaps work through organizations such as CLAC, EDUCAUSE IDM list, EDUCAUSE CIO list, EDUCAUSE Security list, REN ISAC, ACUA (Auditors List)
Ann gave a presentation with others at AACRAO Tech - There were 25- 30 registrars in the room. Talked about attribute release policy and data stakeholders and consent work. This talk was well received. http://www.aacrao.org/professional-development/meetings/past-meetings/2017-technology-and-transfer-conference
• InCommon support for REFEDS Assurance Framework v1.0 metadata attribute
• MFA Interop Profile Status update (Karen Herrington is working on an update to the wiki page)
• AAC participation on new TAC Working Group: Attributes for Collaboration and Federation WG - Draft Charter: https://spaces.at.internet2.edu/x/ipiTBg
Next AAC call: Wed., Aug. 2, 2017 at 4pm ET