Where is the fragment size configured when using FRF.12 link fragmentation and interleaving? (Exhibit)

A.
within the physical serial interface

B.
within the Frame Relay map-class

C.
within the MQC policy-map

D.
within the MQC class-map

E.
within the MQC service-policy

F.
within the logical multilink interface

Explanation:

The purpose of end-to-end FRF.12 fragmentation is to support real-time and non-real-time data packets on lower-speed links without causing excessive delay to the real-time data. FRF.12 fragmentation is defined by the FRF.12 Implementation Agreement. This standard was developed to allow long data frames to be fragmented into smaller pieces (fragments) and interleaved with real-time frames. In this way, real-time and non-real-time data frames can be carried together on lower-speed links without causing excessive delay to the real-time traffic. End-to-end FRF.12 fragmentation is recommended for use on permanent virtual circuits (PVCs) that share links with other PVCs that are transporting voice and on PVCs transporting Voice over IP (VoIP). Although VoIP packets should not be fragmented, they can be interleaved with fragmented packets.
To configure the map class to support FRF.12 fragmentation, use the following map-class configuration command: