< draft-liu-teas-transport-network-slice-yang-01.txt   draft-liu-teas-transport-network-slice-yang-02.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: January 13, 2021 Apstra Networks Expires: May 6, 2021 Apstra 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
July 12, 2020 November 2, 2020
Transport Network Slice YANG Data Model IETF Network Slice YANG Data Model
draft-liu-teas-transport-network-slice-yang-01 draft-liu-teas-transport-network-slice-yang-02
Abstract Abstract
This document describes a YANG data model for managing and This document describes a YANG data model for managing and
controlling transport network slices, defined as transport slices in controlling IETF network slices, defined in
[I-D.nsdt-teas-transport-slice-definition]. [I-D.nsdt-teas-ietf-network-slice-definition].
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 January 13, 2021. This Internet-Draft will expire on May 6, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 43 skipping to change at page 2, line 43
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
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 transport network slices, representing, managing, and controlling IETF network slices, defined
defined as transport slices in in [I-D.nsdt-teas-ietf-network-slice-definition]
[I-D.nsdt-teas-transport-slice-definition]
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 transport for configurations and state retrievals, so as to support network
network slicing as a service. Through this model, a client can learn slicing as a service. Through this model, a client can learn the
the slicing capabilities and the available resources of the provider. slicing capabilities and the available resources of the provider. A
A client can request or negotiate with a transport network slicing client can request or negotiate with a network slicing provider to
provider to create an instance. The client can incrementally update create an instance. The client can incrementally update its
its requirements on individual topology elements in the slice requirements on individual topology elements in the slice instance,
instance, and retrieve the operational states of these elements. and retrieve the operational states of these elements. With the help
With the help of other mechanisms and data models defined in IETF, of other mechanisms and data models defined in IETF, the telemetry
the telemetry information can be published to the client. information can be published to the client.
The YANG data model in this document conforms to the Network The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA) [RFC8342]. Management Datastore Architecture (NMDA) [RFC8342].
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119] [RFC8174] when, and only when, they appear in all 14, [RFC2119] [RFC8174] when, and only when, they appear in all
skipping to change at page 3, line 36 skipping to change at page 3, line 35
o data node o data node
1.2. Tree Diagrams 1.2. Tree Diagrams
Tree diagrams used in this document follow the notation defined in Tree diagrams used in this document follow the notation defined in
[RFC8340]. [RFC8340].
2. Modeling Considerations 2. Modeling Considerations
A transport slice is modeled as network topology defined in An IETF network slice is modeled as network topology defined in
[RFC8345], with augmentations. A new network type "network-slice" is [RFC8345], with augmentations. A new network type "network-slice" is
defined in this document. When a network topology data instance defined in this document. When a network topology data instance
contains the network-slice network type, it represents an instance of contains the network-slice network type, it represents an instance of
a transport slice. an IETF network slice.
2.1. Relationships to Related Topology Models 2.1. Relationships to Related Topology Models
There are several related YANG data models that have been defined in There are several related YANG data models that have been defined in
IETF. Some of these are: IETF. Some of these are:
Network Topology Model: Network Topology Model:
Defined in [RFC8345]. Defined in [RFC8345].
OTN Topology Model: OTN Topology Model:
Defined in [I-D.ietf-ccamp-otn-topo-yang]. Defined in [I-D.ietf-ccamp-otn-topo-yang].
L2 Topology Model: L2 Topology Model:
Defined in [I-D.ietf-i2rs-yang-l2-network-topology]. Defined in [I-D.ietf-i2rs-yang-l2-network-topology].
L3 Topology Model: L3 Topology Model:
Defined in [RFC8346]. Defined in [RFC8346].
TE Topology Model: TE Topology Model:
Defined in [I-D.ietf-teas-yang-te-topo]. 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 |
+------------------------+ +------------------------+
| |
skipping to change at page 4, line 36 skipping to change at page 4, line 36
+----------+ +----------+ +----------+ +----------+ ............ +----------+ +----------+ +----------+ +----------+ ............
| OTN | | L2 | | L3 | | TE | : Network : | OTN | | L2 | | L3 | | TE | : Network :
| Topology | | Topology | | Topology | | Topology | : Slice : | Topology | | Topology | | Topology | | Topology | : Slice :
| Model | | Model | | Model | | Model | : Model : | Model | | Model | | Model | | Model | : Model :
+----------+ +----------+ +----------+ +----------+ '''''''''''' +----------+ +----------+ +----------+ +----------+ ''''''''''''
Figure 1: Model Relationships Figure 1: Model Relationships
2.2. Network Slice with TE 2.2. Network Slice with TE
In many situations, a transport network slide needs to have TE In many situations, an IETF network slide needs to have TE (Traffic
(Traffic Engineering) capabilities to achieve certain network Engineering) capabilities to achieve certain network characteristics.
characteristics. The TE Topology Model defined in The TE Topology Model defined in [RFC8795] can be used to make an
[I-D.ietf-teas-yang-te-topo] can be used to make a transport slice TE IETF network slice TE capable. To achieve this, an IETF network
capable. To achieve this, a transport slice instance will be slice instance will be configured to have both "network-slice" and
configured to have both "network-slice" and "te-topology" network "te-topology" network types, taking advantage of the multiple
types, taking advantage of the multiple inheritance capability inheritance capability featured by the network topology model
featured by the network topology model [RFC8345]. The following [RFC8345]. The following diagram shows their relations.
diagram shows their relations.
+--------------------+ +--------------------+ +--------------------+ +--------------------+
| Network Slice | | TE Topology | | Network Slice | | TE Topology |
| ietf-network-slice | | ietf-te-topology | | ietf-network-slice | | ietf-te-topology |
+--------------------+ +--------------------+ +--------------------+ +--------------------+
\ / \ /
\ / \ /
\ / \ /
v v v v
+------------------------+ +------------------------+
| Network Slice with TE | | Network Slice with TE |
| | | |
+------------------------+ +------------------------+
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 [I-D.ietf-teas-yang-te-topo], and "l3-unicast- topology" defined in [RFC8795], and "l3-unicast-topology" defined in
topology" defined in [RFC8346], this network topology instance [RFC8346], this network topology instance becomes an IETF network
becomes a transport slice instance that can perform layer 3 traffic slice instance that can perform layer 3 traffic engineering.
engineering.
2.3. ACTN for Network Slicing 2.3. ACTN for Network Slicing
Since ACTN topology data models are based on the network topology Since ACTN topology data models are based on the network topology
model defined in [RFC8345], the augmentations defined in this model defined in [RFC8345], the augmentations defined in this
document are effective augmentations to the ACTN topology data document are effective augmentations to the ACTN topology data
models, resulting in making the ACTN framework [RFC8453] and data models, resulting in making the ACTN framework [RFC8453] and data
models [I-D.ietf-teas-actn-yang] capable of slicing networks with the models [I-D.ietf-teas-actn-yang] capable of slicing networks with the
required network characteristics. required network characteristics.
3. Model Applicability 3. Model Applicability
There are many technologies to achieve transport network slicing. There are many technologies to achieve network slicing. The data
The data model defined in this document can be applied to a wide model defined in this document can be applied to a wide ranges of
ranges of cases. This section describes how this data model is cases. This section describes how this data model is applied to a
applied to a few cases. few cases.
3.1. Network Slicing by Virtualization 3.1. Network Slicing by Virtualization
In the case shown in Figure 3, node virtualization is used to In the case shown in Figure 3, node virtualization is used to
separate and allocate resources in physical devices. Two virtual separate and allocate resources in physical devices. Two virtual
routers VR1 and VR2 are created over physical router R1. Each of the routers VR1 and VR2 are created over physical router R1. Each of the
virtual routers takes a portion of the resources such as ports and virtual routers takes a portion of the resources such as ports and
memory in the physical router. Depending on the requirements and the memory in the physical router. Depending on the requirements and the
implementations, they may share certain resources such as processors, implementations, they may share certain resources such as processors,
ASICs, and switch fabric. ASICs, and switch fabric.
skipping to change at page 8, line 7 skipping to change at page 8, line 7
======|R1 |=========|R2 | ======|R1 |=========|R2 |
+---+ +---+ +---+ +---+
\ +---+ \ +---+
----------|R4 |------ ----------|R4 |------
+---+ +---+
Figure 3: Network Slicing by Virtualization Figure 3: Network Slicing by Virtualization
3.2. Network Slicing by TE Overlay 3.2. Network Slicing by TE Overlay
Figure 5 shows a case where TE (Traffic Engineering) overlay is Figure 4 shows a case where TE (Traffic Engineering) overlay is
applied to achieve logically separated client transport network applied to achieve logically separated client IETF network slices.
slices. In the underlay TE capable network, TE tunnels are In the underlay TE capable network, TE tunnels are established to
established to support the TE links in the overlay network. These support the TE links in the overlay network. These links and tunnels
links and tunnels maintain the characteristics required by the maintain the characteristics required by the clients. The provider
clients. The provider selects the proper logical nodes and links in selects the proper logical nodes and links in the overlay network,
the overlay network, assigns them to specific transport network assigns them to specific IETF network slices, and uses the data model
slices, and uses the data model defined in this document to send the defined in this document to send the results to the clients.
results to the clients.
Client Topology Client Topology Client Topology Client Topology
Network Slice Blue Network Slice Red Network Slice Blue Network Slice Red
+---+ +---+ +---+ +---+ +---+ +---+
-----|R3 |--- ---|R2 |------|R3 | -----|R3 |--- ---|R1 |------|R2 |
/ +---+ +---+ +---+ / +---+ +---+ +---+
+---+ +---+ \ +---+ +---+ +---+ \ +---+
---|R1 |------|R2 | -----|R4 |--- ---|R1 |------|R2 | -----|R4 |---
+---+ +---+ +---+ +---+ +---+ +---+
Clients Clients
--------------------------------------------------------------------- ---------------------------------------------------------------------
Provider Provider
Customized Topology Customized Topology
skipping to change at page 10, line 7 skipping to change at page 10, line 7
======|R1 |--|R5 |--|R2 | ======|R1 |--|R5 |--|R2 |
+---+ +---+ +---+ +---+ +---+ +---+
############## \ +---+ ############## \ +---+
TE Tunnel for Network Slice Red ----------|R4 |------ TE Tunnel for Network Slice Red ----------|R4 |------
+---+ +---+
Figure 4: Network Slicing by TE Overlay Figure 4: Network Slicing by TE Overlay
4. Model Tree Structure 4. Model Tree Structure
TODO - Complete IETF network slice attributes that are technology-
agnostic and common to all use cases.
module: ietf-network-slice module: ietf-network-slice
augment /nw:networks/nw:network/nw:network-types: augment /nw:networks/nw:network/nw:network-types:
+--rw network-slice! +--rw network-slice!
augment /nw:networks/nw:network: augment /nw:networks/nw:network:
+--rw network-slice +--rw network-slice
+--rw optimization-criterion? identityref +--rw optimization-criterion? identityref
+--rw delay-tolerance? boolean +--rw delay-tolerance? boolean
+--rw periodicity* uint64 +--rw periodicity* uint64
+--rw isolation-level? identityref +--rw isolation-level? identityref
augment /nw:networks/nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
skipping to change at page 10, line 31 skipping to change at page 10, line 34
augment /nw:networks/nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw network-slice +--rw network-slice
+--rw delay-tolerance? boolean +--rw delay-tolerance? boolean
+--rw periodicity* uint64 +--rw periodicity* uint64
+--rw isolation-level? identityref +--rw isolation-level? identityref
5. YANG Module 5. YANG Module
This module references [RFC8345], [RFC8776], and [GSMA-NS-Template] This module references [RFC8345], [RFC8776], and [GSMA-NS-Template]
<CODE BEGINS> file "ietf-network-slice@2020-07-12.yang" <CODE BEGINS> file "ietf-network-slice@2020-11-01.yang"
module ietf-network-slice { module ietf-network-slice {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-network-slice"; namespace "urn:ietf:params:xml:ns:yang:ietf-network-slice";
prefix "ns"; prefix "ns";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference "RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology { import ietf-network-topology {
skipping to change at page 11, line 41 skipping to change at page 11, line 44
<mailto:sergio.belotti@nokia.com> <mailto:sergio.belotti@nokia.com>
Editor: Reza Rokui Editor: Reza Rokui
<mailto:reza.rokui@nokia.com> <mailto:reza.rokui@nokia.com>
"; ";
description description
"YANG data model for representing and managing network "YANG data model for representing and managing network
slices. slices.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2020 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2020-07-12 { revision 2020-11-01 {
description "Initial revision"; description "Initial revision";
reference reference
"RFC XXXX: YANG Data Model for Network Slices"; "RFC XXXX: YANG Data Model for Network Slices";
} }
/* /*
* Identities * Identities
*/ */
identity isolation-level { identity isolation-level {
description description
"Base identity for the isolation-level."; "Base identity for the isolation-level.";
reference reference
"GSMA-NS-Template: Generic Network Slice Template, "GSMA-NS-Template: Generic Network Slice Template,
Version 1.0."; Version 3.0.";
} }
identity no-isolation { identity no-isolation {
base isolation-level; base isolation-level;
description description
"Network slices are not separated."; "Network slices are not separated.";
} }
identity physical-isolation { identity physical-isolation {
base isolation-level; base isolation-level;
description description
"Network slices are physically separated (e.g. different rack, "Network slices are physically separated (e.g. different rack,
skipping to change at page 13, line 48 skipping to change at page 13, line 50
description description
"Optimization criterion applied to this topology."; "Optimization criterion applied to this topology.";
} }
leaf delay-tolerance { leaf delay-tolerance {
type boolean; type boolean;
description description
"'true' if is not too critical how long it takes to deliver "'true' if is not too critical how long it takes to deliver
the amount of data."; the amount of data.";
reference reference
"GSMA-NS-Template: Generic Network Slice Template, "GSMA-NS-Template: Generic Network Slice Template,
Version 1.0."; Version 3.0.";
} }
leaf-list periodicity { leaf-list periodicity {
type uint64; type uint64;
units seconds; units seconds;
description description
"A list of periodicities supported by the network slice."; "A list of periodicities supported by the network slice.";
reference reference
"GSMA-NS-Template: Generic Network Slice Template, "GSMA-NS-Template: Generic Network Slice Template,
Version 1.0."; Version 3.0.";
} }
leaf isolation-level { leaf isolation-level {
type identityref { type identityref {
base isolation-level; base isolation-level;
} }
description description
"A network slice instance may be fully or partly, logically "A network slice instance may be fully or partly, logically
and/or physically, isolated from another network slice and/or physically, isolated from another network slice
instance. This attribute describes different types of instance. This attribute describes different types of
isolation:"; isolation:";
skipping to change at page 14, line 49 skipping to change at page 15, line 4
type string; type string;
description description
"Reference to a compute node instance specified in "Reference to a compute node instance specified in
a data model specifying the computing resources."; a data model specifying the computing resources.";
} }
leaf storage-id { leaf storage-id {
type string; type string;
description description
"Reference to a storage instance specified in "Reference to a storage instance specified in
a data model specifying the storage resources."; a data model specifying the storage resources.";
} }
} // network-slice } // network-slice
} // network-slice-node-attributes } // network-slice-node-attributes
grouping network-slice-link-attributes { grouping network-slice-link-attributes {
description "Network Slice link scope attributes"; description "Network Slice link scope attributes";
container network-slice { container network-slice {
description description
"Containing Network Slice attributes."; "Containing Network Slice attributes.";
leaf delay-tolerance { leaf delay-tolerance {
type boolean; type boolean;
description description
"'true' if is not too critical how long it takes to deliver "'true' if is not too critical how long it takes to deliver
the amount of data."; the amount of data.";
reference reference
"GSMA-NS-Template: Generic Network Slice Template, "GSMA-NS-Template: Generic Network Slice Template,
Version 1.0."; Version 3.0.";
} }
leaf-list periodicity { leaf-list periodicity {
type uint64; type uint64;
units seconds; units seconds;
description description
"A list of periodicities supported by the network slice."; "A list of periodicities supported by the network slice.";
reference reference
"GSMA-NS-Template: Generic Network Slice Template, "GSMA-NS-Template: Generic Network Slice Template,
Version 1.0."; Version 3.0.";
} }
leaf isolation-level { leaf isolation-level {
type identityref { type identityref {
base isolation-level; base isolation-level;
} }
description description
"A network slice instance may be fully or partly, logically "A network slice instance may be fully or partly, logically
and/or physically, isolated from another network slice and/or physically, isolated from another network slice
instance. This attribute describes different types of instance. This attribute describes different types of
isolation:"; isolation:";
skipping to change at page 17, line 38 skipping to change at page 17, line 40
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
/nw:networks/nw:network/nw:network-types/ns:network-slice /nw:networks/nw:network/nw:network-types/ns:network-slice
This subtree specifies the network slice type. Modifying the This subtree specifies the network slice type. Modifying the
configurations can make network slice type invalid and cause configurations can make network slice type invalid and cause
interruption to transport network slices. interruption to IETF network slices.
/nw:networks/nw:network/ns:network-slice /nw:networks/nw:network/ns:network-slice
This subtree specifies the topology-wide configurations. This subtree specifies the topology-wide configurations.
Modifying the configurations here can cause traffic Modifying the configurations here can cause traffic
characteristics changed in this transport network slice and characteristics changed in this IETF network slice and related
related networks. networks.
/nw:networks/nw:network/nw:node/ns:network-slice /nw:networks/nw:network/nw:node/ns:network-slice
This subtree specifies the configurations of the nodes in a This subtree specifies the configurations of the nodes in a IETF
transport network slice. Modifying the configurations in this network slice. Modifying the configurations in this subtree can
subtree can change the traffic characteristics on this node and change the traffic characteristics on this node and the related
the related networks. networks.
/nw:networks/nw:network/nt:link/ns:network-slice /nw:networks/nw:network/nt:link/ns:network-slice
This subtree specifies the configurations of the links in a This subtree specifies the configurations of the links in a IETF
transport network slice. Modifying the configurations in this network slice. Modifying the configurations in this subtree can
subtree can change the traffic characteristics on this link and change the traffic characteristics on this link and the related
the related networks. networks.
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
/nw:networks/nw:network/nw:network-types/ns:network-slice /nw:networks/nw:network/nw:network-types/ns:network-slice
Unauthorized access to this subtree can disclose the network slice Unauthorized access to this subtree can disclose the network slice
type. type.
/nw:networks/nw:network/ns:network-slice /nw:networks/nw:network/ns:network-slice
Unauthorized access to this subtree can disclose the topology-wide Unauthorized access to this subtree can disclose the topology-wide
states. states.
/nw:networks/nw:network/nw:node/ns:network-slice /nw:networks/nw:network/nw:node/ns:network-slice
Unauthorized access to this subtree can disclose the operational Unauthorized access to this subtree can disclose the operational
state information of the nodes in a transport network slice. state information of the nodes in a IETF network slice.
/nw:networks/nw:network/nt:link/ns:network-slic /nw:networks/nw:network/nt:link/ns:network-slic
Unauthorized access to this subtree can disclose the operational Unauthorized access to this subtree can disclose the operational
state information of the links in a transport network slice. state information of the links in a IETF network slice.
8. Acknowledgements 8. Acknowledgements
The TEAS Network Slicing Design Team (NSDT) members included Aijun The TEAS Network Slicing Design Team (NSDT) members included Aijun
Wang, Dong Jie, Eric Gray, Jari Arkko, Jeff Tantsura, John E Drake, Wang, Dong Jie, Eric Gray, Jari Arkko, Jeff Tantsura, John E Drake,
Luis M. Contreras, Rakesh Gandhi, Ran Chen, Reza Rokui, Ricard Luis M. Contreras, Rakesh Gandhi, Ran Chen, Reza Rokui, Ricard
Vilalta, Ron Bonica, Sergio Belotti, Tomonobu Niwa, Xuesong Geng, and Vilalta, Ron Bonica, Sergio Belotti, Tomonobu Niwa, Xuesong Geng, and
Xufeng Liu. Xufeng Liu.
9. References 9. References
skipping to change at page 20, line 14 skipping to change at page 20, line 19
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Common YANG Data Types for Traffic Engineering", "Common YANG Data Types for Traffic Engineering",
RFC 8776, DOI 10.17487/RFC8776, June 2020, RFC 8776, DOI 10.17487/RFC8776, June 2020,
<https://www.rfc-editor.org/info/rfc8776>. <https://www.rfc-editor.org/info/rfc8776>.
[I-D.ietf-teas-yang-te-topo] [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and O. Gonzalez de Dios, "YANG Data Model for Traffic
O. Dios, "YANG Data Model for Traffic Engineering (TE) Engineering (TE) Topologies", RFC 8795,
Topologies", draft-ietf-teas-yang-te-topo-22 (work in DOI 10.17487/RFC8795, August 2020,
progress), June 2019. <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
1.0", NG.116, May 2019. 3.0", NG.116, May 2020.
[I-D.nsdt-teas-transport-slice-definition] [I-D.nsdt-teas-ietf-network-slice-definition]
Rokui, R., Homma, S., Makhijani, K., and L. Contreras, Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J.
"IETF Definition of Transport Slice", draft-nsdt-teas- Tantsura, "Definition of IETF Network Slices", draft-nsdt-
transport-slice-definition-02 (work in progress), April teas-ietf-network-slice-definition-00 (work in progress),
2020. October 2020.
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. Dios, "A
YANG Data Model for Optical Transport Network Topology", YANG Data Model for Optical Transport Network Topology",
draft-ietf-ccamp-otn-topo-yang-10 (work in progress), draft-ietf-ccamp-otn-topo-yang-11 (work in progress),
March 2020. September 2020.
[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-14 (work in progress), ietf-i2rs-yang-l2-network-topology-18 (work in progress),
June 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., Dios, O.,
Shin, J., and S. Belotti, "Applicability of YANG models Shin, J., and S. Belotti, "Applicability of YANG models
for Abstraction and Control of Traffic Engineered for Abstraction and Control of Traffic Engineered
Networks", draft-ietf-teas-actn-yang-05 (work in Networks", draft-ietf-teas-actn-yang-06 (work in
progress), February 2020. progress), August 2020.
[I-D.nsdt-teas-ns-framework] [I-D.nsdt-teas-ns-framework]
Gray, E. and J. Drake, "Framework for Transport Network Gray, E. and J. Drake, "Framework for Transport Network
Slices", draft-nsdt-teas-ns-framework-03 (work in Slices", draft-nsdt-teas-ns-framework-04 (work in
progress), April 2020. 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.
{ {
 End of changes. 39 change blocks. 
89 lines changed or deleted 90 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/