Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Internet2 fall12


Published on

  • Be the first to comment

  • Be the first to like this

Internet2 fall12

  1. 1. The Future of Federation Policy?Nicole HarrisInternet2 Fall Member Meeting, 02 October 2012 1
  2. 2. 2
  3. 3. 3
  4. 4. What are the problems?• We don‟t know what to call them;• We don‟t know what they are;• We don‟t agree on how to structure them;• We don‟t agree on the content;• We all start from scratch when writing them;• We ask the wrong questions to the wrong people.Apart from that it is ALLLL fine. 4
  5. 5. 5
  6. 6. Proposal? Federation Policy Best Practise Approach • Analysis of 15 federation policies; • Content „blocks‟ for policy areas defined; • Preferred structure / ORDER proposed; • Example wording given; • Chose your areas, leave out others. 6
  7. 7. SECTION A: StructureA: STUCTURE.GENERAL INFORMATION ABOUT HOW YOUR FEDERATION WORKS• RFC2119.• Definitions.• Background and Purpose.• Governance.• Eligibility.• How to Join.• How to Withdraw.STATUS: COMPLETE 7
  8. 8. SECTION B: Terms of UseB: TERMS OF USE.WHAT EVERYONE IS ALLOWED AND NOT ALLOWED TO DO• Terms of Use (IdP).• Terms of Use (SP).• Termination / Dispute Resolution.• Logging.• Data Protection.• Audit.• Use of Attributes.• Operator Rights / Role.• Interfederation / Publish rights.STATUS: IN PROGRESS 8
  9. 9. SECTION C: LegalC: LEGAL.ALL THE LEGAL STUFF• Liability.• Jurisdiction and Legal.• Fee schedule.• Copyright.STATUS: IN PROGRESS 9
  10. 10. Common Mistakes• What am I signing?• Eligibility mistakes;• Publication (interfederation);• Enabling exchange or protection your XXXX?• Writing policy without all the information;• Ignoring interoperability issues. 10
  11. 11. Learning from Your Mistakes – eduGAIN (1) Getting your metadata in a tangle“Any metadata file which makes use of parts of metadata published by eduGAIN MUST include either a reference with a URL to the eduGAIN Metadata Terms of Use [ToU] or the entire ToU text. ItMUST be placed at the top of the metadata file formatted as an XML comment.”• Over-specification of downstream metadata.• eduGain metadata must be managed separately.•Cannot be managed as part of a hierarchical aggregate. 11
  12. 12. Learning from Your Mistakes – eduGAIN (2) Backing yourself in to a corner "Publications under clause 1 above will be at the request of the Member who controls each Entity."• Over constrained management of metadata inclusion.• Requires members to understand they are using eduGain.• Requires a specific aggregate for eduGain.• LET THE METADATA FLOW. 12
  13. 13. Learning from Your Mistakes – eduGAIN (3) Not realising the implications• eduGain requires you to apply their terms of use to any metadata you republish.• Fundamental misunderstanding of how metadata is managed and signed.• Should only apply to the public metadata file.• Don‟t tell federations it is mandatory to protect themselves in a certain way. 13
  14. 14. Next Steps?• Surfacing issues  Making changes.• Will any EXISTING federations adopt?• Working with the new technical models (eduGAIN, PEER etc.)• More support for SPs, making sense of federations. 14