ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an...
Transcript of ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an...
![Page 1: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/1.jpg)
ETSF15: Lecture 6- Transport protocols- DHCP, DNS, ICMP- Encapsulation- Real Internets
Jens A Andersson
![Page 2: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/2.jpg)
The objective of a switch?
Connects networks with same L2 protocol Selects next network for incoming frames depending on destination address.
![Page 3: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/3.jpg)
3
Routing
Routing = selection of best path to destination Router generic name for a best path selector on layer 3 Some layer 2 protocols include some form of routing
Adapt best path to dynamics in the network Based on Graph theoryE.g. Dijkstra Shortest Path First
Switching/Forwarding = select output interface and next hop based on best path
![Page 4: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/4.jpg)
4
Flooding
Incoming frames are copied out on all other ports. To break loops: All frames must have a hop counter.
Switch
![Page 5: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/5.jpg)
5
Link cost metrics
Capacity/Bit rateLoadType of networkFixedMobileWifi
LatencyEtc …
![Page 6: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/6.jpg)
6
Least-hop path
Least-hop path assumes link/edge cost is equal for all links/edgesPath with least hop is preferred
A
D
B
E
C
![Page 7: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/7.jpg)
7
Least-cost path
Adapt to different link/edge costPath with least cumulative cost is preferred
A
D
B
E
C2 3
11
3
11
![Page 8: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/8.jpg)
Network Protocol
networkprotocol
link
interface
network
application
link
interface
network
application
link
interface
network
interface
link
Sender Receiver
routernetworkprotocol
![Page 9: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/9.jpg)
One Network Protocol: IP
IP = Internet ProtocolIP used on what is called Internet.IP defines IP addresses.Data transfered in IP packets/datagrams.Connection Free datatransfer. No error detection or control.This is called ”best-effort”.
![Page 10: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/10.jpg)
10
Connection Oriented data transfer
New connectionConnection approved
Data transfer
End connectionConnection ended
![Page 11: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/11.jpg)
11
Connection Free data transfer
Data transfer
![Page 12: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/12.jpg)
Internet Protocol• Two versions in parallel: version 4 (IPv4) och version 6
(IPv6). • Incompatible• Translation needed
• IPv4 developed during 1970s. • All IPv4 addresses are allocated!
• IPv6 supports • More addresses• Realtime media transfer (built in)• Encryption and autentication (built in)
![Page 13: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/13.jpg)
13
IPv4 address structure (2)
Two parts: Network identity (net id)Host identity (host id)
One EIT IP address = 130.235.202.173
EIT network id = 130.235.200????
![Page 14: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/14.jpg)
IPv6 address structure
IPv6 addresses are 128 bits long 3.4 1038 individual addresses
010A : 1234 : E4F5 : 1003 : 4567 : BC98 : 0000 : 234116
![Page 15: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/15.jpg)
15
Check Sum (Hash Sum)
Split the bit vector into equal sized segments Calculate sum over all the segments Remove carry bits and add to the sum
Before transmissionCalculate the sum’s one complement
Send segments and the one complemented sum
![Page 16: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/16.jpg)
From IP address to MAC-adress
• Hosts have to know MAC addresses to be able to communicate on one LAN
• Find out the MAC/IP address mapping• IPv6 uses sub protocol of Neighbor Discovery Protocol
(NDP)• IPv4 uses Address Resolution Protocol (ARP)
![Page 17: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/17.jpg)
17
ARP (1)
![Page 18: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/18.jpg)
18
ARP (2)
![Page 19: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/19.jpg)
From IPv6 address to MAC address
• NDP ion stead of ARP• NDP is part of ICMPv6
• Internet Control Message Protocol• Supporting protocol for IPv6
• Neighbor-Solicitation Message corresponds to ARP request
• Neighbor-Advertisement Message corresponds to ARP reply
![Page 20: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/20.jpg)
20
Transport protocols
transport protocol
applikation protocolapplication
transport
link
phys
net
application
transport
link
phys
net
• TCP: Förbindelseorieterat• UDP: Förbindelsefritt
![Page 21: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/21.jpg)
Transport protocols
• End to end = Application to application• Indepenedent of underlaying network structures
![Page 22: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/22.jpg)
UDP
UDP = User Datagram Protocol.Connection free.”best effort”Adds only multiplexing on top of IP.
![Page 23: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/23.jpg)
TCP
TCP = Transport Control Protocol.Connection oriented.Reliable transfer.ARQ = Go-Back-NFlow control
Receiver control sender’s window size
Congestion control Requests for retransmission (= packet loss) indicates congestion Controls sender’s window size
![Page 24: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/24.jpg)
TCP Three Way Handshake
![Page 25: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/25.jpg)
TCP Connection termination
![Page 26: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/26.jpg)
TCP Half-close
![Page 27: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/27.jpg)
Addressis on transport layer
Ports addresses application.Source and destination
Well defined destination ports:80 : http (web)25 : smtp (mail)22 : ssh
Source randomly selected
![Page 28: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/28.jpg)
28
Two layered reference models
OSI model TCP/IP model
ApplicationApplicationPresentation
SessionTransport Transport
Net NetLink
IP carrying netsPhysical
![Page 29: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/29.jpg)
29
OSI model Protocol Stack (1)
ApplicationPresentation
SessionTransport
NetLinkPhys
ApplicationPresentation
SessionTransport
NetLinkPhys
LinkPhys Phys
Sender Receiver
Bridge,Switch
Data
![Page 30: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/30.jpg)
30
Switches used in a LAN
![Page 31: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/31.jpg)
31
OSI model Protocol Stack (2)
ApplicationPresentation
SessionTransport
NetLinkPhys
ApplicationPresentation
SessionTransport
NetLinkPhys
NetLink LinkPhys Phys
Sender Receiver
Router
Data
![Page 32: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/32.jpg)
32
Routers used between networks with same net protocol
IP net IP net
![Page 33: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/33.jpg)
33
OSI model Protocol Stack (3)
ApplicationPresentation
SessionTransport
NetLinkPhys
ApplicationPresentation
SessionTransport
NetLinkPhys
ApplicationP. P.S. S.T. T.
Net NetLink LinkPhys Phys
Sender ReceiverGatewayData
![Page 34: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/34.jpg)
34
Gateways used between nets with different application protocols
IP net POTS
![Page 35: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/35.jpg)
35
Internet’s protocol stack
HTTP, FTP, SMTP etc.Application
TCP UDPTransportIPNet
Ethernet, PPP, ATM etc.Link
DNS
ICMP ARP
![Page 36: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/36.jpg)
36
Encapsulation Sender Side
application AHS
transport AHSTHS
AHSTHSNHSnet
AHSTHSNHSLHSlink
11010101100011100011....phys
data
data
data
![Page 37: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/37.jpg)
37
Switch
11010101100... phys
Ethernet switchar do not change headers.
AHSTHSNHSLHS Incoming link header
To outgoing link
LHS Outgoing link header=
AHSTHSNHS
![Page 38: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/38.jpg)
38
Router
11010101100... phys
Router creates new link headerNet header basically(?) unchanged.
to next network
old headersAHSTHSNHSLHX
new headersAHSTHSNHS’LHU
![Page 39: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/39.jpg)
39
Receiver side decapsulation
application AHS
transport AHSTHS
AHSTHSNHZLHUlink
110100111011000011....phys
AHSTHSNHZnet
![Page 40: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/40.jpg)
40
ICMP
IP supporting protocolMessages
Error msgs Host unreachable Net unreachable TTL expired
Request Echo request
![Page 41: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/41.jpg)
MTU
Maximum Transmission Unit• Maximum payload size• Exemple:
• Ethernet MTU = 1500• PPP link over modem = 256/512• Gigabit Ethernet Jambo Frames = 9600• IPv4 = 65536 inkl header• IPv6 = 65536 exkl header
41
![Page 42: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/42.jpg)
42
Fragmentation
When upper layer frame is bigger than underlayingpayload to small
H1 datalayer 1
H2 H1+data dataH2layer 2
![Page 43: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/43.jpg)
43
Defragmentation
Performed by receiver
H2 H1+data dataH2layer 2
H1 datalayer 1
![Page 44: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/44.jpg)
IP fragmentation
• IPv6: only performed by original source.• IPv4: performed by routers if needed
• Defragmentation always performed by final reciever.
44
![Page 45: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/45.jpg)
What to configure
IP address Net mask (specifies network id) Default Gateway (at least one) DNS server (at least one)
Server’s ip address
Other stuff TFTP server Configuration file Executable image download
![Page 46: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/46.jpg)
Obtaining an IP address (bootp)
Bootstrap
![Page 47: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/47.jpg)
Dynamic Host Configuration Protocol (DHCP) BOOTP
Not dynamic!
DHCP IP address
Allocation from pool or static
Network maskDefault gatewayDNS server(s)
![Page 48: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/48.jpg)
48
Domain Name System (DNS)
Hierarchical name system consisting of a number of levels.Internet is divided into a number of domains, and each domain has its own name.On top goegraphical or generic root domains.Each domain contains subdomains.Relies on Domain Name Servers and resolvers (clients)
![Page 49: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/49.jpg)
49
DNS exemple
myhost.eit.lth.se
Host name
Institutionen för Elektro- och informationsteknik
Lunds TekniskaHögskola
Sweden
![Page 50: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/50.jpg)
50
From name to IP address (1)
magi.magicnet.seberga.trollnet.se
1. magi.magicnet.se ?
ns.trollnet.se
![Page 51: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/51.jpg)
51
From name to IP address (2)
berga.trollnet.semagi.magicnet.se
ns.trollnet.se x.ns.se
2. magicnet.se ?
3. Ask ns.magicnet.se
x=[a..j]
![Page 52: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/52.jpg)
52
From name to IP address (3)
berga.trollnet.semagi.magicnet.se
ns.trollnet.sens.magicnet.se
4. magi.magicnet.se ?
5. IP = 194.52.54.47
6. IP = 194.52.54.47
![Page 53: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/53.jpg)
53
Internet?
Consists of linked independent networks all running TCP/IP.”Controlled” by Internet Society (ISOC).
![Page 54: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/54.jpg)
54
Internet’s structure
Kunder ISP IX, lokal knutpunkt
![Page 55: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/55.jpg)
55
Traffic exchange, pair
![Page 56: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/56.jpg)
56
Traffic exchange, internet exchange
![Page 57: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/57.jpg)
57
The home netISP
FW + NAT(server,WLAN)
Switch
CPE Firewall Router
![Page 58: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/58.jpg)
58
Minor enterpriceISP
FW + NAT
Switch with VLAN
Hosting(DMZ)
Clients
Servers
WLAN
”Router on a stick”
![Page 59: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/59.jpg)
59
GigaLUNET
![Page 60: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/60.jpg)
60
OptoSUNET
![Page 61: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/61.jpg)
61
OptoSUNET
![Page 62: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/62.jpg)
NORDUnet
62
![Page 63: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/63.jpg)
NORDUnet NOX
63
![Page 64: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/64.jpg)
64
GLIF(Global Lambda Integrated Facility)
![Page 65: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/65.jpg)
65
Historia: Internet
1961-69 Forskning packet switching1969 ARPANET sätts i drift1971 Email uppfinns1974 Cerf & Kahn publicera spec för TCP/IP1978 TCP/IP delas upp i TCP och IP. UDP tillkommer.1983 Hela ARPANET byter till IP/TCP/UDP 1/1 09.00.
1984 ARPANET delas. MILNET tillkommer. Sammankopplas med router. DNS tas i drift.
1986 NFSNET blir ryggradsnät i USA.
1987 Första INTEROP.1990 ARPANET upphör.1991 Berners-Lee skapar WWW.1993 Webläsaren Mosaic erövrar världen
1995 NFSNET återgår till rent forskningsnät. Tillräckligt med kommersiella ryggradsnät.1996 Internet2 grundas.
![Page 66: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/66.jpg)
66
Historia: LUNET och SUNET
1956 SMIL tas i drift1970 SMIL ersätts med Univac1981-82 Sverigetäckande nät för terminaler byggs, kallas SUNET. 1982 Terminalväxelnät börjar byggas i Lund, LUNET.1982-83 Lokala termvxnät ansluts till SUNET. Nu nät för termvxnät.1984 LDC och Ehuset bygger varsitt Ethernet. 1985 Optofiber förbinder de två ethernet:en. lth.se och lu.se registreras.
1986 SUNET byggs om till DECnet.1988 Ryggradsnät (ethernet + optofiber) börjar byggas i Lund. SUNET kör IP. Lund ansluts till Internet.1991-92 SUNET uppgraderas.1992-94 Lunds termvxnät läggs ner.1994 SUNET uppgraderas.1997 Uppgradering av LUNET påbörjas.1998 SUNET-155 tas i drift.2002 Giga-SUNET tas i drift2006 GigaLUNET och OptoSUNET tas i drift
![Page 67: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/67.jpg)
ARPAnet was developed in 1968
Robert Taylor at ARPA (later DARPA) had three terminals for connecting with different sites:
“For each of these three terminals, I had three different sets of user commands. So if I was talking online with someone at S.D.C. and I wanted to talk to someone I knew at Berkeley or M.I.T. about this, I had to get up from the S.D.C. terminal, go over and log into the other terminal and get in touch with them. I said, oh, man, it's obvious what to do: If you have these three terminals, there ought to be one terminal that goes anywhere you want to go where you have interactive computing. That idea is the ARPAnet.”
67Source: http://partners.nytimes.com
![Page 68: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/68.jpg)
ARPAnet
Four Interactive Message Processors (IMP) at four universities connected with leased lines of 50 kbps.
The IMPs could store and forward messages.
The picture shows Leonard Kleinrock with the first IMP at UCLA.
68Source: http://www.lk.cs.ucla.edu
![Page 69: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/69.jpg)
ARPAnet evolution
69
![Page 70: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/70.jpg)
Telnet
Telnet was invented in 1969, and provided access to a remote terminal.
70
TELNET,klient
Terminaldriver
Network
TELNET,server
Local computer
Applications
Pseudoterminaldriver
![Page 71: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/71.jpg)
Ray Tomlinson sent the first email in 1971 between two computers in the same room. To separate a specific user on a host computer, he used the ”@” sign, which was unused onthe keyboard.
71
![Page 72: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/72.jpg)
Today, email basically works the same way:
72Source: http://www.tekguard.com
![Page 73: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/73.jpg)
File Transfer Protocol (FTP)
Another original application was FTP, which was developed in 1971, and that enabled file transfer between two host computers.
73Source: http://opcenter.cites.uiuc.edu
![Page 74: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/74.jpg)
Internet protocol
In 1973, Robert E. Kahn and Vincent Cerf at DARPA developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate with each other. The ideas were defined as the Transmission Control Protocol (TCP) protocol in 1974, where the term ”Internet” was introduced.Later, some parts of the TCP protocol were moved to the Internet protocol (IP), creating the TCP/IP protocol suite.
74
![Page 75: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/75.jpg)
Basic idea of Kahn and Cerf’s internetworking
75
Host identification (Addresses)
Forwarding of messages between networks (routing)
End-to-end reliability (error and flow control)
![Page 76: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/76.jpg)
Internet was bornThe Internet protocol suite was formalized in 1982.Jan 1 1983, all networks connected to the Internet had to use the TCP/IP protocol suite.
76
![Page 77: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/77.jpg)
1991: World Wide Web (WWW)
1984-1990: Tim Berners-Lee and his group at CERN worked on the ideas of information presentation and sharing.1990: HyperText Transfer Protocol (HTTP), HyperTextMarkup Language (HTML), a web browser, and server software were presented at CERN.1991: WWW goes public1993: Mosaic, the first public web browser was presented.
77Source: http://info.cern.ch/
![Page 78: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/78.jpg)
First web site: http://info.cern.ch
The first web site is still working. WWW is based on a simple client/server protocol HTTP, where clients send requests for pages to the server.
78
![Page 79: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/79.jpg)
1991: The Trojan Coffee room pot
The people working at the Computer Laboratory at the University of Cambridge implemented the first real-time Internet video application for their coffee pot. The application server sent real-time images of the coffee pot to the clients.
79Source: http://www.cl.cam.ac.uk/coffee/coffee.html
![Page 80: ETSF15: Lecture 6 - Transport protocols - DHCP, DNS, ICMP ... · developed the ideas of an internetwork protocol that made it possible for hosts on different networks to communicate](https://reader034.fdocuments.us/reader034/viewer/2022051607/602c94a3156d6f28d80d77c2/html5/thumbnails/80.jpg)
The rest is almost not history
1994: Pizza Hut started first online webshop 1997: AOL instant messenger 1997: Sixdegrees.com (first modern social network) 1997: Google.com 1999: Napster 2001: BitTorrent 2003: Skype 2005: YouTube 2005: Facebook.com 2008: Spotify
80