1 / 20

TCP / IP

TCP / IP. Internet protocol Suite. Where did TCP/IP come from? TCP/IP Standards Status Internet Standards Process Protocol Structure Network Interface Layer Internet Layer Transport Layer Application Layer. Core Protocols IP ARP ICMP IGMP TCP UDP APIs Windows Sockets NetBios.

lorin
Download Presentation

TCP / IP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TCP / IP Internet protocol Suite

  2. Where did TCP/IP come from? TCP/IP Standards Status Internet Standards Process Protocol Structure Network Interface Layer Internet Layer Transport Layer Application Layer Core Protocols IP ARP ICMP IGMP TCP UDP APIs Windows Sockets NetBios Topics

  3. Where did TCP/IP Come From? • Developed in the U.S. in 1969 • Developed for use on the Advanced Research Projects Agency (DARPA) network • Designed for large inter-networks spanning wide area network (WAN) links • Purpose was to provide high-speed communication network links

  4. Standards are published in Request for Comments (RFCs) Can describe network services, protocols, protocol implementations or policies Not all RFCs are standards Developed by consensus Anyone can submit an RFC Reviewed by a technical expert, task force or RFC editor TCP/IP Standards

  5. Status Required Recommended Elective Limited Use Not Recommended Internet Standards Process Proposed Standard Draft Standard Internet Standard TCP/IP Standards (continued)

  6. Protocol Structure

  7. Protocol Structure (continued) • Four Layers • Application • Host-to-Host Transport Layer • Internet Layer • Network Interface Layer • Loosely fits the 7 layer OSI model

  8. Network Interface Layer • Also called Network Access Layer • Responsible for placing/receiving packets on the network • Independent from network access method, format and medium • Encompasses the Data Link and Physical Layers of the OSI Model • Unreliability is assumed

  9. Internet Layer • Responsible for Addressing, Packaging and Routing • Equivalent to Network layer of the OSI model • Uses 4 major protocols • Internet Protocol (IP) • Address Resolution Protocol (ARP) • Internet Control Message Protocol (ICMP) • Internet Group Management Protocol (IGMP)

  10. Transport Layer • Also reffered to as Host-to-Host Transport Layer • Responsible for session and datagram communication services • Uses 2 core protocols • TCP • UDP • Provides the functionality of the Session and Transport layers of the OSI model

  11. Application Layer • Provides applications with the ability to access services of other layers • Defines protocols that applications use to exchange data • New protocols are always being developed • Some application layer protocols are • Hyper Text Transfer Protocol (HTTP) • File Transfer Protocol (FTP) • Simple Mail Transfer Protocol (SMTP) • Provides protocols for use and management of TCP/IP networks • Provides Application Programming Interfaces (APIs) for TCP/IP Applications

  12. Routable protocol for addressing and fragmentation/reassembly of packets Connectionless and unreliable datagram protocol Will always make a best effort to deliver packet Does not attempt to recover from errors If packet is to large for destination network IP will fragment original packet into smaller packets in a process known as fragmentation and reassembly Core Protocols – Internet Protocol (IP)

  13. Core Protocols – Address Resolution Protocol (ARP) • IP address must be resolved to Media Access Control (MAC) address • Uses MAC-level broadcasts to resolve • ARP Cache • ARP Process

  14. ICMP Provides troubleshooting facilities and error reporting Will send a Destination Unreachable message to the source host Not a reliable protocol Messages carried as unacknowledged IP datagrams IGMP Protocol to mangage IP multicast groups Host can join or leave group dynamically, registration accomplished using IGMP Host group can be of any size Used to query for membership Core Protocols –Internet Control Message Protocol (ICMP)Internet Group Management Protocol (IGMP)

  15. Core Protocols – TCP • Reliable connection-oriented delivery service • Data is transmitted in segments • Acknowledgement (ACK) used to verify delivery • Data is retransmitted if ACK not received • Uses byte-stream communications • Uses Ports to specify delivery locations • Uses 3 way handshake

  16. Core Protocols – UDP • Unreliable connectionless datagram service • Best-effort delivery, arrival not guaranteed • Does not recover from errors through retransmission • Used by applications that do not require an ACK • Uses ports to specify delivery address

  17. APIs – Windows Sockets • Standard interface for Windows applications • Provides services that allow applications to bind to particular port and IP address • Stream and datagram sockets • Socket is defined by a protocol and an address

  18. APIs – NetBIOS • Stands for Network Basic Input/Output System • Developed for IBM in 1983 by Sytek corp. • Session level interface and Session management/data transport protocol • NetBIOS Frames Protocol (NBFP, component of NetBEUI) • NetBIOS over TCP/IP (NetBT) • Datagrams • Sessions

  19. Where did TCP/IP come from? TCP/IP Standards Status Internet Standards Process Protocol Structure Network Interface Layer Internet Layer Transport Layer Application Layer Core Protocols IP ARP ICMP IGMP TCP UDP APIs Windows Sockets NetBios Topics covered

  20. Web References • http://www.darpa.mil/ • http://www.rfc-editor.org/

More Related