Jaringan Komputer LANJUT

D/H Topik Dalam Jaringan Komputer

Introduction
Direction: Breadth vs Depth?
Marking:
Weekly writing: 1 page critical review
Midterm Project : Issues
Final Project: Solution
Tools:
NS2, NS3, Opnet, Wireshark, PacketTracer (cisco)
Readings: IEEExplore, Kurose (Comp
Networking)
Nice to know
Network Programming
TCP/IP
Design/Addressing/subnetting
Flow control
Modeling and Simulation

4
Internet 1 (history)
Mid 1960: Papers on Packet Switching emerge.
End 1969s: ARPA sponsors the development of a packet-switching
network, called the ARPANET. First four nodes are
UCLA, SRI, U. Utah, UCSB.
1974: The TCP/IP protocols and model are being proposed by
Cerf/Kahn.
1980: IPv4 is introduced
1983: ARPANET adopts TCP/IP. At this time, the ARPANET has 200
routers.
1984: NSF funds a TCP/IP based backbone network. This
backbone grows into the NSFNET, which becomes the
successor of the ARPANET.
1995: NSF stops funding of NSFNET. The Internet is
completely commercial.
Time Line
Internet 2 (current)
Commercial
Multi owners
Client server
Ubiquitous, social network
Multi media
Cyber crime
Some TCP problems
Slow recovery
Small/tight loss probability
Confused by lossy links
Bandwith share = f(1/RTT)
Short flows last relatively longer
Tend to Fill up buffers
The Design Goals of Internet, v1
This set of goals might seem to be nothing more
than a checklist of all the desirable network
features. It is important to understand that these
goals are in order of importance, and an entirely
different network architecture would result if the
order were changed.
Interconnection/Multiplexing (packet switching)
Resilience/Survivability (fate sharing)
Heterogeneity
Different types of services
Different types of networks
Distributed management
Cost effectiveness
Ease of attachment
Accountability
These goals were prioritized for a military network.
Should priorities change as the network evolves?
Decreasing
Priority
Fundamental Goal: Interconnection
Need to interconnect many existing networks
Hide underlying technology from applications
Decisions:
Network provides minimal functionality
Narrow waist
Tradeoff: No assumptions, no guarantees.
Technology
Applications
email WWW phone...
SMTP HTTP RTP...
TCP UDP

IP

ethernet PPP
CSMA async sonet...
copper fiber radio...
The Curse of Narrow Waist
IP over anything, anything over IP
Has allowed for much innovation both above and
below the IP layer of the stack
An IP stack gets a device on the Internet

Drawback: very difficult to make changes to IP
Butpeople are trying
NSF GENI project: http://www.geni.net/
OpenFlow, SDN, Mobility First, NGN
Internet 3.0 Wish list
Energy efficient
Identity Address separation
Location aware
Client server support
Person to person communication
Security
All in band (data, control)
Isolation vs convergence
Symmetry
QOS. Anything else?