Skip to Content.
Sympa Menu

interfed - [inc-interfed] June 11 agenda / June 4 notes

Subject: Interfederation

List archive

[inc-interfed] June 11 agenda / June 4 notes


Chronological Thread 
  • From: "Basney, Jim" <>
  • To: "" <>
  • Subject: [inc-interfed] June 11 agenda / June 4 notes
  • Date: Tue, 4 Jun 2013 17:50:55 +0000
  • Accept-language: en-US
  • Authentication-results: sfpop-ironport02.merit.edu; dkim=neutral (message not signed) header.i=none

Proposed agenda for June 11 call:

* InCommon-eduGAIN timeline needed by LIGO
* Agreeing on WG recommendations to TAC
* Future of this WG

Minutes from June 4 call:

attending: JimB, IanY, ScottC, MarkS

Limited attendance due to conflict with TNC.
Discussion of WG continuing beyond June.
Haven't reached sustainable momentum yet for InCommon interfed.
WG needs to keep pushing beyond June.
JimB: Maybe go to calls once per month?
IanY: That's better than closing the group.
Coming back to interfed after WG hiatus would be problematic.
MarkS: Continued WG effort would be valuable for The Quilt/InCommon.
Policy and process discussions around eduGAIN can inform
interfederation with regionals.
Also learning more from hub-and-spoke models and K-12 support models
in Europe can be valuable to The Quilt/InCommon effort.
New topic: Comparing eduGAIN to REEP
REEP is a registrar, eduGAIN isn't. Each eduGAIN participant is a
registrar with a baseline of practice, but eduGAIN doesn't guarantee
consistent practice across eduGAIN members.
IanY and JohnK talked on Friday about this.
Ideally we want trustworthy interchange of trustworthy metadata about
trustworthy entities.
Bilateral interfed gives you trustworthy exchange of metadata.
eduGAIN will give trustworthy exchange of metadata.
How do we know metadata itself is trustworthy
(i.e., registration practices)?
eduGAIN registrars each have documented practices.
InCommon could review registration practices for each eduGAIN member.
Not scalable but a way forward in short-term.
In long-term need standard baseline for registration practices.
Interest in REFEDS codifying registration practices.
Would be helpful for UK and US to document their registration
requirements as input to REFEDS.
Joining eduGAIN doesn't mean InCommon needs to immediately use all
metadata from all eduGAIN participants.
A roadmap forward:
* bilateral metadata exchange between InCommon and UK
* bilateral registration trust between InCommon and UK
* switch to metadata exchange via eduGAIN rather than directly
but keeping bilateral registration trust
Ongoing issue: limited effort/focus for many InCommon tasks.
InCommon needs effort on metadata signing.
That might take some focus off of interfed.
IanY talked with LeifJ on Monday: agreed to exchange metadata between
Sweden and UK on trial basis as precursor for using eduGAIN for
metadata exchange.
KB+ service in UK hooked up with IdPs in Sweden.
IanY and ScottK also starting to work on connecting Glasgow w/ LIGO.




Archive powered by MHonArc 2.6.16.

Top of Page