The standards developed by this team will integrate campus-wide architecture interests and perspectives. Agenda review Keith Hazelton reviewed the agenda, noting that the primary objectives were to continue reviewing the team charter and to begin indentifying key stakeholders for directory services. Groups in the directory Keith recounted the uncertainty from the first meeting about whether to include groups as well as individuals in the directory. He briefly described the work of the Network Security Team on authentication and authorization and that the Directory Services team could assume that this aspect of directory services would be considered there. This is the key scope question for the team.
People identify with groups, because they remain as individuals come and go.
In telephone directory language, the issue is whether to include yellow pages as well as white pages. There was a team consensus to defer the question of whether and how to include groups, and a feeling that we would probably want to include them and that this would significantly increase the scope of the team's work. An example is the need to identify and protect private information. Another is the need to associate an absolutely unique identifier with each individual. Another is the issue of central vs. decentralized directory services.