Refeds


Subject Re: Input for InCommon's Steward Program
From Niels van Dijk <niels.vandijk@xxxxxxxxxx>
Date Mon, 9 Nov 2015 21:43:48 +0100 (CET)

Hello David,

Sorry for not responding to your questions but asking one in return:
Do you have any use cases where you would need to "label" these K-12 schools and community colleges so Services would be able to distinguish between such entities and higher ed entities?

many thanks,
Niels

----- Original Message -----
> From: "David Walker" <dwalker@xxxxxxxxxxxxx>
> To: refeds@xxxxxxxxxx
> Cc: "DWI2" <dwalker@xxxxxxxxxxxxx>
> Sent: Monday, 9 November, 2015 21:04:12
> Subject: [refeds] Input for InCommon's Steward Program

> In order to address the scaling of effort required for onboarding and
> metadata vetting for K-12 schools and community colleges, InCommon is
> partnering with US regional R&E network providers to pilot a Steward
> Program in which Stewards, InCommon Participants that meet certain
> criteria and sign specific agreements, are authorized to do two things:
> 
> 
> 1.
> 
>    Register IdPs and SPs that use domain names belonging to other
>    organizations for scopes and end-points.  Those other organizations
>    are called Represented Constituents.
> 
>      *
> 
>        In order to do this, we require that the Steward be authorized
>        to use its Represented Constituents' domain names as well as to
>        verify that the Represented Constituents own those domain names
>        in the same manner that InCommon verifies its full-fledged
>        Participants' domain names.
> 
> 2.
> 
>    Perform vetting of metadata submissions on behalf of InCommon.
> 
>      *
> 
>        Stewards will do this under contract to InCommon and will follow
>        the same procedures for metadata vetting as InCommon itself does.
> 
>      *
> 
>        Note that the primary use of this capability will be to vet its
>        own submissions for its Represented Constituents (as InCommon is
>        allowed to vet its own metadata submissions).  We will require
>        that the same person cannot both submit and vet metadata.
> 
>      *
> 
>        Do you have any concerns with InCommon contracting with other
>        organizations to perform metadata verification?
> 
>      *
> 
>        Would you be willing to interact with Steward-registered
>        entities the same as other InCommon-registered entities?
> 
> 
> Initially, only US regional R&E network providers may become Stewards,
> and only K-12 and community college institutions may become Represented
> Constituents.
> 
> 
> InCommon would like to ask the larger community for its guidance related
> to this change.  It's unlikely that entities registered via this model
> will be exported to eduGAIN in the near future, but it is likely that
> some will be exported or play a role in the larger R&E federation space
> in the longer term.
> 
> 
> David Walker