Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  • Nature of Declaration: Signing the declaration creates no new legal obligations or rights (section 9), nor is there any financial consideration (section 12). Each federation is signing a one-sided declaration, which is neither a contract nor an agreement.

Constitution

  • eduGAIN Governance: eduGAIN is governed by an Executive Committee, which today is the GÉANT Executive Committee and a "Steering Group" comprised of Participating Federations. Each Federation appoints a Delegate and a Deputy.
  • Operational Team: eduGAIN Operational Team handles most administrative tasks for eduGAIN.
  • Peering: eduGAIN has no direct peering relationships at present, but has contingencies in the constitution to allow them should they exist.
  • Approval of Changes: There are multiple levels of approval for important decisions to ensure that changes will not exclude participant federations, either directly or indirectly.
  • Entities Registration in eduGAIN: There is no direct registration of entities with eduGAIN and a Participant Federation is responsible for making sure non-eduGAIN entities are not presented to eduGAIN.
  • Metadata Registration Practice Statement: Each federation must publish a Metadata Registration Practice Statement prior to exchanging metadata.
  • Leaving eduGAIN: Federations must give one (1) month notice prior to leaving eduGAIN; however, there are no constraints on a federation for dropping any given IdP or SP metadata entity from its metadata export. Likewise, there are no constraints on a federation for dropping any given IdP or SP from its import pipeline prior to republishing for its own members.
  • eduGAIN Technical Overview: eduGAIN Technical Overview document mentioned in the constitution is currently not published.
  • Signing of Declaration: The eduGAIN Operational Team verifies that the signing party on the declaration for a participant federation is authorized to sign on behalf of the federation. For expediency, the Operational Team requests a scanned copy of the signed declaration followed eventually by a paper copy.
  • Pre-approval: Certain federations have been pre-approved by the eduGAIN Steering Committee for admittance. InCommon has been pre-approved.
  • Required vs Optional Profiles: The only required profile for participant federations at present is the SAML 2.0 Metadata Profile.

Metadata Profile

  • Required Elements: not all elements required by the eduGAIN Metadata Profile are currently implemented in InCommon metadata.
  • MDS Aggregation Practice Statement: the MDS Aggregation Practice Statement mentioned in this document does not exist yet.
  • Filtering metadata during aggregation: eduGAIN aggregation is supposed to be transparent and does not remove or validate metadata elements during aggregation—this is the responsibility of the participant federation that registers the entity into metadata.

...