Skip to Content.
Sympa Menu

interfed - Re: [inc-interfed] recommendations to TAC

Subject: Interfederation

List archive

Re: [inc-interfed] recommendations to TAC


Chronological Thread 
  • From: Mark Scheible <>
  • To:
  • Subject: Re: [inc-interfed] recommendations to TAC
  • Date: Wed, 12 Jun 2013 12:37:49 -0400
  • Authentication-results: sfpop-ironport04.merit.edu; dkim=neutral (message not signed) header.i=none

Per Jim's comments below...

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?

I think the idea of splitting some of the work up between groups is a good idea, however, I think having the TAC (or some Interfederation Subgroup) retain the responsibility for the items will keep the efforts coordinated.  Similar to the REFEDS workplan items, but the actual work may be done by someone else (e.g. InCommon Operations, The Quilt, etc.).

Just my $.02.

Mark


On Wed, Jun 12, 2013 at 11:54 AM, Basney, Jim <> wrote:
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




--

Mark A. Scheible
Sr. Lead IAM Solutions Architect
MCNC, Research Triangle Park, NC
Office: (919) 248-1997
Cell: (919) 609-8595
Fax: (919) 248-8419



Archive powered by MHonArc 2.6.16.

Top of Page