Page History

...

Decision Point for TAC

A dichotomy has been created for convenience but of course a range of options are possible.

Option #1

• Existing R&S IdPs have two choices:
  1. Modify their configs Recognize the REFEDS R&S entity attribute value (as described in the previous section)
  2. Do nothing
• New R&S IdPs have two choices:
  1. Release attributes to all R&S SPs, including R&S SPs from other federations
  2. Release attributes to R&S SPs registered by InCommon
  3. Release attributes to all R&S SPs, including R&S SPs from other federations
• Messaging:
  • R&S IdPs that migrate to REFEDS R&S will be among the first IdPs exported to eduGAIN.
  • Only the REFEDS R&S entity attribute value will be exported to eduGAIN; in particular, the legacy InCommon R&S entity attribute value will not be exported to eduGAIN.
  • The legacy
  The
  • InCommon R&S entity attribute value
  remains
  • will remain in InCommon metadata indefinitely.

Option #2

• Existing R&S IdPs have two choices:
  1. Modify their configs Recognize the REFEDS R&S entity attribute value (as described in the previous section)
  2. Do nothing
• New R&S IdPs have one choice: 
  1. Release attributes to all R&S SPs, including R&S SPs from other federations
• Messaging:
  • R&S IdPs that migrate to REFEDS R&S will be among the first IdPs exported to eduGAIN.
  • Only the REFEDS R&S entity attribute value will be exported to eduGAIN; in particular, the legacy InCommon R&S entity attribute value will not be exported to eduGAIN.
  • The legacy InCommon R&S entity attribute value will be completely removed from metadata at the end of June 2016.