This consultation is now closed. It was open from June 22 to August 18, 2017. See http://doi.org/10.26869/TI.105.1
Document for review/consultation
NB: The draft document contains yellow-highlighted portions that identify specific time intervals or constants. Your feedback about how best to set each of these values is especially solicited.
- Baseline Expectations for Trust in Federation
- InCommon Community Assurance Webinar of June 7, 2017
Change Proposals and Feedback - We welcome your feedback/suggestions here
If you have comments that do not lend themselves well to the tabular format below, please create a new Google doc and link to it in the suggestion section below.
|Section, if applicable (overall comments also welcome)|
Current Text if applicable (overall comments also welcome)
Proposed Text / Query / Suggestion
|1||Under 'Baseline Expectations of Service Providers'||We've found (unfortunately) more SP setups are taking the ownership of handling provisioning and/or deprovisioning of access and attribute data themselves. And so, should we include an SP expectation around proper life cycle management of this access and data.||Technical and/or business processes are in place to ensure user access and data are properly retired and/or deprovisioned from the SP to ensure a consistent and secure user application lifecycle.||Garrett King / CMU||Great suggestion for the next revision of the Baseline Expectations. Once the process for Community Consensus is available, the AAC recommends seeding this question through that process.|