Page History

FY09Q1

IPv6

11/19/2008

Data Network Engineering reports that they will begin investing in IPv6 effective FY11Q1.  It is not clear what modification(s) to our architecture and applications will need to happen to take advantage of this.

Resolution:
In speaking with Eric Cronise (NCS CCDAT representative) we believe that deploying the IPv6 protocol on the campus backbone network will not have a negative impact on our current applications and infrastructure.

Customers that want to use IPv6 in their local area networks will need to first arrange connectivity to the IPv6-enabled campus backbone.  There are a variety of connection options and choosing the appropriate option will depend on the customers requirements. Additional services that may be required are DHCPv6, DNSv6, and 6to4 gateways.  CIT needs to decide if and how they will support these IPv6 services.  Plans to make IPv6 available to customer networks as a service would need to address these issues.  Since the full capability to support IPv6 isn't planned until FY11Q1 we believe there is ample time to work these issues out.

FY09Q1

CUSSP

11/24/2008

Identity Management lists CUSSP (the libraries and/or protocol) as moving to an unsupported state as of FY11Q1.   CUSSP has a dependency on Kerberos 4 (though it also supports Kerberos 5 in certain implementations) which they have listed as being unsupported effective FY09Q3.

Resolution:
Steve Edgar has informed me that the CUSSP libraries will live on utilizing K5 capabilities previously built in to the libraries.   Thus, it is possible to continue supporting CUSSP even after K4 is turned off.

FY09Q1

cusspclient

11/24/2008

ATSUS Customer Service lists that they will be moving to "unsupported" status with respect to their use of cusspclient effective FY11Q3.    This product depends on Kerberos 4 which Identity Management has being unsupported effective FY09Q3.

Resolution:
Steve Edgar has informed me that JP Brannan will be supplied with a K5 version of cusspclient that will allow JP's applications to continue working even after K4 has been turned off.

FY09Q1

ColdFusion 7

11/24/2008

IS Infrastructure reports that ColdFusion 7 will be unsupported effective FY11Q1.   The Cold Fusion applications group reports that they will be "maintaining" ColdFusion 7 based applications for all three fiscal years.

Resolution:
Further discussion with Steve Lutter reveals that he is prepared to move away from ColdFusion 7 whenever the hosting group needs to turn off support for it.  Steve will modify his inventory report next quarter to accurately reflect this.

FY09Q1

CUPeople

12/15/2008

IS Infrastructure reports that CUPeople is being "Maintained" all three fiscal years.   There are known security issues with the current product and it is CCDAT's understanding that the current product is being phased out.

Resolution:
Kevin Leonard informed me that the CUPeople service will be updated to a K5 solution before Identity Management will turn off support for K4.   The new service will likely utilize either DAVPortal or KProxy technology.

FY09Q1

KFront/MVS Dispatchers

12/15/2008

IS Infrastructure lists KFront and MVS Dispatchers as "Disinvest" for all three fiscal  years.   CCDAT believes that Identify Management is looking to "turn off" Kerberos 4 sometime during FY09Q3, and both KFront and the MVS Dispatchers depend on K4.

Resolution:
Kevin Leonard informed me that this issue falls under the K5 Migration project in IS which is being led by Benoit McNicoll (project manager).  The dispatchers (through KFront) are still seeing a fair amount of traffic all authenticated with Kerberos 4.    A team from IS and Identity Management are meeting weekly to identify the source of the remaining traffic.   A decision will be made as to whether or not the KFront service should be upgraded to K5 OR if the remaining consumers can be served in an alternate manner.