CS155b: E-Commerce Lecture 4: Jan 18, 2001 How Does the Internet Work? (continued) Acknowledgement: J. Rexford and Lessons Learned From Netscape.

Slides:



Advertisements
Similar presentations
Prentice HallHigh Performance TCP/IP Networking, Hassan-Jain Chapter 2 TCP/IP Fundamentals.
Advertisements

CCNA – Network Fundamentals
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 OSI Transport Layer Network Fundamentals – Chapter 4.
Transmission Control Protocol (TCP)
Intermediate TCP/IP TCP Operation.
UDP & TCP Where would we be without them!. UDP User Datagram Protocol.
CSE551: Computer Network Review r Network Layers r TCP/UDP r IP.
CP476 Internet Computing TCP/IP 1 Lecture 3. TCP / IP Objective: A in-step look at TCP/IP Purposes and operations Header specifications Implementations.
Lecture 5: TCP/IP OSI layers 3 (IP) and 4 (TCP/UDP) IPv4 – addresses and routing, “best-effort” service Ethernet, Appletalk, etc wrap IP packets with their.
UNIT-IV Computer Network Network Layer. Network Layer Prepared by - ROHIT KOSHTA In the seven-layer OSI model of computer networking, the network layer.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 OSI Transport Layer Network Fundamentals – Chapter 4.
CPSC156a: The Internet Co-Evolution of Technology and Society Lecture 3: September 11, 2003 Internet Basics, continued Acknowledgments: R. Wang and J.
TCP/IP Lecture Extra. TCP/IP Developed by DARPA (Defense Advanced Research Projects) TCP is a connection-oriented transport protocol that sends data as.
CPSC156a: The Internet Co-Evolution of Technology and Society Lecture 6: September 23, 2003 Introduction to Internet-based Business.
CPSC156a: The Internet Co-Evolution of Technology and Society Lecture 4: September 16, 2003 Internet Layers and “the Web”
Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Transport Protocols Slide 1 Transport Protocols.
CS335 Networking & Network Administration Tuesday, April 20, 2010.
TCP. Learning objectives Reliable Transport in TCP TCP flow and Congestion Control.
CPSC156: The Internet Co-Evolution of Technology and Society Lecture 2: January 18, 2007 Internet Basics, continued Acknowledgments: R. Wang and J. Rexford.
TCP: Software for Reliable Communication. Spring 2002Computer Networks Applications Internet: a Collection of Disparate Networks Different goals: Speed,
3-1 Transport services and protocols r provide logical communication between app processes running on different hosts r transport protocols run in end.
Transport Layer TCP and UDP IS250 Spring 2010
Figure 2-17 Relationship of layers and addresses in TCP/IP Example: web browser implementing HTTP Implemented in TCP and UDP software. HTTP uses TCP. Interface.
CS155b: E-Commerce Lecture 3: Jan. 21, 2003 How Does the Internet Work? (continued) Acknowledgements: J. Rexford and V. Ramachandran.
IP-UDP-RTP Computer Networking (In Chap 3, 4, 7) 건국대학교 인터넷미디어공학부 임 창 훈.
Gursharan Singh Tatla Transport Layer 16-May
What Can IP Do? Deliver datagrams to hosts – The IP address in a datagram header identify a host IP treats a computer as an endpoint of communication Best.
Process-to-Process Delivery:
TRANSPORT LAYER T.Najah Al-Subaie Kingdom of Saudi Arabia Prince Norah bint Abdul Rahman University College of Computer Since and Information System NET331.
1 Transport Layer Computer Networks. 2 Where are we?
G64INC Introduction to Network Communications Ho Sooi Hock Internet Protocol.
Presentation on Osi & TCP/IP MODEL
What is a Protocol A set of definitions and rules defining the method by which data is transferred between two or more entities or systems. The key elements.
1 Chapter Overview TCP/IP DoD model. 2 Network Layer Protocols Responsible for end-to-end communications on an internetwork Contrast with data-link layer.
1 Chapter 1 OSI Architecture The OSI 7-layer Model OSI – Open Systems Interconnection.
TCP/IP Essentials A Lab-Based Approach Shivendra Panwar, Shiwen Mao Jeong-dong Ryoo, and Yihan Li Chapter 5 UDP and Its Applications.
Chapter 5 Transport layer With special emphasis on Transmission Control Protocol (TCP)
CPSC156: The Internet Co-Evolution of Technology and Society Lecture 3: January 23, 2007 More about Internet Layers and “the Web”
Introduction to Networks CS587x Lecture 1 Department of Computer Science Iowa State University.
Chap 9 TCP/IP Andres, Wen-Yuan Liao Department of Computer Science and Engineering De Lin Institute of Technology
TCP : Transmission Control Protocol Computer Network System Sirak Kaewjamnong.
Fundamentals of Computer Networks ECE 478/578 Lecture #19: Transport Layer Instructor: Loukas Lazos Dept of Electrical and Computer Engineering University.
1 The Internet and Networked Multimedia. 2 Layering  Internet protocols are designed to work in layers, with each layer building on the facilities provided.
TCP1 Transmission Control Protocol (TCP). TCP2 Outline Transmission Control Protocol.
CCNA 1 v3.0 Module 11 TCP/IP Transport and Application Layers.
Dr. John P. Abraham Professor UTPA
Internetworking Internet: A network among networks, or a network of networks Allows accommodation of multiple network technologies Universal Service Routers.
Internetworking Internet: A network among networks, or a network of networks Allows accommodation of multiple network technologies Universal Service Routers.
Internet 1) Internet basic concepts 2) The IP protocol stack 3) The IP datagram header (IPv4 and IPv6) 4) Addressing and routing 5) Example: downloading.
Network Protocols n ISO OSI 7-layer model n TCP/IP suite l TCP/UDP l IP l Ethernet/Token Ring l ICMP.
Networking Basics CCNA 1 Chapter 11.
Chapter 24 Transport Control Protocol (TCP) Layer 4 protocol Responsible for reliable end-to-end transmission Provides illusion of reliable network to.
CSC 600 Internetworking with TCP/IP Unit 5: IP, IP Routing, and ICMP (ch. 7, ch. 8, ch. 9, ch. 10) Dr. Cheer-Sun Yang Spring 2001.
Transport Protocols.
1 Transport Layer: Basics Outline Intro to transport UDP Congestion control basics.
01_NF_Ch04 – OSI Transport Layer ( 傳輸層 ) Source: CCNA Exploration.
IP1 The Underlying Technologies. What is inside the Internet? Or What are the key underlying technologies that make it work so successfully? –Packet Switching.
Data Communications and Networks Chapter 6 – IP, UDP and TCP ICT-BVF8.1- Data Communications and Network Trainer: Dr. Abbes Sebihi.
McGraw-Hill Chapter 23 Process-to-Process Delivery: UDP, TCP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
TCP/IP1 Address Resolution Protocol Internet uses IP address to recognize a computer. But IP address needs to be translated to physical address (NIC).
Communication Networks NETW 501 Tutorial 2
1 Transmission Control Protocol (TCP) RFC: Introduction The TCP is intended to provide a reliable process-to-process communication service in a.
The Transport Layer Implementation Services Functions Protocols
Introduction to TCP/IP networking
Dr. John P. Abraham Professor UTPA
Process-to-Process Delivery:
Dr. John P. Abraham Professor UTRGV, EDINBURG, TX
Dr. John P. Abraham Professor UTPA
Net 323 D: Networks Protocols
Process-to-Process Delivery: UDP, TCP
Presentation transcript:

CS155b: E-Commerce Lecture 4: Jan 18, 2001 How Does the Internet Work? (continued) Acknowledgement: J. Rexford and Lessons Learned From Netscape

Layering in the IP Protocols Internet Protocol Transmission Control Protocol User Datagram Protocol Telnet HTTP (Web) SONETATM Ethernet Real-Time Protocol Domain Name Service

Internet Architecture ISP 1 ISP 2 ISP 3 NAP commercial customer access router gateway router dial-in access destination interdomain protocols intradomain protocols private peering

IP Connectionless Paradigm No error detection or correction for packet data –Higher-level protocol can provide error checking Successive packets may not follow the same path –Not a problem as long as packets reach the destination Packets can be delivered out-of-order –Receiver can put packets back in order (if necessary) Packets may be lost or arbitrarily delayed –Sender can send the packets again (if desired) No network congestion control (beyond “drop”) –Send can slow down in response to loss or delay

IP Packet Structure 4-bit Version 4-bit Header Length 8-bit Type of Service (TOS) 16-bit Total Length (Bytes) 16-bit Identification 3-bit Flags 13-bit Fragment Offset 8-bit Time to Live (TTL) 8-bit Protocol 16-bit Header Checksum 32-bit Source IP Address 32-bit Destination IP Address Options (if any) Payload 20-byteHeader

Main IP Header Fields Version number (e.g., version 4, version 6) Header length (number of 4-byte words) Header checksum (error check on header) Source and destination IP addresses Upper-level protocol (e.g., TCP, UDP) Length in bytes (up to 65,535 bytes) IP options (security, routing, timestamping, etc.)

Time-to-Live Field Potential robustness problem –What happens if a packet gets stuck in a routing loop? –What happens if the packet arrives much later? Time-to-live field in packet header –TTL field decremented by each router on the path –Packet is discarded when TTL field reaches 0 –Discard generates “timer expired” message to source Expiry message exploited in traceroute tool –Generate packets with TTL of i=1, 2, 3, 4, … –Extract router id from the “timer expired” message –Provides a way to gauge the path to destination

Type-of-Service Bits Initially, envisioned for type-of-service routing –Low-delay, high-throughput, high-reliability, etc. –However, current IP routing protocols are static –And, most routers have first-in-first-out queuing –So, the ToS bits are ignored in most routers today Now, heated debate for differentiated services –ToS bits used to define a small number of classes –Affect router packet scheduling and buffering polices –Arguments about consistent meaning across networks

Transmission Control Protocol (TCP) Byte-stream socket abstraction for applications Retransmission of lost or corrupted packets Flow-control to respond to network congestion Simultaneous transmission in both directions Multiplexing of multiple logical connections sourcenetworkdestination TCP connection

TCP Header 16-bit destination port number 32-bit sequence number 32-bit acknowledgement number 16-bit TCP checksum Options (if any) Payload 20-byteHeader 16-bit source port number 16-bit window size 4-bit header length FINFIN SYNSYN RSTRST PSHPSH ACKACK URGURG 16-bit urgent pointer

Establishing a TCP Connection Three-way handshake to establish connection –Host A sends a SYN (open) to the host B –Host B returns a SYN acknowledgement (ACK) –Host A sends an ACK to acknowledge the SYN ACK Closing the connection –Finish (FIN) to close and receive remaining bytes (and other host sends a FIN ACK to acknowledge) –Reset (RST) to close and not receive remaining bytes SYN SYN ACK ACK Data FIN FIN ACK ACK time A B

Lost and Corrupted Packets Detecting corrupted and lost packets –Error detection via checksum on header and data –Sender sends packet, sets timeout, and waits for ACK –Receiver sends ACKs for received packets Retransmission from sender –Sender retransmits lost/corrupted packets –Receiver reassembles and reorders packets –Receiver discards corrupted and duplicated packets Packet loss rates are high (e.g., 10%), causing significant delay (especially for short Web transfers)!

TCP Flow Control Packet loss used to indicate network congestion –Router drop packets when buffers are (nearly) full –Affected TCP connection reacts by backing-off Window-based flow control –Sender limits number of outstanding bytes –Sender reduces window size when packets are lost –Initial slow-start phase to learn a good window size TCP flow-control header fields –Window size (maximum # of outstanding bytes) –Sequence number (byte offset from starting #) –Acknowledgement number (cumulative bytes)

User Datagram Protocol (UDP) Some applications do not want or need TCP –Don’t need recovery from lost or corrupted packets –Don’t want flow control to respond to loss/congestion Amount of UDP packets is rapidly increasing –Commonly used for multimedia applications –UDP traffic interferes with TCP performance –But, many firewalls do not accept UDP packets Dealing with the growth in UDP traffic –Pressure for applications to apply flow control –Future routers may enforce “TCP-like” behavior –Need better mathematical models of TCP behavior

Classless Inter-Domain Routing (CIDR) IP addresses are all 32 bits in length –“Dotted-decimal” notation: –IP address has “network” part and “host” part Addresses used to have a natural network length –Class A: 8-bit network and 24-bit host part –Class B: 16-bit network and 16-bit host part –Class C: 24-bit network and 8-bit host part Now any division of the 32 bits is fine –Arbitrary division into prefix and mask –E.g.: /24 for mask of

Getting an IP Packet From A to B Host must know at least three IP addresses –Host IP address (to use as its own source address) –Domain Name Service (to map names to addresses) –Default router to reach other hosts (e.g., gateway) Simple customer/company –Connected to a single service provider –Has just one router connecting to the provider –Has a set of IP addresses allocated in advance –Does not run an Internet routing protocol

Open Shortest-Path First (OSPF) Routing Network is a graph with routers and links –Each unidirectional link has a weight (1-63,535) –Shortest-path routes from sum of link weights Weights are assigned statically (configuration file) –Weights based on capacity, distance, and traffic –Flooding of info about weights and IP addresses Large networks can be divided in multiple domains

Example Network and Shortest Path link router OSPF domain / /24, / /24, / /24

IP Routing in OSPF Each router has a complete view of the topology –Each router transmits information about its links –Reliable flooding to all routers in the domain –Updates periodically or on link failure/installation Each router computes shortest path(s) –Maintenance of a complete link-state database –Execution of Dijkstra’s shortest-path algorithm Each router constructs a forwarding table –Forwarding table with next hop for each destination –Hop-by-hop routing independently by each router

Routing Software Routing protocol software –Checking connection with neighboring routers (“hello”) –Exchanging link-state information with other routers –Computing shortest paths and IP forwarding table –Handling of packets with IP options selected –Exchanging routing information between providers Router management and configuration –Configuration files to configure addresses, routing, etc. –Command-line interface to inspect/change configuration –Logging of statistics in management information base –More complex traffic measurement (e.g., NetFlow)

Connecting to Other Networks AOL Autonomous System (AS) EarthLink Autonomous System (AS) WorldNet Autonomous System: A collection of IP subnets and routers under the same administrative authority. under the same administrative authority. Interior Routing Protocol (e.g., Open Shortest Path First) Exterior Routing Protocol (e.g., Border Gateway Protocol)

Connecting With Our Neighbors Public peering –Network Access Points (e.g., MAE East, MAE West) –Public location for connecting routers –Routers exchange data and routing information Private peering –Private connections between two peers (e.g., MCI) –Private peers exchange direct traffic (no transit) –Private peers must exchange similar traffic volumes Transit networks –Provider pays another for transit service (e.g., BBN) –Improve performance and reach more addresses

Application FTPHTTPNFS Transport TCPUDP Internet IP Host-to-network Ethernet ATM Application Presentation Session Transport Network Data link Physical TCP/IP model OSI model HTTP  Standard protocol for web transfer  Request-response interaction  Request methods: GET, HEAD, PUT, POST, DELETE, …  Response: Status line + additional info (e.g., a web page)

HTML  The language in which web pages are written  Contains formatting commands  Tells browser what to display & how to display Welcome to Yale - The head of this page is “Welcome to Yale” Great News! - Set “Great News!” in boldface Yale Computer Science Department -A link pointing to the web page: “ -with the text: “Yale Computer Science Department” displayed.

httpwww.cs.yale.eduindex.html ProtocolHost domain name Local file What does “ mean?

 Late 1990: WWW, HTTP, HTML, “Browser” invented by Tim Berners-Lee  Mid-1994: Mosaic Communications founded (later renamed to Netscape Communications)  Summer of 1995: Market share 80%+  August 1995: Windows 95 released with Internet Explorer  January 1998: Netscape announced that its browser would thereafter be free; the development of the browser would move to an open-source process

% 80% 60% 40% 20% Estimated Market Share of Netscape NOTE: data are from different sources and not exact Nov 1998: AOL buys Netscape

Perfectly Captures the Essence of Internet Business Enormous power of Internet architecture and ethos (e.g., layering, “stupid network,” open standards) Must bring new technology to market quickly to build market share Internet is the distribution channel –First via FTP, then via HTTP (using Netscape!) –Downloadable version available free and CD version sold

Uses Many “Internet Business Models” (esp. those that involve making money by “giving away” an information product) Complementary products (esp. server code) Bundling –Communicator includes browser, tool, collaboration tool, calendar and scheduling tool, etc. One “learning curve,” integration, compatibility, etc. Usage monitoring –Datamining, strategic alliances –“Installed base” = “Active installed base”

Browser as “Soul of the Internet” “New layer” (Note Internet architectural triumph!) Portal business –Early “electronic marketplace” –Necessity of strategic alliances –“Positive transfers” to customers (Temporarily?) Killed R&D efforts in user interfaces

Pluses and Minuses of Network Effects + Initial “Metcalf’s Law”- based boom + Initial boom accelerated by bundling, complementary products, etc. - Market share = lock in high market cap = high switching costs - Network effects strong for “browser” but weak for any particular browser

Exposed the True Nature of Microsoft 1995: Navigator released, MS rushes IE to market 1996: Version 3.0 of IE no longer technically inferior (“Openness” and standardization begets commoditization) MS exploits advantage with strategic allies (Windows!) –Contracts with ISPs to make IE the default –Incents OEMs not to load Netscape products –Exclusive access to premium content (from, e.g., Star Trek) 1998: MS halts browser-based version of these “strategies” under DoJ scrutiny of its contracts with ISPs.

Internet-ERA Anti-Trust Questions are Still Open Can consumers benefit from full integration of browser and OS? How to prevent “pre-emptive strikes” on potential competitors in the Windows- monopoly universe? –(“post-desktop era” technical Solution?) Remember: DoJ case is not about protecting Netscape!