Interfederation

["Basney, Jim" <>]

attending: JimB, IJK, IanY, ScottC, WarrenA, TomS, SteveC, ChrisP, JohnK,
MarkS, AnnW

Warren Anderson from LIGO joined us.
Interfed work very important to LIGO.
Warren might be willing to lead follow-on subgroup.
TomS: Does charter give option to go beyond June 28?
Follow-on subgroup will need a new charter.
Recommendations to TAC (https://spaces.internet2.edu/x/Dw9OAg):
Too many items. Some way to bundle them?
Additional flexibility needed in metadata infrastructure.
Interfed group provides specific requirements for metadata flexibility to
metadata working group.
Discussion of trust practices/policy could proceed in parallel.
Grouping possibilities:
* Trust practices/policy for entity registration/publishing
* Code of Conduct: Attribute release / privacy policy
* Technical aspects of metadata management/publication/aggregation/tagging
* International Interfederation agreements with eduGAIN/UK
* Inside US ("Domestic") Interfederation (The Quilt)
Use case of one university wanting a metadata distribution of only its
own entities. Separate metadata aggregate? Filtering?
In this use case some local entities would not be included in InCommon
aggregate.
Numbered list of recommendations instead of bullets.
Mention Canadian Access Federation in eduGAIN paragraph.
What is role of follow-on group versus InC Operations?
Can Operations help us understand how subgroup can help?
Subgroup can provide advisory/review role to assist operations.
MDRPI work is a pre-requisite for eduGAIN work?
Label 4th bullet as "input aggregate".
1st bullet (eduGAIN): Explore facilitating interoperation with
InCommon and eduGAIN entities. Policy/trust issues. Learning how to
import aggregates and product export aggregates.
Overall goal: interoperable interfederation.
Policy and mechanism/technical items.
Becoming eduGAIN member isn't totality of interfederation.
Where does code of conduct fit?
Privacy should be its own high-level item.
What is process for forming next group?
TAC members from this group will participate in TAC-level discussion.
Recommendations to be discussed on Jun 27 TAC call.
Then need a new proposed charter.
JimB will propose a follow-on charter to TAC on Jun 27.
What is driver for follow-on?
Pilot project with eduGAIN would be a good concrete effort.
Organize follow-on effort around LIGO driving use case.
Warren agrees that LIGO can continue to help drive things forward.
Driving use case on national side?
About "InCommon support for hierarchical federation":
Confusing to say "hierarchical".
This is about K-12 use cases.
This is "Inside US Interfederation"?
"Domestic interfederation"? "Cross sector"?
UNC system was interested but conflict with this group's meeting times.
Wisconsin system could also be interested.

Stand by for follow-up messages from JimB after wiki edits...