Skip to Content.
Sympa Menu

interfed - Re: [inc-interfed] value of InCommon joining eduGAIN

Subject: Interfederation

List archive

Re: [inc-interfed] value of InCommon joining eduGAIN


Chronological Thread 
  • From: Tom Scavo <>
  • To: Interfederation TAC Subgroup <>
  • Subject: Re: [inc-interfed] value of InCommon joining eduGAIN
  • Date: Tue, 28 May 2013 18:07:19 -0400
  • Authentication-results: sfpop-ironport02.merit.edu; dkim=pass (signature verified)

On Tue, May 28, 2013 at 5:10 PM, Ian Young
<>
wrote:
>
> On 28 May 2013, at 21:36, Tom Scavo
> <>
> wrote:
>
>> I'm pretty confident in saying eduGAIN metadata would NOT be bundled
>> in the current InCommon aggregate.
>
> It's worth clarifying which of the following you mean:
>
> * nothing that comes through eduGAIN can ever be bundled into InCommon's
> production aggregate

Not without additional policy and procedure that essentially renders
that metadata equivalent (in terms of technical trust).

> * after reviewing participant registration policies, metadata from *some*
> eduGAIN participants and acquired through eduGAIN might be bundleable into
> InCommon's production aggregate

I don't read InCommon POP statements and I won't be reading federation
registration policies any time soon. Like the POP, I would be in favor
of operationalizing these policies, that is, creating infrastructure
that would allow a responsible person to self-attest compliance to
some written, concrete set of requirements, at which point I would add
an entity attribute or entity descriptor to metadata.

> * nothing that comes through eduGAIN can ever be republished even as a
> separate "InCommon+interfederation" aggregate

If we were to sign the eduGAIN agreement, I assume we would
immediately make the eduGAIN metadata available to our members. The
wiki page that goes along with that new aggregate will be written by
John, however.

Whether or not InCommon entity descriptors would appear alongside
other entity descriptors is an open question. In either case, the
member has to configure a separate metadata aggregate, so I'd rather
keep the entity descriptors separate, in separate files.

> * after reviewing participant registration policies, metadata from *some*
> eduGAIN participants and acquired through eduGAUN might be republishable as
> part of a separate "InCommon+interfederation" aggregate

No need for this if we're willing to accept the previous option, right?

> Remember, there's really no such thing as "eduGAIN metadata", just metadata
> registered by eduGAIN participant federations that is aggregated by the
> eduGAIN service.

Same thing.

Tom



Archive powered by MHonArc 2.6.16.

Top of Page