Date: Fri, 29 Mar 2024 06:39:12 +0000 (UTC) Message-ID: <716626815.7561.1711694352313@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7560_1014582969.1711694352311" ------=_Part_7560_1014582969.1711694352311 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Attendi= ng= : Eric Kool-Brown, Matt Brookover, Janemarie Duh , Kim Mil= ford, Heather Flanagan, Mike Grady, Keith Wessel, Mark Scheible, Eric Goodm= an, Judith Bush, Tom Demeranville
With: Ian= Young, David Walker, Shannon Roddy, Dave Shafer, Ann West, Steve Zoppi
Working on Federation Manager interface related to= Baseline Expectations
Rolled out upgrades to metadata aggregator<= /p>
Shannon Rodd= y and Scott Cantor discussed the XML vulnerability revealed last month and = that several vendors are vulnerable. The level of responsiveness varies. Th= e discussion led to an idea to involve REN-ISAC to facilitate a private dis= cussion among schools about those vendors. This would also help schools to = work together rather than individually. The intent would be to work with th= e vendors on fixes. Kim Milford said that REN-ISAC has not discussed this, = but in a previous effort, used a Google document to track comments fr= om campuses and the status of each affected vendor. That may serve as a mod= el for this.
Today, InCom= mon is sending a 90-day notice about the change in the Participation Agreem= ent (PA). This also will serve as the notice of the change in the FOPP (whi= ch is effective immediately). The new PA and FOPP are both on the website. = That means Baseline Expectations goes into effect as of the end of the 90-d= ay notice (June 15). The PA changes are mainly changing the dispute resolut= ion process and citing Baseline Expectations (and eliminating the POP).
The Communit= y Trust and Assurance Board is refining the community consensus process and= dispute resolution process for the June 15 date.
Project Portfolio - Ann shared the updated = project portfolio, which will become a standing item on the TAC information= al items. The document also includes links to working group updates. InComm= on staff will work with the working group chairs to update these monthly. <= /span>
Deploym= ent Profile (Keith Wessel) - The group is working through a list of minor cha= nges to their report and expect to have a finished SAML2int draft next week= .
OIDC (Eri= c Kool-Brown) - No report; the last two meetings have been cancelled.
Streaml= ining SP Onboarding (Judith) - The group is editing a questionnaire. Janemari= e reported that she used some of the working group=E2=80=99s work with a ve= ndor this past week - the vendor belongs to InCommon but does not have an S= P in metadata. The WG is also working on a value statement for joining InCo= mmon and on a Shibboleth primer.
Attribu= tes for Collaboration (Mark Scheible) - Working group members have wrapped up= interviews with CIOs of some organizations that are not releasing R&S = attributes. The group is also analyzing the results of a survey and will wo= rk on a summary and development of a white paper.
Nick Roy d= rafted updates for duties of TAC and other aspects of the TAC charter. The char= ter revision is being driven by changes in TAC responsibilities, the move t= oward more global interactions, and other items. Discussion of the charter = included:
Should the charter list an educational component/r= esponsibility for TAC? Do TAC responsibilities include recommending educati= onal needs related to the technology and use of the Federation? As a sideli= ght, there is a need to organize existing information to make it easier to = find.
There is little related to technology in the chart= er. That may be good, but it may also indicate the need for a name change f= or TAC.
Working Groups generally have a technical focus, b= ut they typically identify needs for education and outreach, as well.
It would be good to ask Steering about their expec= tations for TAC
TAC=E2=80=99= s focus for 2018 will likely include:
How TAC relates to CACTI (with Chris Phillips) = - now scheduled for April 12th call
ADFS support in InCommon (also with Chris Phill= ips) - now scheduled for April 12th call
= li>Review of the implementation profile and deploy= ment profile work with Walter Hoehn and Keith Wessel - why/how/what did we = intend to influence (in prep for next steps with this work)
"What are your challenges in federation?"
How to get the US community more engaged in REF= EDS working groups
REFEDS meeting at TechEx
TAC leadership endorsement of community partici= pation in REFEDS
Possibly have Nicole Harris talk to TAC about R= EFEDS (background, current work plan)?
Focus on TAC/CACTI partnership/relationship
Others?