DOC PREVIEW
Berkeley ELENG 122 - Network Architecture

This preview shows page 1-2-16-17-18-33-34 out of 34 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

EECS 122: Introduction to Computer Networks Network ArchitectureThe ProblemSoftware ModularityNetwork ModularityOutlineLayeringISO OSI Reference Model for LayersLayering Solves ProblemOSI Model ConceptsPhysical Layer (1)Datalink Layer (2)Network Layer (3)Transport Layer (4)Session Layer (5)Presentation Layer (6)Application Layer (7)Who Does What?Logical CommunicationPhysical CommunicationEncapsulationStandards BodiesOSI vs. InternetMultiple InstantiationsMultiple Instantiations of LayersSolutionHourglassImplications of HourglassBack to RealityPlacing FunctionalityBasic ObservationExample: Reliable File TransferExample (cont’d)ConclusionSummary1Katz, Stoica F04EECS 122:Introduction to Computer NetworksNetwork ArchitectureComputer Science DivisionDepartment of Electrical Engineering and Computer SciencesUniversity of California, BerkeleyBerkeley, CA 94720-17763Katz, Stoica F04The ProblemRe-implement every application for every technology?No! But how does the Internet architecture avoid this?Telnet FTP NFSPacketradioCoaxial cableFiberopticApplicationTransmissionMediaHTTP5Katz, Stoica F04Software ModularityBreak system into modules:Well-defined interfaces gives flexibility-Change implementation of modules-Extend functionality of system by adding new modulesInterfaces hide information-Allows for flexibility-But can hurt performance6Katz, Stoica F04Network ModularityLike software modularity, but with a twist:Implementation distributed across routers and hostsMust decide:-How to break system into modules-Where modules are implementedWe will address these questions in turn7Katz, Stoica F04OutlineLayering-How to break network functionality into modulesEnd-to-End Argument-Where to implement functionality8Katz, Stoica F04LayeringLayering is a particular form of modularizationSystem is broken into a vertical hierarchy of logically distinct entities (layers)Service provided by one layer is based solely on the service provided by layer belowRigid structure: easy reuse, performance suffers9Katz, Stoica F04ISO OSI Reference Model for LayersApplicationPresentationSessionTransportNetworkDatalinkPhysical10Katz, Stoica F04Layering Solves ProblemApplication layer doesn’t know about anything below the presentation layer, etc.Information about network is hidden from higher layersEnsures that we only need to implement an application once!Caveat: not quite....11Katz, Stoica F04OSI Model ConceptsService: what a layer doesService interface: how to access the service -Interface for layer abovePeer interface (protocol): how peers communicate-Set of rules and formats that govern the communication between two network boxes-Protocol does not govern the implementation on a single machine, but how the layer is implemented between machines12Katz, Stoica F04Physical Layer (1)Service: move information between two systems connected by a physical linkInterface: specifies how to send a bit Protocol: coding scheme used to represent a bit, voltage levels, duration of a bitExamples: coaxial cable, optical fiber links; transmitters, receivers13Katz, Stoica F04Datalink Layer (2)Service: -Framing (attach frame separators) -Send data frames between peers-Others:•arbitrate the access to common physical media•per-hop reliable transmission•per-hop flow controlInterface: send a data unit (packet) to a machine connected to the same physical mediaProtocol: layer addresses, implement Medium Access Control (MAC) (e.g., CSMA/CD)…14Katz, Stoica F04Network Layer (3)Service: -Deliver a packet to specified network destination-Perform segmentation/reassemble-Others:•packet scheduling•buffer managementInterface: send a packet to a specified destinationProtocol: define global unique addresses; construct routing tables15Katz, Stoica F04Transport Layer (4)Service:-Demultiplexing-Optional: error-free and flow-controlled deliveryInterface: send message to specific destinationProtocol: implements reliability and flow controlExamples: TCP and UDP16Katz, Stoica F04Session Layer (5)Service:-Full-duplex-Access management (e.g., token control)-Synchronization (e.g., provide check points for long transfers)Interface: depends on serviceProtocol: token management; insert checkpoints, implement roll-back functions17Katz, Stoica F04Presentation Layer (6)Service: convert data between various representationsInterface: depends on serviceProtocol: define data formats, and rules to convert from one format to another18Katz, Stoica F04Application Layer (7)Service: any service provided to the end userInterface: depends on the applicationProtocol: depends on the applicationExamples: FTP, Telnet, WWW browser19Katz, Stoica F04Who Does What?Seven layers-Lower three layers are implemented everywhere-Next four layers are implemented only at hostsApplicationPresentationSessionTransportNetworkDatalinkPhysicalApplicationPresentationSessionTransportNetworkDatalinkPhysicalNetworkDatalinkPhysicalPhysical mediumHost A Host BRouter20Katz, Stoica F04Logical CommunicationLayers interacts with corresponding layer on peerApplicationPresentationSessionTransportNetworkDatalinkPhysicalApplicationPresentationSessionTransportNetworkDatalinkPhysicalNetworkDatalinkPhysicalPhysical mediumHost A Host BRouter21Katz, Stoica F04Physical CommunicationCommunication goes down to physical network, then to peer, then up to relevant layerApplicationPresentationSessionTransportNetworkDatalinkPhysicalApplicationPresentationSessionTransportNetworkDatalinkPhysicalNetworkDatalinkPhysicalPhysical mediumHost A Host BRouter22Katz, Stoica F04EncapsulationA layer can use only the service provided by the layer immediate below itEach layer may change and add a header to data packetdatadatadatadatadatadatadatadatadatadatadatadatadatadata26Katz, Stoica F04Standards BodiesISO: International Standards Organization-Professional bureaucrats writing standards-Produced OSI layering modelIETF: Internet Engineering Task Force-Started with early Internet hackers-More technical than bureaucratic“We reject kings, presidents, and voting. We believein rough consensus and running code” (David Clark) running code .27Katz, Stoica F04OSI vs. InternetOSI: conceptually define services, interfaces, protocolsInternet: provide a successful implementation ApplicationPresentationSessionTransportNetworkDatalinkPhysicalInternetNet


View Full Document

Berkeley ELENG 122 - Network Architecture

Documents in this Course
Lecture 6

Lecture 6

22 pages

Wireless

Wireless

16 pages

Links

Links

21 pages

Ethernet

Ethernet

10 pages

routing

routing

11 pages

Links

Links

7 pages

Switches

Switches

30 pages

Multicast

Multicast

36 pages

Switches

Switches

18 pages

Security

Security

16 pages

Switches

Switches

18 pages

Lecture 1

Lecture 1

56 pages

OPNET

OPNET

5 pages

Lecture 4

Lecture 4

16 pages

Ethernet

Ethernet

65 pages

Models

Models

30 pages

TCP

TCP

16 pages

Wireless

Wireless

48 pages

Load more
Download Network Architecture
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Network Architecture and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Network Architecture 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?