Universidad Tecnolgica Nacional

Facultad Regional La Plata

Departamento de Ingeniera en Sistemas de Informacin

Ctedra:
Internetworking
Prctica 6

TCP

2014
Esta obra est bajo una licencia Reconocimiento-NoComercial-CompartirIgual de Creative Commons. Para ver una
copia de esta licencia, visite http://creativecommons.org/licenses/by-nc-sa/2.5/ o envie una carta a Creative Commons,
559 Nathan Abbott Way, Stanford, California 94305, USA.

1
02/07/2014

Internetworking Prctica 6: TCP

TCP provee una capa de transporte fiable, orientada a la conexin y orientada a un flujo de bytes. TCP
empaqueta los datos del usuario en segmentos. Cada vez que se enva un segmento se establece un tiempo
de espera para la recepcin de un asentimiento. Adems TCP reordena los datos que llegan fuera de
orden, descarta los datos duplicados, verifica errores y provee control de flujo de extremo a extremo.
El formato general del segmento TCP, encapsulado dentro de un datagrama IP es el siguiente:
0

7 8

15

16

Puerto de origen

31
Puerto de destino

Nmero de secuencia

FIN

RST

SYN

PSH

Reservado

ACK

Longitud del
header

URG

Nmero de asentimiento

Checksum

Tamao de ventana
Puntero a datos urgentes

Opciones (si las hay)

Datos (si los hay)

Ejercicio 1
Analice la siguiente secuencia de segmentos TCP correspondiente a una sesin SMTP. Qu extremo
solicita la finalizacin de la conexin?.
23:54:32.582881 172.16.16.1.1036 > 172.16.16.2.smtp: S
487845903:487845903(0) win 32120 <mss 1460,sackOK,timestamp 61145
0,nop,wscale 0> (DF) (ttl 64, id 205)
23:54:32.591247 172.16.16.2.smtp > 172.16.16.1.1036: S
1035743573:1035743573(0) ack 487845904 win 17520 <mss 1460> (DF) (ttl
64, id 69)
23:54:32.591361 172.16.16.1.1036 > 172.16.16.2.smtp: .
487845904:487845904(0) ack 1035743574 win 32120 (DF) (ttl 64, id 206)
23:54:32.735665 172.16.16.2.1024 > 172.16.16.1.auth: S
1035779851:1035779851(0) win 16384 <mss 1460> (DF) (ttl 64, id 70)
23:54:32.735781 172.16.16.1.auth > 172.16.16.2.1024: R 0:0(0) ack
1035779852 win 0 (ttl 255, id 207)
23:54:32.862045 172.16.16.2.smtp > 172.16.16.1.1036: P
1035743574:1035743664(90) ack 487845904 win 17520 (DF) (ttl 64, id 71)
23:54:32.862157 172.16.16.1.1036 > 172.16.16.2.smtp: .
487845904:487845904(0) ack 1035743664 win 32120 (DF) (ttl 64, id 208)
23:54:56.245807 172.16.16.1.1036 > 172.16.16.2.smtp: F
487845904:487845904(0) ack 1035743664 win 32120 (DF) (ttl 64, id 209)

Internetworking Prctica 6: TCP

23:54:56.259868 172.16.16.2.smtp > 172.16.16.1.1036: .
1035743664:1035743664(0) ack 487845905 win 17520 (DF) (ttl 64, id 72)
23:54:56.266464 172.16.16.2.smtp > 172.16.16.1.1036: F
1035743664:1035743664(0) ack 487845905 win 17520 (DF) (ttl 64, id 73)
23:54:56.266578 172.16.16.1.1036 > 172.16.16.2.smtp: .
487845905:487845905(0) ack 1035743665 win 32120 (DF) (ttl 64, id 210)
Ejercicio 2
Analice la siguiente secuencia de segmentos TCP.
23:53:04.459609 172.16.16.1.1035 > 172.16.16.2.discard: S
404078080:404078080(0) win 32120 <mss 1460,sackOK,timestamp 52333
0,nop,wscale 0> (DF) (ttl 64, id 204)
23:53:04.463902 172.16.16.2.discard > 172.16.16.1.1035: R 0:0(0) ack
404078081 win 0 (ttl 64, id 68)
Ejercicio 3
Analice la siguiente secuencia de segmentos TCP correspondiente a una sesin SMTP. Qu sucede
entre el 7 y 12 segmento? Cules pueden ser las causas?
00:00:33.080419 172.16.16.1.1038 > 172.16.16.2.smtp: S
892754819:892754819(0) win 32120 <mss 1460,sackOK,timestamp 97195
0,nop,wscale 0> (DF) (ttl 64, id 212)
00:00:33.085810 172.16.16.2.smtp > 172.16.16.1.1038: S
1100608322:1100608322(0) ack 892754820 win 17520 <mss 1460> (DF) (ttl
64, id 155)
00:00:33.085934 172.16.16.1.1038 > 172.16.16.2.smtp: .
892754820:892754820(0) ack 1100608323 win 32120 (DF) (ttl 64, id 213)
00:00:33.218398 172.16.16.2.1025 > 172.16.16.1.auth: S
1100656730:1100656730(0) win 16384 <mss 1460> (DF) (ttl 64, id 156)
00:00:33.218509 172.16.16.1.auth > 172.16.16.2.1025: R 0:0(0) ack
1100656731 win 0 (ttl 255, id 214)
00:00:33.317164 172.16.16.2.smtp > 172.16.16.1.1038: P
1100608323:1100608413(90) ack 892754820 win 17520 (DF) (ttl 64, id
157)
00:00:33.317279 172.16.16.1.1038 > 172.16.16.2.smtp: .
892754820:892754820(0) ack 1100608413 win 32120 (DF) (ttl 64, id 215)
00:01:04.012787 172.16.16.1.1038 > 172.16.16.2.smtp: P
892754820:892754828(8) ack 1100608413 win 32120 (DF) (ttl 64, id 216)
00:01:07.007393 172.16.16.1.1038 > 172.16.16.2.smtp: P
892754820:892754828(8) ack 1100608413 win 32120 (DF) (ttl 64, id 217)
00:01:13.007392 172.16.16.1.1038 > 172.16.16.2.smtp: P
892754820:892754828(8) ack 1100608413 win 32120 (DF) (ttl 64, id 218)
00:01:25.007402 172.16.16.1.1038 > 172.16.16.2.smtp: P
892754820:892754828(8) ack 1100608413 win 32120 (DF) (ttl 64, id 219)

Internetworking Prctica 6: TCP

00:02:07.872825 172.16.16.2.smtp > 172.16.16.1.1038: .
1100608413:1100608413(0) ack 892754828 win 17512 (DF) (ttl 64, id 158)
00:02:07.875059 172.16.16.2.smtp > 172.16.16.1.1038: .
1100608413:1100608413(0) ack 892754828 win 17512 (DF) (ttl 64, id 159)
00:02:07.877231 172.16.16.2.smtp > 172.16.16.1.1038: .
1100608413:1100608413(0) ack 892754828 win 17512 (DF) (ttl 64, id 160)
00:02:07.884602 172.16.16.2.smtp > 172.16.16.1.1038: P
1100608413:1100608487(74) ack 892754828 win 17520 (DF) (ttl 64, id
161)
00:02:07.897391 172.16.16.1.1038 > 172.16.16.2.smtp: .
892754828:892754828(0) ack 1100608487 win 32120 (DF) (ttl 64, id 222)
00:03:36.196701 172.16.16.1.1038 > 172.16.16.2.smtp: P
892754828:892754834(6) ack 1100608487 win 32120 (DF) (ttl 64, id 223)
00:04:57.933568 172.16.16.2.smtp > 172.16.16.1.1038: P
1100608487:1100608531(44) ack 892754834 win 17520 (DF) (ttl 64, id
162)
00:04:57.935264 172.16.16.2.smtp > 172.16.16.1.1038: F
1100608531:1100608531(0) ack 892754834 win 17520 (DF) (ttl 64, id 163)
00:04:57.935343 172.16.16.1.1038 > 172.16.16.2.smtp: .
892754834:892754834(0) ack 1100608532 win 32120 (DF) (ttl 64, id 226)
00:04:57.958356 172.16.16.1.1038 > 172.16.16.2.smtp: F
892754834:892754834(0) ack 1100608532 win 32120 (DF) (ttl 64, id 227)
00:04:57.970318 172.16.16.2.smtp > 172.16.16.1.1038: .
1100608532:1100608532(0) ack 892754835 win 17520 (DF) (ttl 64, id 164)
Ejercicio 4
Analice la siguiente conexin TCP. Explique el comportamiento de los tamaos de ventana. Cules
pueden ser los motivos de este comportamiento?
00:23:22.772762 172.16.16.1.1045 > 172.16.16.2.discard: S
2346883656:2346883656(0) win 32120 <mss 1460,sackOK,timestamp 234164
0,nop,wscale 0> (DF) (ttl 64, id 315)
00:23:22.776013 172.16.16.2.discard > 172.16.16.1.1045: S
1314158845:1314158845(0) ack 2346883657 win 17520 <mss 1460> (DF) (ttl
64, id 311)
00:23:22.776124 172.16.16.1.1045 > 172.16.16.2.discard: .
2346883657:2346883657(0) ack 1314158846 win 32120 (DF) (ttl 64, id 16)
00:23:52.228115 172.16.16.1.1045 > 172.16.16.2.discard: P
2346883657:2346885117(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
317)
00:23:52.228177 172.16.16.1.1045 > 172.16.16.2.discard: P
2346885117:2346886297(1180) ack 1314158846 win 32120 (DF) (ttl 64, id
318)

Internetworking Prctica 6: TCP

00:23:52.338045 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346886297 win 14880 (DF) (ttl 64, id
312)
00:24:01.885190 172.16.16.1.1045 > 172.16.16.2.discard: P
2346886297:2346887757(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
319)
00:24:01.968170 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346887757 win 13420 (DF) (ttl 64, id
313)
00:24:01.968278 172.16.16.1.1045 > 172.16.16.2.discard: P
2346887757:2346888312(555) ack 1314158846 win 32120 (DF) (ttl 64, id
320)
00:24:02.068033 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346888312 win 12865 (DF) (ttl 64, id
314)
00:24:12.750842 172.16.16.1.1045 > 172.16.16.2.discard: P
2346888312:2346889772(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
321)
00:24:12.750895 172.16.16.1.1045 > 172.16.16.2.discard: P
2346889772:2346891232(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
322)
00:24:12.750924 172.16.16.1.1045 > 172.16.16.2.discard: P
2346891232:2346892408(1176) ack 1314158846 win 32120 (DF) (ttl 64, id
323)
00:24:12.858313 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346892408 win 8769 (DF) (ttl 64, id 315)
00:24:23.583730 172.16.16.1.1045 > 172.16.16.2.discard: P
2346892408:2346893868(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
324)
00:24:23.583784 172.16.16.1.1045 > 172.16.16.2.discard: .
2346893868:2346895328(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
325)
00:24:23.583812 172.16.16.1.1045 > 172.16.16.2.discard: P
2346895328:2346896504(1176) ack 1314158846 win 32120 (DF) (ttl 64, id
326)
00:24:23.687954 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346896504 win 4673 (DF) (ttl 64, id 316)
00:24:35.549445 172.16.16.1.1045 > 172.16.16.2.discard: .
2346896504:2346897964(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
327)
00:24:35.549499 172.16.16.1.1045 > 172.16.16.2.discard: .
2346897964:2346899424(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
328)
00:24:35.549528 172.16.16.1.1045 > 172.16.16.2.discard: P
2346899424:2346900600(1176) ack 1314158846 win 32120 (DF) (ttl 64, id
329)

Internetworking Prctica 6: TCP

00:24:35.688066 172.16.16.2.discard > 172.16.16.1.1045: .

1314158846:1314158846(0) ack 2346900600 win 577 (DF) (ttl 64, id 317)
00:24:58.537413 172.16.16.1.1045 > 172.16.16.2.discard: .
2346900600:2346901177(577) ack 1314158846 win 32120 (DF) (ttl 64, id
330)
00:24:58.648021 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 0 (DF) (ttl 64, id 358)
00:24:59.347384 172.16.16.1.1045 > 172.16.16.2.discard: .
2346901176:2346901176(0) ack 1314158846 win 32120 (DF) (ttl 64, id
331)
00:24:59.352543 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 0 (DF) (ttl 64, id 359)
00:24:59.947385 172.16.16.1.1045 > 172.16.16.2.discard: .
2346901176:2346901176(0) ack 1314158846 win 32120 (DF) (ttl 64, id
332)
00:24:59.952252 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 0 (DF) (ttl 64, id 360)
00:25:01.147385 172.16.16.1.1045 > 172.16.16.2.discard: .
2346901176:2346901176(0) ack 1314158846 win 32120 (DF) (ttl 64, id
333)
00:25:01.151578 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 0 (DF) (ttl 64, id 361)
00:25:03.547387 172.16.16.1.1045 > 172.16.16.2.discard: .
2346901176:2346901176(0) ack 1314158846 win 32120 (DF) (ttl 64, id
334)
00:25:03.553513 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 0 (DF) (ttl 64, id 362)
00:25:08.347381 172.16.16.1.1045 > 172.16.16.2.discard: .
2346901176:2346901176(0) ack 1314158846 win 32120 (DF) (ttl 64, id
335)
00:25:08.353852 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 0 (DF) (ttl 64, id 363)
00:25:17.947385 172.16.16.1.1045 > 172.16.16.2.discard: .
2346901176:2346901176(0) ack 1314158846 win 32120 (DF) (ttl 64, id
336)
00:25:17.950522 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 0 (DF) (ttl 64, id 364)
00:25:37.147385 172.16.16.1.1045 > 172.16.16.2.discard: .
2346901176:2346901176(0) ack 1314158846 win 32120 (DF) (ttl 64, id
337)
00:25:37.151894 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 0 (DF) (ttl 64, id 365)

Internetworking Prctica 6: TCP

00:26:00.406920 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 8192 (DF) (ttl 64, id 366)
00:26:00.407036 172.16.16.1.1045 > 172.16.16.2.discard: .
2346901177:2346902060(883) ack 1314158846 win 32120 (DF) (ttl 64, id
338)
00:26:00.407059 172.16.16.1.1045 > 172.16.16.2.discard: .
2346902060:2346903520(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
339)
00:26:00.407073 172.16.16.1.1045 > 172.16.16.2.discard: P
2346903520:2346904980(1460) ack 1314158846 win 32120 (DF) (ttl 64, id
340)
00:26:00.411767 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346901177 win 16384 (DF) (ttl 64, id
367)
00:26:00.579218 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346904980 win 17520 (DF) (ttl 64, id
368)
00:26:00.579336 172.16.16.1.1045 > 172.16.16.2.discard: P
2346904980:2346905613(633) ack 1314158846 win 32120 (DF) (ttl 64, id
341)
00:26:00.687757 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346905613 win 17520 (DF) (ttl 64, id
369)
00:26:14.554635 172.16.16.1.1045 > 172.16.16.2.discard: P
2346905613:2346905619(6) ack 1314158846 win 32120 (DF) (ttl 64, id
342)
00:26:14.658236 172.16.16.2.discard > 172.16.16.1.1045: .
1314158846:1314158846(0) ack 2346905619 win 17520 (DF) (ttl 64, id
370)
00:26:31.161653 172.16.16.2.discard > 172.16.16.1.1045: F
1314158846:1314158846(0) ack 2346905619 win 17520 (DF) (ttl 64, id
371)
00:26:31.161762 172.16.16.1.1045 > 172.16.16.2.discard: .
2346905619:2346905619(0) ack 1314158847 win 32120 (DF) (ttl 64, id
343)
00:26:31.161984 172.16.16.1.1045 > 172.16.16.2.discard: F
2346905619:2346905619(0) ack 1314158847 win 32120 (DF) (ttl 64, id
344)
00:26:31.309694 172.16.16.2.discard > 172.16.16.1.1045: .
1314158847:1314158847(0) ack 2346905620 win 17520 (DF) (ttl 64, id
372)

Internetworking Prctica 6: TCP

Ejercicio 5
Analice los campos de los siguientes segmentos TCP.
00:29:41.217960 172.16.16.1.1048 > 172.16.16.2.discard: S
2744403552:2744403552(0) win 32120 <mss 1460,sackOK,timestamp 272009
0,nop,wscale 0> (DF) (ttl 64, id 356)

4500 003c 0164 4000 4006 c134 ac10 1001

ac10 1002 0418 0009 a394 4660 0000 0000
a002 7d78 3dc8 0000 0204 05b4 0402 080a
0004 2689 0000 0000 0103 0300
00:29:41.224848 172.16.16.2.discard > 172.16.16.1.1048: S
1382585531:1382585531(0) ack 2744403553 win 17520 <mss 1460> (DF) (ttl
64, id 382)

4500 002c 017e 4000 4006 c12a ac10 1002

ac10 1001 0009 0418 5268 94bb a394 4661
6012 4470 0648 0000 0204 05b4 0000
00:29:41.224967 172.16.16.1.1048 > 172.16.16.2.discard: .
2744403553:2744403553(0) ack 1382585532 win 32120 (DF) (ttl 64, id 57)

4500 0028 0165 4000 4006 c147 ac10 1001

ac10 1002 0418 0009 a394 4661 5268 94bc
5010 7d78 e4fc 0000
00:31:32.276311 172.16.16.1.1048 > 172.16.16.2.discard: P
2744403553:2744403600(47) ack 1382585532 win 32120 (DF) (ttl 64, id
358)

4500 0057 0166 4000 4006 c117 ac10 1001

ac10 1002 0418 0009 a394 4661 5268 94bc
5018 7d78 05ed 0000 5369 2064 6563 6f64
6966 6963 6173 2065 7374 6f20 6176 6973
616d 6520 6120 6261 7263 6540 6c69 6e65
732e 6564 750d 0a
00:31:32.398118 172.16.16.2.discard > 172.16.16.1.1048: .
1382585532:1382585532(0) ack 2744403600 win 17520 (DF) (ttl 64, id
423)
00:31:37.371260 172.16.16.1.1048 > 172.16.16.2.discard: F
2744403600:2744403600(0) ack 1382585532 win 32120 (DF) (ttl 64, id
359)

4500 0028 0167 4000 4006 c145 ac10 1001

ac10 1002 0418 0009 a394 4690 5268 94bc
5011 7d78 e4cc 0000
00:31:37.383926 172.16.16.2.discard > 172.16.16.1.1048: .
1382585532:1382585532(0) ack 2744403601 win 17520 (DF) (ttl 64, id
424)

4500 0028 01a8 4000 4006 c104 ac10 1002

ac10 1001 0009 0418 5268 94bc a394 4691

Internetworking Prctica 6: TCP

5010 4470 1dd5 0000 0000 0000 0000

00:31:37.390646 172.16.16.2.discard > 172.16.16.1.1048: F
1382585532:1382585532(0) ack 2744403601 win 17520 (DF) (ttl 64, id
425)
00:31:37.390759 172.16.16.1.1048 > 172.16.16.2.discard: .
2744403601:2744403601(0) ack 1382585533 win 32120 (DF) (ttl 64, id
360)
Ejercicio 6
Analice los campos de los siguientes segmentos TCP correspondientes a una sesin HTTP.
00:33:27.060350 172.16.16.1.1049 > 172.16.16.2.www: S
2960269198:2960269198(0) win 32120 <mss 1460,sackOK,timestamp
2945930,nop,wscale 0> (DF) (ttl 64, id 361)
00:33:27.067211 172.16.16.2.www > 172.16.16.1.1049: S
1423193723:1423193723(0) ack 2960269199 win 17520 <mss 1460> (DF) (ttl
64, id 426)
00:33:27.067350 172.16.16.1.1049 > 172.16.16.2.www: .
2960269199:2960269199(0) ack 1423193724 win 32120 (DF) (ttl 64, id
362)
00:33:27.073750 172.16.16.1.1049 > 172.16.16.2.www: P
2960269199:2960269863(664) ack 1423193724 win 32120 (DF) (ttl 64, id
363)
00:33:27.202690 172.16.16.2.www > 172.16.16.1.1049: .
1423193724:1423195184(1460) ack 2960269863 win 17520 (DF) (ttl 64, id
427)
00:33:27.202818 172.16.16.1.1049 > 172.16.16.2.www: .
2960269863:2960269863(0) ack 1423195184 win 30660 (DF) (ttl 64, id
364)
00:33:27.213171 172.16.16.2.www > 172.16.16.1.1049: P
1423195184:1423195505(321) ack 2960269863 win 17520 (DF) (ttl 64, id
428)
00:33:27.217410 172.16.16.1.1049 > 172.16.16.2.www: .
2960269863:2960269863(0) ack 1423195505 win 32120 (DF) (ttl 64, id
365)
00:33:27.277131 172.16.16.2.www > 172.16.16.1.1049: F
1423195505:1423195505(0) ack 2960269863 win 17520 (DF) (ttl 64, id
429)
00:33:27.277237 172.16.16.1.1049 > 172.16.16.2.www: .
2960269863:2960269863(0) ack 1423195506 win 32120 (DF) (ttl 64, id
366)
00:33:27.282601 172.16.16.1.1049 > 172.16.16.2.www: F
2960269863:2960269863(0) ack 1423195506 win 32120 (DF) (ttl 64, id
367)
00:33:27.293952 172.16.16.2.www > 172.16.16.1.1049: .
1423195506:1423195506(0) ack 2960269864 win 17520 (DF) (ttl 64, id
430)

Internetworking Prctica 6: TCP

Diagrama de estados de TCP

starting point

CLOSED

appl: passive open

send: <nothing>

T
RS
:
cv

recv: SYN
send: SYN, ACK
simoultaneous open

SYN_RECVD
CK g>
: A hin
cv ot
re : <n
nd
se

ESTABLISHED

appl: close
send: FIN

SYN_SENT
active open

appl: close
or timeout

recv: FIN
send: ACK

CLOSE_WAIT

ap
p
se l: clo
nd
: F se
IN

data transfer
status

appl: close
send: FIN

re

LISTEN
passive open

re
cv
:
se SY
nd N,
:A A
CK CK

n
pe
eo
tiv YN
ta
ac
S
da
pl: d:
ap en
nd N
s
se SY
pl: d:
ap sen

:
cv
re

;
YN

:
nd
se

C
,A
N
Y

LAST_ACK

recv:ACK
send: <nothing>

passive close

FIN_WAIT_1
recv: ACK
send: <nothing>

CK
,A
IN CK
:F A
cv d:
re sen

recv: ACK
send: <nothing>

simultaneous close

recv: FIN
send: ACK

FIN_WAIT_2

recv: FIN
send: ACK

TIME_WAIT

CLOSING

2MSL timeout

active close
indicate normal transitions for client
indicate normal transitions for server
appl:

indicate state transitions taken when application issues operation

recv:

indicate state transitions taken when segment received

send:

indicate what is sent for this transition

10