Revision as of 15:22, 7 December 2011 edit JeffMorriss (talk \| contribs) 210 edits →Packet type and multiplexing: Fix up some English. ← Previous edit		Revision as of 09:29, 7 November 2012 edit undo Isidore (talk \| contribs) Extended confirmed users 1,256 edits m →Packet type and multiplexing: punctuation Next edit →
Line 21: The latter scheme, in which the hosts use a single virtual circuit for multiple protocols, is referred to in RFC 2684 as "LLC Encapsulation". The standards suggest that hosts should use a standard [[IEEE 802.2]] ''[[Logical Link Control]]'' (LLC) header, followed by a ''[[Subnetwork Access Protocol]]'' (SNAP) header if necessary. This scheme 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~~The agreement may involve manual configuration. == Datagram encapsulation and IP MTU size==

ATM Adaptation Layer 5: Difference between revisions