Traffic Router 2.0

The below links may be stale. Use the [Traffic Control 3](Traffic Control 3) pages for new features and plans after the Postgres migration

Overview

Version 2.0 of Traffic Router will focus on improving scalability, localization, and security. Proposed enhancements/changes include but are not limited to:

• Enable localization for more DNS request types
  • Ensure resolvers to use the closest Traffic Router
  • Ensure requests for HTTP routing are localized to closest Traffic Router
  • Enable health protocol for Traffic Router such that requests are serviced by available instances
• Popularity based routing
  • An interface to allow external systems to influence routing of certain URLs based on popularity or other needs
• Steering delivery services
  • A special delivery service that administratively steers traffic to one delivery service or another
• SDN integration
  • The current "magnet" approach in use with the CZF/Geolocation providers does not always yield the shortest physical path
• Use client metrics to improve routing
  • Implementation should be secured such that no rogue clients could influence routing
• Add support for HTTPS
• Remove dependency on jdnssec library
• Generate and append query parameter for url signature when issuing the 302 for a signed delivery service?