Make bTCP finite state diagram in Draw.io

[basthijssen]

A drawing of the bTCP connection management finite state machine has to be made. On this we will base our own implementation of the bTCP project.

• [x] Initial version (based on online diagram)
• [ ] Final version (based on the requirements from the quote below and our actual implementation)

[basthijssen]

Comments from Mattermost:

In general, I would say to keep the FSM simple. The only things that should be present in the FSM are the things directly related to connection set up and teardown, i.e., the SYN, FIN, and ACK messages that are exchanged between client and server, the timeouts, the retry counters, and such. You do not need to include your RDT protocol in this FSM. In other words, your FSM will look something like this (a cloud involving things related to connection set up) --> a CONNECTED state --> (a cloud involving things related to connection teardown).