science

Multiprotocol Encapsulation over ATM

Multiprotocol Encapsulation over ATM is a science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Multiprotocol Encapsulation over ATM rather than just read about it. In short: 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.

Key takeaways

Multiprotocol Encapsulation over ATM belongs to science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect Multiprotocol Encapsulation over ATM to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of Multiprotocol Encapsulation over ATM from memory before moving on to harder problems.

Reference excerpt

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. It replaces RFC 1483, a standard data link access protocol supported by DSL modems. RFC 2684 describes two encapsulation mechanisms for network traffic: Virtual Circuit Multiplexing and LLC Encapsulation. Either mechanism carries either routed or bridged protocol data units, and DSL modems often include a setting for RFC 1483 bridging. This is distinct from other "bridge modes" commonly found in combined DSL modems and routers, which turn off the router portion of the DSL modem. In VC Multiplexing (VC-MUX), the hosts agree on the high-level protocol for a given circuit. 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. In LLC Encapsulation the hosts use a single virtual circuit for multiple protocols. This 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, and 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. 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.

See also Asynchronous Transfer Mode (ATM) Point-to-Point Protocol over ATM (PPPoA) Broadband Remote Access Server

External links ATM Forum Understanding IPoEoATM and RFC 1483 bridging Cisco Systems

Worked examples

Example 1 — a first encounter with Multiprotocol Encapsulation over ATM

Start with the simplest possible case. Write down what Multiprotocol Encapsulation over ATM claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Multiprotocol Encapsulation over ATM before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Multiprotocol Encapsulation over ATM ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Multiprotocol Encapsulation over ATM

In research: Multiprotocol Encapsulation over ATM appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses Multiprotocol Encapsulation over ATM in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: Multiprotocol Encapsulation over ATM is common in secondary-school and first-year university syllabi. It links to neighbouring topics Internet Standards, so understanding it makes those chapters shorter.
In everyday life: Look for Multiprotocol Encapsulation over ATM outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Multiprotocol Encapsulation over ATM in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what Multiprotocol Encapsulation over ATM means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain Multiprotocol Encapsulation over ATM out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Multiprotocol Encapsulation over ATM in simple terms?

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.

Why does Multiprotocol Encapsulation over ATM matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Multiprotocol Encapsulation over ATM?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Multiprotocol Encapsulation over ATM.