Release Notes

Note: these are abbreviated release notes. For more information, see the full changelog.

New Features

Added support for Let's Encrypt
Support for ATS Slice plugin in Traffic Ops, including new Delivery Service Raw Remap __RANGE_DIRECTIVE__ directive
Ability to enable EDNS0 client subnet at the delivery service level
New IPv6 changes:
- Traffic Portal and Traffic Ops now accept IPv6-only servers
- Traffic Monitor now polls caches over IPv6 in addition to IPv4, separating the availability status of each (make sure to update the allow_ip6 profile parameter to include the IPv6 addresses of your Traffic Monitors, otherwise they will fail to poll over IPv6 and consider those caches to be unavailable over IPv6)
- Traffic Router will route IPv4 clients to caches with IPv4 availability and route IPv6 clients to caches with IPv6 availability
Traffic Router DNSSEC zone diffing performance enhancement
Traffic Monitor optimistic quorum
Traffic Ops API 2.0. This new major API version contains several new routes but does not contain many deprecated routes from API 1.x (which will be available until the ATC 5.0 release). API clients should begin migrating to API 2.0 as soon as possible. For the full lists of new or deprecated routes, please see the changelog.
Ability to choose the TLS version used for Traffic Ops to make requests to Traffic Vault. Note: the default is now TLSv1.1, which may require configuration changes to Riak. See Enabling TLS 1.1

This release contains many new bug fixes. For the full list, please see the changelog.

The Traffic Ops db/admin.pl script has now been removed. Please use the db/admin binary instead.
Removed from Traffic Portal the ability to view cache server config files as the contents are no longer reliable through the TO API due to the introduction of atstccfg.
Traffic Ops Python client no longer supports Python 2.