April 2013 (Summer drive) Bachelor of Computer Application (BCA) Semester 5 BC0055 TCP/IP Protocol Suite 4 Credits (Book

ook ID: B0965)

(60 Marks) Attempt all the questions:
1. Explain the architecture of the TCP/IP protocol suite. [10 marks] 2. Explain the principle of operation of REXEC protocol. [8 marks] 3. Explain the concept of multi-protocol encapsulation in ATM networks. [8 marks] 4. Bring out the differences between POP and IMAP4. [8 marks] 5. Discuss User Datagram protocol. [10 marks] 6. Explain the various steps in TCP congestion control. [10 marks] 7. Differentiate between FQDN and PQDN [6 marks] 1. Explain the architecture of the TCP/IP protocol suite. Answer : The TCP/IP protocol suite maps to a four-layer conceptual model known as the DARPA model, which was named after the U.S. government agency that initially developed TCP/IP. The four layers of the DARPA model are: Application, Transport, Internet, and Network Interface. Each layer in the DARPA model corresponds to one or more layers of the seven-layer OSI model. Figure shows the architecture of the TCP/IP protocol suite. The TCP/IP protocol suite has two sets of protocols at the Internet layer: IPv4, also known as IP, is the Internet layer in common use today on private intranets and the Internet. IPv6 is the new Internet layer that will eventually replace the existing IPv4 Internet layer.

Network Interface Layer The Network Interface Layer (also called the Network Access Layer) sends TCP/IP packets on the network medium and receives TCP/IP packets off the network medium. TCP/IP was designed to be independent of the network access method, frame format, and medium. Therefore, you can use TCP/IP to communicate across differing network types that use LAN technologies such as Ethernet and 802.11 wireless LAN and WAN technologies such as Frame Relay and Asynchronous Transfer Mode (ATM). By being independent of any specific network technology, TCP/IP can be adapted to new technologies. The Network Interface layer of the DARPA model encompasses the Data Link and Physical layers of the OSI model. The Internet layer of the DARPA model does not take advantage of sequencing and acknowledgment services that might be present in the Data Link layer of the OSI model. The Internet layer assumes an unreliable Network Interface layer and that reliable communications through session establishment and the sequencing and acknowledgment of packets is the responsibility of either the Transport layer or the Application layer. Internet Layer The Internet layer responsibilities include addressing, packaging, and routing functions. The Internet layer is analogous to the Network layer of the OSI model. The core protocols for the IPv4 Internet layer consist of the following: The Address Resolution Protocol (ARP) resolves the Internet layer address to a Network Interface layer address such as a hardware address. The Internet Protocol (IP) is a routable protocol that addresses, routes, fragments and reassembles packets. The Internet Control Message Protocol (ICMP) reports errors and other information to help you diagnose unsuccessful packet delivery. The Internet Group Management Protocol (IGMP) manages IP multicast groups. Transport Layer The Transport layer (also known as the Host-to-Host Transport layer) provides the Application layer with session and datagram communication services. The Transport layer encompasses the responsibilities of the OSI Transport layer. The core protocols of the Transport layer are TCP and UDP. TCP provides a one-to-one, connection-oriented, reliable communications service. TCP establishes

connections, sequences and acknowledges packets sent, and recovers packets lost during transmission. In contrast to TCP, UDP provides a one-to-one or one-to-many, connectionless, unreliable communications service. UDP is used when the amount of data to be transferred is small (such as the data that would fit into a single packet), when an application developer does not want the overhead associated with TCP connections, or when the applications or upper-layer protocols provide reliable delivery. TCP and UDP operate over both IPv4 and IPv6 Internet layers. Application Layer The Application layer allows applications to access the services of the other layers, and it defines the protocols that applications use to exchange data. The Application layer contains many protocols, and more are always being developed. The most widely known Application layer protocols help users exchange information: The Hypertext Transfer Protocol (HTTP) transfers files that make up pages on the World Wide Web. The File Transfer Protocol (FTP) transfers individual files, typically for an interactive user session. The Simple Mail Transfer Protocol (SMTP) transfers mail messages and attachments. Additionally, the following Application layer protocols help you use and manage TCP/IP networks: The Domain Name System (DNS) protocol resolves a host name, such a www.cisco.com, to an IP address and copies name information between DNS servers. The Routing Information Protocol (RIP) is a protocol that routers use to exchange routing information on an IP network. The Simple Network Management Protocol (SNMP) collects and exchanges network management information between a network management console and network devices such as routers, bridges, and servers. Windows Sockets and NetBIOS are examples of Application layer interfaces for TCP/IP applications

2) Explain the principle of operation of REXEC protocol. Answer: Remote Execution Command Daemon (REXECD) is a server that allows the execution of jobs submitted from a remote host over the TCP/IP network. The client uses the REXEC or Remote Shell Protocol (RSH) command to transfer the job across to the server. Any standard output or error output is sent back to the client for display or further processing. Principle of Operation REXECD is a server (or daemon). It handles commands issued by foreign hosts and transfers orders to subordinate virtual machines for job execution. The daemon performs automatic login and user authentication when a user ID and password are entered. The REXEC command is used to define the user ID, password, host address, and the process to be started on the remote host. However, RSH does not require you to send a user name and password; it uses a host access file instead. Both server and client are linked over the TCP/IP network. REXEC uses TCP port 512 and RSH uses TCP port 514.

3) Explain the concept of multi-protocol encapsulation in ATM networks. Answer: Asynchronous Transfer Mode (ATM) based networks are of increasing interest for both local and wide area applications. This memo describes two different methods for carrying connectionless network interconnect traffic, routed and bridged Protocol Data Units (PDUs), over an ATM network. The first method allows multiplexing of multiple protocols over a single ATM virtual circuit. The protocol of a carried PDU is identified by prefixing the PDU by an IEEE 802.2Logical Link Control (LLC) header. This method is in the following called "LLC Encapsulation" and a subset of it has been earlier defined for SMDS [1]. The second method does higher-layer protocol multiplexing implicitly by ATM Virtual Circuits (VCs). It is in the following called "VC Based Multiplexing".

ATM is a cell based transfer mode that requires variable length userinformation to be segmented and reassembled to/from short, fixedlength cells. This memo doesn't specify a new Segmentation AndReassembly (SAR) method for bridged and routed PDUs. Instead, thePDUs are carried in the Payload field of Common Part Convergence Sublayer (CPCS) PDU of ATM Adaptation Layer type 5 (AAL5) [2]. Note that this memo only describes how routed and bridged PDUs are carried directly over the CPCS of AAL5, i.e., when the Service Specific Convergence Sublayer (SSCS) of AAL5 is empty. If Frame 4) Bring out the differences between POP and IMAP4 Answer: The using of IMAP to access your mailbox has advantages over POP3 and the difference of their working mechanism can be summarized in the following table. POP3 Since email needs to be downloaded into desktop PC before being displayed, you may have the following problems for POP3 access:

IMAP Since email is kept on server, it would gain the following benefits for IMAP access:

You need to download all email again when using another desktop PC to check your email. May get confused if you need to check email both in the office and at home.

No need to download all email when using other desktop PC to check your email. Easier to identify the unread email.

The downloaded email may be deleted from the server depending on the setting of your

email client. All messages as well as their attachments will be downloaded into desktop PC during the 'check new email' process. Mailboxes can only be created on desktop PC. There is only one mailbox (INBOX) exists on the server. Filters can transfer incoming/outgoing messages only to local mailboxes. A whole message will be downloaded only when it is opened for display from its content. Multiple mailboxes can be created on the desktop PC as well as on the server.

Filters can transfer incoming/outgoing messages to other mailboxes no matter where the mailboxes locate (on the server or the PC). Outgoing email can be filtered to a mailbox on server for accessibility from other machine. Messages can be deleted directly on the server to make it more convenient to clean up your mailbox on the server. The occurrence of reloading messages from the server to PC is much less when compared to POP3

Outgoing email is stored only locally on the desktop PC.

Messages are deleted on the desktop PC. Comparatively, it is inconvenient to clean up your mailbox on the server. Messages may be reloaded onto desktop PC several times due to the corruption of system files.

5) Discuss User Datagram protocol. Answer: The service provided by UDP is an unreliable service that provides no guarantees for delivery and no protection from duplication (e.g. if this arises due to software errors within an Intermediate System (IS)). The simplicity of UDP reduces the overhead from using the protocol and the services may be adequate in many cases. UDP provides a minimal, unreliable, best-effort, message-passing transport to applications and upperlayer protocols. Compared to other transport protocols, UDP and its UDP-Lite variant are unique in that they do not establish end-to-end connections between communicating end systems. UDP communication consequently does not incur connection establishment and teardown overheads and there is minimal associated end system state. Because of these characteristics, UDP can offer a very efficient communication transport to some applications, but has no inherent congestion control or reliability. A second unique characteristic of UDP is that it provides no inherent On many platforms, applications can send UDP datagrams at the line rate of the link interface, which is often much greater than the available path capacity, and doing so would contribute to congestion along the path, applications therefore need to be designed responsibly [RFC 4505]. One increasingly popular use of UDP is as a tunneling protocol, where a tunnel endpoint encapsulates the packets of another protocol inside UDP datagrams and transmits them to another tunnel endpoint, which decapsulates the UDP datagrams and forwards the original packets contained in the payload. Tunnels

establish virtual links that appear to directly connect locations that are distant in the physical Internet topology, and can be used to create virtual (private) networks. Using UDP as a tunneling protocol is attractive when the payload protocol is not supported by middleboxes that may exist along the path, because many middleboxes support UDP transmissions. UDP does not provide any communications security. Applications that need to protect their communications against eavesdropping, tampering, or message forgery therefore need to separately provide security services using additional protocol mechanisms. Protocol Header A computer may send UDP packets without first establishing a connection to the recipient. A UDP datagram is carried in a single IP packet and is hence limited to a maximum payload of 65,507 bytes for IPv4 and 65,527 bytes for IPv6. The transmission of large IP packets usually requires IP fragmentation. Fragmentation decreases communication reliability and efficiency and should theerfore be avoided. To transmit a UDP datagram, a computer completes the appropriate fields in the UDP header (PCI) and forwards the data together with the header for transmission by the IP network layer.

The UDP protocol header consists of 8 bytes of Protocol Control Information (PCI) The UDP header consists of four fields each of 2 bytes in length:

Source Port (UDP packets from a client use this as a service access point (SAP) to indicate the session on the local client that originated the packet. UDP packets from a server carry the server SAP in this field) Destination Port (UDP packets from a client use this as a service access point (SAP) to indicate the service required from the remote server. UDP packets from a server carry the client SAP in this field) UDP length (The number of bytes comprising the combined UDP header information and payload data) UDP Checksum (A checksum to verify that the end to end data has not been corrupted by routers or bridges in the network or by the processing in an end system. The algorithm to compute the checksum is the Standard Internet Checksum algorithm. This allows the receiver to verify that it was the intended destination of the packet, because it covers the IP addresses, port numbers and protocol number, and it verifies that the packet is not truncated or padded, because it covers the size field. Therefore, this protects an application against receiving corrupted payload data in place of, or in addition to, the data that was sent. In the cases where this check is not required, the value of 0x0000 is placed in this field, in which case the data is not checked by the receiver.

Like for other transport protocols, the UDP header and data are not processed by Intermediate Systems (IS) in the network, and are delivered to the final destination in the same form as originally transmitted.

At the final destination, the UDP protocol layer receives packets from the IP network layer. These are checked using the checksum (when >0, this checks correct end-to-end operation of the network service) and all invalid PDUs are discarded. UDP does not make any provision for error reporting if the packets are not delivered. Valid data are passed to the appropriate session layer protocol identified by the source and destination port numbers (i.e. the session service access points). UDP and UDP-Lite also may be used for multicast and broadcast, allowing senders to transmit to multiple receivers. Using UDP Application designers are generally aware that UDP does not provide any reliability, e.g., it does not retransmit any lost packets. Often, this is a main reason to consider UDP as a transport. Applications that do require reliable message delivery therefore need to implement appropriate protocol mechanisms in their applications (e.g. tftp). UDP's best effort service does not protect against datagram duplication, i.e., an application may receive multiple copies of the same UDP datagram. Application designers therefore need to verify that their application gracefully handles datagram duplication and may need to implement mechanisms to detect duplicates. The Internet may also significantly delay some packets with respect to others, e.g., due to routing transients, intermittent connectivity, or mobility. This can cause reordering, where UDP datagrams arrive at the receiver in an order different from the transmission order. Applications that require ordered delivery must restore datagram ordering themselves. The burdon of needing to code all these protocol mechanims can be avoided by using

6) Explain the various steps in TCP congestion control Answer: The TCP/IP Protocol Suite The TCP/IP protocol suite maps to a four-layer conceptual modelknown as the DARPA model, which was named after the U.S. government agency that initiallydeveloped TCP/IP. The four layers of the DARPA model are: Application, Transport, Internet,and Network Interface. Each layer in the DARPA model corresponds to one or more layers of theseven-layer OSI model. Figure 1.2 shows the architecture of the TCP/IP protocol suite. TheTCP/IP protocol suite has two sets of protocols at the Internet layer: IPv4, also known as IP, isthe Internet layer in common use today on private intranets and the Internet. IPv6 is the newInternet layer that will eventually replace the existing IPv4 Internet layer. Network Interface Layer The Network Interface Layer (also called the Network Access Layer )sends TCP/IP packets on the network medium and receives TCP/IP packets off the network medium. TCP/IP was designed to be independent of the network access method, frame format,and medium.

Therefore, you can use TCP/IP to communicate across differing network types thatuse LAN technologies such as Ethernet and 802.11 wireless LAN and WAN technologies such as Frame Relay and Asynchronous Transfer Mode (ATM). By being independent of anyspecific network technology, TCP/IP can be adapted to new technologies. The Network Interfacelayer of the DARPA model encompasses the Data Link and Physical layers of the OSI model.The Internet layer of the DARPA model does not take advantage of sequencing andacknowledgment services that might be present in the Data Link layer of the OSI model. TheInternet layer assumes an unreliable Network Interface layer and that reliable communicationsthrough session establishment and the sequencing and acknowledgment of packets is theresponsibility of either the Transport layer or the Application layer. Internet Layer The Internet layer responsibilities include addressing, packaging, androuting functions. The Internet layer is analogous to the Network layer of the OSI model.The core protocols for the IPv4 Internet layer consist of the following:The Address Resolution Protocol (ARP) resolves the Internet layer address to a NetworkInterface layer address such as a hardware address. Sikkim Manipal University Page No. 9

7) Differentiate between FQDN and PQDN Answer: A fully qualified domain name (FQDN) is one that names both the host name and the domain name. Www.blurtit.com is an FQDN - www is the host name and blurtit.com is the domain name. If blurtit operated an FTP site it might be named ftp.blurtit.com - ftp would be the host name. I think you must be looking for the description of a "partially qualified domain name" (PQDN) as FQDNs are what the public uses. A PQDN is one that you could use if you were on the internal network of given site. For example, you are hired by blurtit to be a system administrator. When you come in to the office and pull up your browser you should be able to access their web site by simply typing "www" - just the host name. If your computer was configured correctly (of course it would be) then it would assume "blurtit.com" for the domain name and would take you to www.blurtit.com.