< draft-liu-teas-transport-network-slice-yang-02.txt		draft-liu-teas-transport-network-slice-yang-03.txt >
	Network Working Group X. Liu		Network Working Group X. Liu
	Internet-Draft Volta Networks		Internet-Draft Volta Networks
	Intended status: Standards Track J. Tantsura		Intended status: Standards Track J. Tantsura
	Expires: May 6, 2021 Apstra Networks		Expires: November 3, 2021 Juniper Networks
	I. Bryskin		I. Bryskin
	Individual		Individual
	L. Contreras		L. Contreras
	Telefonica		Telefonica
	Q. Wu		Q. Wu
	Huawei		Huawei
	S. Belotti		S. Belotti
	R. Rokui		R. Rokui
	Nokia		Nokia
	November 2, 2020		May 2, 2021
	IETF Network Slice YANG Data Model		IETF Network Slice YANG Data Model
	draft-liu-teas-transport-network-slice-yang-02		draft-liu-teas-transport-network-slice-yang-03
	Abstract		Abstract
	This document describes a YANG data model for managing and		This document describes a YANG data model for managing and
	controlling IETF network slices, defined in		controlling IETF network slices, defined in
	[I-D.nsdt-teas-ietf-network-slice-definition].		[I-D.ietf-teas-ietf-network-slices].
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on May 6, 2021.		This Internet-Draft will expire on November 3, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 2, line 44 ¶		skipping to change at page 2, line 44 ¶
	9.2. Informative References . . . . . . . . . . . . . . . . . 20		9.2. Informative References . . . . . . . . . . . . . . . . . 20
	Appendix A. Data Tree for the Example in Section 3.1. . . . . . 22		Appendix A. Data Tree for the Example in Section 3.1. . . . . . 22
	A.1. Native Topology . . . . . . . . . . . . . . . . . . . . . 22		A.1. Native Topology . . . . . . . . . . . . . . . . . . . . . 22
	A.2. Network Slice Blue . . . . . . . . . . . . . . . . . . . 26		A.2. Network Slice Blue . . . . . . . . . . . . . . . . . . . 26
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
	1. Introduction		1. Introduction
	This document defines a YANG [RFC7950] data model for for		This document defines a YANG [RFC7950] data model for for
	representing, managing, and controlling IETF network slices, defined		representing, managing, and controlling IETF network slices, defined
	in [I-D.nsdt-teas-ietf-network-slice-definition]		in [I-D.ietf-teas-ietf-network-slices]
	The defined data model is an interface between clients and providers		The defined data model is an interface between clients and providers
	for configurations and state retrievals, so as to support network		for configurations and state retrievals, so as to support network
	slicing as a service. Through this model, a client can learn the		slicing as a service. Through this model, a client can learn the
	slicing capabilities and the available resources of the provider. A		slicing capabilities and the available resources of the provider. A
	client can request or negotiate with a network slicing provider to		client can request or negotiate with a network slicing provider to
	create an instance. The client can incrementally update its		create an instance. The client can incrementally update its
	requirements on individual topology elements in the slice instance,		requirements on individual topology elements in the slice instance,
	and retrieve the operational states of these elements. With the help		and retrieve the operational states of these elements. With the help
	of other mechanisms and data models defined in IETF, the telemetry		of other mechanisms and data models defined in IETF, the telemetry
	skipping to change at page 20, line 29 ¶		skipping to change at page 20, line 29 ¶
	[RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and		[RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
	O. Gonzalez de Dios, "YANG Data Model for Traffic		O. Gonzalez de Dios, "YANG Data Model for Traffic
	Engineering (TE) Topologies", RFC 8795,		Engineering (TE) Topologies", RFC 8795,
	DOI 10.17487/RFC8795, August 2020,		DOI 10.17487/RFC8795, August 2020,
	<https://www.rfc-editor.org/info/rfc8795>.		<https://www.rfc-editor.org/info/rfc8795>.
	[GSMA-NS-Template]		[GSMA-NS-Template]
	GSM Association, "Generic Network Slice Template, Version		GSM Association, "Generic Network Slice Template, Version
	3.0", NG.116, May 2020.		3.0", NG.116, May 2020.
	[I-D.nsdt-teas-ietf-network-slice-definition]		[I-D.ietf-teas-ietf-network-slices]
	Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J.		Farrel, A., Gray, E., Drake, J., Rokui, R., Homma, S.,
	Tantsura, "Definition of IETF Network Slices", draft-nsdt-		Makhijani, K., Contreras, L. M., and J. Tantsura,
	teas-ietf-network-slice-definition-00 (work in progress),		"Framework for IETF Network Slices", draft-ietf-teas-ietf-
	October 2020.		network-slices-00 (work in progress), April 2021.
	9.2. Informative References		9.2. Informative References
	[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",		[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
	RFC 7951, DOI 10.17487/RFC7951, August 2016,		RFC 7951, DOI 10.17487/RFC7951, August 2016,
	<https://www.rfc-editor.org/info/rfc7951>.		<https://www.rfc-editor.org/info/rfc7951>.
	[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",		[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
	BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,		BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
	<https://www.rfc-editor.org/info/rfc8340>.		<https://www.rfc-editor.org/info/rfc8340>.
	[RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for		[RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for
	Abstraction and Control of TE Networks (ACTN)", RFC 8453,		Abstraction and Control of TE Networks (ACTN)", RFC 8453,
	DOI 10.17487/RFC8453, August 2018,		DOI 10.17487/RFC8453, August 2018,
	<https://www.rfc-editor.org/info/rfc8453>.		<https://www.rfc-editor.org/info/rfc8453>.
	[I-D.ietf-ccamp-otn-topo-yang]		[I-D.ietf-ccamp-otn-topo-yang]
	Zheng, H., Busi, I., Liu, X., Belotti, S., and O. Dios, "A		Zheng, H., Busi, I., Liu, X., Belotti, S., and O. G. D.
	YANG Data Model for Optical Transport Network Topology",		Dios, "A YANG Data Model for Optical Transport Network
	draft-ietf-ccamp-otn-topo-yang-11 (work in progress),		Topology", draft-ietf-ccamp-otn-topo-yang-12 (work in
	September 2020.		progress), February 2021.
	[I-D.ietf-i2rs-yang-l2-network-topology]		[I-D.ietf-i2rs-yang-l2-network-topology]
	Dong, J., Wei, X., WU, Q., Boucadair, M., and A. Liu, "A		Dong, J., Wei, X., Wu, Q., Boucadair, M., and A. Liu, "A
	YANG Data Model for Layer 2 Network Topologies", draft-		YANG Data Model for Layer 2 Network Topologies", draft-
	ietf-i2rs-yang-l2-network-topology-18 (work in progress),		ietf-i2rs-yang-l2-network-topology-18 (work in progress),
	September 2020.		September 2020.
	[I-D.ietf-teas-actn-yang]		[I-D.ietf-teas-actn-yang]
	Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B., Dios, O.,		Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B. Y., and S.
	Shin, J., and S. Belotti, "Applicability of YANG models		Belotti, "Applicability of YANG models for Abstraction and
	for Abstraction and Control of Traffic Engineered		Control of Traffic Engineered Networks", draft-ietf-teas-
	Networks", draft-ietf-teas-actn-yang-06 (work in		actn-yang-07 (work in progress), February 2021.
	progress), August 2020.
	[I-D.nsdt-teas-ns-framework]
	Gray, E. and J. Drake, "Framework for Transport Network
	Slices", draft-nsdt-teas-ns-framework-04 (work in
	progress), July 2020.
	Appendix A. Data Tree for the Example in Section 3.1.		Appendix A. Data Tree for the Example in Section 3.1.
	A.1. Native Topology		A.1. Native Topology
	This section contains an example of an instance data tree in the JSON		This section contains an example of an instance data tree in the JSON
	encoding [RFC7951]. The example instantiates "ietf-network" for the		encoding [RFC7951]. The example instantiates "ietf-network" for the
	native topology depicted in Figure 3.		native topology depicted in Figure 3.
	{		{
	skipping to change at page 32, line 13 ¶		skipping to change at page 32, line 13 ¶
	}		}
	Authors' Addresses		Authors' Addresses
	Xufeng Liu		Xufeng Liu
	Volta Networks		Volta Networks
	EMail: xufeng.liu.ietf@gmail.com		EMail: xufeng.liu.ietf@gmail.com
	Jeff Tantsura		Jeff Tantsura
	Apstra Networks		Juniper Networks
	EMail: jefftant.ietf@gmail.com		EMail: jefftant.ietf@gmail.com
	Igor Bryskin		Igor Bryskin
	Individual		Individual
	EMail: i_bryskin@yahoo.com		EMail: i_bryskin@yahoo.com
	Luis Miguel Contreras Murillo		Luis Miguel Contreras Murillo
	Telefonica		Telefonica
End of changes. 12 change blocks.
	28 lines changed or deleted		22 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/