Skip to Content.
Sympa Menu

interfed - [inc-interfed] recommendations to TAC

Subject: Interfederation

List archive

[inc-interfed] recommendations to TAC


Chronological Thread 
  • From: "Basney, Jim" <>
  • To: "" <>
  • Subject: [inc-interfed] recommendations to TAC
  • Date: Wed, 12 Jun 2013 15:54:29 +0000
  • Accept-language: en-US
  • Authentication-results: sfpop-ironport01.merit.edu; dkim=neutral (message not signed) header.i=none

Hi,

I made a first pass at turning our "Potential future work" items [1] into
recommendations to TAC [2]. In summary:

The subgroup recommends that TAC convene a follow-on subgroup to work on
the following items:


* InCommon becoming an eduGAIN member.
* InCommon interfederating with UK federation.
* InCommon adding <mdrpi:PublicationInfo> and <mdrpi:RegistrationInfo>
elements in metadata.

* InCommon providing one or more production interfederation metadata
aggregates for its members.

* InCommon providing one or more production "export" metadata aggregates
for consumption by external partners (UK, eduGAIN, etc.).

* Documentation of InCommon registration practices.
* InCommon support for hierarchical federation.
* InCommon support for additional entity tags.

* InCommon support for a version of the Code of Conduct that extends
beyond the EU.


There's additional explanatory text on the wiki page [2].

This is a long list of work items for a single subgroup. Are some items
better suited to other subgroups? Should the hierarchical federation item
be owned by The Quilt group and the entity tag and mdrpi items owned by
the metadata group and the documentation of registration practices owned
by an operations subgroup? Should we just say "one or more follow-on
subgroups" and leave it to TAC to organize?

As always, please feel free to edit the wiki directly.

Thanks,
Jim

[1]
https://spaces.internet2.edu/display/incinterfed/Interfederation+Lessons+Le
arned#InterfederationLessonsLearned-Potentialfuturework
[2]
https://spaces.internet2.edu/display/incinterfed/June+2013+Recommendations+
to+TAC




Archive powered by MHonArc 2.6.16.

Top of Page