The following guidelines apply to multi-class MLPPP:
MC-MLPPP must be configured before links are added to a bundle.
MC-MLPPP and LFI (config>port>ml-bundle>interleave-fragment) are mutually exclusive.
MC-MLPPP is not supported when port is configured as network mode.
MC-MLPPP can be enabled on every MLPPP bundle and bundle protection group.
MC-MLPPP is supported only on ASAP MDAs (for example, m4-choc3-as-sfp, m1-choc12-as-sfp, m4-chds3-as, m12-chds3-as).
Short and long sequence packet formats are supported (both ends must be of the same type) with static mapping of forwarding classes to MC-MLPPP class (based on the number of classes negotiated with the far end).
Single fragment size for all classes is supported.
Prefix elision is not supported. The prefix elision (compressing common header bytes) option advises the peer that, in each of the classes, the implementation expects to receive only packets with a specific prefix; this prefix is not to be sent as part of the information in the fragments of this class.
Fractional DS1/E1 MLPPP links are supported. This is applicable to MLPPP bundles on ASAP MDAs. Fractional E1 and Fractional DS1 links cannot be combined in the same bundle.