l3vpn model changes: 1. can you tell if more changes planned, or this is the final model?2. regarding ie-profile (=vpn-instance-profile) can you please elaborate what is the active-vpn-instance-profiles ? I see it has its own configs, so I am not sure why do we need the vpn-instance-profile for? For instance in your example I see profile1 which has route targets config, And the node is associated with profile1, but also has route targets configured under the active-vpn-instance-profile. So question is do we need to accumulate the route targets coming from the active also? 3. I see the profile role so it means in case of hub;spoke we cant assign profile to a node with different role? 
<ol>I believe Sahithi answered this in the email thread but I will re-iterate here:</ol><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>Hi Haim/Idan,There should not be any major changes from the model mentioned below for M4 release:Models:https://wwwin-github.cisco.com/nso-function-pack/tsdn-fp-configs/tree/master/CNC-5.0/CoreFP-Models/ietf-l3vpn-ntw/yangSample Configs:https://wwwin-github.cisco.com/nso-function-pack/tsdn-fp-configs/tree/master/CNC-5.0/CoreFP-Models/ietf-l3vpn-ntw/sample-configsWe will update this thread or email when there are changes to the models.ThanksSahithi</pre></div></div>2. The details can be found here:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>  'vpn-instance-profiles': Defines reusable parameters for the same   'vpn-service'.</pre></div></div><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>  'active-vpn-instance-profiles': Lists the set of active VPN instance   profiles for this VPN node. Concretely, one or more VPN instance   profiles that are defined at the VPN service level can be enabled   at the VPN node level; each of these profiles is uniquely   identified by means of 'profile-id'. The structure of 'active-   vpn-instance-profiles' is the same as the structure discussed in   Section 7.4, except that the structure of 'active-vpn-instance-   profiles' includes 'router-id' but does not include the 'role'   leaf. The value of 'router-id' indicated under 'active-vpn-   instance-profiles' takes precedence over the 'router-id' under the   'vpn-node' for the indicated address family. For example, Router   IDs can be configured per address family. This capability can be   used, for example, to configure an IPv6 address as a Router ID   when such a capability is supported by involved routers.   Values defined in 'active-vpn-instance-profiles' override the   values defined at the VPN service level. An example is shown in   Appendix A.3.</pre></div></div>To summarize, the "vpn-instance-profile" are just profile definitions and are not configured on the device unless if these "vpn-instance-profile" definitions are configured as the "active-vpn-instance-profile", which also allows overriding some of the configuration for "vpn-instance-profile"3. You would need separate "vpn-instance-profiles", one for "hub" and one for "spoke, then assign those profiles to your vpn-nodesthank you for the info