Subject: | Re: [TAC-InC] Trust and Identity document stewardship |
---|---|
Date: | Wed, 12 Oct 2016 12:42:25 -0600 |
From: | Steve Olshansky <olshansky@isoc.org> |
To: | tac@incommon.org |
CC: | Ann West <awest@internet2.edu>, Tom Barton <tbarton@uchicago.edu>, DWI2 <dwalker@internet2.edu>, Emily Eisbruch <emily@internet2.edu>, kjk@internet2.edu |
Further Comments
Subject: | Re: [TAC-InC] Trust and Identity document stewardship |
---|---|
Date: | Wed, 12 Oct 2016 13:16:53 -0700 |
From: | David Walker <dwalker@internet2.edu> |
Reply-To: | tac@incommon.org |
To: | Steve Olshansky <olshansky@isoc.org>, tac@incommon.org |
CC: | Ann West <awest@internet2.edu>, Tom Barton <tbarton@uchicago.edu>, Emily Eisbruch <emily@internet2.edu>, kjk@internet2.edu |
Thanks, Steve. This is, of course, a move toward more structured process, but I think the main issue here is potential standards' scope. While T&I would not establish SAML standards, it very well could establish standards for R&S certifications within the scope of InCommon (as it did originally), or propose an R&S standard to REFEDS with an international scope (which it did later). Either of the latter require knowing when something is officially Trust and Identity, as opposed to one or more people who have a relationship with Trust and Identity. That's what the process is about.
Subject: | Re: [TAC-InC] Trust and Identity document stewardship |
---|---|
Date: | Wed, 12 Oct 2016 15:26:34 -0500 |
From: | Tom Barton <tbarton@uchicago.edu> |
To: | Steve Olshansky <olshansky@isoc.org>, tac@incommon.org |
CC: | Ann West <awest@internet2.edu>, DWI2 <dwalker@internet2.edu>, Emily Eisbruch <emily@internet2.edu>, kjk@internet2.edu |
Hi Steve,
As the author of those words -- my bad! You're right of course, that use of the term was loose. Internet2 would not be the last stop for some things becoming standards in the sense you mean, though it is sometimes the first stop, eg, the SAML Interoperability Profile. And other things become "community standards", having similar effect but in a more constrained scope. Eg, eduperson, Bronze, MFA Profile, and Baseline Expectations, to sample a range.
In any case, your question helps to underscore the value of having something like the Document Stewardship stuff in place. We want items like those above to have maximum impact, so we should make it easier to for them to have a more uniformly good quality and be referenceable in a "standard" and persistent way. If someone has an idea about those docs or the approach they embody might help us all produce a better outcome, now's the time to post it on the community review page!
Thanks,
TomB
Subject: | Re: [TAC-InC] Trust and Identity document stewardship |
---|---|
Date: | Wed, 12 Oct 2016 15:57:02 -0600 |
From: | Steve Olshansky <olshansky@isoc.org> |
To: | David Walker <dwalker@internet2.edu> |
CC: | tac@incommon.org, Ann West <awest@internet2.edu>, Tom Barton <tbarton@uchicago.edu>, Emily Eisbruch <emily@internet2.edu>, kjk@internet2.edu |
Subject: | Re: [TAC-InC] Trust and Identity document stewardship |
---|---|
Date: | Wed, 12 Oct 2016 16:02:10 -0600 |
From: | Steve Olshansky <olshansky@isoc.org> |
To: | Tom Barton <tbarton@uchicago.edu> |
CC: | tac@incommon.org, Ann West <awest@internet2.edu>, DWI2 <dwalker@internet2.edu>, Emily Eisbruch <emily@internet2.edu>, kjk@internet2.edu |
Subject: | Re: [TAC-InC] Trust and Identity document stewardship |
---|---|
Date: | Wed, 12 Oct 2016 18:05:37 -0400 |
From: | Michael Gettes <mrg30@psu.edu> |
To: | tac@incommon.org |
CC: | Tom Barton <tbarton@uchicago.edu>, DWI2 <dwalker@internet2.edu>, Ann West <awest@internet2.edu>, Emily Eisbruch <emily@internet2.edu>, kjk@internet2.edu |
Getting this right from the outset is important. I fully support SteveO's concerns and Tom's clarification.
/mrg
Subject: | Re: [TAC-InC] Trust and Identity document stewardship |
---|---|
Date: | Wed, 12 Oct 2016 16:07:13 -0600 |
From: | Nick Roy <nroy@internet2.edu> |
Reply-To: | tac@incommon.org |
To: | tac@incommon.org |
From an InCommon perspective, 10 years has taught us that interoperability is an enormous problem, and requiring behavior is probably the last unused trick in the book. In order to require behavior, we need both standards and certification. Hopefully those requirements don't get us in hot water. I'm hoping they will get us out of the situation we are in, <hyperbole> which is that InCommon has become a change management mechanism for bilateral federation between campuses and their ERPs. </hyperbole>
Nick