The IETF and in the industry in general currently specifies a series of YANG models for network element configuration. While focusing on YANG models to configure features on individual network elements is the right first step, the end goal is the configuration of end to end services across networks. Taking into account that both features and services data models are complementary, this short-lived WG is tasked to create a first service model at the IETF, based on the ‘service’ level aspects of the L3VPN. This L3VPN services model is not a L3VPN configuration model, i.e. not the ‘combined configuration’ model of all the different parameters required for the L3VPN configuration on network elements. It contains the characteristics of the service, as discussed between the operators and their customers. The outcome of this WG will provide the required information to evaluate the YANG model feature coverage. Indeed, in order to configure L3VPN services, many different protocol or topology-specific YANG models are required: some of are already published as RFC, some are working group or individual documents, and some are clearly missing. The deliverable in this WG will generate requirements for lower-layer protocol configuration models, will help mapping the service parameters into inputs that can be used by protocol models. In other words, help evaluating the current catalog of models. Specifying this L3VPN service model in YANG would seem logical as it provides the advantage of easy mapping with other YANG models. However, this is not a requirement. As a starting point, draft-l3vpn-service-yang should be considered. Milestones: Jan 2016 L3VPN Services (YANG) Model to the IESG