Computer Networking
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Computer Networking

on

  • 353 views

 

Statistics

Views

Total Views
353
Views on SlideShare
353
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Computer Networking Presentation Transcript

  • 1. Computer Networking Yishay Mansour (mansour@cs.tau.ac.il) Nir Andelman (http://www.cs.tau.ac.il/~andelmni)
  • 2. Course Information
    • Lectures: Tuesday 9-12
    • Exercises: Wendsday 10-11
    Web site: http://www.cs.tau.ac.il/~andelmni/courses/comnet05/ An Engineering Approach to Computer Networking / Keshav Computer Networks / Tanenbaum Data Networks / Bertsekas and Gallager A Top-down Approach to Computer Networking / Kurouse-Ross Books:
  • 3. Practical Information Homework assignment: Mandatory Both theoretical and programming Done in pairs Grades: Final Exam: 60% February 5 and October 18 theory exercises: 20% Programming exercises: 20%
  • 4. Motivation
    • Today’s economy
      • manufacturing, distributing, and retailing goods
      • but also creating and disseminating information
        • publishing
        • banking
        • film making….
      • part of the ‘information economy’
    • Future economy is likely to be dominated by information!
  • 5. Information?
    • A representation of knowledge
    • Examples:
      • books
      • bills
      • CDs
    • Can be represented in two ways
      • analog (atoms)
      • digital (bits)
    • the Digital Revolution
      • convert information as atoms to information as bits
      • use networks to move bits around instead of atoms
  • 6. The Challenges
    • represent all types of information as bits.
    • move the bits
      • In large quantities ,
      • everywhere,
      • cheaply ,
      • Securely,
      • with quality of service,
      • … .
  • 7. Today’s Networks are complex!
      • hosts
      • routers
      • links of various media
      • applications
      • protocols
      • hardware, software
    Tomorrow’s will be even more!
  • 8. This course’s Challenge
    • To discuss this complexity in an organized way, that will make today’s computer networks (and their limitations) more comprehensive.
    • identification, and understanding relationship of complex system’s pieces.
    • Problems that are beyond a specific technology
  • 9. Early communications systems
    • I.e. telephone
    • point-to-point links
    • directly connect together the users wishing to communicate
    • use dedicated communication circuit
    • if distance between users increases beyond the length of the cable, the connection is formed by a number of sections connected end-to-end in series.
  • 10. Data Networks
    • set of interconnected nodes exchange information
    • sharing of the transmission circuits= "switching".
    • many links allow more than one path between every 2 nodes.
    • network must select an appropriate path for each required connection.
  • 11. Networking Issues - Telephone
    • Addressing - identify the end user
    • phone number 1-201-222-2673 = country code + city code + exchange + number
    • Routing - How to get from source to destination.
    • Telephone circuit switching: Based on the phone number.
    • Information Units - How is information sent
    • telephone Samples @ Fixed sampling rate. not self descriptive! have to know where and when a sample came
  • 12. Networking Issues - Internet
    • Addressing - identify the end user
    • IP addresses 132.66.48.37, Refer to a host interface = network number + host number
    • Routing- How to get from source to destination
    • Packet switching: move packets (chunks) of data among routers from source to destination independently.
    • Information Units - How is information sent.
    • Self-descriptive data: packet = data + metadata (header).
  • 13.
    • Telephone networks support a single, end-to-end quality of service but is expensive to boot
    Internet supports no quality of service but is flexible and cheap A future network will have to support a range of service qualities at a reasonable cost
  • 14. History 1961-1972: Early packet-switching principles
    • 1961: Kleinrock - queuing theory shows effectiveness of packet-switching
    • 1964: Baran - packet-switching in military networks
    • 1967: ARPAnet – conceived by Advanced Research Projects Agency
    • 1969: first ARPAnet node operational
    • 1972: ARPAnet demonstrated publicly
      • NCP (Network Control Protocol) first host-host protocol
      • first e-mail program
      • ARPAnet has 15 nodes
  • 15. History 1972-1980: Internetworking, new and proprietary nets
    • 1970: ALOHAnet satellite network in Hawaii
    • 1973: Metcalfe’s PhD thesis proposes Ethernet
    • 1974: Cerf and Kahn - architecture for interconnecting networks
    • late70’s: proprietary architectures: DECnet, SNA, XNA
    • late 70’s: switching fixed length packets (ATM precursor)
    • 1979: ARPAnet has 200 nodes
  • 16. Cerf and Kahn’s internetworking principles:
      • minimalism, autonomy - no internal changes required to interconnect networks
      • best effort service model
      • stateless routers
      • decentralized control
    Defines today’s Internet architecture
  • 17. History 1980-1990: new protocols, proliferation of networks
    • 1983: deployment of TCP/IP
    • 1982: SMTP e-mail protocol defined
    • 1983: DNS defined for name-to-IP-address translation
    • 1985: FTP protocol defined
    • 1988: TCP congestion control
    • new national networks: CSnet, BITnet, NSFnet, Minitel
    • 100,000 hosts connected to confederation of networks
  • 18. History 1990 - : commercialization and WWW
    • early 1990’s: ARPAnet decomissioned
    • 1991: NSF lifts restrictions on commercial use of NSFnet (decommissioned, 1995)
    • early 1990s: WWW
      • hypertext [Bush 1945, Nelson 1960’s]
      • HTML, http: Berners-Lee
      • 1994: Mosaic, later Netscape
      • late 1990’s: commercialization of WWW
  • 19. Demand and Supply
    • Huge growth in users
      • The introduction of the web
    • Faster home access
      • Better user experience.
    • Infrastructure
      • Significant portion of telecommunication.
    • New evolving industries
      • Although, sometimes temporary setbacks
  • 20. Internet: Users
  • 21. Users around the Globe (2002)
  • 22. Users around the Globe (2005)
  • 23. Users around the Globe (2005)
  • 24. Technology: Modem speed
  • 25. Today’s options
    • Modem: 56 K
    • ISDN: 64K – 128K
    • Frame Relay: 56K ++
    • Today High Speed Connections
      • All are available at 5Mb (2005)
      • Cable, ADSL, Satellite.
  • 26. Coming soon:
  • 27. Today
  • 28. Protocol Layers
    • A way for organizing structure of network
    • The idea: a series of steps
    • … Or at least our discussion of networks
  • 29. JFK Transport Handling Routing To: Yishay From: Vered Haifa TLV BGN To: Boston From: TLV Shipment 792 Pack. 3 of 3 To: Yishay From: Vered To: Boston To: Yishay From: Vered Shipment 792 Pack. 3 of 3 To: Boston From: TLV To: Yishay From: Vered To: Yishay From: Vered Shipment 792 Pack. 3 of 3 Shipment 792 Pack. 2 of 3 Shipment 792 Pack. 1 of 3 To: Yishay From: Vered
  • 30. To: Yishay From: Vered To: Yishay From: Vered To: Yishay From: Vered To: Yishay From: Vered Shipment 792 Pack. 3 of 3 Shipment 792 Pack. 2 of 3 Shipment 792 Pack. 1 of 3 N.Y. Boston JFK To: Yishay From: Vered To: Yishay From: Vered Shipment 792 Pack. 3 of 3 To: Boston From: TLV To: Boston Shipment 792 Pack. 3 of 3 To: Boston From: TLV
  • 31. Layers: Person delivery of parcel Post office counter handling Ground transfer: loading on trucks Airport transfer: loading on airplane Airplane routing from source to destination
    • each layer implements a service
      • via its own internal-layer actions
      • relying on services provided by layer below
    Peer entities
  • 32. Advantages of Layering
    • explicit structure allows identification & relationship of complex system’s pieces
      • layered reference model for discussion
    • modularization eases maintenance & updating of system
      • change of implementation of layer’s service transparent to rest of system
  • 33. Protocols
    • A protocol is a set of rules and formats that govern the communication between communicating peers
      • set of valid messages
      • meaning of each message
    • Necessary for any function that requires cooperation between peers
  • 34.
    • A protocol provides a service
      • For example: the post office protocol for reliable parcel transfer service
    • Peer entities use a protocol to provide a service to a higher-level peer entity
      • for example, truck drivers use a protocol to present post offices with the abstraction of an unreliable parcel transfer service
    Protocols
  • 35. Protocol Layers
    • A network that provides many services needs many protocols
    • Some services are independent, But others depend on each other
    • A Protocol may use another protocol as a step in its execution
      • for example, ground transfer is one step in the execution of the example reliable parcel transfer protocol
    • This form of dependency is called layering
      • Post office handling is layered above parcel ground transfer protocol.
  • 36. Open protocols and systems
    • A set of protocols is open if
      • protocol details are publicly available
      • changes are managed by an organization whose membership and transactions are open to the public
    • A system that implements open protocols is called an open system
    • International Organization for Standards (ISO) prescribes a standard to connect open systems
      • open system interconnect (OSI)
    • Has greatly influenced thinking on protocol stacks
  • 37. ISO OSI reference model
    • Reference model
      • formally defines what is meant by a layer, a service etc.
    • Service architecture
      • describes the services provided by each layer and the service access point
    • Protocol architecture
      • set of protocols that implement the service architecture
      • compliant service architectures may still use non-compliant protocol architectures
  • 38. The seven Layers End system End system Intermediate system Presentation Application Session Transport Network Data Link Physical Presentation Application Session Transport Network Data Link Physical Network Data Link Physical
  • 39. The seven Layers - protocol stack data DH+data+DT bits TH Network Data Link Physical
    • Session and presentation layers are not so important, and are often ignored
    Presentation Application Session Transport Network Data Link Physical Presentation Application Session Transport Network Data Link Physical data data data data AH PH SH data NH
  • 40. Postal network
      • Application: people using the postal system
      • Session and presentation: chief clerk sends some priority mail, and some by regular mail ; translator translates letters going abroad.
      • mail clerk sends a message, retransmits if not acked
      • postal system computes a route and forwards the letters
      • datalink layer: letters carried by planes, trains, automobiles
      • physical layer: the letter itself
  • 41. Internet protocol stack
    • application: supporting network applications
      • ftp, smtp, http
    • transport: host-host data transfer
      • tcp, udp
    • network: routing of datagrams from source to destination
      • ip, routing protocols
    • link: data transfer between neighboring network elements
      • ppp, ethernet
    • physical: bits “on the wire”
    application transport network link physical
  • 42. Protocol layering and data application transport network Link physical source destination message segment datagram frame application transport network Link physical M M M M H t H t H n H t H n H l M M M M H t H t H n H t H n H l
  • 43. Physical layer
    • Moves bits between physically connected end-systems
    • Standard prescribes
      • coding scheme to represent a bit
      • shapes and sizes of connectors
      • bit-level synchronization
    • Internet
      • technology to move bits on a wire, wireless link, satellite channel etc.
  • 44. Datalink layer
    • Reliable communication over a single link.
    • Introduces the notion of a frame
      • set of bits that belong together
    • Idle markers tell us that a link is not carrying a frame
    • Begin and end markers delimit a frame
    • Internet
      • a variety of datalink layer protocols
      • most common is Ethernet
      • others are FDDI, SONET, HDLC
  • 45. Datalink layer (contd.)
    • Datalink layer protocols are the first layer of software
    • Very dependent on underlying physical link properties
    • Usually bundle both physical and datalink in hardware.
    • Ethernet (broadcast link)
      • end-system must receive only bits meant for it
      • need datalink-layer address
      • also need to decide who gets to speak next
      • these functions are provided by Medium ACcess sublayer (MAC)
  • 46. Network layer
    • Carries data from source to destination.
    • Logically concatenates a set of links to form the abstraction of an end-to-end link
    • Allows an end-system to communicate with any other end-system by computing a route between them
    • Hides idiosyncrasies of datalink layer
    • Provides unique network-wide addresses
    • Found both in end-systems and in intermediate systems
  • 47. Network layer types
    • In datagram networks
      • provides both routing and data forwarding
    • In connection-oriented network
      • separate data plane and control plane
      • data plane only forwards and schedules data (touches every byte)
      • control plane responsible for routing, call-establishment, call-teardown (doesn’t touch data bytes)
  • 48. Network layer (contd.)
    • Internet
      • network layer is provided by Internet Protocol
      • found in all end-systems and intermediate systems
      • provides abstraction of end-to-end link
      • segmentation and reassembly
      • packet-forwarding, routing, scheduling
      • unique IP addresses
      • can be layered over anything, but only best-effort service
  • 49.
    • At intermediate systems
      • participates in routing protocol to create routing tables
      • responsible for forwarding packets
      • schedules the transmission order of packets
      • chooses which packets to drop
    Network layer (contd.)
    • At end-systems
      • primarily hides details of datalink layer
      • segments and reassemble
      • detects errors
  • 50. Transport layer
    • Reliable end-to-end communication.
    • creates the abstraction of an error-controlled , flow-controlled and multiplexed end-to-end link
    • (Network layer provides only a ‘raw’ end-to-end service)
    • Some transport layers provide fewer services
      • e.g. simple error detection, no flow control, and no retransmission
    • Internet
      • TCP provides error control, flow control, multiplexing
      • UDP provides only multiplexing
  • 51. Transport layer (contd.)
    • Error control
      • GOAL: message will reach destination despite packet loss, corruption and duplication
      • ACTIONS: retransmit lost packets; detect, discard, and retransmit corrupted packets; detect and discard duplicated packets
    • Flow control
      • match transmission rate to rate currently sustainable on the path to destination, and at the destination itself
    • Multiplexes multiple applications to the same end-to-end connection
      • adds an application-specific identifier ( port number) so that receiving end-system can hand in incoming packet to the correct application
  • 52. Session layer
    • Not common
    • Provides full-duplex service, expedited data delivery, and session synchronization
    • Internet
      • doesn’t have a standard session layer
  • 53.
    • Duplex
      • if transport layer is simplex, concatenates two transport endpoints together
    • Expedited data delivery
      • allows some messages to skip ahead in end-system queues, by using a separate low-delay transport layer endpoint
    • Synchronization
      • allows users to place marks in data stream and to roll back to a prespecified mark
    Session layer (cont.)
  • 54. Presentation layer
    • Usually ad hoc
    • Touches the application data
    • (Unlike other layers which deal with headers)
    • Hides data representation differences between applications
      • characters (ASCII, unicode, EBCDIC.)
    • Can also encrypt data
    • Internet
      • no standard presentation layer
      • only defines network byte order for 2- and 4-byte integers
  • 55. Application layer
    • The set of applications that use the network
    • Doesn’t provide services to any other layer
  • 56. Discussion
    • Layers break a complex problem into smaller, simpler pieces.
    • Why seven layers?
      • Need a top and a bottom  2
      • Need to hide physical link; so need datalink  3
      • Need both end-to-end and hop-by-hop actions; so need at least the network and transport layers  5
  • 57. Course outline Multimedia and QoS 10 Distributed Algorithms 12 Network Security 11 Flow Control 9 End to End Window Based Protocols 8 Reliable Data Transfer 7 Routing 6 Switching Fabrics 5 Scheduling and Buffer Management 4 Hubs, Bridges and Routers 3 Data Link: Multi Access 2 Introduction and Layering 1