Make it harder to identify STREAM packets on the wire

[emschwartz]

Ideas for obscuring which transport protocol is being used:

• Pad packets to the maximum data size by default
• Randomize the expiry time
• Use a different connection tag for every packet
• Use amount tranches (send only increments of 1, 10, 100, etc instead of whatever the connector says the maximum packet amount is)

It's an interesting question whether any of this is worth doing, because connectors can probably figure out which transport protocols (or even which implementations of transport protocols) are being used just by looking at the timing of packets and behavior in response to certain kinds of errors.

[emschwartz]

More things to consider:

• How STREAM implementations respond to connector congestion errors
• Error messages servers return (see https://github.com/interledgerjs/ilp-protocol-stream/commit/75b9dcd544cec1aa4d1cc357f300429af86736e4)
• How implementations ramp up / down packet sizes and number of packets

[emschwartz]

This paper might have some useful ideas: Reducing Metadata Leakage from Encrypted Files and Communication with PURBs