This repository was archived by the owner on Nov 13, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 77
Traffic Router 3
Jan van Doorn edited this page Sep 11, 2016
·
4 revisions
(From Jeff's 2.0 page)
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?
[Traffic Control 3](Traffic Control 3)
[Traffic Control 2.0](Traffic Control 2.0)
[Notes and Processes](Notes and Processes)