%% You should probably cite draft-ietf-teas-ns-models-applicability instead of this I-D. @techreport{barguil-teas-network-slices-instantation-08, number = {draft-barguil-teas-network-slices-instantation-08}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-barguil-teas-network-slices-instantation/08/}, author = {Samier Barguil and Luis M. Contreras and Victor Lopez and Oscar Gonzalez de Dios and Mohamed Boucadair and Reza Rokui}, title = {{Applicability of IETF-Defined Service and Network Data Models for RFC XXXX Network Slice Service Management}}, pagetotal = 30, year = , month = , day = , abstract = {This document exemplifies how the various data modeles that are produced in the IETF can be combined in the context of RFC XXXX Network Slice Services delivery. Specifically, this document describes the relationship between the RFC XXXX Network Slice Service models for requesting Network Slice Services and both Service (e.g., the Layer-3 Service Model, the Layer-2 Service Model) and Network (e.g., the Layer-3 Network Model, the Layer-2 Network Model) models used during their realizations. In addition, this document describes the communication between an RFC XXXX Network Slice Controller (NSC) and the network controllers for the realization of RFC XXXX Network Slices. The RFC XXXX Network Slice Service YANG model provides a customer- oriented view of the intended Network slice Service. Thus, once an NSC receives a request for a Slice Service request, the NSC has to map it to accomplish the specific objectives expected by the network controllers. Existing YANG network models are analyzed against the RFC XXXX Network Slice requirements, and the gaps in existing models are identified. Note to the RFC Editor: Please replace "RFC XXXX" with the RFC number assigned to I-D.ietf-teas-ietf-network-slices.}, }