1. Behrouz A. Forouzan TCP/IP Protocol Suite, 3rd Ed.
Introduction and review

2. PROTOCOLS AND STANDARDS
In this section, we define two widely used terms: protocols and standards. First, we define protocol, which is synonymous with rule. Then we discuss standards, which are agreed-upon rules.

3. PROTOCOLS
Two entities (anything capable of sending or receiving information) can’t simply send bit streams to each other and expect to be understood.
So, the entities must agree on a protocol.
A protocol is a set of rules that govern data communications.
A protocol defines what is communicated, how it is communicated, and when it is communicated

4. PROTOCOLS Key elements of protocol are: Syntax Semantics
refers to the structure or format of the data
first 8 bits = source address.
Semantics
refers to the meaning of each section of bits.
How is a particular pattern to be interpreted.
What action is to be taken based on that interpretation.
e.g. does an address identify the route to be taken or the final destination of the message.

5. PROTOCOLS Timing When data should be sent. How fast they can be sent.
E.g. matching the speed between the sender and receiver

6. STANDARDS
Standards are essential for creating a competitive market for equipment and guaranteeing interoperability of data and telecommunication.

7. STANDARDS Two categories:
De facto: Standards that have not been approved by an organized body but have been adopted as standards through widespread use.
De jure: Standards that have been legislated by an officially recognized body.
Standards are developed through the cooperation of standards creation committees, forums, and government regulatory agencies.

8. Internet standard
An Internet standard is a thoroughly tested specification that is useful and adhered to those who work with the internet.
There is a strict procedure by which a specification attains Internet standard status.
A specification begins as an internet draft.
Internet draft is a working document (work in progress) with no official status and a 6 month lifetime.

9. Internet standard
After recommendation from the Internet authority, a draft may be published as a Request for Comment (RFC).
Each RFC is edited, assigned a number, and made available to all interested parties.
Then, RFC might become a standard after going through maturity levels

10. Maturity levels of an RFC

11. Maturity levels of an RFC
Proposed Standard
A proposed standard is a specification that is stable, well understood, and of sufficient interest to the Internet community. At this level, the specification is usually tested and implemented by several different groups.
Draft Standard
A proposed standard is elevated to draft standard status after at least two successful independent and interoperable implementations. Barring difficulties, a draft standard, with modifications if specific problems are encountered, normally becomes an Internet standard.

12. Maturity levels of an RFC
Internet Standard
A draft standard reaches Internet standard status after demonstrations of successful implementation.
Historic
The historic RFCs are significant from a historical perspective. They either have been superseded by later specifications or have never passed the necessary maturity levels to become an Internet standard.

13. Maturity levels of an RFC
Experimental
An RFC classified as experimental describes work related to an experimental situation that does not affect the operation of the Internet. Such an RFC should not be implemented in any functional Internet service.
Informational
An RFC classified as informational contains general, historical, or tutorial information related to the Internet. It is usually written by someone in a non-Internet organization, such as a vendor.

14. Requirement levels of an RFC

15. Requirement levels of an RFC
Required
An RFC is labeled required if it must be implemented by all Internet systems to achieve minimum conformance. For example, IP and ICMP are required protocols.
Recommended
An RFC labeled recommended is not required for minimum conformance; it is recommended because of its usefulness. For example, FTP and TELNET are recommended protocols.

16. Requirement levels of an RFC
Elective
An RFC labeled elective is not required and not recommended. However, a system can use it for its own benefit.
Limited Use
An RFC labeled limited use should be used only in limited situations. Most of the experimental RFCs fall under this category.
Not Recommended
An RFC labeled not recommended is inappropriate for general use. Normally a historic (deprecated) RFC may fall under this category.

17. The OSI Model

18. The OSI Model

19. Organization of the Layers
Layers 1, 2, and 3—physical, data link, and network—are the network support layers; they deal with the physical aspects of moving data from one device to another (such as electrical specifications, physical connections, physical addressing, and transport timing and reliability).
Layers 5, 6, and 7—session, presentation, and application—can be thought of as the user support layers
Layer 4, the transport layer, links the two subgroups and ensures that what the lower layers have transmitted is in a form that the upper layers can use.
The upper OSI layers are almost always implemented in software; lower layers are a combination of hardware and software, except for the physical layer, which is mostly hardware.

20. The OSI Model

21. OSI Model Layers

22. Physical Layer
The physical layer is concerned with transmitting raw bits over a communication channel.
It deals with mechanical and electrical specifications of interfaces and medium.
It also defines the procedures and functions that physical devices and interfaces have to perform for transmission to occur.

23. Physical Layer
The physical layer is also concerned with the following:
Physical characteristics of interfaces and media. The physical layer defines the characteristics of the interface between the devices and the transmission media. It also defines the type of transmission media.
Representation of bits. The physical layer data consists of a stream of bits (sequence of 0s or 1s) with no interpretation. To be transmitted, bits must be encoded into signals—electrical or optical. The physical layer defines the type of encoding (how 0s and 1s are changed to signals).

24. Physical Layer
Data rate. The transmission rate—the number of bits sent each second—is also defined by the physical layer. In other words, the physical layer defines the duration of a bit, which is how long it lasts.
Synchronization of bits. The sender and receiver must not only use the same bit rate but must also be synchronized at the bit level. In other words, the sender and the receiver clocks must be synchronized.
Line configuration. The physical layer is concerned with the connection of devices to the media. In a point-to-point configuration, two devices are connected together through a dedicated link. In a multipoint configuration, a link is shared between several devices.

25. Physical Layer
Physical topology. The physical topology defines how devices are connected to make a network. Devices can be connected using a mesh topology (every device connected to every other device), a star topology (devices are connected through a central device), a ring topology (each device is connected to the next, forming a ring), or a bus topology (every device on a common link).
Transmission mode. The physical layer also defines the direction of transmission between two devices: simplex, half-duplex, or full-duplex.

26. Physical Layer

27. Physical Layer Example

28. Physical layer

29. Data Link Layer
The data link layer is responsible for moving frames from one hop (node) to the next.

30. Data Link Layer
The data link layer transform the physical layer, a raw transmission facility, to a reliable link.
It makes the physical layer appear error-free.
Framing
Physical Addressing
Flow Control
Error Control
Access Control
Determine which device has control over the link

31. Data Link Layer

32. Data Flow from Data Link Layer

33. Hop-to-hop delivery

34. Network Layer
The network layer is responsible for the delivery of individual packets from the source host to the destination host.

35. Network Layer Logical Addressing Routing
The physical addressing implemented by the data link layer handles the addressing problem locally.(same link)
If a packet passes the network boundary, we need another addressing system to help distinguish the source and destination systems. (different links)
Routing

36. Network Layer

37. Data Flow from Network Layer

38. Source-to-destination delivery

39. Transport Layer
The transport layer is responsible for the delivery of a message from one process to another.

40. Transport Layer Service-Point Addressing Segmentation and Reassembly
Computers run several programs at the same time.
Process-to-process delivery means delivery from a specific process (running program) on one computer to a specific process on the other.
The transport layer header must include a type of address called a service point address.
Segmentation and Reassembly
A message is divided into transmittable segments.
Each segment containing a sequence number.

41. Transport Layer Connection Control Flow Control Error Control
The transport layer can be either connectionless or connection-oriented.
Flow Control
Error Control

42. Process-to-Process delivery

43. Session Layer
The session layer is responsible for dialog control and synchronization.

44. Session Layer Dialog control Synchronization
Allows two systems to enter into a dialog.(half/full duplex)
Synchronization
Allows a process to add checkpoints, to a stream of data.

45. Presentation Layer
The presentation layer is concerned with the syntax and semantics of the information exchanged between two systems.

46. Presentation Layer Translation Encryption
The processes in two systems are usually exchanging information in the form of character strings, numbers, and so on.
The information must be changed to bit streams before being transmitted.
Encryption
Encryption means that the sender transform the original information to another form and sends the resulting message out over the network.

47. Presentation Layer compression
Decryption reverses the original process to transform the message back to its original form.
compression
Data compression reduces the number of bits contained in the information.

48. Application Layer It enables the user to access the network.
contains a variety of protocols that are commonly needed by users.

49. Application Layer Network Virtual Terminal
It allows user to log on to a remote host.
File Transfer, Access and Management
It allows user to access and manage files in a remote host.
Mail Services
Directory Services
It provides distributed database sources and access for global information about various objects and services.

50. Summary of layers

51. TCP/IP Protocol Suite
The TCP/IP protocol suite was developed prior to the OSI model.
The layers in the TCP/IP protocol suite do not exactly match those in the OSI model.
The original TCP/IP protocol suite was defined as having four layers:
host-to-network, internet, transport, and application

52. TCP/IP Protocol Suite

53. Internet Layer Internetworking Protocol (IP)
It is unreliable and connectionless protocol
IP transports data in packets called datagrams
Each of which is transported separately.
Address Resolution Protocol (ARP)
ARP is used to associate a logical address with a physical address.
Reverse Address Resolution Protocol (RARP)
RARP allows a host to discover its internet address when it knows only its physical address.

54. Internet Layer Internet Control Message Protocol (ICMP)
ICMP is a mechanism used by hosts gateways to send notification of datagram problems back to the sender.
Internet Group Message Protocol (IGMP)
IGMP is used to facilitate the simultaneous transmission o a message to a group of recipients.

55. Transport Layer User Datagram Protocol (UDP)
Transmission Control Protocol (TCP)
Stream Control Transmission Protocol (SCTP)
It provides support for newer application such as voice over the internet.

56. Addressing
Four levels of addresses are used in an internet employing the TCP/IP protocols: physical, logical, port, and specific.

57. Addressing in TCP/IP

58. Physical addresses
The physical address (link address) is the address of a node as defined by its LAN or WAN
It is included in the frame used by the data link layer
The size and format of these addresses vary depending on the network.
Ethernet uses a 6 byte physical address tht is imprinted on the network interface card (NIC).
LocalTalk (Apple) has a 1 byte dynamic address that changes each time the station comes up.

59. Physical addresses
Most local-area networks use a 48-bit (6-byte) physical address written as 12 hexadecimal digits; every byte (2 hexadecimal digits) is separated by a colon, as shown below:
07:01:02:01:2C:4B

60. Logical addresses
Logical addresses are necessary for universal communications that are independent of underlying physical networks.
A universal addressing system is needed in which each host can be identified uniquely, regardless of the underlying physical network.
A logical address in the Internet is currently a 32-bit address that can uniquely define a host connected to the Internet.

61. Example
The figure below shows a part of an internet with two routers connecting three LANs. Each device (computer or router) has a pair of addresses (logical and physical) for each connection. In this case, each computer is connected to only one link and therefore has only one pair of addresses. Each router, however, is connected to three networks (only two are shown in the figure). So each router has three pairs of addresses, one for each connection.

62. Logical addresses

63. Port addresses
In the TCP/IP architecture, the label assigned to a process is called a port address.
A port address in TCP/IP is 16 bits in length.
It is represented by one decimal number as 753.

64. Port addresses

65. Example
The figure above shows two computers communicating via the Internet. The sending computer is running three processes at this time with port addresses a, b, and c. The receiving computer is running two processes at this time with port addresses j and k. Process a in the sending computer needs to communicate with process j in the receiving computer. Note that although physical addresses change from hop to hop, logical and port addresses remain the same from the source to destination.

66. Internet today