Date: Thu, 28 Mar 2024 20:53:13 +0000 (UTC) Message-ID: <479339204.6991.1711659193298@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6990_1022986546.1711659193295" ------=_Part_6990_1022986546.1711659193295 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Attending:
Action Items
[AI] (Tom) develop guiding principles for dispute resolution process
[AI] (Ann) continue to work on the Draft Processes to Implement and Maintai=
n Baseline Expectations
[AI] (Brett) make additional updates to the Diagram, Community Dispute=
Resolution Process=E2=80=A8.
[AI] (Tom and Brett) review documents to make them more generic so they cou=
ld apply more broadly, such as to handle issues around tags such as R&S=
or SIRTFI. =E2=80=A8
Representative from AAC to TIER working groups
Joanna is participating on TIER security and Audit Working Group, chaired b=
y Helen Patton. Joanna primarily listens and is available to provide =
an audit perspective as needed. Joanna will keep the AAC informed. &n=
bsp;
Key documents:
Ann has edited the Dr= aft Processes to Implement and Maintain Baseline Expectations docu= ment and done some reorganization .As discussed on the last AAC call,= a goal is to be able to use this process for other purposes, beyond baseli= ne expectations, such as to handle issues around tags such as R&S or SI= RTFI. =E2=80=A8Complaints to be handled through this process may come= from =E2=80=A8
The plan being considered is that the =E2=80=9CAAC docket=E2=80=9D will = be public. Security incidents will get moved to incident response process a= nd will not be on the AAC docket. InCommon adds the entity complained again= st to the public AAC docket list along with a lightweight description (ie = =E2=80=9Cmetadata inaccuracy=E2=80=9D). The list that=E2=80=99s on th= e AAC docket will be added to the monthly InCommon newsletter. If iss= ue is not addressed by next InCommon newsletter, then action is taken (such= as removing the entity from metadata).
It was noted that much detailed work was done on the bronze and silver p= rofiles that is not used on regular basis. We want to keep in mind to start= simple and develop as needed as we develop baseline practices.
Sharing Baseline Expectations Implementation work with InCommon =
staff and with Steering
It would be good to share some of the AAC=E2=80=99s work around baseline ex=
pectation implementation with InCommon Steering and other groups at Global =
Summit. Steering has already approved the Baseline Expectations polic=
y. Sharing of baseline expectations implementation plans would be an =
FYI. Ann is currently sharing the implementation plans with InCommon =
staff. Ann hopes we will be underway with the baseline expectations =
rollout by end of 2017.
Strawman Schedule for implementing Baseline Expectations is here.
Meeting with Kantara on Sunday, April 23, 2017
At Global Summit, there will be discussion with Kantara on Sunday April 23= span>, 10am - 2pm to talk about aligning profiles between InCommon and = Kantara. Complying with the new NIST SP 800-63 could be time consuming and = working together will be helpful. One topic may be the expected upcoming wo= rk around the revised NIST SP 800-63 digital identity guidelines.
It was noted that NIST SP 800-63 input period (for the parent docu= ment only) has been extended until May 1. For details see here.
Global Summit Session of interest:
AAC Face-to-Face = at Global Summit is Tues. April 25, 2:30pm - 4pm=E2=80=A8 ET
Suggested agenda=E2=80=A8 items=E2=80=A8
Community Assurance Calls (not discussed on the AA=
C call due to lack of time)
=E2=80=A2 Next InCommon Community Assurance Call : Wed. May 3 at noon ET=E2=
=80=A8
=E2=80=A2 Plans for this call?=E2=80=A8
Next AAC call after Global Summit: Wed May 10, 201= 7 at 4pm ET