Internet Exchange Points (IXPs)

More documents

Recommendations

Info

hosts.txt does not scale✗ Huge file (traffic and load)✗ Name collisions (name uniqueness)✗ Consistency✗ Always out of date✗ Single point of Administration✗ Did not scale well
The Domain Name Systemwas born DNS is a distributed database for holdingname to IP address (and other) information Distributed:Shares the AdministrationShares the Load Robustness and improved performanceachieved throughreplicationand caching Employs a client-server architecture A critical piece of the <strong>Internet</strong>'s infrastructure
Page 1: Internet Exchange Points (IXPs)
Page 4 and 5: What is an Exchange Point Network A
Page 6 and 7: Internet Exchange PointWhy peer? Co
Page 8 and 9: Internet Exchange PointWhy peer? Mu
Page 10 and 11: Internet Exchange PointWhy peer? So
Page 12 and 13: Faculty Qualifications—PN• ONLY
Page 14 and 15: Internet Exchange PointWhy peer? Pe
Page 16 and 17: Internet Exchange Point SolutionEve
Page 18 and 19: Why use an IXP? PEERING Shared medi
Page 20 and 21: Why use an IXP? SAVES MONEY!!! Traf
Page 22 and 23: Exchange Point DesignISP 6ISP 5 ISP
Page 24 and 25: Peering at an IXP Each participant
Page 26 and 27: Exchange Point examples LINX in Lon
Page 28 and 29: DHCP: Dynamic HostConfiguration Pro
Page 30 and 31: DHCP client-server scenarioDHCP ser
Page 32 and 33: Computers use IP addresses.Why do w
Page 36 and 37: DNS is Hierarchical.(root)/ (root)u
Page 38 and 39: DNS: iterated queriesroot name serv
Page 40 and 41: Domain Names are (almost)unlimited
Page 42 and 43: Commonly seen ResourceRecords (RRs)
Page 44 and 45: Possible results from a Query POSIT
Page 46 and 47: DNS is a Client-Serverapplication (
Page 48 and 49: Three roles in DNS RESOLVERTakes re
Page 50 and 51: ROLE 1: THE RESOLVER A piece of sof
Page 52 and 53: How do you choose whichcache(s) to
Page 54 and 55: Example: Unix resolverconfiguration
Page 56 and 57: The trailing dot# dig lboro.ac.uk.
Page 58 and 59: Understanding output from dig STATU
Page 60 and 61: DNS recordsDNS: distributed db stor
Page 62 and 63: DNS protocol, messagesName, type fi
Page 64 and 65: HTTP overviewHTTP: hypertext transf
Page 66 and 67: HTTP connectionsNonpersistent HTTP
Page 68 and 69: Nonpersistent HTTP (cont.)5. HTTP c
Page 70 and 71: Persistent HTTPNonpersistent HTTP i
Page 72 and 73: HTTP request message:general format
Page 74 and 75: Method typesHTTP/1.0 GET POST HEADa
Page 76 and 77: HTTP response messagestatus line(pr
Page 78 and 79: Trying out HTTP (client side) for y
Page 80 and 81: Cookies: keeping “state” (cont.
Page 82 and 83: User-server interaction:authorizati
Page 84 and 85:
Web caches (proxy server)Goal: sati
Page 86 and 87:
Content distribution networks(CDNs)
Page 88 and 89:
FTP(File Transfer Protocol)
Page 90 and 91:
FTP: separate control, data connect
Page 92 and 93:
E-Mail(SMTP, POP, IMAP)
Page 94 and 95:
Electronic MailMail Serversmailbox
Page 96 and 97:
Scenario: Alice sends messageto Bob
Page 98 and 99:
Try SMTP interaction foryourself: t
Page 100 and 101:
Mail message formatSMTP: protocol f
Page 102 and 103:
MIME typesContent-Type: type/subtyp
Page 104 and 105:
POP3 Short for Post Office Protocol
Page 106 and 107:
POP3 (more) and IMAPMore about POP3
Page 108 and 109:
POP3 vs IMAPWith IMAP, all your mai
Page 110 and 111:
EximExim is an open source mail tra
Page 112 and 113:
NAT: Network AddressTranslation Mot
Page 114 and 115:
Private Addresses
Page 116 and 117:
NAT: Network AddressTranslationImpl
Page 118 and 119:
NAT: Network AddressTranslation 16-
Page 120 and 121:
Provider NATs? ConsideredHarmful156
Page 122 and 123:
TURN protocol Protocol for UDP/TCP
Page 124 and 125:
STUN (RFC 3489) Defines operations
Page 126 and 127:
Configuring NAT in LinuxLinux uses
Page 128 and 129:
Multimedia Networking
Page 130 and 131:
GoalsPrinciples Classify multimedia
Page 132 and 133:
Streaming stored multimedia Streami
Page 134 and 135:
Streaming live multimediaExamples:
Page 136 and 137:
A few words about audiocompression
Page 138 and 139:
Packet loss and delay Network loss:
Page 140 and 141:
How should the Internet evolveto be
Page 142 and 143:
Principles for QOS Guarantees Examp
Page 144 and 145:
Principles for QOS Guarantees Alloc
Page 146 and 147:
Summary of QoS Principles
Page 148 and 149:
Scheduling Policies: morePriority s
Page 150 and 151:
Scheduling Policies: still moreWeig
Page 152 and 153:
Diffserv ArchitectureEdge router: p
Page 154 and 155:
Classification and Conditioning Pac
Page 156 and 157:
Firewalls156
Page 158 and 159:
Firewall goals All traffic from out
Page 160 and 161:
Traditional packet filtersAnalyzes
Page 162 and 163:
Access control listsApply rules fro
Page 164 and 165:
Advantages and disadvantages oftrad
Page 166 and 167:
Firewall lab: iptables iptables Pro
Page 168 and 169:
iptables: Example commandiptables -
Page 170 and 171:
iptables Options-p protocol type (t
Page 172 and 173:
Firewall Lab: Part B Rules for outg
Page 174 and 175:
Stateful filters: example Log each
Page 176:
Demarcation Zone (DMZ)applicationga
show all

Internet Exchange Points (IXPs)

Create successful ePaper yourself

Delete template?

Save as template?