CNET_read_physical returns either a corrupt frame, or (frame, seq- seqno) CNET_read application returns msg set frame.msg = msg and frame.seq = seqno CNET write_physical (frame) start timer null null set seqno=o/ so: Wait for application msg S1: Wait for ACK CNET read physical returns frame CNET_read physical returns a good frame && (frame.seqseqno) timeout null set seqno = 1 -seqno stop timer CNET write _physical (last transmitted frame) start timer In the sender shown above, state Si has a self-transition with a null action. Suppose we re place this null action with "CNET write physical (last transmitted frame)". For the modified sender, draw a timing diagram illustrating a sequence of message exchanges where the sender has 3 packets to transmit, and the sender prematurely times out on each of the three packets. You may assume that all data and ACK packets are delivered correctly. How many packets are transmitted by the sender in this scenario? Explain CNET_read_physical returns either a corrupt frame, or (frame, seq- seqno) CNET_read application returns msg set frame.msg = msg and frame.seq = seqno CNET write_physical (frame) start timer null null set seqno=o/ so: Wait for application msg S1: Wait for ACK CNET read physical returns frame CNET_read physical returns a good frame && (frame.seqseqno) timeout null set seqno = 1 -seqno stop timer CNET write _physical (last transmitted frame) start timer In the sender shown above, state Si has a self-transition with a null action. Suppose we re place this null action with "CNET write physical (last transmitted frame)". For the modified sender, draw a timing diagram illustrating a sequence of message exchanges where the sender has 3 packets to transmit, and the sender prematurely times out on each of the three packets. You may assume that all data and ACK packets are delivered correctly. How many packets are transmitted by the sender in this scenario? Explain