Date: Thu, 28 Mar 2024 20:50:31 +0000 (UTC) Message-ID: <398008697.6985.1711659031038@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6984_961429988.1711659031038" ------=_Part_6984_961429988.1711659031038 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
https= ://meetings.internet2.edu/2019-technology-exchange/detail/10005609/
Thanks to John Krienke for these notes
For reference
Welcome and Intro
Baseline Expectations (BE) next phase
Review 5 items for proposed community consensus:
What issues do you anticipate we=E2=80=99ll encounter with each of= these?
What timeframe should we ask the community to meet each of these r= equirements?
A rough timeline framework for BE next steps:
All these steps may take up to one year from concept presentation,= consensus process, implementation, and may vary based on community uptake.=
Additional topics and notes:
Community Dispute Re= solution Process. To remedy disputes between and among InC= ommon Participants.
Important to note: There is no unilateral decision that CTAB will = make to change Baseline Expectations. The community consensus process is al= ways invoked for changes.
A Guidance Document is being created by Albert Wu of CTAB. ( =
v1 adherence draft
Discussion of the 5 proposed changes:
SIRTFI: SIRTFI is also making some changes.= How will the changes and requirements be managed? SIRTFI will manage versi= ons with version control numbers (i.e., 1.0, 2.0).
TLS: Moving targets may also be an issue with TLS= as well. There might be a way to use a benchmarking tool like SSL Labs.&nb= sp;
Ways to measure each of the components of BE. The guidance d= ocument (URL above) intends to capture how we will implement and measure me= eting each requirement.
ErrorURL: This one speaks to a = consistent user experience. What content should be on the page? Comments?&n= bsp;
There was agreement that ErrorURL=
is for sending users to on a fatal error where the SP can't function. =
; Otherwise the SP should continue, perhaps suggesting the user contact the=
IdPO about the "problem".
MFA: Just the ability to signal MFA. <= /span>
Begin communicating now that changes are afoot, even though we may= not be ready with the actual recommendation.
Maybe a Roadmap that we will eventually be going here.
SP side. We need to tap into new voices.
End of session.