The Internet; Its Edge and Core

Tom Kelliher, CS 325

Jan. 28, 2011

Administrivia

Announcements

Assignment

Read 1.4-1.7.

From Last Time

Introduction

Outline

More on the Internet.
Network edge.
Network core.

Coming Up

Characteristics of packet-switched networks, and protocols.

More on the Internet

Infrastructure view:

A network of networks.
Unit of transmission: the packet.
USPS analogy. A data stream is split into discrete packets.
Connected via ``packet switches'': switches and routers.
How do packets move about the network? Store and forward; routing.

Protocols: TCP, UDP, IP.

What is a protocol?

Example SMTP protocol exchange:

bluebird:~/Class/Cs325/Lectures
% Mail -v -s "Protocol illustration" kelliher@phoenix.goucher.edu
SMTP protocol demonstration.
Cc: 
kelliher@phoenix.goucher.edu... Connecting to [127.0.0.1] via relay...
220 bluebird.goucher.edu ESMTP Sendmail 8.13.8/8.13.8; Thu, 31 Jan 2008 18:36:28 -0500
>>> EHLO bluebird.goucher.edu
250-bluebird.goucher.edu Hello bluebird.goucher.edu [127.0.0.1], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH GSSAPI DIGEST-MD5 CRAM-MD5
250-DELIVERBY
250 HELP
>>> MAIL From:<kelliher@bluebird.goucher.edu> SIZE=94 AUTH=kelliher@bluebird.goucher.edu
250 2.1.0 <kelliher@bluebird.goucher.edu>... Sender ok
>>> RCPT To:<kelliher@phoenix.goucher.edu>
>>> DATA
250 2.1.5 <kelliher@phoenix.goucher.edu>... Recipient ok
354 Enter mail, end with "." on a line by itself
>>> .
250 2.0.0 m0VNaSul003537 Message accepted for delivery
kelliher@phoenix.goucher.edu... Sent (m0VNaSul003537 Message accepted for delivery)
Closing connection to [127.0.0.1]
>>> QUIT
221 2.0.0 bluebird.goucher.edu closing connection

``Doing it yourself'' via a telnet connection to SMTP port (25).

Protocols in TCP/IP:

$\begin{figure}\centering\includegraphics[]{Figures/layers.eps}\end{figure}$

The role of ISPs.

Services view:

A foundation for distributed applications: HTTP, SMTP, SSH, DNS, POP, IMAP, etc.
Properties of the foundation (Qos, etc.)
APIs.

Network Edge

Hosts -- clients, servers.
How does peer-to-peer fit in?
Distributed applications.
Access from the edge. Residential and commercial.
1. Dial-up modems through POTS to traditional ISPs.
  Length limits bandwidth
2. DSL access.
  Phone company is ISP. Shorter link length means higher speed. Still, there's only so much bandwidth available in twisted pair.
  Dedicated access.
3. Cable modem access.
  Coaxial cable has much higher bandwidth.
  Shared broadcast.
4. Fiber to the home -- Verizon's FIOS.
  Much higher bandwidth.
5. T1 (1.544 mb/s; copper or fiber), T3 (43.232 mb/s; fiber?), OC3 (155 mb/s).
  Commercial access.
  A cable modem gives access approximately equal to a T1.
  Goucher: four T1 lines in 2002. How many today? Why doesn't Goucher just use cable modems?
6. Wireless access -- 802.11.
  Network integrity, security issues.

Network Core

Circuit switching
1. Roots in telephone service.
2. Guaranteed connection, guaranteed bandwidth.
3. Overhead for establishing the circuit.
4. Unused bandwidth for one circuit can't be used by another (waste).
5. Time division multiplexing. CPU scheduling. Slots in a frame.
6. Frequency division multiplexing. Radio broadcasts. Use a unique slice of the available bandwidth.
Packet switching
1. Roots in computer networks.
2. Best-effort service. Bottlenecks -- consider the Beltway. Leads to packet loss.
3. No overhead.
4. Dynamic allocation of bandwidth built in.
5. Store-and-forward from link to link -- no ``pipelining.''
Connectivity between ISPs.
1. Tier 1: a tier 1 ISP is connected to every other tier 1 ISP -- maximum redundancy.
  Peering.
  Connections to a large number of tier 2 ISPs (clients).
2. Tier 2: connects to a small number of tier 1 ISPs and perhaps some other tier 2 ISPs.
  Connections to a large number of tier 3 ISPs (clients).
3. Tier 3: Consumer access to the Internet.

Thomas P. Kelliher 2011-01-27

Tom Kelliher