< draft-liu-teas-transport-network-slice-yang-03.txt		draft-liu-teas-transport-network-slice-yang-04.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: November 3, 2021 Juniper Networks		Expires: January 10, 2022 Microsoft
	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
	May 2, 2021		July 9, 2021
	IETF Network Slice YANG Data Model		IETF Network Slice YANG Data Model
	draft-liu-teas-transport-network-slice-yang-03		draft-liu-teas-transport-network-slice-yang-04
	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.ietf-teas-ietf-network-slices].		[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
	skipping to change at page 1, line 42 ¶		skipping to change at page 1, line 42 ¶
	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 November 3, 2021.		This Internet-Draft will expire on January 10, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 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
	skipping to change at page 2, line 24 ¶		skipping to change at page 2, line 24 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3		1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
	1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3		1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
	2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 3		2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 3
	2.1. Relationships to Related Topology Models . . . . . . . . 3		2.1. Relationships to Related Topology Models . . . . . . . . 3
	2.2. Network Slice with TE . . . . . . . . . . . . . . . . . . 4		2.2. Network Slice with TE . . . . . . . . . . . . . . . . . . 4
	2.3. ACTN for Network Slicing . . . . . . . . . . . . . . . . 5		2.3. ACTN for Network Slicing . . . . . . . . . . . . . . . . 5
	3. Model Applicability . . . . . . . . . . . . . . . . . . . . . 5		3. Model Applicability . . . . . . . . . . . . . . . . . . . . . 6
	3.1. Network Slicing by Virtualization . . . . . . . . . . . . 5		3.1. Network Slicing by Virtualization . . . . . . . . . . . . 6
	3.2. Network Slicing by TE Overlay . . . . . . . . . . . . . . 8		3.2. Network Slicing by TE Overlay . . . . . . . . . . . . . . 8
	4. Model Tree Structure . . . . . . . . . . . . . . . . . . . . 10		4. Model Tree Structure . . . . . . . . . . . . . . . . . . . . 10
	5. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 10		5. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 10
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 17		7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
	9.1. Normative References . . . . . . . . . . . . . . . . . . 18		9.1. Normative References . . . . . . . . . . . . . . . . . . 18
	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
	skipping to change at page 4, line 17 ¶		skipping to change at page 4, line 17 ¶
	L3 Topology Model:		L3 Topology Model:
	Defined in [RFC8346].		Defined in [RFC8346].
	TE Topology Model:		TE Topology Model:
	Defined in [RFC8795].		Defined in [RFC8795].
	Figure 1 shows the relationships among these models. The box of		Figure 1 shows the relationships among these models. The box of
	dotted lines denotes the model defined in this document.		dotted lines denotes the model defined in this document.
	+------------------------+		+-------------------------+
	| |		| |
	| Network Topology Model |		| Network Topology Model |
	| RFC 8345 |		| RFC 8345 |
	+------------------------+		+------------^------------+
	|		|
	+-------------+-------------+-------------+-------------+		| augments
	| | | | |		+--------------+------+-------+--------------+
	V V V V V		| | | |
	+----------+ +----------+ +----------+ +----------+ ............		| | | |
	| OTN | | L2 | | L3 | | TE | : Network :		+-----^----+ +-----^----+ +-----^----+ ......^.....
	| Topology | | Topology | | Topology | | Topology | : Slice :		| L2 | | L3 | | TE | : Network :
	| Model | | Model | | Model | | Model | : Model :		| Topology | | Topology | | Topology | : Slice :
	+----------+ +----------+ +----------+ +----------+ ''''''''''''		| Model | | Model | | Model | : Model :
			+----------+ +----------+ +-----^----+ ''''''''''''
			|
			|
			+-----^----+
			| OTN |
			| Topology |
			| Model |
			+----------+
	Figure 1: Model Relationships		Figure 1: Model Relationships
	2.2. Network Slice with TE		2.2. Network Slice with TE
	In many situations, an IETF network slide needs to have TE (Traffic		In many situations, an IETF network slide needs to have TE (Traffic
	Engineering) capabilities to achieve certain network characteristics.		Engineering) capabilities to achieve certain network characteristics.
	The TE Topology Model defined in [RFC8795] can be used to make an		The TE Topology Model defined in [RFC8795] can be used to make an
	IETF network slice TE capable. To achieve this, an IETF network		IETF network slice TE capable. To achieve this, an IETF network
	slice instance will be configured to have both "network-slice" and		slice instance will be configured to have both "network-slice" and
	"te-topology" network types, taking advantage of the multiple		"te-topology" network types, taking advantage of the multiple
	inheritance capability featured by the network topology model		inheritance capability featured by the network topology model
	[RFC8345]. The following diagram shows their relations.		[RFC8345]. The following diagram shows their relations.
	+--------------------+ +--------------------+		+---------------------+ +---------------------+
	| Network Slice | | TE Topology |		| Network Slice | | TE Topology |
	| ietf-network-slice | | ietf-te-topology |		| ietf-network-slice | | ietf-te-topology |
	+--------------------+ +--------------------+		+----------^----------+ +----------^----------+
	\ /		| inherits attributes from |
	\ /		\ /
	\ /		\ /
	v v		\ /
	+------------------------+		+--------------------------------------------------------+
	| Network Slice with TE |		| Network Slice with TE |
	| |		+--------------------------------------------------------+
	+------------------------+		| ietf-network-topology: |
			| network-id (key) |
			| network-types: { |
			| network-slice{} |
			| te-topology{} |
			| } |
			| <other network topology attributes> |
			+-----------------------------+--------------------------+
			| ietf-network-slice: | ietf-te-topology: |
			| <network slice attributes>| <TE attributes> |
			+-----------------------------+--------------------------+
	Figure 2: Network Slice with TE		Figure 2: Network Slice with TE
	This method can be applied to other types of network topology models		This method can be applied to other types of network topology models
	too. For example, when a network topology instance is configured to		too. For example, when a network topology instance is configured to
	have the types of "network-slice" defined in this document, "te-		have the types of "network-slice" defined in this document, "te-
	topology" defined in [RFC8795], and "l3-unicast-topology" defined in		topology" defined in [RFC8795], and "l3-unicast-topology" defined in
	[RFC8346], this network topology instance becomes an IETF network		[RFC8346], this network topology instance becomes an IETF network
	slice instance that can perform layer 3 traffic engineering.		slice instance that can perform layer 3 traffic engineering.
	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
	Juniper Networks		Microsoft
	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. 8 change blocks.
	33 lines changed or deleted		51 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/