Date: Fri, 29 Mar 2024 06:20:19 +0000 (UTC) Message-ID: <451251612.7541.1711693219055@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7540_2067593364.1711693219047" ------=_Part_7540_2067593364.1711693219047 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Attending
Mary Catherine Martinez, Inno= Soft (chair)
David Bantz, University of Al= aska (vice-chair)
Rachana Ananthakrishnan, Glob= us, University of Chicago
Tom Barton, University Chicag= o and Internet2
Brad Christ, Eastern Washingt= on University
Eric Goodman, UCOP - TAC Repr= esentative to CTAB
John Hover, Brookhaven Nation= al Lab
Jon Miner, University of Wisc= - Madison
John Pfeifer, University of M= aryland
Chris Whalen,
Ann West, Internet2
Albert Wu, Internet2= p>
Emily Eisbruch, Internet2&nbs= p;
Regrets
Brett Bieber, University of N= ebraska
Chris Hable, University of Mi= chigan
= Adam Lewenberg, Stanford
Draft Report to InCommo= n Steering to Close out Baseline Expectations Phase 1 = span>
There are two documents to be p= resented to InCommon Steering
1. Exec summary = span>
this will go to Docume= nt Repository
2. InCommon Baseline Expectat= ions Closeout plan, this is an Appendix listing orgs with entities not meet= ing Baseline Expectations
Broken into relevant categori= es
Recommended actions are based= on risk level
There is also an Appendix wit=
h summary of outreach that has occurred
Decision: on March 28, = 2019 there will be an announcement that April 8 we are turning on enforceme= nt of consequences for those not meeting Baseline Expectations <= /span>
April 15, 2019 we will announ= ce to community the results of the InCommon Steering decision
May 15, 2019 will move = to remove entities not meeting Baseline Expectations from metadata= p>
For bilateral entities, will = not remove from federation, but will notify the bilateral partners if we ca= n find that info
Suggestion to add more detail= in the closeout plan report around handling of bilateral entities= p>
Question about using the term =E2= =80=9Ccloseout=E2=80=9D; could sound too final since there are next phases = of Baseline Expectations
Decision: remove the wo= rd =E2=80=9Cfinal=E2=80=9D
Should report be seen as comi= ng from CTAB to InCommon Steering? Instead of from =E2=80=9C InCommon Ops a= nd CTAB=E2=80=9D YES, DONE
Risk Level to federation, in = what context? We should define this better .
Risk to reputation?
Risk of leaving these entitie= s not meeting baseline?
What is the downside to takin= g this entity out of metadata?
Decision: change =E2=80=9Cris= k=E2=80=9D to =E2=80=9Cimpact to the federation of recommended= action =E2=80=9D
Albert made this change= this
Best way to handle&nb= sp;test IDPs that do not meet baseline? Suggestion to remove = them
Albert reports that there i= s only one test IDP not meeting Baseline. Albert resolved that issue in the= doc.
Albert provided an over= view of the rollback plan so if need be, it will be possible to place an en= tity back into federation.
This addresses the risk that = site admin sees entity in edit mode and can=E2=80=99t comply with BE, and w= e need to work to accommodate them.
It was noted that SPs on the = list of entities not meeting baseline is an area of concern
Suggestion to add info on whi= ch entities have not paid their InCommon invoice
[AI] Albert will add to the r= eport info on which entities that have not met Baseline Expectations have n= ot paid their InCommon invoice
Albert has started drafting= notice about mandatory enforcement in Federation Manager and will share th= at and hopes to send tomorrow.
Tom moved that CTAB approve= the report. ChrisW seconded
All agreed.
There will be a pre-read as= k to InCommon Steering
Albert will draft slides fo= r Monday April 1, 2019 InCommon Steering call
=Next CTAB = Call: Wed. April 10, 2019<= /span>