Page History

The constitution is heavily based on the assumption of use of SAML and use of the MDS as the trust broker.  Two options exist here: have a constitution per technology / operational model OR update the constitution to reflect a more agnostic approach.  If the constitution is to be updated, the following issues would need to be address:

• Terminology / glossary review.  Particularly around the use of the term "federation" and proposed new use cases. 
• Use of SAML terminology in the document - this should be changed to refer to the relevant technology profile.  May want to consider reducing existing profiles in to one technology profile and moving CoCo profile to a best practice document status. 
• Role of operational team.  Current constitution envisages one operational team with responsibility for "eduGAIN" - how does this fit with the proposed model?
• Include references to trust broker.  The MDS as a trust broker is not mentioned at all in the current documentation - it is implicit that this forms the core of operation. If multiple approaches are to be used it is essential that this element is called out in appropriate document.  The eduGAIN "practice statement" is mentioned in several documents but has not been written, this will be essential if different approaches are to be introduced. 
• Appropriateness of current SG model.  SG representatives tend to currently be from SAML federations - will this allow the right representation for multiple technology approach?

CHANGES TO SG: Federations should ensure that representatives can represent all technology profiles.  Federations may vote on all constitutional changes and new profiles but my only vote on changes to technical profiles they use.  Delete bullet 7.

CHANGES TO EXEC: The edugain executive comprises representatives from organisations that fund edugain operations.  The current exective is documented (on the edugain website).   Change bullet 2 to changes to service scope and cost of service changes.   Add designate an edugain operator as a bullet.

Add Federation Operator definition.

A document highlighting areas where the constitution would need to change is available: https://docs.google.com/document/d/1zqq1BRloo0gwxnNtX0X189sMXbODTflLKJzzOxYui34/edit.  This is not intended to be a proposed amended document for ratification, but simply highlights the problem areas.

The CoCo is for SAML implementations only and its current status is a bit unclear and causes some confusion, particularly as it is broadly about entity implementation and blurs the lines between instructions to federations / instructions to entities. 

May be better to pull this out into a section of "best practice endorsed by eduGAIN SG" OR point specifically to documentation for how federations should implement CoCo.