When you connect with DHCP, you are assigned a

8
When you connect with DHCP, you are assigned a Authoritative DNS server Local DNS server

description

When you connect with DHCP, you are assigned a. Authoritative DNS server Local DNS server. DNS uses. TCP UDP. TvF: Each socket is identified by a port number. Not the case for TCP sockets, holds for UDP - PowerPoint PPT Presentation

Transcript of When you connect with DHCP, you are assigned a

Page 1: When you connect with DHCP, you are assigned a

When you connect with DHCP, you are assigned a

Authoritative DNS server Local DNS server

Page 2: When you connect with DHCP, you are assigned a

DNS uses

TCP UDP

Page 3: When you connect with DHCP, you are assigned a

TvF: Each socket is identified by a port number

Not the case for TCP sockets, holds for UDP Webservers use port 80 for HTTP requests,

then how can you have dedicated TCP socket connection for each client?

A TCP socket is identified by source IP and source port# in addition to destination port#

Page 4: When you connect with DHCP, you are assigned a

If client starts earlier than server for a TCP connection:

a)I don't know

b)when server starts, we can have business as usual

c)client gets stuck

Page 5: When you connect with DHCP, you are assigned a

If client starts earlier than server for a UDP connection:

a)I don't know

b)when server starts, we can have business as usual

c)client gets stuck

Page 6: When you connect with DHCP, you are assigned a

Take home message 1 from Chp3

Transport layer protocols are implemented in the end systems (where in the end systems?), but not in the network routers

Routers do not examine the transport later segment encapsulated with the datagram

Page 7: When you connect with DHCP, you are assigned a

IP is the narrow-waist

Everything over IP, IP over everything

Page 8: When you connect with DHCP, you are assigned a

Which service does nonpersistent HTTP use?

UDP? TCP?