questionaire 0.1.0 (1999-Dec-16-Thu)
(the real questionaire)

These questions are asking about the protocol you have actually written
in the transport.c you turned in, even if it's not fully debugged yet;
they are not asking about a more elaborate protocol you may have planned
to write, for which major pieces of code are absent.

To get an idea of the level of detail we're looking for, remember that
this questionaire is taking the place of a 15-20 minute interview.

First, what are the names of all the team members?

What are your packet formats?  What do the fields mean?

Describe your data structures.

Of the four retransmission protocols we studied in class (stop-and-wait,
alternating-bit, go-back-N, selective-repeat), yours most closely
resembles which one?  What are the main differences?

Under what conditions does your transport source refuse to accept bytes
from the byte source?

What does the transport source do...

...when it accepts bytes from the byte source?

...when it receives an in-order ack (an ack you were expecting)?

...when it receives an out-of-order ack (an ack for sent data, but not
the ack you were expecting)?  (Depending on your protocol, there may be
no such thing as an out-of-order ack.)

...when it receives a redundant ack (an ack for data that has already
been acknowledged)?

...when a retransmission timer expires?

What does the transport sink do...

...when in-order data arrives?

...when out-of-order data arrives?

...when already-acknowledged data arrives?

...when its go-ahead method is called?

What value do you use for the retransmission timeout?  If you estimate
the round-trip time, how do you do that?

Do you implement any extensions?  If so, for each one, what does your
transport layer do to meet the extra requirements (that's not already
covered above)?

Efficiency and flow control:

Multiplexing:

Congestion control:

If there are any other questions you wish we had asked, feel free to
volunteer the answers.