The Bits and Bytes of Computer Networking: Module 3; Terms

0.0(0)
studied byStudied by 0 people
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/37

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

38 Terms

1
New cards

ACK flag

One of the TCP control flags. ACK is short for acknowledge. A value of one in this field means that the acknowledgment number field should be examined.

2
New cards

Acknowledgement number

The number of the next expected segment in a TCP sequence.

3
New cards

Application layer

The layer that allows network applications to communicate in a way they understand.

4
New cards

Application layer payload

The entire contents of whatever data applications want to send to each other.

5
New cards

CLOSE

A connection state that indicates that the connection has been fully terminated, and that no further communication is possible.

6
New cards

CLOSE_WAIT

A connection state that indicates that the connection has been closed at the TCP layer, but that the application that opened the socket hasn't released its hold on the socket yet.

7
New cards

Connection-oriented protocol

A data-transmission protocol that establishes a connection at the transport layer, and uses this to ensure that all data has been properly transmitted.

8
New cards

Connectionless protocol

A data-transmission protocol that allows data to be exchanged without an established connection at the transport layer. The most common of these is known as UDP, or User Datagram Protocol.

9
New cards

Data offset field

The number of the next expected segment in a TCP packet/datagram.

10
New cards

Demultiplexing

Taking traffic that's all aimed at the same node and delivering it to the proper receiving service.

11
New cards

Destination port

The port of the service the TCP packet is intended for.

12
New cards

ESTABLISHED

Status indicating that the TCP connection is in working order, and both sides are free to send each other data.

13
New cards

FIN

One of the TCP control flags. FIN is short for finish. When this flag is set to one, it means the transmitting computer doesn't have any more data to send and the connection can be closed.

14
New cards

FIN_WAIT

A TCP socket state indicating that a FIN has been sent, but the corresponding ACK from the other end hasn't been received yet.

15
New cards

Firewall

It is a device that blocks or allows traffic based on established rules.

16
New cards

FTP

An older method used for transferring files from one computer to another, but you still see it in use today.

17
New cards

Handshake

A way for two devices to ensure that they're speaking the same protocol and will be able to understand each other.

18
New cards

Instantiation

The actual implementation of something defined elsewhere.

19
New cards

Listen

It means that a TCP socket is ready and listening for incoming connections.

20
New cards

Multiplexing

It means that nodes on the network have the ability to direct traffic toward many different receiving services.

21
New cards

Options field

It is sometimes used for more complicated flow control protocols.

22
New cards

Port

It is a 16-bit number that's used to direct traffic to specific services running on a networked computer.

23
New cards

Presentation layer

It is responsible for making sure that the unencapsulated application layer data is actually able to be understood by the application in question.

24
New cards

PSH flag

One of the TCP control flags. PSH is short for push. This flag means that the transmitting device wants the receiving device to push currently-buffered data to the application on the receiving end as soon as possible.

25
New cards

RST flag

One of the TCP control flags. RST is short for reset. This flag means that one of the sides in a TCP connection hasn't been able to properly recover from a series of missing or malformed segments.

26
New cards

Sequence number

A 32-bit number that's used to keep track of where in a sequence of TCP segments this one is expected to be.

27
New cards

Server or Service

A program running on a computer waiting to be asked for data.

28
New cards

Session layer

The network layer responsible for facilitating the communication between actual applications and the transport layer.

29
New cards

Socket

The instantiation of an endpoint in a potential TCP connection.

30
New cards

Source port

A high numbered port chosen from a special section of ports known as ephemeral ports.

31
New cards

SYN flag

One of the TCP flags. SYN stands for synchronize. This flag is used when first establishing a TCP connection and make sure the receiving end knows to examine the sequence number field.

32
New cards

SYN_RECEIVED

A TCP socket state that means that a socket previously in a listener state, has received a synchronization request and sent a SYN_ACK back.

33
New cards

SYN_SENT

A TCP socket state that means that a synchronization request has been sent, but the connection hasn't been established yet.

34
New cards

TCP checksum

A mechanism that makes sure that no data is lost or corrupted during a transfer.

35
New cards

TCP segment

A payload section of an IP datagram made up of a TCP header and a data section.

36
New cards

TCP window

The range of sequence numbers that might be sent before an acknowledgement is required.

37
New cards

URG flag

One of the TCP control flags. URG is short for urgent. A value of one here indicates that the segment is considered urgent and that the urgent pointer field has more data about this.

38
New cards

Urgent pointer field

A field used in conjunction with one of the TCP control flags to point out particular segments that might be more important than others.