Do we need tcsd?  Should we just move all ports to IANA dynamic ranges?  Changing these ports now requires involvement from labs, troopers, acq-netops, and secops.

According to https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt (please excuse the caps), specifically the last sentence:

************************************************************************
 * PLEASE NOTE THE FOLLOWING:                                           *
 *                                                                      *
 * ASSIGNMENT OF A PORT NUMBER DOES NOT IN ANY WAY IMPLY AN             *
 * ENDORSEMENT OF AN APPLICATION OR PRODUCT, AND THE FACT THAT NETWORK  *
 * TRAFFIC IS FLOWING TO OR FROM A REGISTERED PORT DOES NOT MEAN THAT   *
 * IT IS "GOOD" TRAFFIC, NOR THAT IT NECESSARILY CORRESPONDS TO THE     *
 * ASSIGNED SERVICE. FIREWALL AND SYSTEM ADMINISTRATORS SHOULD          *
 * CHOOSE HOW TO CONFIGURE THEIR SYSTEMS BASED ON THEIR KNOWLEDGE OF    *
 * THE TRAFFIC IN QUESTION, NOT WHETHER THERE IS A PORT NUMBER          *
 * REGISTERED OR NOT.                                                   *
 ************************************************************************

I have no idea if I need tscd, but it's running on my workstation and causing tests to fail.

it's not clear to me that tcsd is actually used on non-laptops, so I'd probably try to stop it and see what happens. But, it might be used to manage googletnetworkaccess et al.

Moving masters is kind of expensive as per comment #1, so I would be disinclined to do it as a task on its own. However, if we wanted to bundle this into converting the master to builders.pyl or (better) swarmbucket, that seems reasonable. I'll check to see if we think we'd be willing to move this master to swarmbucket.

It's not clear to me that this is a big problem, so I'm going to deprioritize this for now. If this does become a problem that is really annoying people, we should follow up on my comments in #3.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot