1: Introduction1 Internet History r 1961: Kleinrock - queueing theory shows effectiveness of packet- switching r 1964: Baran - packet- switching in military.

Slides:



Advertisements
Similar presentations
TA: Xifan Zheng Welcome to CPSC 441!
Advertisements

IP and Networking Basics Scalable Infrastructure Workshop AfNOG 2011.
Application Layer 2-1 Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Application Layer – Lecture.
EEC-484/584 Computer Networks Lecture 3 Wenbing Zhao (Part of the slides are based on Drs. Kurose & Ross ’ s slides for their Computer.
Application Layer-11 CSE401N: Computer Networks Lecture-4 Application Layer Overview HTTP.
Introduction1-1 Chapter 1: Introduction Our goal:  get context, overview, “feel” of networking  more depth, detail later in course  approach: m descriptive.
Introduction1-1 Introduction to Computer Networks Our goal:  get “feel” and terminology  more depth, detail later in course  approach:  use Internet.
1 Application Layer. 2 Writing Networked Applications TCP UDP IP LL PL TCP UDP IP LL PL TCP UDP IP LL PL Web Browser Web Server Ftp Server Ftp Client.
Introduction1-1 Communication Systems Lecturer Dr. Marina Kopeetsky Lecture 1: Introduction Computer Networking: A Top Down Approach Featuring the Internet,
EEC-484/584 Computer Networks Lecture 3 Wenbing Zhao (Part of the slides are based on Drs. Kurose & Ross ’ s slides for their Computer.
1: Introduction1 Protocol “Layers” Networks are complex! r many “pieces”: m hosts m routers m links of various media m applications m protocols m hardware,
EEC-484/584 Computer Networks Lecture 3 Wenbing Zhao (Part of the slides are based on Drs. Kurose & Ross ’ s slides for their Computer.
EEC-484/584 Computer Networks Lecture 3 Wenbing Zhao (Part of the slides are based on Drs. Kurose & Ross ’ s slides for their Computer.
Introduction to the Application Layer Computer Networks Computer Networks Spring 2012 Spring 2012.
2: Application Layer1 Chapter 2: Application Layer Our goals: r conceptual, implementation aspects of network application protocols m transport-layer service.
Introduction1-1 Data Communication and Networks Lecture 2 Overview (Part 2) September 16, 2004 Joseph Conron Computer Science Department New York University.
1 Computer Networks Transport Layer Protocols. 2 Application-layer Protocols Application-layer protocols –one “piece” of an app –define messages exchanged.
Introduction 1-1 Chapter 1 Introduction slides are modified from J. Kurose & K. Ross CPE 400 / 600 Computer Communication Networks.
Dr. Philip Cannata 1 Principles of Network Applications.
Introduction 1 Lecture 5 Application Layer slides are modified from J. Kurose & K. Ross University of Nevada – Reno Computer Science & Engineering Department.
1: Introduction1 Part I: Introduction Goal: r get context, overview, “feel” of networking r more depth, detail later in course r approach: m descriptive.
Chapter 2 Application Layer Computer Networking: A Top Down Approach, 5 th edition. Jim Kurose, Keith Ross Addison-Wesley, April A note on the use.
Chapter 2, slide: 1 CS 372 – introduction to computer networks* Monday June 28 Announcements: r Lab 1 is due today r Lab 2 is posted today and is due next.
2: Application Layer1 Chapter 2 Application Layer These slides derived from Computer Networking: A Top Down Approach, 6 th edition. Jim Kurose, Keith Ross.
Computer Networking Introduction, Part II.
Communications Recap Duncan Smeed. Introduction 1-2 Chapter 1: Introduction Our goal: get “feel” and terminology more depth, detail later in course.
1 Review of Important Networking Concepts Introductory material. This module uses the example from the previous module to review important networking concepts:
Throughput: Internet scenario
Application Layer 2-1 Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012.
1 Application Layer Lecture 4 Imran Ahmed University of Management & Technology.
1 CS 455/555 Intro to Networks and Communications Client/Server Computing and Socket Programming (2.1, ) Michele Weigle Department of Computer Science.
CS 381 Introduction to computer networks Chapter 1 - Lecture 4 2/10/2015.
Course info1 1 st Semester 2007 MI305 Computer Networks  Instructor: Jen-Liang Cheng   Office: H501-1( 福田樓 )  Lectures:
1 Protocol “Layers” Networks are complex! r many “pieces”: m hosts m routers m links of various media m applications m protocols m hardware, software Question:
What makes a network good? Ch 2.1: Principles of Network Apps 2: Application Layer1.
Internet Engineering Course Application Layer Protocols.
CS 381 Introduction to computer networks Lecture 2 1/29/2015.
Introduction 1-1 Chapter 1 Introduction Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 CS3516:
Sockets process sends/receives messages to/from its socket
CPSC 411 Tutorial TA: Fang Wang. Fang Wang 9:00am-5:00pm, Mon-Fri.
Prof. Younghee Lee 1 1 Computer Networks u Lecture 1: Introduction Prof. Younghee Lee u Some part of this teaching materials are prepared referencing the.
TCP/IP Network.
1 End-user Protocols, Services and QoS. 2 Layering: logical communication application transport network link physical application transport network link.
CS 3830 Day 6 Introduction 1-1. Announcements  Program 2 posted this afternoon (due date will be week of 9/24) Introduction 1-2.
Lecture 1: Overview of Internet Architecture Communication Networks ELEN E6761 Instructor: Javad Ghaderi Lecture Slides adapted from “Computer Networking:
Application Layer 2-1 Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012.
Internet History CS 4244: Internet Programming Dr. Eli Tilevich.
1: Introduction1 Introduction 3. 1: Introduction2 Delay in packet-switched networks packets experience delay on end-to-end path r four sources of delay.
1: Introduction1 Protocol “Layers” Networks are complex! r many “pieces”: m hosts m routers m links of various media m applications m protocols m hardware,
Welcome to CS 340 Introduction to Computer Networking.
Lecture 1: Facts of network technologies developments
@Yuan Xue A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their.
A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their original slides that accompany the.
IP and Networking Basics Scalable Infrastructure Workshop AfNOG 2012.
CSI 450 Review. Introduction What’s the Internet: “nuts and bolts” view millions of connected computing devices: hosts = end systems running network apps.
IP and Networking Basics
EEC-484/584 Computer Networks
An Aleksandar,   Accounts have been created for any students in EECS 340 who did not already have one.  Physical access to the labs has.
Protocol “Layers” Question: Networks are complex! many “pieces”: hosts
Lecture 1: Facts of network technologies developments
EEC-484/584 Computer Networks
EEC-484/584 Computer Networks
EEC-484/584 Computer Networks
Protocol “Layers” Question: Networks are complex! many “pieces”: hosts
Protocol “Layers” Question: Networks are complex! many “pieces”: hosts
Protocol “Layers” Question: Networks are complex! many “pieces”: hosts
Computer Networking.
Lecture 1: Facts of network technologies developments
Lecture 1: Facts of network technologies developments
Presentation transcript:

1: Introduction1 Internet History r 1961: Kleinrock - queueing theory shows effectiveness of packet- switching r 1964: Baran - packet- switching in military nets r 1967: ARPAnet conceived by Advanced Reearch Projects Agency r 1969: first ARPAnet node operational r 1972: m ARPAnet demonstrated publicly m NCP (Network Control Protocol) first host- host protocol m first program m ARPAnet has 15 nodes : Early packet-switching principles

1: Introduction2 Internet History r 1970: ALOHAnet satellite network in Hawaii r 1973: Metcalfe’s PhD thesis proposes Ethernet r 1974: Cerf and Kahn - architecture for interconnecting networks r late70’s: proprietary architectures: DECnet, SNA, XNA r late 70’s: switching fixed length packets (ATM precursor) r 1979: ARPAnet has 200 nodes Cerf and Kahn’s internetworking principles: m minimalism, autonomy - no internal changes required to interconnect networks m best effort service model m stateless routers m decentralized control define today’s Internet architecture : Internetworking, new and proprietary nets

1: Introduction3 Internet History r 1983: deployment of TCP/IP r 1982: smtp protocol defined r 1983: DNS defined for name-to-IP- address translation r 1985: ftp protocol defined r 1988: TCP congestion control r new national networks: Csnet, BITnet, NSFnet, Minitel r 100,000 hosts connected to confederation of networks : new protocols, a proliferation of networks

1: Introduction4 Internet History r Early 1990’s: ARPAnet decomissioned r 1991: NSF lifts restrictions on commercial use of NSFnet (decommissioned, 1995) r early 1990s: WWW m hypertext [Bush 1945, Nelson 1960’s] m HTML, http: Berners-Lee m 1994: Mosaic, later Netscape m late 1990’s: commercialization of the WWW Late 1990’s: r est. 50 million computers on Internet r est. 100 million+ users r backbone links runnning at 1 Gbps 1990’s: commercialization, the WWW

1: Introduction5 ATM: Asynchronous Transfer Mode nets Internet: r today’s de facto standard for global data networking 1980’s: r telco’s develop ATM: competing network standard for carrying high-speed voice/data r standards bodies: m ATM Forum m ITU ATM principles: r small (48 byte payload, 5 byte header) fixed length cells (like packets) m fast switching m small size good for voice r virtual-circuit network: switches maintain state for each “call” r well-defined interface between “network” and “user” (think of telephone company)

1: Introduction6 ATM layers r ATM Adaptation Layer (AAL): interface to upper layers m end-system m segmentation/rea ssembly r ATM Layer: cell switching r Physical AAL ATM physical AAL ATM physical AAL ATM physical AAL ATM physical ATM physical Where’s the application? r ATM: lower layer r functionality only r IP-over ATM: later application TCP/UDP IP application TCP/UDP IP application TCP/UDP IP application TCP/UDP IP

1: Introduction7 Summary on Introduction Covered a “ton” of material! r Internet overview r what’s a protocol? r network edge, core, access network r performance: loss, delay r layering and service models r backbones, NAPs, ISPs r history r ATM network You now hopefully have: r context, overview, “feel” of networking r more depth, detail later in course

1: Introduction8 Application Layer Goals: r conceptual + implementation aspects of network application protocols m client server paradigm m service models r learn about protocols by examining popular application-level protocols More goals r specific protocols: m http m ftp m smtp m pop m dns r programming network applications m socket programming

1: Introduction9 Applications and application-layer protocols Application: communicating, distributed processes m running in network hosts in “user space” m exchange messages to implement app m e.g., , file transfer, the Web Application-layer protocols m one “piece” of an app m define messages exchanged by apps and actions taken m user services provided by lower layer protocols application transport network data link physical application transport network data link physical application transport network data link physical

1: Introduction10 Client-server paradigm Typical network app has two pieces: client and server application transport network data link physical application transport network data link physical Client: r initiates contact with server (“speaks first”) r typically requests service from server, r e.g.: request WWW page, send Server: r provides requested service to client r e.g., sends requested WWW page, receives/stores received request reply

1: Introduction11 Application-layer protocols (cont). API: application programming interface r defines interface between application and transport layer r socket: Internet API m two processes communicate by sending data into socket, reading data out of socket Q: how does a process “identify” the other process with which it wants to communicate? m IP address of host running other process m “port number” - allows receiving host to determine to which local process the message should be delivered … lots more on this later.

1: Introduction12 What transport service does an app need? Data loss r some apps (e.g., audio) can tolerate some loss r other apps (e.g., file transfer, telnet) require 100% reliable data transfer Timing r some apps (e.g., Internet telephony, interactive games) require low delay to be “effective” Bandwidth r some apps (e.g., multimedia) require minimum amount of bandwidth to be “effective” r other apps (“elastic apps”) make use of whatever bandwidth they get

1: Introduction13 Transport service requirements of common apps Application file transfer Web documents real-time audio/video stored audio/video interactive games financial apps Data loss no loss loss-tolerant no loss Bandwidth elastic audio: 5Kb-1Mb video:10Kb-5Mb same as above few Kbps up elastic Time Sensitive no yes, 100’s msec yes, few secs yes, 100’s msec yes and no

1: Introduction14 Internet apps: their protocols and transport protocols Application remote terminal access Web file transfer streaming multimedia remote file server Internet telephony Application layer protocol smtp [RFC 821] telnet [RFC 854] http [RFC 2068] ftp [RFC 959] proprietary (e.g. RealNetworks) NSF proprietary (e.g., Vocaltec) Underlying transport protocol TCP TCP or UDP typically UDP