Date: Fri, 29 Mar 2024 02:15:50 +0000 (UTC) Message-ID: <801201740.7415.1711678550894@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7414_100921990.1711678550893" ------=_Part_7414_100921990.1711678550893 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
&nbs= p;
Attending
Action Items
AI] (Brett) respond to the one line of feedback received during the Base= line Expectations Implementation consultation.This email may also include n= otice that implementation is coming and highlighting areas important t= o start thinking about.
[AI] (Brett) work on proposed updates to AAC charter. Ann is available t= o assist.
[AI] Tom will add a =E2=80=9Cswim lane=E2=80=9D for InCommon Steer= ing on the Baseline Expectations roadmap.
[AI] (Tom) do minor editing to the Baseline Expectations Implementation = and Maintenance Plan. Once the updates are made the plan is to put th= is document into the Trust and Identity Document Repository. It has been as= signed a doc ID number of TI.35.1 but is not yet in the repository.
AI] (Ann) prepare quick list of InCommon participants= in various buckets based on the InCommon fee structure.
[AI] (Ann) consult with Internet2 Legal Dept. about the InCommon FOPP an=
d InCommon Participation Agreement changes suggested for Baseline Expectati=
ons=E2=80=A8
[AI] (Brett) clarify who can contact InCommon support about a baseline expe=
ctations concern.
[AI] (Brett) move some of the details (regarding contacts/metadata and proc=
ess to notify InCommon Community) to an operational appendix in the D=
raft Processes to Implement and Maintain Baseline Expectations (Brett=
started this)=E2=80=A8
[AI] (Brett) make additional updates to the Diagram, Community Dispute Reso=
lution Process=E2=80=A8[AI] (Tom) develop guiding principles for dispute re=
solution process=E2=80=A8[AI] (Brett) develop thought piece for InCommon St=
eering regarding approach around supporting available profiles
DISCUSSION
Next Steps for Baseline Expectations Implementation
Brett presented the plans for Baseline Expectations Implementation on th= e Sept 11, 2017 InCommon Steering Call. It was mentioned on that call= that Baseline Expectations might be on the agenda for the Trust and Identi= ty PAG meeting at 2017 TechEx. https://meetings.internet2.edu/2017-technology-exchange/detail/10004889/= The next InCommon Steering call is October 2.
[AI] TomB do minor editing to the Baseline Expectations Implementation a= nd Maintenance Plan. Once the updates are made the plan is to put thi= s document into the Trust and Identity Document Repository. It has been ass= igned a doc ID number of TI.35.1 but is not yet in the repository.
[AI] (Brett) respond to the piece of feedback we received during the con= sultation. Note: Please see Brett's draft in the AAC scribing d= oc and provide feedback.
Baseline Processes Roadmap
The InCommon staff is meeting regularly to plan baseline expectatio= ns implementation. A Baseline Processes Roadmap is under development b= y Ann, Erin, Dean and Tom. Nick Roy is reviewing it.
This roadmap includes the term =E2=80=9Centity healthcheck=E2=80= =9D which seems like a good framing. It was noted that Nick Roy= had raised some concern around the feasibility of the timeframe, The goal = is to present this roadmap to Steering at their call prior to TechEx
[AI] Tom will add a =E2=80=9Cswim lane=E2=80=9D for InCommon Steer= ing on the Baseline Expectations roadmap. Could be shown as a continu= um from the AAC to Steering. Tom will add the term docket
Outreach on Baseline Expectations Implementation
It was suggested to have a monthly blog in on Baseline Expectations as p= art of the Trust and Identity Newsletter. This could involve regular notifi= cations of entities who have not updated their metadata (the docket).  = ; For reference on past blogs on the BE topic, see =E2=80=9CThis Af= fects You! InCommon Federation Requirements Changing=E2=80=9D <= span style=3D"color: rgb(0,0,0);">blog from July 2017 by Tom Barton:= https://www.internet2.edu/blogs/detail/14285 There may b= e future blog post(s) that includes the stats presented for Steering regard= ing MDUI issues. The goal is to see improvement in numbers over the m= onths. Another approach could be to include a graph on the baseline expecta= tions wiki and show improvement over time.
Community Assurance Call for Wed., October 4, 2017
The Community Assurance call for Oct 4 will focus on
Charting the Assurance Advisory Com= mittee=E2=80=99s Future
Survey results of InC Bronze memb= ers
Baseline Expectations and AAC res= ponsibilities
Membership changes needed in the = AAC
Adjustments to AAC charter and re= cruitment of new members
Brett will lead this call with Ann = and Tom.
[AI] (Brett) work on proposed updates to AAC charter. Ann is available t= o assist.
https://www.incommon.org/docs/assurance/AAC_Charter.pdf=
Renewals of InCommon Bronze Certifications
Other Topics
FICAM
Program Review of InCommon Assuranc= e Program=E2=80=A8 (Tom)
Results of Tom=E2=80=99s outreach= to the InCommon Assurance Bronze institutions for feedback.
InCommon support for REFEDS Assuran= ce Framework v1.0 metadata attribute=E2=80=A8
NB from Tom. There will likely be= no entity attribute in v1.0 of the framework.
AAC participation on new TAC Workin= g Group: Attributes for Collaboration and Federation WG - Draft Charter:=E2= =80=A8 https://spaces.at.internet2.edu/x/ipiTBg<= /span> -- Mark Scheible would like a representative from the= AAC to participate on this WG. Brett will represent the AAC.
Brett noted that on a recent REFEDs IdP Categorisation call, there= was a question about entity categorisation and possible objections to an e= ntity=E2=80=99s use of a particular category. Brett mentioned on that= call that AAC has developed a dispute resolution process to handle issues = like this. Nicole stated that REFEDs has such a process and working t= hru 1st case currently.
Next AAC call: Wed., Sept. 27, 2017 at 4pm ET&nbs= p;