April 11, 2006
Present: Renetta Johnson, Tony Houdek, Kevin Danielson, Jeff Cox, Doug Osowski, Michelle Rakoczy,
Jay Smith, Brandon Thorvilson, Carl Warrene, Daniel Eaton, John Wold, Roy Beard, Bryan Ford, Derek
Stinchfield, and Bonnie Jundt
Absent: Larry Fisk, Brad Miller, Dale Ricke, Josh Jones, Corey Quirk, Don Larson, Chad Gratton, David
Belgarde, Barry Pederson, Harold Bruce, Corey Shock, and Jing Wang
John brought Derek Stinchfield to our meeting. Derek recently began working as a network analyst at
Aerospace. He was a student employee in ITSS Network Services for more than 5 years prior to accepting his position at Aerospace.
Carl introduced his assistant systems administrator, Daniel Eaton. Daniel may attend some of our meetings when Carl is unavailable. There is some planned turnover of positions at the Law School which is likely to keep Carl occupied.
Nathan Hageman has been hired at The Ralph to replace Brent Logan. We will invite him to join our subcouncil when we begin meeting again in September. I’ll send him a link to our posted minutes.
Marach 14 th minutes – approved and posted
Follow-up from March meeting minutes:
Kevin Danielson is leading the discussion within ITSS on UND DNS policy. Craig Cerkowniak will be taking the DRAFT policy to the IT Manager Sub-council for review and feedback.
Bonnie asked if anyone has still been experiencing voice mail problems. No one was aware of continuing problems.
UND DRAFT DNS policy – Kevin
UND DNS servers, named DNSone, were implemented on campus. We are now working on policies that add to the North Dakota University System policies. The solution at UND supports user accounts enabling different areas of campus to manage their own sub-domains. Kevin created a rough draft of DNS policy considerations and it was reviewed and revised per suggestions from staff within ITSS. Kevin distributed a copy of the revised draft, provided an overview and answered questions. It will be added as an attachment to these minutes.
Aerospace is currently responsible for managing the address space of their sub-domains on DNSone. ITSS
Network Services is working with Harold and Jeff at the School of Business to delegate authority to them for their IP address ranges. Along with DNS policy, a document will be created to provide guidelines to assist the different areas of campus with using consistent DNS practices across campus with the Infoblox appliance.
Kevin asked attendees if anyone is aware of a need to run their own departmental DNS services. No one knew of a need, however Aerospace runs caching DNS servers, and other areas may choose to run one in the future to keep that traffic local to their subnet.
There was a question regarding the possibility of a future requirement for all departments to manage DNS for their local address space. At this time, it does not appear to be a direction. It is the responsibility of
ITSS, however where it is more efficient and beneficial for departments to have local control it is an overall advantage.
Kevin asked for volunteers to assist in developing procedures. Jeff and Doug responded with their willingness. Anyone else interested may contact Kevin.

Voice over IP (VoIP) and IP Telephony (IPT) – Larry (Bonnie reported for Larry)
A workshop was held on March 23 rd for the North Dakota University System with a focus on pre-planning for VoIP with campus administrators. There was attendance from most, if not all, campuses in the NDUS.
There appeared to be an interest, and also concern about the needs and how to prepare. The main speakers included:

A consultant with experience with VoIP and with the Avaya phone switches currently used in the
NDUS

The director of Telecommunications at Information Technology Department with State
Government and responsible for STAGENet

A network administrator from University of Oklahoma with VoIP experience on their campus
There isn’t an immediate need to do more with VoIP at UND. UND and NDSU have done VoIP trunking between their telephone switches for a couple of years. There is an industry-wide move with all main telephone vendors to move away from traditional TDM toward VoIP. The UND switch was upgraded to meet requirements for vendor support. These upgrades included support for VoIP services. The cabling infrastructure at UND will continue to support traditional phone services in existing buildings, however when major renovation is done or new buildings are planned we need to begin making decisions based on current and future needs for communications. Some of the considerations for support of VoIP and IPT include:

Organizing IT departments to support the needs of VoIP and IPT, including application, server, network, helpdesk and customer support.

Sufficient and well-trained staff (need to gain experience from pilots)

Power – UPS needs and maintaining batteries, generator backups, POE

Network - Redundancy and reliability, adequate and protected (QoS) bandwidth

E911 – there are solutions, but it’s still early and it’s not widely supported or understood

Challenges of wireless
When, where and why might UND look at doing IPT?

Opportunities in new construction

Customer expectations

Flexibility for telephone moves, adds, changes

Image

Gain experience through pilot projects
With better awareness, when new construction is planned it will be more likely that discussions will take place to help make decisions based on different options for communications services. Roy indicated his willingness to have this discussion for the new EERC buildings.
Wireless and open port authentication – Kevin
The wireless access point at Wilkerson now requires authentication with Cisco Clean Access.
We’ve had a request for statistics on the number of wireless users in the Chester Fritz Library. The way
Clean Access is set up today, if users don’t logout prior to powering off their laptop it appears that their connection is still active until they hit the 12 hour timeout. Wireless network management, such as WLSE currently used at Aerospace, would provide that information along with number of users on each access point or total numbers of users on access points in a VLAN.
Renetta stated that Nursing didn’t receive approval for the wireless project they were planning and requested that the School of Nursing be considered as a potential location for wireless networking if STF funding is approved for extending current wireless at some locations on campus.
Michelle said Housing is ready to move ahead with access points in some of the residence halls and in the basement of Swanson. They will work with ITSS to determine final configuration and details.

The Law School has wireless throughout their building and Kevin asked Carl about their willingness to authenticate with Clean Access. Clean Access provides authentication for MACs but it doesn’t support the process that checks the system for current updates, viruses, worms, etc. Apparently there is a plug-in with
Firefox which allows a system to skip the Clean Access checks; Kevin will visit further with staff at the
Law School to learn more about it. Carl and Daniel are supportive of implementing Clean Access to be consistent with the Memorial Union, Library and other places on campus.
STAGENet 2006 – Bonnie
The March 22 nd STAGEnet 2006 update from ITD reported that they are still in the planning and design stage. Preparation and testing will follow. The goal is to have the new network in place prior to the start of fall semester.
Networking updates from around campus – Attendees
Renetta
Nursing has been working on portal. They are still hopeful that wireless access can be added in their building. Construction of the new Nursing Research building is scheduled to begin in the fall.
Michelle
Michelle questioned the on-call procedures for 24X7 network operations. When she got a call at 1:30 in the morning reporting that DHCP services were unavailable in some buildings she didn’t know the preferred procedure. ITSS staff suggested that good judgment be used with making calls during the non-
Helpdesk hours of 1:00 to 5:00 A.M. If the impact is judged to be severe, then the call should be made.
Bonnie is willing to take calls to help with determining the criticality and next step, but past experience indicates that all Network Services staff will take calls and respond as needed. As critical services are put on the campus network, procedures may need to be reviewed.
The new residence hall is scheduled to be opened fall of 2007. At that time Dakota Hall may no longer be needed as a residence hall.
Installation of a 3 rd DSLAM to increase the number of potential DSL connections in campus apartments is in progress. Housing is looking at providing DSL to all apartments as a service which is included in their rent. That would require providing a different type of network service for buildings, such as Virginia Rose and the 6plexes which are wired for network access. Changing this service will require additional discussion and planning.
Doug
Two new servers are planned at Facilities. One will be for building automation equipment. The other is for all utility meters on campus. They will have Ethernet connections.
Jay
Larry provided an estimate from ITSS for upgrading the wireless access at the Union.
John
John shared information about WLSE and how it helps them with planning for additional access points. It recently helped him find a non-functioning access point due to a bug in the hardware which prevented it from accepting connections. The usage graphs from WLSE continually showed no connections so they became aware of the problem and worked with Cisco TAC to resolve. Displays from the access point itself indicated that everything was normal.
Roy
Ground breaking for the new EERC building is scheduled for Monday. Depending on the decision about the old Engelstad Arena, there may be three more buildings added within the next two years.
Next meeting – May 9 th – We are anticipating a presentation from Infoblox.

Domain Name System (DNS) policy DRAFT
Apri1 11
KAD
The Domain Name System (DNS) maps Internet Protocol (IP) numeric addressing schemes to descriptive names, so that individuals browsing the Internet do not have to remember numeric addresses.
Information Technology Systems and Services (ITSS) has responsibility for administering both public and private IP addresses used at UND, and the und.edu and und.nodak.edu domains. In this capacity ITSS allocates, registers, arbitrates, delegates and maintains the “name space” providing best performance, fair use and compliance with NDUS DNS policy and the University of North Dakota policies. (Link to ITSS policies)
All DNS domains using the University networking resources must reside in the ITSS domain name servers as either a primary or secondary domain. ITSS is responsible for the security, operation and maintenance of the University of North Dakota name servers.
ITSS retains all primary management and oversight responsibility for IP address ranges and DNS domains using campus IP addresses. ITSS may delegate primary operational responsibility for IP address ranges and DNS domains to department or college IT staff.
Upon delegation of responsibility to department or college IT staff they would be responsible for the following:
1.
Define new or change current DNS records to meet department or college needs.
2.
Maintain compliance with UND and NDUS policies.
3.
Manage only records within their assigned/delegated sub-domain.
4.
Follow the guidelines set forth in the DNS guidelines document.
Support for non und.edu domains will be limited to entities directly affiliated with the
University. Entities will be responsible for registering their own non und.edu domain name but must list the University of North Dakota as the technical contact ( und-dnstech@mail.und.edu
). Records within these domains must be CNAME records pointing at a valid address record within the und.edu domain.