behave-05----Page:3
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
|
Req # 1 – TCP State Machine(SM) TCP NAT Sessions MUST be stateful. NAT MUST use light-weight TCP State Machine for managing timers, seq/ack adjustments etc. TCP NAT Sessions can be light-weight and must carry three states at a minimum – STARTUP, ACTIVE, CLOSING. A TCP NAT Session enters STARTUP state upon seeing the first SYN for a TCP session. A TCP NAT Session enters ACTIVE state upon completing 3-way handshake. A TCP NAT Session enters CLOSING state upon seeing FIN or RST for the session. |