Sponsor J

Timeline

2012 June - 2013 June

Deliverables

1. shall provide and operate, either directly or by subcontracting, 125 Tor relay servers, using leased cloud virtual servers or dedicated hosting services, with a total aggregate bandwidth (burst capacity) of no less than 12.5 Gigabits-per-second (Gbps) and monthly data transfer capacity equal to or greater than 95th percentile traffic at 100 Megabits-per-second (Mbps). Tor shall ensure at least 30% of these Tor relays are operational within 60 days of award of this contract, at least 60% operational within 90 days of award, and the remainder operational within 120 days of award.
2. shall provide and operate, either directly or by subcontracting, 75 Tor bridge servers, using leased cloud virtual servers or dedicated hosting services, with a total aggregate bandwidth (burst capacity) of no less than 7.5 Gigabits-per-second (Gbps) and monthly data transfer capacity equal to or greater than 95th percentile traffic at 100 Megabits-per-second (Mbps). Tor shall ensure at least 30% of these Tor bridges are operational within 60 days of award of this contract, at least 60% operational within 90 days of award, and the remainder operational within 120 days of award.
3. In order to provide additional capacity, improved performance, and enhanced security for users of the Tor software in countries with government-imposed Internet censorship, Tor shall ensure that all Tor relay servers and Tor bridge servers operated under the terms of this contract shall be located in geographically diverse locations with diverse Internet Protocol (IP) addresses which are not in contiguous ranges in order to not be easily blocked by foreign government censors. To ensure diversity of IP addresses, no more than 2 servers may reside in the same /24 IP subnet, and to ensure geographical diversity, no more than 25 Tor relay servers or 7 Tor bridge servers may reside in the same data center, and at a minimum Tor must host servers across at least 1 data center facility in North America, 1 data center facility in Europe, and 1 data center facility in Asia.
4. shall configure the Tor relays operated with an exit policy that at a minimum allows traffic destined for TCP ports 80, 443, 554, and 1755, and UDP ports 554 and 1755 to enable access to the world wide web and multimedia streaming.
5. shall provide up to 12 customized versions of the Tor Browser Bundle software, which allow, at a minimum, for the default start page of the bundled web browser to be set to a URL as designated by Sponsor J. (#7030 (moved))
6. shall track updates to the software components of the Tor Browser Bundle, and at no additional charge, produce and deliver updates to the customized versions. (#7031 (moved))
7. shall test the Tor Browser Bundle on multiple computer systems, including all supported operating systems, and analyze these systems afterwards for any changes to the system that may have been made by use of the Tor Browser Bundle. Tor shall document any such traces found and design and deliver a plan with suggestions to reduce the footprint of Tor Browser Bundle use, as well as warnings and suggestions for Tor Browser Bundle end users to properly set security and privacy expectations for users. (#6845 (closed), #6846 (closed))
8. shall produce, release, and make available regular Tor package builds which are preconfigured to be a bridge relay.
9. shall deliver a plan for additional Tor bridge deployment strategies, such as short-term browser-based bridges which allow volunteers to become Tor bridges without downloading any additional software.
10. Improvements to Tor Browser to improve security and media streaming. (#7006 (closed))
11. Improvements for safe use of Flash within Tor Browser. (#7680 (moved))
12. Improvements to HTTPS Everywhere Firefox/Chrome browser extension. (#7007 (moved))
13. shall evaluate the current Tor design and limitations on Tor relays which operate on dynamic IP addresses, and propose and implement technical improvements to reduce or eliminate these limitations. (#7009 (moved))

Project tickets

[[TicketQuery(keywords~=SponsorJ,format=table,col=id|summary|keywords|owner|component)]]