#Use this template to capture proposal for a new Incubator Activity - delete this line after using the template#
Participants
Panel |
---|
|
#Enter the persons who are submitter of the Activity - delete this line after using the template#Name | Organisation |
---|
Mihály Héder | SZTAKI/KIFÜ | Niels van Dijk | SURF |
|
Panel |
---|
| #Enter the persons who are participating in the team that works on this Activity - delete this line after using the template# |
Name | Organisation | Role |
---|
Martin | SURF | Team member | Mihály | SZTAKI/KIFÜ | Team member | Halil | GRNET | Team member | Andrej |
| Team member |
|
Panel |
---|
|
#Enter the persons who are internal projects or external stakeholders of this Activity - delete this line after using the template# Name | Organisation | Role |
---|
Davide Vaghetti | GARR | Task lead of eduGAIN service team | Leif Johansson | SUNET | HSM operator | Halil Adem | GRNET | federation operator |
|
Activity overview
Panel |
---|
|
#Please describe the high-level goal of the incubator Activity, provide an overview of the anticipated work and needed resources and skills. Please also describe how commitment from various partners is warranted. - delete this line after using the template# <Enter here> With the growth of the metadata feeds all over the world, together with the increased need for catering for multiple federations at once, Service Providers are increasingly reliant on the MetaData Query (MDQ) protocol, for Relying Party metadata lookup. (MDQ is also commonly referred to as MDX (MetaData eXchange) for historical reasons: the name of a mailing list where the spec was discussed.) For MDQ there is only one implementation in common use: pyFF. The MDQ protocol is quite simple however, |
Panel |
---|
|
The aim is to deliver EntityDescriptors as flat files in such a way this mimics MDQ protocol and combine that with Global DNS to create a super fast and highly redundant distribution mechanism for MDQ. |
Panel |
---|
|
#Please describe the goals of Activity, including what needs to be delivered, participants, the community(ies) that require a solution. Describe when the Activity is done and how to measure the success of it, in a SMART way. - delete this line after using the template# <Enter here> |
Activity Details
Panel |
---|
|
#Please describe the technical details for the Activity. - delete this line after using the template#<Enter here> Potential features of such an alternative MDX solution are: - Federations must remain in control of metadata signing
- Solution must not depend on how federations sign metadata
- Solution must respect SAML metadata ‘business rules’ with regard to TTL
- Effort for participation in distribution network should be minimal
- Solution should be highly available
- Solution should support almost real-time updates
|
Panel |
---|
|
#What is the business case for the Activity? Who would be beneficiaries of the results of the Activity and what would potential business case look like if applicable? - delete this line after using the template#
<Enter here> |
...
Panel |
---|
title | Definition of Done (DoD) |
---|
|
- An alternative MDX solution is designed and a PoC is implemented
- Architecture overview with MVP
- Geographically distributed MDQ (geoDNS)
- A test suite and trial site is created/deployed
- An infrastructure deployment is tested with some federation operators
- A documentation for installation and configuration is provided
#Please describe here the set of criteria that the product must meet in order to be considered finished. - delete this line after using the template# <Enter here> |
Panel |
---|
|
- The design, source code and documentation will be made available to the community
- A hosted, distributed MDX solution could be provided to support federations that do not run an MDQ
#How are the results of the Activity intended to be used? If this requires further engagement, can you describe how you intent to sustain it? - delete this line after using the template# <Enter here> |
Activity Results
Panel |
---|
|
This activity is still ongoing#Please provide pointers to completed and intermediary results of this activity - delete this line after using the template#
|
Meetings
Date | Activity | Owner | Minutes |
---|
January 1, 2017 | Kickoff meeting |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...