The mac-vrf routing-instance type is used for large-scale, multi-tenant EVPN deployments, often where overlapping VLANs are required. This instance type mandates the use of a "service-provider style" interface configuration on host-facing ports. This involves configuring logical units under the physical interface with specific VLAN tagging and encapsulation (e.g., encapsulation vlan-bridge). Additionally, mac-vrf instances support different service models, including vlan-based, where each VLAN is mapped to its own unique bridge domain and VNI, providing traffic separation.

B. Host-facing interfaces must be configured using enterprise-style configuration.

Enterprise-style configuration (interface-mode trunk, vlan members) is used with virtual-switch instances, not mac-vrf.

C. Spine-facing interfaces must be configured using an enterprise-style configuration.

Spine-facing interfaces are part of the IP underlay and are configured as standard L3 interfaces, not for VLAN services.

1. Juniper Networks TechLibrary, "Configuring EVPN with a MAC-VRF Routing Instance," EVPN Feature Guide. This guide explicitly states, "For each MAC-VRF instance, you must configure the instance-type mac-vrf statement...On the interfaces that you configure in the MAC-VRF instance, you must use a service-provider-style configuration."

2. Juniper Networks TechLibrary, "service-type (MAC-VRF)," EVPN Feature Guide. This page documents the available options for the service-type statement within a mac-vrf instance, which include vlan-based and vlan-aware.