Newer
Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
module ietf-network-slice-service {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-network-slice-service";
prefix ietf-nss;
import ietf-inet-types {
prefix inet;
reference
"RFC 6991: Common YANG Types.";
}
import ietf-vpn-common {
prefix vpn-common;
reference
"RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3
VPNs.";
}
import ietf-te-types {
prefix te-types;
reference
"RFC 8776: Common YANG Data Types for Traffic Engineering.";
}
import ietf-te-packet-types {
prefix te-packet-types;
reference
"RFC 8776: Common YANG Data Types for Traffic Engineering.";
}
organization
"IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group";
contact
"WG Web: <https://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org>
Editor: Bo Wu
<lana.wubo@huawei.com>
Editor: Dhruv Dhody
<dhruv.ietf@gmail.com>
Editor: Reza Rokui
<reza.rokui@nokia.com>
Editor: Tarek Saad
<tsaad@juniper.net>
Author: Liuyan Han
<hanliuyan@chinamobile.com>";
description
"This module defines a model for the IETF Network Slice service.
Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Revised BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices.";
revision 2022-07-11 {
description
"initial version.";
reference
"RFC XXXX: A Yang Data Model for IETF Network Slice service
operation";
}
/* Features */
/* Identities */
identity service-tag-type {
description
"Base identity for IETF Network Slice service tag type.";
}
identity service-tag-customer {
base service-tag-type;
description
"The IETF Network Slice service customer ID tag type.";
}
identity service-tag-service {
base service-tag-type;
description
"The IETF Network Slice service tag type.";
}
identity service-tag-opaque {
base service-tag-type;
description
"The IETF Network Slice service opaque tag type.";
}
identity attachment-circuit-tag-type {
description
"Base identity for the attachment circuit tag type.";
}
identity attachment-circuit-tag-vlan-id {
base attachment-circuit-tag-type;
description
"The attachment circuit VLAN ID tag type.";
}
identity attachment-circuit-tag-ip-mask {
base attachment-circuit-tag-type;
description
"The attachment circuit tag IP mask.";
}
identity service-isolation-type {
description
"Base identity for IETF Network slice service isolation level.";
}
identity service-isolation-shared {
base service-isolation-type;
description
"Shared resources (e.g. queues) are associated with the
slice service traffic. Hence, the traffic can be impacted
by effects of other services traffic
sharing the same resources.";
}
identity service-isolation-dedicated {
base service-isolation-type;
description
"Dedicated resources (e.g. queues) are associated with the
Network Slice service traffic. Hence, the service traffic
is isolated from other servceis traffic
sharing the same resources.";
}
identity service-security-type {
description
"Base identity for for slice service security level.";
}
identity service-security-authenticate {
base service-security-type;
description
"Indicates the slice service requires authentication.";
}
identity service-security-integrity {
base service-security-type;
description
"Indicates the slice service requires data integrity.";
}
identity service-security-encryption {
base service-security-type;
description
"Indicates the slice service requires data encryption.";
}
identity point-to-point {
base vpn-common:vpn-topology;
description
"Identity for point-to-point IETF Network Slice
service connectivity.";
}
identity point-to-multipoint {
base vpn-common:vpn-topology;
description
"Identity for point-to-point IETF Network Slice
service connectivity.";
}
identity multipoint-to-multipoint {
base vpn-common:vpn-topology;
description
"Identity for point-to-point IETF Network Slice
service connectivity.";
}
identity multipoint-to-point {
base vpn-common:vpn-topology;
description
"Identity for point-to-point IETF Network Slice
service connectivity.";
}
identity sender-role {
base vpn-common:role;
description
"A SDP is acting as a sender.";
}
identity receiver-role {
base vpn-common:role;
description
"A SDP is acting as a receiver.";
}
identity service-slo-metric-type {
description
"Base identity for IETF Network Slice service SLO metric type.";
Loading
Loading full blame…