Child pages
  • 2021-09-17 R&S 2.0 Notes
Skip to end of metadata
Go to start of metadata

Attendees

Pre-Reading

Working Draft

Agenda

  1. Recap of consensus for Personalized Authorization so far - note that all changes will need to be validated via the consultation process
    1. if schacHomeOrg is present, then it's the value to be used; if not present, eduPersonScopedAffiliation should be used. (See 2021-07-01 R&S 2.0 Notes)
      1. this is more appropriate for the other entity categories; for Personalized, we're requiring schacHomeOrg and so this statement does not apply
    2. We will adopt the following from R&S 1.3: "Service Providers SHOULD limit their data requirements to the bundle of attributes defined in Section 5, but MAY negotiate for additional data as required via mechanisms that are outside the scope of this specification." (See 2021-07-01 R&S 2.0 Notes)
    3. The entity categories (Anonymous Authorization, Pseudonymous, and Personalized) are mutually exclusive (See 2021-07-01 R&S 2.0 Notes)
    4. We will use subject-id for this specification. (See 2021-08-10 R&S 2.0 Notes)
  2. Reviewing the draft spec
    1. Assurance text
    2. Any other changes
    3. Consensus call

Notes

  1. Recap of consensus for Personalized Authorization so far - note that all changes will need to be validated via the consultation process
    1. if schacHomeOrg is present, then it's the value to be used; if not present, eduPersonScopedAffiliation should be used. (See 2021-07-01 R&S 2.0 Notes)
      1. this is more appropriate for the other entity categories; for Personalized, we're requiring schacHomeOrg and so this statement does not apply
    2. We will adopt the following from R&S 1.3: "Service Providers SHOULD limit their data requirements to the bundle of attributes defined in Section 5, but MAY negotiate for additional data as required via mechanisms that are outside the scope of this specification." (See 2021-07-01 R&S 2.0 Notes)
    3. The entity categories (Anonymous Authorization, Pseudonymous, and Personalized) are mutually exclusive (See 2021-07-01 R&S 2.0 Notes)
    4. We will use subject-id for this specification. (See 2021-08-10 R&S 2.0 Notes)
  2. Reviewing the draft spec
    1. Assurance text - unanimously approved
      1. Some discussion regarding requirements for non-reassignability and how that requirement in the RAF might impact implementing this entity category; no changes made to the spec as a result
    2. Any other changes - fix grammatical errors and indicate where work will be completed post-consultation
  3. Consensus: the spec is ready for community consultation. This will start on 20 September 2021.