Date: Fri, 29 Mar 2024 14:07:47 +0000 (UTC)
Message-ID: <1628761899.8073.1711721267869@ip-10-10-7-29.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_8072_1012946796.1711721267869"
------=_Part_8072_1012946796.1711721267869
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
InCommon TAC Meeting Minutes - October 7, 2015
Attending: Keith Hazelton, Tom Barton, Michael Gettes, =
Steve Carmody, Jim Basney, Scott Cantor, David Walker, Steve Olshansky
With: Nick Roy, Ann West, Dean Woodbeck, Tom Scavo, Pau=
l Caskey, Nate Klingenstein, Steve Zoppi, IJ Kim
InCommon Road=
map
TAC went through a process of determining which of the proposed 2016 roa=
dmap topics need clarity. This is the beginning of a process for developing=
2016 priorities. Relevant documents include:
Comments on specific topics included:
- IdPv3 adoption -- much of this is is communications, training, outreach=
work (as opposed to technical work)=E2=80=A8
- MDQ project - is this software production level? The metadata aggregato=
r is basic to eduGAIN. (AI) TAC needs an assessment of the MDQ project/soft=
ware=E2=80=A8
- Making Federation Easier - This topic is still receiving contributions =
from a number of areas (packaging WG, developing communications plans, deve=
loping curricula, doing marketing survey)=E2=80=A8
- Executive Portal Production - This will save time (particularly for Ang=
i and Sally), but we have limited time from developers. Federating the CM w=
ould also be a time saver.=E2=80=A8
- IdP of Last Resort - A main concern in any recommendation of an IdPoLR =
is ensuring longevity and sustainability.=E2=80=A8
- Consent Early Adoption - (AI) TAC needs to develop a consent strategy, =
asking for feedback from the LARPP group (Lifestyles of the Attribute Rich =
and Privacy Preserved)=E2=80=A8
TAC Membership<=
/h3>
There was an extensive discussion about development of criteria that wou=
ld outline TAC=E2=80=99s role and also TAC membership. TAC has evolved to b=
oth supporting InCommon Operations and also representing the community for =
input to InCommon services. Suggestions included:
- Setting up an Ops subcommittee or spinning off an Ops group=E2=80=A8
- membership in this should be based on expertise (and may not require TA=
C membership)=E2=80=A8
- Scoping what TAC does and is responsible for (vs. InCommon Steering and=
TIER Architects). TAC would discuss operations and the long-range planning=
and advice could be moved elsewhere=E2=80=A8
- TAC needs to move away from the model of selecting its own members=E2=
=80=A8
- TAC needs diversity (of institutional size and gender)=E2=80=A8
- TAC needs to be able to detail the expectations of membership to potent=
ial members=E2=80=A8
- TAC needs some sort of exit criteria, perhaps based on requirements (me=
eting attendance, etc)=E2=80=A8
(AI) Steve Carmody will develop a strawman document for TAC membership a=
nd requirements by the next meeting=E2=80=A8
There was consensus that two groups should exist - one that is strategy/=
architecture (which would be broad in scope and membership) and one that is=
focused on operations (with membership based on expertise).
- The Ops group would focus on federation, cert service and eduroam (tact=
ical and technology) and note report to Steering, but to InCommon. Membersh=
ip would be flexible and driven by needs. Focus is on the =E2=80=9Chow.=E2=
=80=9D
- The strategy group would have some members participating based on exper=
tise and some rotating and based on broader community representation. This =
group would focus on prioritization and longer range thinking, focusing on =
=E2=80=9Cwhat=E2=80=9D and =E2=80=9Cwhen.=E2=80=9D This could be a trust/id=
entity group and span InCommon and TIER.=E2=80=A8
Next Meeting - Thursday, Oct. 15 - 2 pm ET
------=_Part_8072_1012946796.1711721267869--