Which of the following are application layer protocols

System Administration Guide: IP Services

The application layer defines standard Internet services and network applications that anyone can use. These services work with the transport layer to send and receive data. Many application layer protocols exist. The following list shows examples of application layer protocols:

• Standard TCP/IP services such as the ftp, tftp, and telnet commands

• UNIX “r” commands, such as rlogin and rsh

• Name services, such as NIS and the domain name system (DNS)

• Directory services (LDAP)

• File services, such as the NFS service

• Simple Network Management Protocol (SNMP), which enables network management

• Router Discovery Server protocol (RDISC) and Routing Information Protocol (RIP) routing protocols

Standard TCP/IP Services

• FTP and Anonymous FTP – The File Transfer Protocol (FTP) transfers files to and from a remote network. The protocol includes the ftp command and the in.ftpd daemon. FTP enables a user to specify the name of the remote host and file transfer command options on the local host's command line. The in.ftpd daemon on the remote host then handles the requests from the local host. Unlike rcp, ftp works even when the remote computer does not run a UNIX based operating system. A user must log in to the remote system to make an ftp connection, unless the remote system has been configured to allow anonymous FTP.

  You can obtain an enormous amount of material from anonymous FTP servers that are connected to the Internet. Universities and other institutions set up these servers to offer software, research papers, and other information to the public domain. When you log in to this type of server, you use the login name anonymous, hence the term “anonymous FTP server.”

  Using anonymous FTP and setting up anonymous FTP servers is outside the scope of this manual. However, many books, such as The Whole Internet User's Guide & Catalog, discuss anonymous FTP in detail. Instructions for using FTP are in System Administration Guide: Network Services. The ftp(1) man page describes all ftp command options that are invoked through the command interpreter. The ftpd(1M) man page describes the services that are provided by the in.ftpd daemon.

• Telnet – The Telnet protocol enables terminals and terminal-oriented processes to communicate on a network that runs TCP/IP. This protocol is implemented as the telnet program on local systems and the in.telnetd daemon on remote machines. Telnet provides a user interface through which two hosts can communicate on a character-by-character or line-by-line basis. Telnet includes a set of commands that are fully documented in the telnet(1) man page.

• TFTP – The Trivial File Transfer Protocol (tftp) provides functions that are similar to ftp, but the protocol does not establish ftp's interactive connection. As a result, users cannot list the contents of a directory or change directories. A user must know the full name of the file to be copied. The tftp(1)man page describes the tftp command set.

UNIX “r” Commands

The UNIX “r” commands enable users to issue commands on their local machines that run on the remote host. These commands include the following:

Instructions for using these commands are in the rcp(1), rlogin(1), and rsh(1) man pages.

Name Services

Oracle Solaris provides the following name services:

• DNS – The domain name system (DNS) is the name service provided by the Internet for TCP/IP networks. DNS provides host names to the IP address service. DNS also serves as a database for mail administration. For a complete description of this service, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP). See also the resolver(3RESOLV) man page.

• /etc files – The original host-based UNIX name system was developed for standalone UNIX machines and then adapted for network use. Many old UNIX operating systems and computers still use this system, but it is not well suited for large complex networks.

• NIS – Network Information Service (NIS) was developed independently of DNS and has a slightly different focus. Whereas DNS focuses on making communication simpler by using machine names instead of numerical IP addresses, NIS focuses on making network administration more manageable by providing centralized control over a variety of network information. NIS stores information about machine names and addresses, users, the network itself, and network services. NIS name space information is stored in NIS maps. For more information on NIS Architecture and NIS Administration, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

Directory Service

Oracle Solaris supports LDAP (Lightweight Directory Access Protocol) in conjunction with the Sun Open Net Environment (Sun ONE) Directory Server, as well as other LDAP directory servers. The distinction between a name service and a directory service is in the differing extent of functionality. A directory service provides the same functionality of a naming service, but provides additional functionalities as well. See System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

File Services

The NFS application layer protocol provides file services for Oracle Solaris. You can find complete information about the NFS service in System Administration Guide: Network Services.

Network Administration

The Simple Network Management Protocol (SNMP) enables you to view the layout of your network and the status of key machines. SNMP also enables you to obtain complex network statistics from software that is based on a graphical user interface (GUI). Many companies offer network management packages that implement SNMP.

Routing Protocols

The Routing Information Protocol (RIP) and the Router Discovery Server Protocol (RDISC) are two available routing protocols for TCP/IP networks. For complete lists of available routing protocols for Oracle Solaris 10, refer to Table 5–1 and Table 5–2.

• © 2010, Oracle Corporation and/or its affiliates

Highest layer of a networked communication model

An application layer is an abstraction layer that specifies the shared communications protocols and interface methods used by hosts in a communications network.[1] An application layer abstraction is specified in both the Internet Protocol Suite (TCP/IP) and the OSI model.[2] Although both models use the same term for their respective highest-level layer, the detailed definitions and purposes are different.[3]

Internet protocol suite

In the Internet protocol suite, the application layer contains the communications protocols and interface methods used in process-to-process communications across an Internet Protocol (IP) computer network.[4] The application layer only standardizes communication and depends upon the underlying transport layer protocols to establish host-to-host data transfer channels and manage the data exchange in a client–server or peer-to-peer networking model.[5] Though the TCP/IP application layer does not describe specific rules or data formats that applications must consider when communicating, the original specification (in RFC 1123) does rely on and recommend the robustness principle for application design.[6][7]

OSI model

In the OSI model, the definition of the application layer is narrower in scope.[9] The OSI model defines the application layer as only the interface responsible for communicating with host-based and user-facing applications.[10] OSI then explicitly distinguishes the functionality of two additional layers, the session layer and presentation layer, as separate levels below the application layer and above the transport layer. OSI specifies a strict modular separation of functionality at these layers and provides protocol implementations for each. In contrast, the Internet Protocol Suite compiles these functions into a single layer.[10]

Sublayers

Originally the OSI model consisted of two kinds of application layer services with their related protocols.[11] These two sublayers are the common application service element (CASE) and specific application service element (SASE).[12] Generally, an application layer protocol is realized by the use of the functionality of a number of application service elements.[13] Some application service elements invoke different procedures based on the version of the session service available.[14]

CASE

The common application service element sublayer provides services for the application layer and request services from the session layer. It provides support for common application services, such as:

• ACSE (Association Control Service Element)[12]
• ROSE (Remote Operation Service Element)
• CCR (Commitment Concurrency and Recovery)
• RTSE (Reliable Transfer Service Element)

SASE

The specific application service element sublayer provides application-specific services (protocols), such as:

• FTAM (File Transfer, Access and Manager)
• VT (Virtual Terminal)
• MOTIS (Message Oriented Text Interchange Standard)
• CMIP (Common Management Information Protocol)
• JTM (Job Transfer and Manipulation)[15]
• MMS (Manufacturing Messaging Specification)
• RDA (Remote Database Access)
• DTP (Distributed Transaction Processing)

Protocols

The IETF definition document for the application layer in the Internet Protocol Suite is RFC 1123. It provided an initial set of protocols that covered the major aspects of the functionality of the early Internet:[6]

• Hypertext documents: Hypertext Transfer Protocol (HTTP)
• Remote login to hosts: Telnet, Secure Shell
• File transfer: File Transfer Protocol (FTP), Trivial File Transfer Protocol (TFTP)
• Electronic mail transport: Simple Mail Transfer Protocol (SMTP)
• Networking support: Domain Name System (DNS)
• Host initialization: BOOTP
• Remote host management: Simple Network Management Protocol (SNMP), Common Management Information Protocol over TCP (CMOT)

Examples

Additional notable application-layer protocols include the following:

• 9P, Plan 9 from Bell Labs distributed file system protocol
• AFP, Apple Filing Protocol
• APPC, Advanced Program-to-Program Communication
• AMQP, Advanced Message Queuing Protocol
• Atom Publishing Protocol
• BEEP, Block Extensible Exchange Protocol
• Bitcoin
• BitTorrent
• CFDP, Coherent File Distribution Protocol
• CoAP, Constrained Application Protocol
• DDS, Data Distribution Service
• DeviceNet
• eDonkey
• ENRP, Endpoint Handlespace Redundancy Protocol
• FastTrack (KaZaa, Grokster, iMesh)
• Finger, User Information Protocol
• Freenet
• FTAM, File Transfer Access and Management
• FTP, File Transfer Protocol
• Gemini, Gemini protocol
• Gopher, Gopher protocol
• HL7, Health Level Seven
• HTTP, Hypertext Transfer Protocol
• Hypercore, formerly dat://
• H.323, Packet-Based Multimedia Communications System
• IMAP, Internet Message Access Protocol
• IRC, Internet Relay Chat
• IPFS, InterPlanetary File System
• Kademlia
• LDAP, Lightweight Directory Access Protocol
• LPD, Line Printer Daemon Protocol
• MIME (S-MIME), Multipurpose Internet Mail Extensions and Secure MIME
• Modbus
• MQTT Protocol
• Netconf
• NFS, Network File System
• NIS, Network Information Service
• NNTP, Network News Transfer Protocol
• NTCIP, National Transportation Communications for Intelligent Transportation System Protocol
• NTP, Network Time Protocol
• OSCAR, AOL Instant Messenger Protocol
• POP, Post Office Protocol
• PNRP, Peer Name Resolution Protocol
• RDP, Remote Desktop Protocol
• RELP, Reliable Event Logging Protocol
• RFB, Remote Framebuffer Protocol
• Rlogin, Remote Login in UNIX Systems
• RPC, Remote Procedure Call
• RTMP, Real Time Messaging Protocol
• RTP, Real-time Transport Protocol
• RTPS, Real Time Publish Subscribe
• RTSP, Real Time Streaming Protocol
• SAP, Session Announcement Protocol
• SDP, Session Description Protocol
• SIP, Session Initiation Protocol
• SLP, Service Location Protocol
• SMB, Server Message Block
• SMTP, Simple Mail Transfer Protocol
• SNTP, Simple Network Time Protocol
• SSH, Secure Shell
• SSMS, Secure SMS Messaging Protocol
• TCAP, Transaction Capabilities Application Part
• TDS, Tabular Data Stream
• Tor (anonymity network)
• Tox
• TSP, Time Stamp Protocol
• VTP, Virtual Terminal Protocol
• Whois (and RWhois), Remote Directory Access Protocol
• WebDAV
• WebRTC
• WebSocket
• X.400, Message Handling Service Protocol
• X.500, Directory Access Protocol (DAP)
• XMPP, Extensible Messaging and Presence Protocol
• Z39.50
• DNS, Domain Name Services

References

1. ^ "Application Layer | Layer 7". The OSI-Model. Retrieved November 5, 2019.
2. ^ "Four Layers of TCP/IP model, Comparison and Difference between TCP/IP and OSI models". www.omnisecu.com. Retrieved November 5, 2019.
3. ^ "What is the difference between TCP/IP and IP protocol?". SearchNetworking. Retrieved November 5, 2019.
4. ^ "What is the difference between TCP/IP and IP protocol?". SearchNetworking. Retrieved November 5, 2019.
5. ^ SEO, Bradley Mitchell An MIT graduate who brings years of technical experience to articles on; computers; Networking, Wireless. "What Is Transmission Control Protocol/Internet Protocol (TCP/IP)?". Lifewire. Retrieved November 5, 2019.
6. ^ a b Robert Braden, ed. (October 1989). "RFC 1123: Requirements for Internet Hosts – Application and Support". Network Working Group of the IETF.
7. ^ "What is the Application Layer?". www.tutorialspoint.com. Retrieved November 5, 2019.
8. ^ "X.225 : Information technology – Open Systems Interconnection – Connection-oriented Session protocol: Protocol specification". Archived from the original on February 1, 2021. Retrieved November 24, 2021.
9. ^ Shaw, Keith (October 22, 2018). "The OSI model explained: How to understand (and remember) the 7 layer network model". Network World. Retrieved November 5, 2019.
10. ^ a b "What Is The OSI Model?". CloudFlare. 2019. Retrieved November 4, 2019.
11. ^ "Application Layer (Layer 7 of the OSI Model)". September 2, 2019.
12. ^ a b Hura, Gurdeep (2001). "Application Layer". Data and Computer Communications: Networking and Internetworking. CRC Press LLC. pp. 710–712. ISBN 9780849309281.
13. ^ Warrier, U.S.; Besaw, L. (April 1989). "Common Management Information Services and Protocol over TCP/IP (CMOT)". doi:10.17487/RFC1095. {{cite journal}}: Cite journal requires |journal= (help)
14. ^ Rose, Marshall T. (December 1988). "ISO presentation services on top of TCP/IP based internets".
15. ^ a former OSI standard

External links

• 
  Media related to Application layer protocols at Wikimedia Commons
• 
  Learning materials related to Application layer at Wikiversity

Retrieved from "https://en.wikipedia.org/w/index.php?title=Application_layer&oldid=1123039780"