Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Open Actions
    1. Miro will send a reminder to the IETF AD's about rfc6338-bis; Heather will follow up with the ADs as necessary
    2. Benn has sent the query to the schema discuss list about the ssh ldap public key schema; there has been discussion on the list but there seems to be a misunderstanding about what is intended and note that we will go ahead with this (given there is no arguments opposed).
      1. Subject to lack of objection from the community, Benn will reach out to the current OID space owner and work on getting this transitioned to Schema Board management.
        •   Benjamin Oshrin will reach out to the owner of the current OID space for the ssh ldap public key schema and work on getting this transitioned to Schema Board management.
  2. Administrivia
    1. (SCHAC URN Registry) Delegation of urn:schac:homeOrganizationType:nz to Tuakiri
      1. Effectively, federation operators are automatically delegated their national extensions in the SCHAC registry. Any other delegation requests will be considered on a case-by-case basis by the Schema Board.
      2. The board should consider the guidance provided in RFC 3613 regarding identifier assignments when considering those additional requests.
  3. Subcommittee status
    1. eduPersonAffiliation - proposal to close
      1. Board approves closure
    2. eduPersonReportingCode
      1. The subcommittee has a rough draft proposal with final text to be added based on some input from David Bantz. When that is done, Heather will post it to the subcommittee and the Schema board for consideration and to determine if it is ready for public consultation.
    3. voPerson
      1. Still a (slow) work in progress. The 2.0 version is usable in the OID space, but the final spec is not complete.
  4. splitting the eduPerson spec into core and supplemental
    1. see: Splitting Protocols From Schema Documents
      1. "core schema" and "attribute dictionaries" are being used as interchangable terms
      2. the only thing that is implementable is the protocol specification
      3. the term "profile" may be too vague.
    2. Will this proposal of a logical taxonomy work for eduPerson? As a reminder, the reason to consider this is because we are dealing with more and more protocols, so we want to make the information natively available to those protocols rather than forcing them through LDAP.
      •  Benjamin Oshrin and Keith Hazelton to update the Splitting Protocols document to describe the proposal in more detail, explaining the ramifications of the potential changes in more detail, and then sharing that with the community before we start work on eduPerson itself
  5. AOB