Date: Fri, 29 Mar 2024 13:20:33 +0000 (UTC)
Message-ID: <1603852540.8005.1711718433435@ip-10-10-7-29.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_8004_346318289.1711718433434"
------=_Part_8004_346318289.1711718433434
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
=
InCommon TAC Meeting 2014-11-13
Thursday, November 13, 2014
1:00pm ET | 12:00pm CT | 11:00am MT | 10:00am PT
Attending: Steve Carmody, Nick Roy, Scott Cantor, Mike =
Lahaye, Keith Hazelton, Tom Barton, Jim Basney, Paul Caskey, David Walker=
p>
With: John Krienke, Dean Woodbeck, Ann West, IJ Kim, Na=
te Klingenstein, Steve Zoppi
Carryover Action=
Items
(AI) Steve Carmody and John Krienke will prune the list to no more than =
a quarter of this size
(AI) TAC review the list and let Dean know if done or not
TAC 2015 Priorities=
This continued the discussion from the Oct. 29, 2014, meeting, concernin=
g the priorities for 2015. The list generated during the Oct. 29 meeting wa=
s split into two lists, one listing =E2=80=9Cproblems=E2=80=9D and the othe=
r listing =E2=80=9Csolutions.=E2=80=9D The goal is to develop a shorter lis=
t to send to the Steering Programs Subcommittee to include with their prior=
ity-setting work.
The five priorities from the "problems" list to be forwarded are:
- There is an insufficient baseline of expectations of Participants and A=
ffiliates, and a lack of monitoring or providing feedback about this status=
, and insufficient tools to implement some desirable expected behaviors.
- InCommon communicates with member campuses via Central IT (whose primar=
y concern may be interoperating with commercial SPs); however, InCommon is =
also serving the instructional and research communities on those campuses, =
and is dependent on the relationship between those groups on each campus. C=
onsequently, InCommon is more effective at supporting commercial SPs, and l=
ess effective at supporting instructional and research SPs.
- It's still too hard for Participants to federate, including internal ci=
rcumstances and implementation of federation technology
- InCommon itself is not yet sufficiently capable of adapting to its evol=
ving environment, technologically and among other R&E Feds. (resources,=
prioritization, process to reach consensus).
- Federation value proposition is not well understood by members and non-=
members alike, or high enough for some parties. Further, InCommon=E2=80=99s=
purpose is not clearly established and understood.
The five priorities from the "priorities/solutions" list are:
- Develop a more effective practice to monitor, measure, report, inform, =
remind, publish, =E2=80=A6, a variety of participant expectations, and to b=
etter establish federation value and effectiveness of its programs
- Outreach programs with the objective to help campuses work their intern=
al circumstances to be able to release attributes and participate in securi=
ty incident response. Might be direct to campus, might be direct to other o=
rgs that in turn reach out to campuses. (reworded by stc =E2=80=93 Change t=
he community=E2=80=99s perception of attribute release, from =E2=80=9Csomet=
hing to be avoided=E2=80=9D to =E2=80=9Csomething that=E2=80=99s necessary,=
in order for our communities to collaborate, and its perfectly legal to do=
so=E2=80=9D.) (Ramp up and focus outreach efforts on getting campuses to a=
dopt recommended best practices; attribute release and security incident re=
sponse)
- Finish specification and implementation of IdPoLR for R&S. (reworde=
d by stc - Create options allowing faculty and staff from campuses that do =
NOT operate IDPs that release attributes to R&S SPs to participate in I=
C. eg idpolr, S2S GW) (in support of research and scholarship)
- Make it easier for a campus to be represented by an IDP (easier for the=
m to deploy, easier for them to get someone else to deploy it for them) (Al=
t IDPs WG recommendations; tie to problem #3)
- Fully design and implement edugain integration. (including participatin=
g in best practice discussions)
(AI) Steven Carmody and Keith Hazelton (and whomever else wishes to) wil=
l edit these for clarification and to send to Steering Program subcommittee=
.
Internet =
Spaces Wiki to eduGAIN
There have been requests to include the spaces wiki as an SP exported to=
eduGAIN. IJ is working on this.
MARI Plan
Scott discussed the MARI plan (which was discussed at ACAMP) and has con=
e a patch. The =E2=80=9Cmeta=E2=80=9D attribute concept was discussed at AC=
AMP and on the REFEDS email list (https://www.terena.org=
/mail-archives/refeds/msg04692.html)
Next Meeting =E2=80=93 Thursday, December 11 =E2=80=93 1 p=
m ET
------=_Part_8004_346318289.1711718433434--