This deprecated read-write object held a single disposition setting (drop, peer, tunnel, etc.) for how the flow point's CPD profile handled LLDP frames, before the MIB split LLDP handling out by individual multicast MAC address, as its description notes. An administrator would have used it to decide whether Link Layer Discovery Protocol frames arriving on an Ethernet flow point were processed locally, passed transparently, or discarded, which affects neighbor-discovery visibility across a carrier Ethernet service. For example, on a UNI flow point carrying a business Ethernet service, an operator would have set it to tunnel LLDP frames through rather than terminate them, but new configurations should instead use the newer per-MAC LLDP disposition objects since this one is superseded.