Layered Model and web System Architecture

Web System Architecture

ClientInternet--- web sever and application server--- database.
Web Browser

Web Server
Application server Internet Backend system

What Is TCP/IP?
The Internet Protocol, or IP, manages the routing of network transmissions from sender to receiver, along with issues related to network and computer addresses, and much more

A working understanding of where TCP/IP comes from, and what motivated its original design, can enhance ones understanding of this essential collection of protocols (often called a protocol suite)

The Origins and History of TCP/IP

In 1969, an obscure arm of the United States Department of Defense (DoD), known as the Advanced Research Projects Agency (ARPA), funded an academic research project for a special type of long-haul network, called a packet-switched network
In a packet-switched network, individual chunks of data (called packets) can take any usable path between the sender and receiver The network built as a result of this project is known as the ARPANET

TCP/IPs Design Goals

The design of the ARPANET and protocols that evolved to support it were based on the following government needs:
A desire to withstand a potential nuclear strike A desire to permit different kinds of computer systems to easily communicate with one another A need to interconnect systems across long distances

A TCP/IP Chronology
TCP/IP didnt really appear on the scene until the 1970s and early 1980s
The original Internet (notice the initial capital letter) helped establish a model for a network composed of other networks The term internetwork (notice the lack of an initial capital letter) refers to a single logical network composed of multiple physical networks, which may all be at a single physical location, or spread among multiple physical locations.

A TCP/IP Chronology
In 1983, the Defense Communications Agency (DCA), now known as the Defense Information Systems Agency, or DISA) took over operation of the ARPANET from DARPA (Defense Research Projects Agency, a.k.a. ARPA)

The Internet and TCP/IP enjoyed a series of events and firsts that ultimately resulted in the global Internet as we know it today

A TCP/IP Chronology
Here are some additional highlights of that history:
1986: The National Science Foundation (NFS) launches a long-haul, high-speed network, known as NSFNET, that creates a network backbone running at 56 Kbps. NSF also imposed a set of policies, known as the Acceptable Use Policies (AUPs) 1987: Number of hosts on the Internet breaks 10,000

1989: Number of hosts on the Internet breaks 100,000

1990: McGill University releases the Archie protocol and service, based on TCP/IP

A TCP/IP Chronology
1990: ARPANET ceases doing business under that name, and commercial, academic, government, and communications company operations begin supporting the Internet as a cooperative venture Work begins in earnest on the Hypertext Transfer Protocol (HTTP) and the notion of the Worldwide Web is born at Centre European Researche Nucleaire (CERN) 1991: The Commercial Internet Exchange (CIX), a consortium of Internet operators, system providers, and other commercial operations with Internet interests, is formed

A TCP/IP Chronology
1991: Thinking Machines Corporation releases the Wide Area Information Service (WAIS), a TCP/IP-based protocol and service University of Minnesota releases Gopher, a TCP/IP-based protocol that not only allows searching of text-based archives and other data types online, but also links all such archives together into a single virtual information universe known as Gopherspace 1992: The Internet Society (ISOC) is chartered

A TCP/IP Chronology
1993: The Internet Network Information Center (InterNIC) is chartered to manage domain names 1994: U.S. Senate and House of Representatives establish information servers on the Internet

1995: Netscape launches Netscape Navigator and begins the commercialization of the Web
1996: Microsoft launches Internet Explorer Web browser, even though Netscape dominates the Web browser marketplace

Who Owns TCP/IP?

Given that its roots are everywhere, and that its reach is unlimited, the ownership and control of TCP/IP is puzzling TCP/IP falls squarely into the public domain because its been funded with public monies since its inception

 The standards groups that are involved with TCP/IP are as follows:
Internet Society (ISOC)

Meet the Standards Groups that Manage TCP/IP

Internet Architecture Board (IAB)

Internet Engineering Task Force (IETF) Internet Research Task Force (IRTF)

Internet Societal Task Force (ISTF)

Internet Corporation for Assigned Names and Numbers (ICANN)

OSI Reference Model and TCP/IP Networking Model Layers

TCP/IP Network Access Layer

The TCP/IP Network Access layer is sometimes called the Network Interface layer
Its the layer wherein LAN technologies, such as Ethernet, token ring, and wireless media and devices, come into play Its also the layer in which WAN and connectionmanagement protocols, such as Serial Line Internet Protocol (SLIP), Point-to-Point Protocol (PPP), and X.25, come into play

TCP/IP Network Access Layer

At the Network Access layer, the Institute for Electrical and Electronic Engineers (IEEE) standards for networking apply These include the IEEE 802 family of standards, which features the following components of interest, among others:
802.1 Internetworking 802.2 Logical Link Control 802.2 Media Access Control 802.3 CSMA/CD: CSMA/CD stands for Carrier Sense Multiple Access with Collision Detection

802.5 Token Ring

TCP/IP Network Access Layer Protocols

The most important TCP/IP Network Access layer protocols include SLIP and PPP PPP is a more modern serial line protocol, which is widely used for Internet and private TCP/IP network connections PPP is protocol neutral, and may be used to simultaneously ferry a range of protocols across a single serial line connection

TCP/IP Network Access Layer Protocols

The Windows implementation of PPP supports all the major Windows protocolsnamely, TCP/IP, Internetwork Packet Exchange Sequenced Packet Exchange (IPX/SPX), and NetBIDS Enhanced User Interface (NetBEUI), along with tunneling protocols, such as Pointto-Point Tunneling Protocol (PPTP), and other Virtual Private Network (VPN) protocolsacross a single connection Other implementations add support for numerous other protocols including AppleTalk and Systems Network Architecture (SNA)to this mix

TCP/IP Internet Layer Functions

The Internet layer handles primary tasks for TCP/IP:
1. Addressing

2. Routing

Internet Layer Protocols

The primary protocols that function at the TCP/IP Internet layer include the following:
Internet Protocol (IP) Internet Control Message Protocol (ICMP) Packet Internetwork Groper(PING) Address Resolution Protocol (ARP) Reverse ARP (RARP) Bootstrap Protocol (BOOTP)

Routing Information Protocol (RIP)

Open Shortest Path First (OSPF) Border Gateway Protocol (BGP)

TCP/IP Transport Layer Functions

Devices that operate on the Internet are generically identified as hosts, so the TCP/IP Transport layer is also sometimes called the host-to-host layer because this layer involves moving data from one host to another

TCP/IP Transport Layer Protocols

There are two TCP/IP Transport layer protocols: the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP)

These two transport protocols come in two flavors: connection-oriented and connectionless, whereby TCP is connection-oriented, and UDP is connectionless

TCP/IP Application Layer

The TCP/IP Application layer is also known as the Process layer because this is where the protocol stack interfaces with applications or processes on a host machine File Transfer Protocol (FTP), Telnet, etc. represent specific TCP/IPbased protocols, and also define services for file transfer, terminal emulation, etc. The best-known TCP/IP-based services use TCP as transports, rather than UDP

But some services (Network File System, NFS) often use USP for transport

TCP/IP Application Layer

TCP/IP services depend on two elements to operate: 1. In UNIX terminology, a special listener process, called a daemon, operates on a server to handle incoming user requests for specific services 2. Each TCP/IP service has an associated port address that uses a 16-bit number to identify a specific process or service. Addresses in the range from 0 to 1024 are often called well-known port addresses and associate a specific port address with a specific service

TCP/IP Application Layer

Any daemon or listener process essentially hangs around, listening for attempts to connect on the well-known port address (or addresses) associated with its services
A well-known port address can often be changed as a configuration option, which is why you sometimes see Web Uniform Resource Locators, or URLs, that specify a different port address at the end of the 25 domain name portion of the string