Michiel de Jong

Note that, actually, [the newer packet types have no extensions, but rely on the envelope length indicator instead](https://github.com/interledger/rfcs/issues/352#issuecomment-361822876). So ilp-packet should accept something like a 'trailingBytes' field (defaulting to 0...

makes sense, though i would say it's more to sandbox your incoming users from each other when they compete for outgoing bandwidth, than to limit a risk you run yourself...

In cases where my outgoing peer is obviously late, as a service to my customers, I can eat the loss and send my customer a timely reject, but that would...

But in https://github.com/interledgerjs/ilp-connector/issues/400#issuecomment-349990901, @emschwartz stated that he wants to use it to allow for shorter message windows? And dynamically increasing maxUnsecuredBalance would require disconnecting and reconnecting the plugin, right? The...

ah, I guess if you still make the calls to `/api/health` then that's pretty much equivalent to the current heartbeat system, just in the other direction :) it gets more...

(this is on version 13, by the way)

so that it also receives asap

ok, so then this would not be necessary, provided the downtime was long enough to make previously broadcasted routes expire, and provided that your peer correctly noticed you have been...

ok, I think we should definitely edit [the readme of this repo](https://github.com/interledgerjs/ilp-connector#accounts) to document that.

Maybe the fact that multi-plugins start to behave as connectors is a sign that we should rethink our software architecture? For instance, deal with BTP and http in the connector,...