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 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#

If client starts earlier than server for a TCP connection: I don't know when server starts, we can have business as usual client gets stuck

If client starts earlier than server for a UDP connection: I don't know when server starts, we can have business as usual client gets stuck

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

IP is the narrow-waist Everything over IP, IP over everything

Which service does nonpersistent HTTP use? UDP? TCP?