The list of all MEPs in the MEG. For a device to create a local MEP it will need to create an entry in the adGenY1731LocalMepConfigTable. Once a local MEP is created, all other entries in the adGenY1731MegMepListTable are automatically considered remote MEPs of the local MEP and their information is used to populate the adGenY1731LocalMepRmepDbTable. The MEG MEP List should be the same across all devices in the MEG and contain the exact same list of adGenY1731MegMepListIdentifiers. On a given device, a MEPID in the MEG MEP list can transition from having no association to a local or remote MEP to any of the following (1) becoming a local MEP, (2) becoming a remote MEP of a local MEP, or (3) becoming both a local MEP and a remote MEP of a local MEP. The third case is possible if two local MEPs in the same MEG are created on the same device.