So I understand, for the most part, how SEQ and ACK numbers are determined (SEEP = Sdn.ncc = ISN + bytes), ACK = RCV NXT = SEQ is expected from the next packet received). What I am thinking is that SEC increments (with SDN.NXT and SNDUNA) send pure ACK packets.
ex: (I'm giving client an a ISN = 1, and server B isn = 100)
A -> (SEQ = 1, ACK = 100, LN = 412 bytes) (A) RCV. NXT = 100, SDNNC = 413, SNDUINA = 1 (B) RCV. NXT = 413, SDN.NET = 100, SDD .AnA = 100A & LT; - (SQ = 100, ACK = 413, LEN = 0) (A) RCV. NECC = 101, SDN NST = 413, SNDUENA = 413 (B) RCV. NECCT = 413, SDN Net = 101, SDUA = 101 ** (or 101?) ** A & lt; - (SEC = 101, ACK = 413, LN = 1448) (A) RCV. NXT = 101, SDN.NET = 413, SNDUANA = 413 (B) RCV. NXT = 413, sdn.net = 1549, SNDUENA = 101A - & gt; (SEQ = 413, ACK = 1549, LAN = 0) (A) RCV. NXT = 1549, sdn.net = 414, snd.una = 414 ** (or 413?) ** (b) RCV. NXT = 414, SND.NXT = 1549, SND.UNA = 1549
It seems that whenever you send packets, every time the SDN Do you increase SND.NA? It seems arbitrarily instead and SND.UNA = ACK is an odd exception for assignment. However, I feel that if you do not do this then your SDN. At the end of an exchange will be closed by one.
Am I missing something?
No comments:
Post a Comment