You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

V/C info

Topic: REFEDS R&S 2.0
Time: Mar 2, 2021 08:00 AM Pacific Time (US and Canada)

Join Zoom Meeting
https://us02web.zoom.us/j/83742805453?pwd=NUZ2SkNzS3V1RG9kbHlMMTJJZUxUdz09

Meeting ID: 837 4280 5453
Passcode: 256764
One tap mobile
+12532158782,,83742805453#,,,,*256764# US (Tacoma)
+16699006833,,83742805453#,,,,*256764# US (San Jose)

Dial by your location
+1 253 215 8782 US (Tacoma)
+1 669 900 6833 US (San Jose)
+1 346 248 7799 US (Houston)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
Meeting ID: 837 4280 5453
Passcode: 256764
Find your local number: https://us02web.zoom.us/u/kxuVBq6G4

Join by Skype for Business
https://us02web.zoom.us/skype/83742805453

Calendar link HERE

Pre-reading

Specifies a person ́s home organization using the domain name of the organization.Issuers of schacHomeOrganization attribute values via SAML are strongly encouraged to publish matching shibmd:Scope elements as part of their IDP's SAML metadata.Relaying Parties recieving schacHomeOrganization values via SAML are stronglyencouraged to check attribute values against the Issuer's published shibmd:Scope elements in SAML metadata, and may discard any non-matching values.

Draft Agenda

  1. Recap of consensus so far

    1. The FAQ will be revised to offer clarity on the term "affiliation" (see Research and Scholarship FAQ) and editorial changes made to the spec to make it more clear (see https://docs.google.com/document/d/1xXMvMV2_tYZBcejfVrItLlABprC7TkkTu9sRcpY22jg/edit)

    2. eduPersonScopedAffiliation will become a required value

    3. R&S will require privacy statements

    4. Encouraging the use of eduPersonAssurance requires further discussion with the Assurance Working group

    5. subject-id should be listed as the new identifier, but the spec would include migration requirement where ePPN would be passed, regardless of reassignment status

    6. R&S 1.3 and R&S 2.0 can co-exist; no migration detail will be included in the spec itself.
    7. ePPN and targeted ID to both be removed from R&S 2.0

  2. Focus on the OIDC section

  3. Come back to the need for organization info (scope? schacHomeOrganization?) if not resolve on the list

  4. Proposal to require DisplayName
  • No labels