ATM Adaptation Layer 5: Difference between revisions

Content deleted Content added
Datagram Encapsulation and IP MTU size: Well, mention that the encapsulation schemes of RFC 2864 are used with RFC 2225.
Line 27:
 
== Datagram Encapsulation and IP MTU size==
[[Internet Protocol|Internet Protocol (IP)]] can use AAL5, andcombined with one of the encapsulation schemes described in RFC 2684, to transfer datagrams across an ATM network, as specified in RFC 2225. Before data can be sent, a [[virtual circuit]] (PVC or SVC) must be in place to the destination host and both ends must agree to use AAL5 on the circuit. To transfer a datagram, the sender passes it to AAL5 along with the VPI/VCI identifying the circuit. AAL5 generates a trailer, divides the datagram into cells, and transfers the cells across the network. At the receiving end, AAL5 reassembles the cells, checks the CRC to verify that no bits were lost or corrupted, extracts the datagram, and passes it to the IP layer.
 
AAL5 uses a 16-bit length field, making it possible to send 65,535 (2^16-1) octets in a single packet. However, RFC 2225 specifies a default MTU of 9180 octets per datagram, so, unless the hosts on both ends of the virtual circuit negotiate a larger MTU, IP datagrams larger than 9180 octets will be fragmented.