Currently default Naming Policy is defined in a way that results in creating name not conforming to DNS name specification. Because of such, generated names cannot be effectively used for naming network resources. This is especially visible if we wanted to reuse Naming Policy to generate names for Kubernetes Pods/Services.

As a current workaround, CNF usecase doesn't utilize default Naming Policy, but rather it's own, as defined in https://gerrit.onap.org/r/#/c/demo/+/102946/

Changes for current Naming Policy to be DNS-compliant are:

• Change Delimiter to "-"
• Change all default strings to lowercase
• Change (or adapt) `VF_MODULE_TYPE` variable source to yield lowercase result (currently it's started with capital letter, e.g. "Base")
• Timestamp be converted not to contain uppercase letters (T)

P.S. I think this issue is more relevant to SDNC component, but maybe it should be changed to POLICY.