Y.1731 device config with prefix L2NM-: Can we remove this prefix L2NM- from the device config cfm-domains-domain-services-service? ethernet-features {                cfm {                  domains {domain md-1 {services {service L2NM-new-l2nm-p2p-sr-1 {continuity-check-interval {       -                    ccm-interval 1s;       -                  }cross-check {cross-check-meps {       -                      cross-check-mep 2;       -                    }}service-properties {       -                    service-type p2p-cross-connect;       -                    group-name new-l2nm-p2p-sr-1;       -                    switching-name new-l2nm-p2p-sr-1;       -                    short-ma-name-format number;       -                    short-ma-name-number 100;       -                  }}}domain-properties {       -                level 0;       -                mdid-format null;       -              }}                  }                }              }</ul>
What issue is the prefix causing? The prefix is used to determine whether the config was initially created by which serviceWhy we change the "service" Id? should it match to the "vpn-service"-"vpn-id" in service configs? In this case it is "new-l2nm-p2p-sr-1".The device configuration is pushed by the internal service, so it pick up the internal service name there. We do this concatenation to determine if the config was pushed by L2NM services or directly from flat-L2vpn service.Why we need to determine this on the device configs level? Who will consume this device config level info (it is pushed by IETF or Flat model)? From AA perspective, it will be more straight forward to match the cfm "service id" on device config to the "vpn-id" in the L2NM service config.Please file a CDETs. We can consider removing the concatenation.Closing ticket, since this issue is now handled by CDETs, 