Attending
- Brett Bieber, University of Nebraska (chair) =E2=80=A8
- Mary Catherine Martinez, InnoSoft (vice chair)
- David Bantz, University of Alaska =E2=80=A8
- Ted Hanss, University of Michigan =E2=80=A8<=
/li>
- Jon Miner, University of Wisc - Madison
- Joanna Rojas, Duke
- Tom Barton, U. Chicago
- Chris Hable, U. Michigan
- Chris Whalen, National Institute of Allergy and Infectious Diseases (NI=
AID)
- Kevin Morooney, Internet2 =E2=80=A8
- Ann West, Internet2 =E2=80=A8
Regrets: Nick Lewis, Emily Eisbruch
New Action Items
- AI Ann ask the InCommon BE Expectations operational staff to revie=
w the community Consensus Process doc prior to community consultation.
- AI Tom, Mary Catherine and ChrisH will participate in conversatio=
n with InCommon Ops on cycle times for escalating health check failure=
s
- AI Brett, David, and Ann will work o=
n scoping the privacy policy guidance effort. ChrisW will help moving forwa=
rd
- AI ChrisH and Brett will work on log=
o issues.
Discussion
Vice Chair
- Congratulations to Mary Catherine Martinez, new Vice Chair of CTAB, aff=
irmed by InCommon Steering.
BE Community Consensus Process Doc
- Doc is coming along well. Thanks to the CTAB members who have worked on=
it
- The group discussed using moderators for discussions and how to address=
anonymous contributions to a discussion (see the Rules of the Road section=
of the doc)
- Decision: Before moving to community consultation it was suggested to a=
llow review by InCommon staff.
- AI Ann ask the InCommon BE Expectations operational staff to revie=
w the community Consensus Process doc prior to community consultation.
Baseline Expectations Progress
- CTAB should help set cycletimes for escalating health check failures
- AI Mary Catherine and ChrisH will participate in conversation wit=
h TomB and InCommon Ops on cycle times for escalating health check fai=
lures
Finalize Privacy Guidance/Recommendations
- Coherent guidance on privacy policy will be needed.
- Need to understand who is the audience
- We are at a discovry phase on what will be useful
- Ann: we could provide communication to InCommon Execs and Site Admins i=
ncluding steps such as these from last call.
- short-term suggestions to the community (there could be more):
- Link to whatever privacy policy you have in your POP (This works =
for the 50% that have POPs)=E2=80=A8
- Refer to privacy policies available through Educause HEISC, even if not=
federation related=E2=80=A8
- Develop a web page that links to established organizational polic=
ies related to privacy (data sharing, FERPA release, AUP, etc) as a first s=
tep=E2=80=A8
- a privacy policy could include info on Logo Guidance, SAMLInt recommend=
ations
- AI Brett, DavidB, Ann will work on scoping the privacy policy guidance =
effort. ChrisW will help moving forward
Questions from John Krienke on community consensus and dispute res=
olution
- Who writes to the Docket? InCommon B Mgr or a CTAB rep?
- Who notifies and communicates with the Participants?
- Does each Dispute need a separate Review Board? Selection based on cont=
acts in MD, so would assume, yes.
- Each CTAB+RB needs its own confidential space, email list, meeting sche=
dule.
- What happens when the 2 month timer runs out?
AI ChrisH and Brett will work on logo guidance issues.
CTAB Meeting at 2018 Global Su=
mmit, Wednesday, May 9, noon-1:00PM
Next CTAB call: Wed. April 25, 2018