Subgroup Suggestion Box

Please identify components of our IT infrastructure that you feel should be addressed by the Infrastructure Futures group. Include the specific reasons why you believe this component should be addressed. Also, please indicate which of these components' assessments you would like to participate in.

At its first meeting, the entire Infrastructure Futures group will select which of the suggested components will be addressed and designate the subgroup members who will analyze alternative approaches to address the issues raised.

Infrastructure Component	Reasons for Assessing Now	People Who are Interested
DNS	The ucdavis.edu namespace is a critical component of a fully developed MS-AD environment	Chip, Hemang,Pam, Adam
Certificate Service	Need to ensure the public key infrastructure supports athoritative control for all security components desired within the Campus AD	Chip,Pam, Adam
Identity Management / Role Database	Our campus really need a reliable role database/managment system so that we don't have to reivent the wheel for each project.	Minh, Pam, Adam
Data Warehouse	One of the largest challenges may department have is in trying to access data	Minh, Pam, Adam
Virtualization	Central virtualization solution that costs less than putting it in my own server room.	Anthony, Jeremy, Pam
Collaboration tools	email,chat, calendar,file storage and sharing	Pam, Adam
Security tools	I realize that we are already utilizing security tools, but we need to continue to address this as infrastructure	Pam, Adam
Private Cloud file storage	We waste a lot of time passing documents back and forth via email. Additionally, many of these files aren't available on mobile devices such as tablets. Some of this may be addressed in collaboration tools or workflow, but this may be larger/more specialized. In particular, we need to look at setting up something that is 1) a secure repository for university documents 2) accessible to non-PC devices such as tablets.	Adam
LDAP	A sub-group of IDM. We want a standards-based LDAP infrastructure that 1) feeds a potential IDM 2) stores password-equivalent hashes for wireless auth 3) stores public keys for password-less SSH logins 4) does so in a secure manner which integrates with other developed infrastructure in Active Directory.	Adam