Multiprotocol Encapsulation over ATM

Multiprotocol Encapsulation over ATM

Multiprotocol Encapsulation over ATM is specified in RFC 2684. It defines two mechanisms for identifying the protocol carried in ATM Adaptation Layer 5 (AAL5) frames.

The AAL5 trailer does not include a type field. Thus, an AAL5 frame is not self-identifying. This means that either the two hosts at the ends of a virtual circuit must agree a priori that the circuit will be used for one specific protocol (e.g., the circuit will only be used to send IP datagrams), or the two hosts at the ends of a virtual circuit must agree a priori that some octets of the data area will be reserved for use as a type field to distinguish packets containing one protocol's data from packets containing another protocol's data.

RFC 2684 describes two encapsulation mechanisms for network traffic, one of which implements the former scheme and one of which implements the latter scheme.

The former scheme, in which the hosts agree on the high-level protocol for a given circuit, is referred to in RFC 2684 as VC Multiplexing (VC-MUX). It has the advantage of not requiring additional information in a packet, which minimises the overhead. For example, if the hosts agree to transfer IP, a sender can pass each datagram directly to AAL5 to transfer, nothing needs to be sent besides the datagram and the AAL5 trailer. The chief disadvantage of such a scheme lies in duplication of virtual circuits: a host must create a separate virtual circuit for each high-level protocol if more than one protocol is used. Because most carriers charge for each virtual circuit, customers try to avoid using multiple circuits because it adds unnecessary cost.

The latter scheme, in which the hosts use a single virtual circuit for multiple protocols, is referred to in RFC 2684 as LLC Encapsulation. It has the advantage of allowing all traffic over the same circuit, but the disadvantage of requiring each packet to contain octets that identify the protocol type, which adds overhead. The scheme also has the disadvantage that packets from all protocols travel with the same delay and priority.

RFC 2684 specifies that hosts can choose between the two methods of using AAL5. Both the sender and receiver must agree on how the circuit will be used, the agreement may involve manual configuration. Furthermore, the standards suggest that when hosts choose to include type information in the packet, they should use a standard IEEE 802.2 Logical Link Control (LLC) header, followed by a Subnetwork Access Protocol (SNAP) header if necessary.

See also

External links


Wikimedia Foundation. 2010.

Игры ⚽ Нужно решить контрольную?

Look at other dictionaries:

  • Multiprotocol over ATM — Multiprotocol Encapsulation over ATM (MPoA) ist eine Technik, um IP Verkehr effizienter über ein ATM basiertes Netz zu transportieren. Da keine LAN Emulation stattfindet, können Schicht 3 Protokolle direkt die Mechanismen von ATM (z. B.… …   Deutsch Wikipedia

  • ATM Adaptation Layer 5 — (AAL5) is used to send variable length packets up to 65,535 octets in size across an Asynchronous Transfer Mode (ATM) network.Unlike most network frames, which place control information in the header, AAL5 places control information in an 8 octet …   Wikipedia

  • ATM Adaptation Layer 5 — (AAL5) est une couche d adaptation ATM utilisée pour envoyer des paquets de longueur variable allant jusqu à 65 535 octets sur un réseau Asynchronous Transfer Mode (ATM). Contrairement à la plupart des trames réseau, qui placent les… …   Wikipédia en Français

  • Point-to-Point Protocol over Ethernet — PPPoE, Point to Point Protocol over Ethernet, is a network protocol for encapsulating Point to Point Protocol (PPP) frames inside Ethernet frames. It is used mainly with ADSL services where individual users connect to the ADSL transceiver (modem) …   Wikipedia

  • Multiprotocol Label Switching — MPLS redirects here. For other uses, see Mpls. MPLS Layer Multiprotocol Label Switching (MPLS) is a mechanism in high performance telecommunications networks that directs data from one network node to the next based on short path labels rather… …   Wikipedia

  • RFC 1483 — Multiprotocol Encapsulation over ATM Adaptation Layer 5. Juha Heinanen. July 1993 …   Acronyms

  • RFC 2684 — Multiprotocol Encapsulation over ATM Adaptation Layer 5. D. Grossman, J. Heinanen. September 1999. (Ersetzt folgendes RFC :RFC 1483) …   Acronyms

  • RFC 1483 — Multiprotocol Encapsulation over ATM Adaptation Layer 5. Juha Heinanen. July 1993 …   Acronyms von A bis Z

  • RFC 2684 — Multiprotocol Encapsulation over ATM Adaptation Layer 5. D. Grossman, J. Heinanen. September 1999. ( Ersetzt folgendes RFC :RFC 1483) …   Acronyms von A bis Z

  • Virtual Circuit Multiplexing — or VC MUX is one of the two (the other being LLC encapsulation) mechanisms for identifying the protocol carried in ATM Adaptation Layer 5 (AAL5) frames specified by RFC 2684, Multiprotocol Encapsulation over ATM.With virtual circuit multiplexing …   Wikipedia

Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”