M2PA: MTP2 Peer-to-peer user Adaptation
MTP2 Peer-to-peer user Adaptation layer (M2PA), a protocol in the SIGTRAN protocol suite, enables SS7 signaling messages over IP using Stream Control Transmission Protocol (SCTP). M2PA is intented to be used on a Peer-to-Peer basis and replace the functionality provided by a traditional SS7 link. M2PA is for an OpenSS7 Network Device.
Standard Organization: IETF
Reference Document: RFC 4165

M2UA: MTP2-User Adaptation layer
MTP2-User Adaptation layer (M2UA), a protocol in the SIGTRAN protocol suite, is for backhauling of SS7 MTP2-User signaling messages over IP using Stream Control Transmission Protocol (SCTP). M2UA is intended to be used on a Provider/User basis where MTP Level 2 resides on a Signalling Gateway (SG) and MTP Level 3 resides on an Application Server (AS). It is not intended for peer-to-peer operation: that is, it is not intended to emulate a signalling link between two SCTP endpoints
Standard Organization: IETF
Reference Document: RFC 3331

M3UA: MTP3-User Adaptation layer
MTP3-User Adaptation layer (M3UA), a protocol in the SIGTRAN protocol suite, supports transport of SS7 MTP3-User signaling over IP using Stream Control Transmission Protocol (SCTP). M3UA is intented to be used on a Provider/User basis where MTP Level 3 resides on a Signalling Gateway (SG) and MTP Users reside on an Application Server (AS).
Standard Organization: IETF
Reference Document: RFC 3332

MacIP: Macintosh Internet Protocol
Macintosh Internet Protocol (MacIP) tunnels IP datagrams inside AppleTalk for a Macintosh client communicating over an AppleTalk network to a MacIP server. The MacIP server pulls the IP packet out of the AppleTalk datagram and forwards it as Native IP. MacIP is ideal for Macs using LocalTalk or AppleTalk Remote Access (ARA) at the Data Link Layer (OSI Layer 2). These data links only support AppleTalk. By tunneling IP inside of AppleTalk packets, IP connectivity can be gained through the MacIP server.
Standard Organization: Apple

MAP: Manufacturing Automation Protocol
Manufacturing Automation Protocol (MAP) is a network architecture created by General Motors to meet the specific needs of the factory floor. MAP specifies a token-passing LAN similar to IEEE 802.4.
Standard Organization: GM

MAP: Mobile Application Part
The Mobile Application Part (MAP), one of the protocols in the SS7 suite, allows for the implementation of the mobile network (GSM) signaling infrastructure. The premise behind MAP is to connect the distributed switching elements, called mobile switching centers (MSCs), with a master database, called the Home Location Register (HLR). The HLR dynamically stores the current location and profile of a mobile network subscriber. The HLR is consulted during the processing of an incoming call.
Standard Organization: ITU-T

MAPOS: Multiple Access Protocol over SONET / SDH
Multiple Access Protocol over SONET/SDH (MAPOS) Multiple Access Protocol over SONET/SDH (MAPOS) is a protocol extension to SONET/SDH that has high performance, supports multiple access, broadcast and multicast transmission. MAPOS is connection-less, like IP, with simple design and seamless interconnectivity for LAN and WAN.
Standard Organization: ITU-T and MAPOS Org

MARS: Multicast Address Resolution Server
Multicast Address Resolution Server (MARS) is a mechanism for supporting IP multicast over an ATM network. A MARS serves a group of nodes (known as a cluster); each node in the cluster is configured with the ATM address of the MARS. The MARS supports multicast through multicast messages of overlaid point-to-multipoint connections or through multicast servers. ATM-based IP hosts and routers use a MARS to support IP multicast over the ATM Forum's UNI 3.0/3.1 point-to-multipoint connection service. Clusters of endpoints share a MARS and use it to track and disseminate information identifying the nodes listed as receivers for given multicast groups.
Standard Organization: IETF
Reference Document: RFC 2022

MATIP: Mapping of airline traffic over IP
Mapping of airline traffic over IP (MATIP) is a protocol for transporting airline reservation, ticketing, and messaging traffic over TCP/IP.
Standard Organization: IETF
Reference Document: RFC 2351

MBGP: Multiprotocol BGP
The multiprotocol BGP (MBGP) adds capabilities to BGP to enable multicast routing policy throughout the Internet and to connect multicast topologies within and between BGP autonomous systems. In other words, multiprotocol BGP (MBGP) is an enhanced BGP that carries IP multicast routes. BGP carries two sets of routes: one set for unicast routing and one set for multicast routing. The routes associated with multicast routing are used by the Protocol Independent Multicast (PIM) to build data distribution trees.
Standard Organization: IETF
Reference Document: RFC 2858

Megaco: Media Gateway Control Protocol
The Media Gateway Control Protocol (Megaco), is for the control of elements in a physically decomposed multimedia gateway, enabling the separation of call control from media conversion. The Media Gateway Control Protocol (Megaco) is a result of joint efforts of the IETF and the ITU-T Study Group 16. Therefore, the IETF-defined Megaco is the same as ITU-T Recommendation H.248.
Standard Organization: ITU-T
Reference Document: H.248

MEL CAS: Mercury Exchange Limited Channel Associated Signaling
Mercury Exchange Limited Channel Associated Signaling (MEL CAS) is a voice signaling protocol used primarily in the United Kingdom.

MFTP: Multisource File Transfer Protocol
Multisource File Transfer Protocol (MFTP) is designed for the purpose of file sharing. This is the communication protocol used by such clients as eMule and eDonkey and, in its extended implementation, by the Overnet network.

MGCP: Media Gateway Control Protocol
Media Gateway Control Protocol (MGCP) is a VOIP protocol, used between elements of a decomposed multimedia gateway, which consists of a Call Agent containing the call control "intelligence" and a media gateway containing the media functions, e.g., conversion from TDM voice to Voice over IP.
Standard Organization: Cisco/ Telcordia
Reference Document: IETF RFC 3435

MHS: Message Handling Service
Message Handling Service, defined in ISO X.400 specifications, is for email transmission specified by the ITU-T and ISO. X.400 is common in Europe and Canada and is an alternative to the more popular email protocol, Simple Mail Transfer Protocol (SMTP), which is defined by IETF. X.400 uses a binary format so it is easy to include binary contents without encoding it for transfer. Also, it is harder for people to fake email addresses and contents than with SMTP, where text messages are used.
Standard Organization: ISO
Reference Document: ISO X.400

Microsoft CIFS: Common Internet File System
The Common Internet File System (Microsoft CIFS), an enhanced version of Microsoft Server Message Block (SMB), is the standard way that computer users share files across intranets and the Internet. CIFS enables collaboration on the Internet by defining a remote file-access protocol that is compatible with the way applications already share data on local disks and network file servers. CIFS runs over TCP/IP, utilizes the Internet's global Domain Naming Service (DNS) for scalability and is optimized to support slower speed dial-up connections common on the Internet.
Standard Organization: Microsoft

Microsoft SOAP: Simple Object Access Protocol
The Simple Object Access Protocol (Microsoft SOAP) is a lightweight and simple XML-based protocol that is designed to exchange structured and typed information on the Web. SOAP can be used in combination with a variety of existing Internet protocols and formats, including Hypertext Transfer Protocol (HTTP), Simple Mail Transfer Protocol (SMTP) and Multipurpose Internet Mail Extensions (MIME), and can support a wide range of applications from messaging systems to remote procedure calls (RPCs).
Standard Organization: Microsoft

MIME: Multipurpose Internet Mail Extensions
Multipurpose Internet Mail Extensions (MIME) specifies how messages must be formatted so that they can be exchanged between different email systems. MIME is a very flexible format, permitting one to include virtually any type of file or document in an email message. MIME messages can contain text, images, audio, video, or other application-specific data.
Standard Organization: IETF
Reference Document: RFC 2049

MISTP: Multiple Instances Spanning Tree Protocol
Multiple Instances Spanning Tree Protocol (MISTP) is a Cisco standard which allows several VLANs to be mapped to a reduced number of spanning-tree instances. This is possible since most networks do not need more than a few logical topologies. Each instance handles multiple VLANs that have the same Layer 2 topology. The Multiple Spanning Tree (MST) Protocol defined in IEEE 802.1s is based on the Cisco MISTP.
Standard Organization: Cisco

MLP: Multilink Procedure
Multilink Procedure (MLP), added upper sublayer of the LAPB, operates between the packet layer and a multiplicity of single data link protocol functions (SLPs) in the data link layer (X.25).
Standard Organization: ISO
Reference Document: ISO 7776

MNG: Multiple-image Network Graphics
Multiple-image Network Graphics (MNG) is a public file format for animated images. MNG is closely related to the PNG image format as an animation-supporting version of PNG.
Standard Organization: W3C

MNP: Microcom Networking Protocol
Microcom Networking Protocol (MNP) is a type of error correcting/compression protocol. MNP were commonly used on early high-speed (2400 bit/s and higher) modems. Originally developed for use on Microcom's own family of modems, the protocol was later openly licensed and used by most of the modem industry, notably Telebit, USRobotics and Hayes. MNP was later supplanted by v.42bis, which was used almost universally on the first v.32bis modems in the early 1990s. MNP has many versions, MNP 1 to MNP 10. Each class/version generally improved performance over earlier versions, which were retained only for backward-compatibility reasons.
Standard Organization: Microcom

Mobile IP
Mobile IP is the key protocol to enable mobile computing and networking, which brings together two of the world's most powerful technologies, the Internet and mobile communication. In Mobile IP, two IP addresses are provided for each computer: home IP address which is fixed and care-of IP address which is changing as the computer moves. When the mobile moves to a new location, it must send its new address to an agent at home so that the agent can tunnel all communications to its new address timely.
Standard Organization: IETF
Reference Document: RFC 3344 and RFC 3775

MODEM7
MODEM7, also known as MODEM7 batch or Batch XMODEM, is a protocol for file transfer capable of batch transfers. MODEM7 was used only for a short time, replaced by more capable batching protocols such as YMODEM.

MOP: Maintenance Operation Protocol
Maintenance Operation Protocol(MOP), a protocol in the DECnet suite, is a utility services such as uploading and downloading system software, remote testing and problem diagnosis. For example, MOP can be used to download a system image to a diskless station.
Standard Organization: DEC/HP

MOSPF: Multicast Extensions to OSPF
Multicast Extensions to OSPF (MOSPF) provides enhancements to OSPF Version 2 to support IP multicast routing. The enhancements have been added in a backward-compatible fashion; routers running the multicast additions will interoperate with non-multicast OSPF routers when forwarding regular (unicast) IP data traffic.
Standard Organization: IETF
Reference Document: RFC 1584

MOUNT
MOUNT is a Netowrk File System protocol used to initiate client access to a server supporting NFS. The NFS mount protocol facilitates the fucntions that allow NFS clients to attach remote directory trees to a mount point in the local file system. A mount point is an empty directory or subdirectory, created as place to attache a remote file system. In order to mount a file system from an NFS server, a user needs an account on the machine where the file system resides. The NFS client passes the UID and GID of the process requesting the mount to the NFS server. The server then validates the request. Mount protocol also allows the server to grant remote access privileges to a restricted set of clients via export control.
Standard Organization: SUN
Reference Document: NFS

MP: Multilink Point-to-Point Protocol
MultiLink Point-to-Point Protocol (MultiPPP, MP or MLP), also known as PPP Multilink protocol, is a method for splitting, recombining and sequencing datagrams across multiple logical data links. This work was originally motivated by the desire to exploit multiple bearer channels in ISDN, but is equally applicable to any situation in which multiple PPP links connect two systems, including async links. MP is based on an LCP option negotiation that permits a system to indicate to its peer that it is capable of combining multiple physical links into a "bundle".
Standard Organization: IETF
Reference Document: RFC 1990

MPEG: Motion Pictures Experts Group
Motion Pictures Experts Group (MPEG) is a working group of ISO/IEC charged with the development of video and audio encoding standards. MPEG includes hundreds of members worldwide from various industries, universities, and research institutions. MPEG's official designation is ISO/IEC JTC1/SC29 WG11. MPEG has defined a group of standards over the years including MPEG-1, MPEG-2, MPEG-3, MPEG-4, MPEG-7 and MPEG-21.
Standard Organization: ISO/IEC

MPEG-1
MPEG-1 is a group of audio and video coding standards defined by Moving Picture Experts Group(MPEG). MPEG-1 video is used by the Video CD format. MPEG-1 consists of several "parts": Part 1, Synchronization and multiplexing of video and audio; Part 2, Compression codec for non-interlaced video signals; and Part 3, Compression codec for perceptual coding of audio signals. MP3 is the MPEG-1 audio layer 3 in MPEG-1 Part 3.
Standard Organization: ISO/IEC

MPEG-2
MPEG-2 is a group of coding standards for digital audio and video, agreed upon by Moving Pictures Experts Group(MPEG). MPEG-2 is typically used to encode audio and video for broadcast signals, including direct broadcast satellite and Cable TV. MPEG-2, with some modifications, is also the coding format used by standard commercial DVD movies. MPEG-2 includes a few parts: Systems part (part 1) defines Transport Stream to carry digital video and audio over somewhat-unreliable media, and are used in broadcast applications. The Video part (part 2) provides support for interlaced video. The MPEG-2 Audio part (Part 3) enhances MPEG-1's audio by allowing the coding of audio programs with more than two channels. In MPEG-2 AAC (Part 7), audio can alternatively be coded in a non-backwards-compatible way, which allows encoders to make better use of available bandwidth.
Standard Organization: ISO/IEC
Reference Document: ISO/IEC 13818

MPEG-21
The MPEG-21 standard defines an open framework for multimedia applications by Moving Picture Experts Group (MPEG). Specifically, MPEG-21 defines a "Rights Expression Language" standard as means of sharing digital rights/permissions/restrictions for digital content from content creator to content consumer. As an XML-based standard, MPEG-21 is designed to communicate machine-readable license information and do so in an "ubiquitous, unambiguous and secure" manner.
Standard Organization: ISO/IEC
Reference Document: ISO 21000

MPEG-3
MPEG-3 is a group of audio and video coding standards agreed upon by Moving Picture Experts Group(MPEG). MPEG-3 was designed to handle HDTV signals in the range of 20 to 40 Mbit/s. It was soon discovered that similar results could be obtained through slight modifications to the MPEG-2 standard. Shortly thereafter, work on MPEG-3 was discontinued.
Standard Organization: ISO/IEC

MPEG-4
MPEG-4 is a video CODEC for web (streaming media) and CD distribution, conversational (videophone), and broadcast television. MPEG-4 absorbs many of the features of MPEG-1 and MPEG-2 and other related standards, adding new features such as (extended) VRML support for 3D rendering, object-oriented composite files (including audio, video and VRML objects), support for externally-specified Digital Rights Management and various types of interactivity. MPEG-4 consists of several standardstermed "parts". Profiles are also defined within the individual "parts", so an implementation of a part is ordinarily not an implementation of an entire part.
Standard Organization: ISO/IEC

MPEG-47
MPEG-47 is a nickname of the combination of MPEG-4 and MPEG-7, which refers to use MPEG-4 to do the content CODEC and distribution and use MPEG-7 to facilidate the distribution with metadata.
Standard Organization: ISO/IEC

MPEG-7
MPEG-7 is a multimedia content description standard defined by Moving Picture Experts Group(MPEG). It is very different from other MPEG CODEC standards like MPEG-1, MPEG-2 and MPEG-4. It uses XML to store metadata, and can be attached to timecode in order to tag particular events, or synchronise lyrics to a song.
Standard Organization: ISO/IEC

MPLS: Multiprotocol Label Switching
Multiprotocol Label Switching (MPLS), an architecture for fast packet switching and routing, provides the designation, routing, forwarding and switching of traffic flows through the network. More specifically, it has mechanisms to manage traffic flows of various granularities. It is independent of the layer 2 and layer 3 protocols, such as ATM and IP. MPLS is used as the protocol for the core network for the next generation networking (NGN).
Standard Organization: IETF
Reference Document: RFC 3031

MPOA: Multi Protocol Over ATM
The Multi Protocol Over ATM (MPOA) deals with the efficient transfer of inter-subnet unicast data in a LANE environment. MPOA integrates LANE and NHRP to preserve the benefits of LAN Emulation, while allowing inter-subnet, internetwork layer protocol communication over ATM VCCs without requiring routers in the data path. MPOA provides a framework for effectively synthesizing bridging and routing with ATM in an environment of diverse protocols, network technologies and IEEE 802.1 virtual LANs.
Standard Organization: ITU-T

MPP: Multichannel Point-to-Point Protocol
Multichannel Point-to-Point Protocol (MPP) supports inverse multiplexing, session management, and bandwidth management. MPP enables the combination of up to 30 individual channels into a single high-speed connection. MPP consists of two components: a low-level channel identification, error monitoring, and error recovery mechanism, and a session management level for supporting bandwidth modifications and diagnostics. MPP enables the Ascend unit to add or remove channels from a connection as bandwidth needs change without disconnecting the link. This capability is called Dynamic Bandwidth Allocation, or DBA.
Standard Organization: Ascend Communication

MPPC: Microsoft Point-to-Point Compression Protocol
Microsoft Point-to-Point Compression Protocol (MPPC) is a scheme of representing arbitrary Point-to-Point Protocol (PPP) packets in a compressed form. The MPPC algorithm is designed to optimize processor utilization and bandwidth utilization in order to support a large number of simultaneous connections. The MPPC algorithm is also optimized to work efficiently in typical PPP scenarios (1500 byte MTU, etc.). The MPPC algorithm uses an LZ [3] based algorithm with a sliding window history buffer. The MPPC algorithm keeps a continous history so that after 8192 bytes of data has been transmitted compressed, there is always 8192 bytes of history to use for compressing, except when the history is flushed.
Standard Organization: IETF / Microsoft
Reference Document: RFC 2118 and RFC 3078

MSDP: Multicast Source Discovery Protocol
The Multicast Source Discovery Protocol (MSDP) describes a mechanism to connect multiple PIM Sparse Mode (PIM-SM) domains together. Each PIM-SM domain uses its own independent RP(s) and does not have to depend on RPs in other domains.
Standard Organization: IETF
Reference Document: RFC 3618

MS-RDP: Microsoft's Remote Desktop Protocol
Microsoft's Remote Desktop Protocol (MS-RDP) is designed to provide remote display and input capabilities over network connections for Windows-based applications running on a server. When TS 4.0 was released, RDP was a new protocol based on an existing ITU T.120 family of protocols with limited features and performances. Windows 2000 Terminal Services and the RDP 5.0 protocol includes several critical new features together with some significant performance improvements over all types of network connections, including LAN, WAN, and dial-up.
Standard Organization: Microsoft

MSRPC: Microsoft Remote Procedure Call
Microsoft Remote Procedure Call (MSRPC) is the Microsoft implementation of the DCE RPC mechanism. Additions include support for Unicode strings, implicit handles, inheritance of interfaces (which are extensively used in DCOM), and complex calculations in the variable-length string and structure paradigms already present in DCE/RPC. Microsoft also added new transport protocols for DCE RPC, the ncacn_np transport, which use named pipes carried into the SMB protocol. MSRPC was used by Microsoft to seamlessly create a client/server model in Windows NT/2000/2003. For example, the Windows Server domains protocols are entirely MSRPC based, as is Microsoft's DNS administrative tool. Microsoft Exchange Server 5.5's administrative front-ends are all MSRPC client/server applications, and its MAPI was made more secure by "proxying" MAPI over a set of simple MSRPC functions that enable encryption at the MSRPC layer without involving the MAPI protocol.
Standard Organization: Microsoft

MST: Multiple Spanning Tree Protocol
Multiple Spanning Tree (MST) Protocol defined in the IEEE 802.1s was based on the Cisco's Multiple Instances Spanning Tree Protocol (MISTP). MST combines the best aspects from both the Cisco Per-VLAN Spanning Tree (PVST+) and the 802.1q. The idea is that several VLANs can be mapped to a reduced number of spanning tree instances because most networks do not need more than a few logical topologies.
Standard Organization: IEEE
Reference Document: IEEE 802.1s

MTP: Message Transfer Part
Message Transfer Part (MTP), a protocol in the SS7/C7 protocol suite, transfers signal messages and performs associated functions, such as error control and signaling link security. Message Transfer Part (MTP) also provides reliable routing within a network. MTP has has three layers: Layers 1 (physical), 2 (data), and 3 (network).
Standard Organization: ITU-T
Reference Document: Q.7XX-series

MTP1: Message Transfer Part Level 1
Message Transfer Part Level 1 (MTP1), a SS7 physical layer unit, defines the physical, electrical, and functional characteristics of the digital signaling link.
Standard Organization: ITU-T
Reference Document: Q.7XX-series

MTP2: Message Transfer Part level 2
Message Transfer Part Level 2 (MTP2) is the signalling protocol at the data link layer of SS7/C7 protocol suite. MTP2 provides error detection, sequence checking, and initiates retransmission in case of erroneous reception of messages. MTP Level 2 uses packets called signal units to transmit SS7 messages. There are three types of signal units: Fill-in Signal Unit (FISU), Link Status Signal Unit (LSSU), Message Signal Unit (MSU).
Standard Organization: ITU-T
Reference Document: Q.7XX-series

MTP3: Message Transfer Part level 3
Message Transfer Part level 3 (MTP3) is the signalling protocol at the network layer of SS7/C7 protocol suite. MTP3 provides routing functionality to transport signaling messages through the SS7 network to the requested endpoint. Each network element in the SS7 network has a unique address, the Signaling Point Code (SPC). Message routing is performed according to this address.
Standard Organization: ITU-T
Reference Document: Q.7XX-series

MultiPPP: MultiLink Point to Point Protocol
MultiLink Point-to-Point Protocol (Multilink PPP, MultiPPP or MP), also known as PPP Multilink protocol, is a method for splitting, recombining and sequencing datagrams across multiple logical data links. This work was originally motivated by the desire to exploit multiple bearer channels in ISDN, but is equally applicable to any situation in which multiple PPP links connect two systems, including async links. MultiPPP is based on an LCP option negotiation that permits a system to indicate to its peer that it is capable of combining multiple physical links into a "bundle".
Standard Organization: IETF
Reference Document: RFC 1990

MZAP: Multicast-Scope Zone Announcement Protocol
Multicast-Scope Zone Announcement Protocol (MZAP) is for the discovery of the multicast administrative scope zones that are relevant at a particular location. MZAP also provides mechanisms to discover common misconfigurations of administrative scope zones.
Standard Organization: IETF
Reference Document: RFC 2776