1 ELEN602 Lecture 2 Review of Last Lecture Layering.

transcript

ELEN602 Lecture 2

• Review of Last Lecture

• Layering

Communication Networks

• Many forms of communication networks around

– Postal mail, telephone, Internet etc.

• Generic steps involved in communication

– Addressing, name-to-address translation, transport, routing, delivery

• Forms of delivery

– Reliable, in-order

– Unreliable, no acknowledgement

The user clicks on a link to indicate which document is to be retrieved.

The browser must determine the address that contains the document. It does this by sending a query to its local name server.

Once the address is known the browser establishes a connection to the specified machine, usually a TCP connection. In order for the connection to be successful, the specified machine must be ready to accept TCP connections.

The browser runs a client version of HTTP, which issues a request specifying both the name of the document and the possible document formats it can handle.

The machine that contains the requested document runs a server version of HTTP. It reacts to the HTTP request by sending an HTTP response which contains the desired document in the appropriate format.

The TCP connection is then closed and the user may view the document.

Steps in Web Surfing

HTTPserver

HTTPclient

Request

Response

Application level View

Steps in HTTP Transfer

• User selects document• Networking software locates the remote machine address &

establishes a 2-way connection• HTTP client sends request for document (GET )• HTTP daemon on remote machine interprets the GET message • Remote HTTP daemon sends the result of GET operation

– Result code, Description of the information, requested file• Remote HTTP daemon disconnects the connection• HTTP client displays the HTML content in the browser.

Domain Name Service

• DNS servers help resolve name-to-address translation

– Given a name such as ee.tamu.edu, find its IP address

• IP addresses = telephone numbers in phone network

• Machines (computers/network elements) know each other by IP addresses

• IP addresses are 32bits in IPv4.

• DNS protocol allows name-to-IP address resolution

– Similar to phone directory assistance (411 or 555-1212)

DNS Example (cont’d)

• QNAME = ee.tamu.edu, QCLASS = IN QTYPE = A

• QNAME = ee.tamu.edu QCLASS = IN QTYPE = A

– IN A 165.91.241.199

• The application will now use 165.91.241.199 whenever it needs to contact ee.tamu.edu

HTTPserver

HTTPclient

TCP TCP

GET 80, #

#, 80 STATUS

Port 80

Ephemeral

Port #

A more detailed view - Transport protocol

Email and SMTP

• Web transfers use HTTP, email uses SMTP (Simple Mail Transfer Protocol) - Application level protocols

• Sender - Local SMTP Server -- Remote SMTP Server - Receiver

• SMTP uses Port 25, HTTP uses port 80

• POP (Post Office Protocol) may be used if receiver not on all the time.

• Sender establishes TCP Connection to SMTP server

• Sends HELO message -identifying itself to SMTP server

• Client sends sender’s email address

• SMTP server acknowledges with 250 if successful

• Client sends receiver’s email address

• SMTRP server acknowledges with 250

• Client sends a DATA message - requesting permission to send email message

• SMTP server sends OK-to-send message

• Client transfers the email message

• SMTP server returns ack with a message ID

• Client indicates that the transfer is complete.

• SMTP confirms the receipt of End-of-transfer message

nentity

n-PDUs

nentity

Abstract View

n+1entity

n entity n entity

H n-SDU

Layering in General

n-PDU n-PDU n-PDU

Segmentation Reassembly

Blocking Unblocking

n-SDUn-SDUn-SDUn-SDUn-SDU

Data Units at different layers

ApplicationLayer

PresentationLayer

SessionLayer

TransportLayer

NetworkLayer

Data LinkLayer

PhysicalLayer

ApplicationLayer

PresentationLayer

SessionLayer

TransportLayer

NetworkLayer

Data LinkLayer

PhysicalLayer

NetworkLayer

Electrical and/or Optical Signals

Application A Application B

Data LinkLayer

PhysicalLayer

NetworkLayer

Data LinkLayer

PhysicalLayer

Communication Network

OSI Seven-layer Model

PS = packet switch

C = computer

Packet-Switched Network

G = gateway/router

An Internetwork

ApplicationLayer

PresentationLayer

SessionLayer

TransportLayer

NetworkLayer

Data LinkLayer

PhysicalLayer

ApplicationLayer

PresentationLayer

SessionLayer

TransportLayer

NetworkLayer

Data LinkLayer

PhysicalLayer

Application A Application Bdata

Headers and Trailers

ApplicationLayer

TransportLayer

InternetLayer

NetworkInterface

ApplicationLayer

TransportLayer

InternetLayer

NetworkInterface

(a) (b)

TCP/IP Network Architecture

Application

Transport

Internet

Network Interface

Application

Transport

Internet

Network Interface

Internet

Network Interface

Network 1 Network 2

Machine A Machine B

Router/Gateway

IP Layer and Network Interface Layer

HTTP SMTP RTP

TCP UDP

Network

Interface 1

Network

Interface 3

Network

Interface 2

IP Hour-Glass Protocol Graph

Net Interface

Ethernet PPP

Router

router

(1,3) r

Ethernet

Server PC

IP Header

Header containssource and destination physical addresses; network protocol type

Frame Check Sequence

Ethernet Header

IP Datagram on an Ethernet

HTTP Request

TCP Header

Header contains source and destination port numbers

Header contains source and destination IP addresses; transport protocol type

IP Header

Header contains source and destination physical addresses; network protocol type

Frame Check Sequence

Ethernet Header

Application 1

Socket

socket interface

kernel

Application 2

kernel

Underlying communication

Protocols

Underlying communication

Protocols

Communications network

Socket

socket interface

socket()

bind()

listen()

read()

close()

socket()

connect()

read()

write()

close()

blocks until server receivesa connect request from client

Server

Clientaccept()

write()

connect negotiation

socket()

bind()

sendto()

close()

socket()

bind()

recvfrom()

sendto()

close()

blocks until serverreceives data from client data

Server

Client

recvfrom()

User Interface

User PI

User DTP

PI = Protocol interpreter

DTP = Data transfer process

User FTP

Server PI

Server DTP

Server FTP

Control

Connection

C:\WINDOWS>ping nal.toronto.edu

Pinging nal.toronto.edu [128.100.244.3] with 32 bytes of data:

Reply from 128.100.244.3: bytes=32 time=118ms TTL=243Reply from 128.100.244.3: bytes=32 time=118ms TTL=243Reply from 128.100.244.3: bytes=32 time=118ms TTL=243Reply from 128.100.244.3: bytes=32 time=118ms TTL=243

C:\WINDOWS>

1 ELEN602 Lecture 2 Review of Last Lecture Layering.

Documents