| 1 |
<pre>Internet Engineering Task Force (IETF) Y. Lee |
| 2 |
Request for Comments: 8454 Huawei |
| 3 |
Category: Informational S. Belotti |
| 4 |
ISSN: 2070-1721 Nokia |
| 5 |
D. Dhody |
| 6 |
Huawei |
| 7 |
D. Ceccarelli |
| 8 |
Ericsson |
| 9 |
B. Yoon |
| 10 |
ETRI |
| 11 |
September 2018 |
| 12 |
|
| 13 |
|
| 14 |
<span class="h1">Information Model for Abstraction and Control of TE Networks (ACTN)</span> |
| 15 |
|
| 16 |
Abstract |
| 17 |
|
| 18 |
This document provides an information model for Abstraction and |
| 19 |
Control of TE Networks (ACTN). |
| 20 |
|
| 21 |
Status of This Memo |
| 22 |
|
| 23 |
This document is not an Internet Standards Track specification; it is |
| 24 |
published for informational purposes. |
| 25 |
|
| 26 |
This document is a product of the Internet Engineering Task Force |
| 27 |
(IETF). It represents the consensus of the IETF community. It has |
| 28 |
received public review and has been approved for publication by the |
| 29 |
Internet Engineering Steering Group (IESG). Not all documents |
| 30 |
approved by the IESG are candidates for any level of Internet |
| 31 |
Standard; see <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>. |
| 32 |
|
| 33 |
Information about the current status of this document, any errata, |
| 34 |
and how to provide feedback on it may be obtained at |
| 35 |
<a href="https://www.rfc-editor.org/info/rfc8454">https://www.rfc-editor.org/info/rfc8454</a>. |
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Lee, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2018 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 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 |
<span class="grey">Lee, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 116 |
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 117 |
<a href="#section-2">2</a>. ACTN Common Interfaces Information Model . . . . . . . . . . <a href="#page-5">5</a> |
| 118 |
<a href="#section-3">3</a>. Virtual Network Primitives . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 119 |
<a href="#section-3.1">3.1</a>. VN Instantiate . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 120 |
<a href="#section-3.2">3.2</a>. VN Modify . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 121 |
<a href="#section-3.3">3.3</a>. VN Delete . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 122 |
<a href="#section-3.4">3.4</a>. VN Update . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 123 |
<a href="#section-3.5">3.5</a>. VN Compute . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 124 |
<a href="#section-3.6">3.6</a>. VN Query . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 125 |
<a href="#section-4">4</a>. TE Primitives . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 126 |
<a href="#section-4.1">4.1</a>. TE Instantiate . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 127 |
<a href="#section-4.2">4.2</a>. TE Modify . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 128 |
<a href="#section-4.3">4.3</a>. TE Delete . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 129 |
<a href="#section-4.4">4.4</a>. TE Topology Update (for TE Resources) . . . . . . . . . . <a href="#page-9">9</a> |
| 130 |
<a href="#section-4.5">4.5</a>. Path Compute . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 131 |
<a href="#section-5">5</a>. VN Objects . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 132 |
<a href="#section-5.1">5.1</a>. VN Identifier . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 133 |
<a href="#section-5.2">5.2</a>. VN Service Characteristics . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 134 |
<a href="#section-5.3">5.3</a>. VN Endpoint . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 135 |
<a href="#section-5.4">5.4</a>. VN Objective Function . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 136 |
<a href="#section-5.5">5.5</a>. VN Action Status . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 137 |
<a href="#section-5.6">5.6</a>. VN Topology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 138 |
<a href="#section-5.7">5.7</a>. VN Member . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 139 |
<a href="#section-5.7.1">5.7.1</a>. VN Computed Path . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 140 |
<a href="#section-5.7.2">5.7.2</a>. VN Service Preference . . . . . . . . . . . . . . . . <a href="#page-16">16</a> |
| 141 |
<a href="#section-6">6</a>. TE Objects . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 142 |
<a href="#section-6.1">6.1</a>. TE Tunnel Characteristics . . . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 143 |
<a href="#section-7">7</a>. Mapping of VN Primitives with VN Objects . . . . . . . . . . <a href="#page-19">19</a> |
| 144 |
<a href="#section-8">8</a>. Mapping of TE Primitives with TE Objects . . . . . . . . . . <a href="#page-20">20</a> |
| 145 |
<a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 146 |
<a href="#section-10">10</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a> |
| 147 |
<a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a> |
| 148 |
<a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a> |
| 149 |
<a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-21">21</a> |
| 150 |
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a> |
| 151 |
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Lee, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 170 |
|
| 171 |
This document provides an information model for Abstraction and |
| 172 |
Control of TE Networks (ACTN). The information model described in |
| 173 |
this document covers the interface requirements identified in the |
| 174 |
ACTN Framework document [<a href="./rfc8453" title=""Framework for Abstraction and Control of TE Networks (ACTN)"">RFC8453</a>]. |
| 175 |
|
| 176 |
The ACTN reference architecture [<a href="./rfc8453" title=""Framework for Abstraction and Control of TE Networks (ACTN)"">RFC8453</a>] identifies a three-tier |
| 177 |
control hierarchy comprising the following as depicted in Figure 1: |
| 178 |
|
| 179 |
o Customer Network Controllers (CNCs) |
| 180 |
o Multi-Domain Service Coordinator (MDSC) |
| 181 |
o Provisioning Network Controllers (PNCs) |
| 182 |
|
| 183 |
+-------+ +-------+ +-------+ |
| 184 |
| CNC-A | | CNC-B | | CNC-C | |
| 185 |
+-------+ +-------+ +-------+ |
| 186 |
\ | / |
| 187 |
------------ | CMI ------------- |
| 188 |
\ | / |
| 189 |
+----------------------+ |
| 190 |
| MDSC | |
| 191 |
+----------------------+ |
| 192 |
/ | \ |
| 193 |
------------ | MPI ------------- |
| 194 |
/ | \ |
| 195 |
+-------+ +-------+ +-------+ |
| 196 |
| PNC | | PNC | | PNC | |
| 197 |
+-------+ +-------+ +-------+ |
| 198 |
|
| 199 |
Figure 1: A Three-Tier ACTN Control Hierarchy |
| 200 |
|
| 201 |
The two interfaces with respect to the MDSC, one north of the MDSC |
| 202 |
and the other south of the MDSC, are referred to as "CMI" (CNC-MDSC |
| 203 |
Interface) and "MPI" (MDSC-PNC Interface), respectively. This |
| 204 |
document models these two interfaces and derivative interfaces |
| 205 |
thereof (e.g., MDSC-to-MDSC in a hierarchy of MDSCs) as a single |
| 206 |
common interface. |
| 207 |
|
| 208 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span> |
| 209 |
|
| 210 |
The terms "Virtual Network (VN)" and "Virtual Network Service (VNS)" |
| 211 |
are defined in [<a href="./rfc8453" title=""Framework for Abstraction and Control of TE Networks (ACTN)"">RFC8453</a>]. Other key terms and concepts, for example, |
| 212 |
"abstraction", can be found in [<a href="./rfc7926" title=""Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks"">RFC7926</a>]. |
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Lee, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. ACTN Common Interfaces Information Model</span> |
| 226 |
|
| 227 |
This section provides an ACTN common interface information model to |
| 228 |
describe primitives, objects, their properties (represented as |
| 229 |
attributes), their relationships, and the resources for the service |
| 230 |
applications needed in the ACTN context. |
| 231 |
|
| 232 |
The standard interface is described between a client controller and a |
| 233 |
server controller. A client-server relationship is recursive between |
| 234 |
a CNC and an MDSC and between an MDSC and a PNC. In the CMI, the |
| 235 |
client is a CNC while the server is an MDSC. In the MPI, the client |
| 236 |
is an MDSC and the server is a PNC. There may also be MDSC-MDSC |
| 237 |
interfaces that need to be supported. This may arise in a hierarchy |
| 238 |
of MDSCs in which workloads may need to be partitioned to multiple |
| 239 |
MDSCs. |
| 240 |
|
| 241 |
Basic primitives (messages) are required between the CNC-MDSC and |
| 242 |
MDSC-PNC controllers. These primitives can then be used to support |
| 243 |
different ACTN network control functions like network topology |
| 244 |
requests/queries, VN service requests, path computation and |
| 245 |
connection control, VN service policy negotiation, enforcement, |
| 246 |
routing options, etc. |
| 247 |
|
| 248 |
There are two different types of primitives depending on the type of |
| 249 |
interface: |
| 250 |
|
| 251 |
o Virtual Network primitives at CMI |
| 252 |
o Traffic Engineering primitives at MPI |
| 253 |
|
| 254 |
As well described in [<a href="./rfc8453" title=""Framework for Abstraction and Control of TE Networks (ACTN)"">RFC8453</a>], at the CMI level, there is no need |
| 255 |
for detailed TE information since the basic functionality is to |
| 256 |
translate customer service information into VNS operation. |
| 257 |
|
| 258 |
At the MPI level, MDSC has the main scope for multi-domain |
| 259 |
coordination and creation of a single end-to-end (E2E) abstracted |
| 260 |
network view that is strictly related to TE information. |
| 261 |
|
| 262 |
As for topology, this document employs two types of topology. |
| 263 |
|
| 264 |
o The first type is referred to as "virtual network topology" and is |
| 265 |
associated with a VN. Virtual network topology is a customized |
| 266 |
topology for view and control by the customer. See <a href="#section-3.1">Section 3.1</a> |
| 267 |
for details. |
| 268 |
|
| 269 |
o The second type is referred to as "TE topology" and is associated |
| 270 |
with provider network operation on which we can apply policy to |
| 271 |
obtain the required level of abstraction to represent the |
| 272 |
underlying physical network topology. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Lee, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Virtual Network Primitives</span> |
| 282 |
|
| 283 |
This section provides a list of main VN primitives related to VNs and |
| 284 |
that are necessary to satisfy the ACTN requirements specified in |
| 285 |
[<a href="#ref-ACTN-REQ">ACTN-REQ</a>]. |
| 286 |
|
| 287 |
The following VN Action primitives are supported: |
| 288 |
|
| 289 |
o VN Instantiate |
| 290 |
|
| 291 |
o VN Modify |
| 292 |
|
| 293 |
o VN Delete |
| 294 |
|
| 295 |
o VN Update |
| 296 |
|
| 297 |
o VN Path Compute |
| 298 |
|
| 299 |
o VN Query |
| 300 |
|
| 301 |
VN Action is an object describing the main VN primitives. |
| 302 |
|
| 303 |
VN Action can assume one of the mentioned above primitives values. |
| 304 |
|
| 305 |
<VN Action> ::= <VN Instantiate> | |
| 306 |
|
| 307 |
<VN Modify> | |
| 308 |
|
| 309 |
<VN Delete> | |
| 310 |
|
| 311 |
<VN Update> | |
| 312 |
|
| 313 |
<VN Path Compute> | |
| 314 |
|
| 315 |
<VN Query> |
| 316 |
|
| 317 |
All these actions will solely happen at CMI level between CNC and |
| 318 |
MDSC. |
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Lee, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. VN Instantiate</span> |
| 338 |
|
| 339 |
VN Instantiate refers to an action from customers/applications to |
| 340 |
request the creation of VNs. VN Instantiate is for CNC-to-MDSC |
| 341 |
communication. Depending on the agreement between client and |
| 342 |
provider, VN instantiate can imply different VN operations. There |
| 343 |
are two types of VN instantiation: |
| 344 |
|
| 345 |
VN Type 1: VN is viewed as a set of edge-to-edge links (VN members). |
| 346 |
|
| 347 |
VN Type 2: VN is viewed as a VN-topology comprising virtual nodes |
| 348 |
and virtual links. |
| 349 |
|
| 350 |
Please see [<a href="./rfc8453" title=""Framework for Abstraction and Control of TE Networks (ACTN)"">RFC8453</a>] for full details regarding the types of VN. |
| 351 |
|
| 352 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. VN Modify</span> |
| 353 |
|
| 354 |
VN Modify refers to an action issued from customers/applications to |
| 355 |
modify an existing VN (i.e., an instantiated VN). VN Modify is for |
| 356 |
CNC-to-MDSC communication. |
| 357 |
|
| 358 |
VN Modify, depending of the type of VN instantiated, can be: |
| 359 |
|
| 360 |
1. a modification of the characteristics of VN members (edge-to-edge |
| 361 |
links) in the case of VN Type 1, or |
| 362 |
|
| 363 |
2. a modification of an existing virtual topology (e.g., adding/ |
| 364 |
deleting virtual nodes/links) in the case of VN Type 2. |
| 365 |
|
| 366 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. VN Delete</span> |
| 367 |
|
| 368 |
VN Delete refers to an action issued from customers/applications to |
| 369 |
delete an existing VN. VN Delete is for CNC-to-MDSC communication. |
| 370 |
|
| 371 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. VN Update</span> |
| 372 |
|
| 373 |
"VN Update" refers to any update to the VN that needs to be updated |
| 374 |
to the customers. VN Update is MDSC-to-CNC communication. VN Update |
| 375 |
fulfills a push model at the CMI level, making customers aware of any |
| 376 |
specific changes in the topology details related to the instantiated |
| 377 |
VN. |
| 378 |
|
| 379 |
VN Update, depending of the type of VN instantiated, can be: |
| 380 |
|
| 381 |
1. an update of VN members (edge-to-edge links) in case of VN Type |
| 382 |
1, or |
| 383 |
|
| 384 |
2. an update of virtual topology in case of VN Type 2. |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Lee, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 391 |
|
| 392 |
|
| 393 |
The connection-related information (e.g., Label Switched Paths |
| 394 |
(LSPs)) update association with VNs will be part of the "translation" |
| 395 |
function that happens in MDSC to map/translate VN request into TE |
| 396 |
semantics. This information will be provided in case the customer |
| 397 |
optionally wants to have more-detailed TE information associated with |
| 398 |
the instantiated VN. |
| 399 |
|
| 400 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. VN Compute</span> |
| 401 |
|
| 402 |
VN Compute consists of a Request and Reply. "VN Compute Request" |
| 403 |
refers to an action from customers/applications to request a VN |
| 404 |
computation. |
| 405 |
|
| 406 |
"VN Compute Reply" refers to the reply in response to VN Compute |
| 407 |
Request. |
| 408 |
|
| 409 |
A VN Compute Request/Reply is to be differentiated from a VN |
| 410 |
Instantiate. The purpose of VN Compute is a priori exploration to |
| 411 |
compute network resources availability and getting a possible VN view |
| 412 |
in which path details can be specified matching customer/applications |
| 413 |
constraints. This a priori exploration may not guarantee the |
| 414 |
availability of the computed network resources at the time of |
| 415 |
instantiation. |
| 416 |
|
| 417 |
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. VN Query</span> |
| 418 |
|
| 419 |
"VN Query" refers to an inquiry pertaining to a VN that has already |
| 420 |
been instantiated. VN Query fulfills a pull model that permits |
| 421 |
getting a topology view. |
| 422 |
|
| 423 |
"VN Query Reply" refers to the reply in response to a VN Query. The |
| 424 |
topology view returned by a VN Query Reply would be consistent with |
| 425 |
the topology type instantiated for any specific VN. |
| 426 |
|
| 427 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. TE Primitives</span> |
| 428 |
|
| 429 |
This section provides a list of the main TE primitives necessary to |
| 430 |
satisfy ACTN requirements specified in [<a href="#ref-ACTN-REQ">ACTN-REQ</a>] related to typical |
| 431 |
TE operations supported at the MPI level. |
| 432 |
|
| 433 |
The TE action primitives defined in this section should be supported |
| 434 |
at the MPI consistently with the type of topology defined at the CMI. |
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Lee, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 447 |
|
| 448 |
|
| 449 |
The following TE action primitives are supported: |
| 450 |
|
| 451 |
o TE Instantiate/Modify/Delete |
| 452 |
|
| 453 |
o TE Topology Update (see <a href="#section-4.4">Section 4.4</a>. for the description) |
| 454 |
|
| 455 |
o Path Compute |
| 456 |
|
| 457 |
TE Action is an object describing the main TE primitives. |
| 458 |
|
| 459 |
TE Action can assume one of the mentioned above primitives values. |
| 460 |
|
| 461 |
<TE Action> ::= <TE Instantiate> | |
| 462 |
|
| 463 |
<TE Modify> | |
| 464 |
|
| 465 |
<TE Delete> | |
| 466 |
|
| 467 |
<TE Topology Update> | |
| 468 |
<Path Compute> | |
| 469 |
|
| 470 |
All these actions will solely happen at MPI level between MDSC and |
| 471 |
PNC. |
| 472 |
|
| 473 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. TE Instantiate</span> |
| 474 |
|
| 475 |
"TE Instantiate" refers to an action issued from MDSC to PNC to |
| 476 |
instantiate new TE tunnels. |
| 477 |
|
| 478 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. TE Modify</span> |
| 479 |
|
| 480 |
"TE Modify" refers to an action issued from MDSC to PNC to modify |
| 481 |
existing TE tunnels. |
| 482 |
|
| 483 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. TE Delete</span> |
| 484 |
|
| 485 |
"TE Delete" refers to an action issued from MDSC to PNC to delete |
| 486 |
existing TE tunnels. |
| 487 |
|
| 488 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. TE Topology Update (for TE Resources)</span> |
| 489 |
|
| 490 |
TE Topology Update is a primitive specifically related to MPI used to |
| 491 |
provide a TE resource update between any domain controller and MDSC |
| 492 |
regarding the entire content of any actual TE topology of a domain |
| 493 |
controller or an abstracted filtered view of TE topology depending on |
| 494 |
negotiated policy. |
| 495 |
|
| 496 |
See [<a href="#ref-TE-TOPO" title=""YANG Data Model for Traffic Engineering (TE) Topologies"">TE-TOPO</a>] for detailed YANG implementation of TE topology update. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Lee, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 503 |
|
| 504 |
|
| 505 |
<TE Topology Update> ::= <TE-topology-list> |
| 506 |
|
| 507 |
<TE-topology-list> ::= <TE-topology> [<TE-topology-list>] |
| 508 |
|
| 509 |
<TE-topology> ::= [<Abstraction>] <TE-Topology-identifier> <Node- |
| 510 |
list> <Link-list> |
| 511 |
<Node-list> ::= <Node>[<Node-list>] |
| 512 |
|
| 513 |
<Node> ::= <Node> <TE Termination Point-list> |
| 514 |
|
| 515 |
<TE Termination Point-list> ::= <TE Termination Point> [<TE- |
| 516 |
Termination Point-list>] |
| 517 |
|
| 518 |
<Link-list> ::= <Link>[<Link-list>] |
| 519 |
|
| 520 |
Where |
| 521 |
|
| 522 |
Abstraction provides information on the level of abstraction (as |
| 523 |
determined a priori). |
| 524 |
|
| 525 |
TE-topology-identifier is an identifier that identifies a specific |
| 526 |
te-topology, e.g., te-types:te-topology-id [<a href="#ref-TE-TOPO" title=""YANG Data Model for Traffic Engineering (TE) Topologies"">TE-TOPO</a>]. |
| 527 |
|
| 528 |
Node-list is detailed information related to a specific node |
| 529 |
belonging to a te-topology, e.g., te-node-attributes [<a href="#ref-TE-TOPO" title=""YANG Data Model for Traffic Engineering (TE) Topologies"">TE-TOPO</a>]. |
| 530 |
|
| 531 |
Link-list is information related to the specific link related |
| 532 |
belonging to a te-topology, e.g., te-link-attributes [<a href="#ref-TE-TOPO" title=""YANG Data Model for Traffic Engineering (TE) Topologies"">TE-TOPO</a>]. |
| 533 |
|
| 534 |
TE Termination Point-list is detailed information associated with the |
| 535 |
termination points of a te-link related to a specific node, e.g., |
| 536 |
interface-switching-capability [<a href="#ref-TE-TOPO" title=""YANG Data Model for Traffic Engineering (TE) Topologies"">TE-TOPO</a>]. |
| 537 |
|
| 538 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Path Compute</span> |
| 539 |
|
| 540 |
Path Compute consists of Request and Reply. "Path Compute Request" |
| 541 |
refers to an action from MDSC to PNC to request a path computation. |
| 542 |
|
| 543 |
"Path Compute Reply" refers to the reply in response to the Path |
| 544 |
Compute Request. |
| 545 |
|
| 546 |
The context of Path Compute is described in [<a href="#ref-Path-Compute">Path-Compute</a>]. |
| 547 |
|
| 548 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. VN Objects</span> |
| 549 |
|
| 550 |
This section provides a list of objects associated to VN action |
| 551 |
primitives. |
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Lee, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. VN Identifier</span> |
| 562 |
|
| 563 |
A VN Identifier is a unique identifier of the VN. |
| 564 |
|
| 565 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. VN Service Characteristics</span> |
| 566 |
|
| 567 |
VN Service Characteristics describes the customer/application |
| 568 |
requirements against the VNs to be instantiated. |
| 569 |
|
| 570 |
<VN Service Characteristics> ::= <VN Connectivity Type> |
| 571 |
|
| 572 |
<VN Directionality> |
| 573 |
|
| 574 |
(<VN Traffic Matrix>...) |
| 575 |
|
| 576 |
<VN Survivability> |
| 577 |
|
| 578 |
Where |
| 579 |
|
| 580 |
<VN Connectivity Type> ::= <P2P>|<P2MP>|<MP2MP>|<MP2P>|<Multi- |
| 581 |
destination> |
| 582 |
|
| 583 |
The Connectivity Type identifies the type of required VN Service. In |
| 584 |
addition to the classical types of services (e.g., P2P/P2MP, etc.), |
| 585 |
ACTN defines the "multi-destination" service that is a new P2P |
| 586 |
service where the endpoints are not fixed. They can be chosen among |
| 587 |
a list of preconfigured endpoints or dynamically provided by the CNC. |
| 588 |
|
| 589 |
VN Directionality indicates if a VN is unidirectional or |
| 590 |
bidirectional. This implies that each VN member that belongs to the |
| 591 |
VN has the same directionality as the VN. |
| 592 |
|
| 593 |
<VN Traffic Matrix> ::= <Bandwidth> |
| 594 |
|
| 595 |
[<VN Constraints>] |
| 596 |
|
| 597 |
The VN Traffic Matrix represents the traffic matrix parameters for |
| 598 |
the required service connectivity. Bandwidth is a mandatory |
| 599 |
parameter, and a number of optional constraints can be specified in |
| 600 |
the VN Constraints (e.g., diversity, cost). They can include |
| 601 |
objective functions and TE metric bounds as specified in [<a href="./rfc5541" title=""Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"">RFC5541</a>]. |
| 602 |
|
| 603 |
Further details on the VN constraints are specified below: |
| 604 |
|
| 605 |
<VN Constraints> ::= [<Layer Protocol>] |
| 606 |
[<Diversity>] |
| 607 |
|
| 608 |
( <Metric> | <VN Objective Function> ) |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Lee, et al. Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 615 |
|
| 616 |
|
| 617 |
Where: |
| 618 |
|
| 619 |
Layer Protocol identifies the layer topology at which the VN |
| 620 |
service is requested. It could be, for example, MPLS, Optical |
| 621 |
Data Unit (ODU), and Optical Channel (OCh). |
| 622 |
|
| 623 |
Diversity allows asking for diversity constraints for a VN |
| 624 |
Instantiate/Modify or a VN Path Compute. For example, a new VN or |
| 625 |
a path is requested in total diversity from an existing one (e.g., |
| 626 |
diversity exclusion). |
| 627 |
|
| 628 |
<Diversity> ::= (<VN-exclusion> (<VN-id>...)) | |
| 629 |
|
| 630 |
(<VN-Member-exclusion> (<VN-Member-id>...)) |
| 631 |
|
| 632 |
Metric can include all the Metrics (cost, delay, delay variation, |
| 633 |
latency) and bandwidth utilization parameters defined and |
| 634 |
referenced by [<a href="./rfc3630" title=""Traffic Engineering (TE) Extensions to OSPF Version 2"">RFC3630</a>] and [<a href="./rfc7471" title=""OSPF Traffic Engineering (TE) Metric Extensions"">RFC7471</a>]. |
| 635 |
|
| 636 |
As for VN Objective Function, see <a href="#section-5.4">Section 5.4</a>. |
| 637 |
|
| 638 |
VN Survivability describes all attributes related to the VN recovery |
| 639 |
level and its survivability policy enforced by the customers/ |
| 640 |
applications. |
| 641 |
|
| 642 |
<VN Survivability> ::= <VN Recovery Level> |
| 643 |
|
| 644 |
[<VN Tunnel Recovery Level>] |
| 645 |
|
| 646 |
[<VN Survivability Policy>] |
| 647 |
Where: |
| 648 |
|
| 649 |
VN Recovery Level is a value representing the requested level |
| 650 |
of resiliency required against the VN. The following values |
| 651 |
are defined: |
| 652 |
|
| 653 |
o Unprotected VN |
| 654 |
|
| 655 |
o VN with per tunnel recovery: The recovery level is defined |
| 656 |
against the tunnels composing the VN, and it is specified in |
| 657 |
the VN Tunnel Recovery Level. |
| 658 |
|
| 659 |
<VN Tunnel Recovery Level> ::= <0:1>|<1+1>|<1:1>|<1:N>|<M:N>| |
| 660 |
<On the fly restoration> |
| 661 |
|
| 662 |
The VN Tunnel Recovery Level indicates the type of protection |
| 663 |
or restoration mechanism applied to the VN. It augments the |
| 664 |
recovery types defined in [<a href="./rfc4427" title=""Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)"">RFC4427</a>]. |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Lee, et al. Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 671 |
|
| 672 |
|
| 673 |
<VN Survivability Policy> ::= [<Local Reroute Allowed>] |
| 674 |
|
| 675 |
[<Domain Preference>] |
| 676 |
|
| 677 |
[<Push Allowed>] |
| 678 |
|
| 679 |
[<Incremental Update>] |
| 680 |
|
| 681 |
Where: |
| 682 |
|
| 683 |
Local Reroute Allowed is a delegation policy to the Server on |
| 684 |
whether or not to allow a local reroute fix upon a failure of |
| 685 |
the primary LSP. |
| 686 |
|
| 687 |
Domain Preference is only applied on the MPI where the MDSC |
| 688 |
(client) provides a domain preference to each PNC (server), |
| 689 |
e.g., when an inter-domain link fails, then PNC can choose the |
| 690 |
alternative peering with this info. |
| 691 |
|
| 692 |
Push Allowed is a policy that allows a server to trigger an |
| 693 |
updated VN topology upon failure without an explicit request |
| 694 |
from the client. Push action can be set as default unless |
| 695 |
otherwise specified. |
| 696 |
|
| 697 |
Incremental Update is another policy that triggers an |
| 698 |
incremental update from the server since the last period of |
| 699 |
update. Incremental update can be set as default unless |
| 700 |
otherwise specified. |
| 701 |
|
| 702 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. VN Endpoint</span> |
| 703 |
|
| 704 |
VN End-Point Object describes the VN's customer endpoint |
| 705 |
characteristics. |
| 706 |
|
| 707 |
<VN End-Point> ::= (<Access Point Identifier> |
| 708 |
|
| 709 |
[<Access Link Capability>] |
| 710 |
[<Source Indicator>])... |
| 711 |
|
| 712 |
Where: |
| 713 |
|
| 714 |
Access Point Identifier represents a unique identifier of the |
| 715 |
client endpoint. They are used by the customer to ask for the |
| 716 |
setup of a virtual network instantiation. A VN End-Point is |
| 717 |
defined against each AP in the network and is shared between |
| 718 |
customer and provider. Both the customer and the provider will map |
| 719 |
it against their own physical resources. |
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Lee, et al. Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 727 |
|
| 728 |
|
| 729 |
Access Link Capability identifies the capabilities of the access |
| 730 |
link related to the given access point (e.g., max-bandwidth, |
| 731 |
bandwidth availability, etc.). |
| 732 |
|
| 733 |
Source Indicator indicates whether or not an endpoint is the |
| 734 |
source. |
| 735 |
|
| 736 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. VN Objective Function</span> |
| 737 |
|
| 738 |
The VN Objective Function applies to each VN member (i.e., each E2E |
| 739 |
tunnel) of a VN. |
| 740 |
|
| 741 |
The VN Objective Function can reuse objective functions defined in |
| 742 |
<a href="./rfc5541#section-4">Section 4 of [RFC5541]</a>. |
| 743 |
|
| 744 |
For a single path computation, the following objective functions are |
| 745 |
defined: |
| 746 |
|
| 747 |
o MCP is the Minimum Cost Path with respect to a specific metric |
| 748 |
(e.g., shortest path). |
| 749 |
|
| 750 |
o MLP is the Minimum Load Path, meaning find a path composted by te- |
| 751 |
link least loaded. |
| 752 |
|
| 753 |
o MBP is the Maximum residual Bandwidth Path. |
| 754 |
|
| 755 |
For a concurrent path computation, the following objective functions |
| 756 |
are defined: |
| 757 |
|
| 758 |
o MBC is to Minimize aggregate Bandwidth Consumption. |
| 759 |
|
| 760 |
o MLL is to Minimize the Load of the most loaded Link. |
| 761 |
|
| 762 |
o MCC is to Minimize the Cumulative Cost of a set of paths. |
| 763 |
|
| 764 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. VN Action Status</span> |
| 765 |
|
| 766 |
VN Action Status is the status indicator whether or not the VN has |
| 767 |
been successfully instantiated, modified, or deleted in the server |
| 768 |
network in response to a particular VN action. |
| 769 |
|
| 770 |
Note that this action status object can be implicitly indicated and, |
| 771 |
thus, not included in any of the VN primitives discussed in |
| 772 |
<a href="#section-3">Section 3</a>. |
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Lee, et al. Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. VN Topology</span> |
| 786 |
|
| 787 |
When a VN is seen by the customer as a topology, it is referred to as |
| 788 |
"VN topology". This is associated with VN Type 2, which is composed |
| 789 |
of virtual nodes and virtual links. |
| 790 |
|
| 791 |
<VN Topology> ::= <Virtual node list> <Virtual link list> |
| 792 |
|
| 793 |
<Virtual node list> ::= <Virtual node> [<Virtual node list>] |
| 794 |
|
| 795 |
<Virtual link list> :: = <Virtual link> [<Virtual link list>] |
| 796 |
|
| 797 |
<span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. VN Member</span> |
| 798 |
|
| 799 |
VN Member describes details of a VN Member that is a list of a set of |
| 800 |
VN Members represented as VN_Member_List. |
| 801 |
|
| 802 |
<VN_Member_List> ::= <VN Member> [<VN_Member_List>] |
| 803 |
|
| 804 |
Where <VN Member> ::= <Ingress VN End-Point> |
| 805 |
|
| 806 |
[<VN Associated LSP>] |
| 807 |
|
| 808 |
<Egress VN End-Point> |
| 809 |
|
| 810 |
Ingress VN End-Point is the VN End-Point information for the ingress |
| 811 |
portion of the AP. See <a href="#section-5.3">Section 5.3</a> for VN End-Point details. |
| 812 |
|
| 813 |
Egress VN End-Point is the VN End-Point information for the egress |
| 814 |
portion of the AP. See <a href="#section-5.3">Section 5.3</a> for VN End-Point details. |
| 815 |
|
| 816 |
VN Associated LSP describes the instantiated LSPs in the Provider's |
| 817 |
network for the VN Type 1. It describes the instantiated LSPs over |
| 818 |
the VN topology for VN Type 2. |
| 819 |
|
| 820 |
<span class="h4"><a class="selflink" id="section-5.7.1" href="#section-5.7.1">5.7.1</a>. VN Computed Path</span> |
| 821 |
|
| 822 |
The VN Computed Path is the list of paths obtained after the VN path |
| 823 |
computation request from a higher controller. Note that the computed |
| 824 |
path is to be distinguished from the LSP. When the computed path is |
| 825 |
signaled in the network (and thus the resource is reserved for that |
| 826 |
path), it becomes an LSP. |
| 827 |
|
| 828 |
<VN Computed Path> ::= (<Path>...) |
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Lee, et al. Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h4"><a class="selflink" id="section-5.7.2" href="#section-5.7.2">5.7.2</a>. VN Service Preference</span> |
| 842 |
|
| 843 |
This section provides the VN Service preference. VN Service is |
| 844 |
defined in <a href="#section-2">Section 2</a>. |
| 845 |
|
| 846 |
<VN Service Preference> ::= [<Location Service Preference >] |
| 847 |
|
| 848 |
[<Client-specific Preference >] |
| 849 |
|
| 850 |
[<End-Point Dynamic Selection Preference >] |
| 851 |
|
| 852 |
Where |
| 853 |
|
| 854 |
Location Service Preference describes the End-Point Location's |
| 855 |
(e.g., data centers (DCs)) support for certain Virtual Network |
| 856 |
Functions (VNFs) (e.g., security function, firewall capability, |
| 857 |
etc.) and is used to find the path that satisfies the VNF |
| 858 |
constraint. |
| 859 |
|
| 860 |
Client-specific Preference describes any preference related to VNS |
| 861 |
that an application/client can enforce via CNC towards lower-level |
| 862 |
controllers. For example, CNC can enforce client-specific |
| 863 |
preferences, e.g., selection of a destination DC from the set of |
| 864 |
candidate DCs based on some criteria in the context of Virtual |
| 865 |
Machine (VM) migration. MSDC/PNC should then provide the DC |
| 866 |
interconnection that supports the Client-specific Preference. |
| 867 |
|
| 868 |
End-Point Dynamic Selection Preference describes if the endpoint |
| 869 |
(e.g., DC) can support load-balancing, disaster recovery, or VM |
| 870 |
migration and so can be part of the selection by MDSC following |
| 871 |
service Preference enforcement by CNC. |
| 872 |
|
| 873 |
|
| 874 |
|
| 875 |
|
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Lee, et al. Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. TE Objects</span> |
| 898 |
|
| 899 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. TE Tunnel Characteristics</span> |
| 900 |
|
| 901 |
Tunnel Characteristics describes the parameters needed to configure |
| 902 |
TE tunnel. |
| 903 |
|
| 904 |
<TE Tunnel Characteristics> ::= [<Tunnel Type>] |
| 905 |
|
| 906 |
<Tunnel Id> |
| 907 |
|
| 908 |
[<Tunnel Layer>] |
| 909 |
|
| 910 |
[<Tunnel end-point>] |
| 911 |
|
| 912 |
[<Tunnel protection-restoration>] |
| 913 |
|
| 914 |
<Tunnel Constraints> |
| 915 |
|
| 916 |
[<Tunnel Optimization>] |
| 917 |
|
| 918 |
Where |
| 919 |
|
| 920 |
<Tunnel Type> ::= <P2P>|<P2MP>|<MP2MP>|<MP2P> |
| 921 |
|
| 922 |
The Tunnel Type identifies the type of required tunnel. In this |
| 923 |
document, only the P2P model is provided. |
| 924 |
|
| 925 |
Tunnel Id is the TE tunnel identifier |
| 926 |
|
| 927 |
Tunnel Layer represents the layer technology of the LSPs supporting |
| 928 |
the tunnel |
| 929 |
|
| 930 |
<Tunnel End Points> ::= <Source> <Destination> |
| 931 |
|
| 932 |
<Tunnel protection-restoration> ::= <prot 0:1>|<prot 1+1>|<prot |
| 933 |
1:1>|<prot 1:N>|prot <M:N>|<restoration> |
| 934 |
Tunnel Constraints are the base tunnel configuration constraints |
| 935 |
parameters. |
| 936 |
|
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Lee, et al. Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 951 |
|
| 952 |
|
| 953 |
Where <Tunnel Constraints> ::= [<Topology Id>] |
| 954 |
|
| 955 |
[<Bandwidth>] |
| 956 |
|
| 957 |
[<Disjointness>] |
| 958 |
|
| 959 |
[<SRLG>] |
| 960 |
|
| 961 |
[<Priority>] |
| 962 |
|
| 963 |
[<Affinities>] |
| 964 |
|
| 965 |
[<Tunnel Optimization>] |
| 966 |
|
| 967 |
[<Objective Function>] |
| 968 |
|
| 969 |
Topology Id references the topology used to compute the tunnel path. |
| 970 |
|
| 971 |
Bandwidth is the bandwidth used as a parameter in path computation. |
| 972 |
|
| 973 |
<Disjointness> ::= <node> | <link> | <srlg> |
| 974 |
|
| 975 |
Disjointness provides the type of resources from which the tunnel has |
| 976 |
to be disjointed. |
| 977 |
|
| 978 |
Shared Risk Link Group (SRLG) is a group of physical resources |
| 979 |
impacted by the same risk from which an E2E tunnel is required to be |
| 980 |
disjointed. |
| 981 |
|
| 982 |
<Priority> ::= <Holding Priority> <Setup Priority> |
| 983 |
|
| 984 |
where |
| 985 |
|
| 986 |
Setup Priority indicates the level of priority for taking resources |
| 987 |
from another tunnel [<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>]. |
| 988 |
|
| 989 |
Holding Priority indicates the level of priority to hold resources |
| 990 |
avoiding preemption from another tunnel [<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>]. |
| 991 |
|
| 992 |
Affinities represents the structure to validate a link belonging to |
| 993 |
the path of the tunnel [<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>]. |
| 994 |
|
| 995 |
<Tunnel Optimization> ::= <Metric> | <Objective Function> |
| 996 |
|
| 997 |
Metric can include all the Metrics (cost, delay, delay variation, |
| 998 |
latency) and bandwidth utilization parameters defined and referenced |
| 999 |
by [<a href="./rfc3630" title=""Traffic Engineering (TE) Extensions to OSPF Version 2"">RFC3630</a>] and [<a href="./rfc7471" title=""OSPF Traffic Engineering (TE) Metric Extensions"">RFC7471</a>]. |
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Lee, et al. Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<Objective Function> ::= <objective function type> |
| 1010 |
|
| 1011 |
<objective function type> ::= <MCP> | <MLP> | <MBP> | <MBC> | <MLL> |
| 1012 |
| <MCC> |
| 1013 |
|
| 1014 |
See <a href="#section-5.4">Section 5.4</a> for a description of objective function type. |
| 1015 |
|
| 1016 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Mapping of VN Primitives with VN Objects</span> |
| 1017 |
|
| 1018 |
This section describes the mapping of VN primitives with VN Objects |
| 1019 |
based on <a href="#section-5">Section 5</a>. |
| 1020 |
|
| 1021 |
<VN Instantiate> ::= <VN Service Characteristics> |
| 1022 |
|
| 1023 |
<VN Member-List> |
| 1024 |
|
| 1025 |
[<VN Service Preference>] |
| 1026 |
|
| 1027 |
[<VN Topology>] |
| 1028 |
|
| 1029 |
<VN Modify> ::= <VN identifier> |
| 1030 |
|
| 1031 |
<VN Service Characteristics> |
| 1032 |
|
| 1033 |
<VN Member-List> |
| 1034 |
|
| 1035 |
[<VN Service Preference>] |
| 1036 |
|
| 1037 |
[<VN Topology>] |
| 1038 |
|
| 1039 |
<VN Delete> ::= <VN Identifier> |
| 1040 |
|
| 1041 |
<VN Update> :: = <VN Identifier> |
| 1042 |
[<VN Member-List>] |
| 1043 |
|
| 1044 |
[<VN Topology>] |
| 1045 |
|
| 1046 |
<VN Path Compute Request> ::= <VN Service Characteristics> |
| 1047 |
|
| 1048 |
<VN Member-List> |
| 1049 |
|
| 1050 |
[<VN Service Preference>] |
| 1051 |
|
| 1052 |
<VN Path Compute Reply> ::= <VN Computed Path> |
| 1053 |
|
| 1054 |
<VN Query> ::= <VN Identifier> |
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Lee, et al. Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<VN Query Reply> ::= <VN Identifier> |
| 1066 |
|
| 1067 |
<VN Associated LSP> |
| 1068 |
|
| 1069 |
[<TE Topology Reference>] |
| 1070 |
|
| 1071 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Mapping of TE Primitives with TE Objects</span> |
| 1072 |
|
| 1073 |
This section describes the mapping of TE primitives with TE Objects |
| 1074 |
based on <a href="#section-6">Section 6</a>. |
| 1075 |
|
| 1076 |
<TE Instantiate> ::= <TE Tunnel Characteristics> |
| 1077 |
|
| 1078 |
<TE Modify> ::= <TE Tunnel Characteristics> |
| 1079 |
|
| 1080 |
<TE Delete> ::= <Tunnel Id> |
| 1081 |
<TE Topology Update> ::= <TE-topology-list> |
| 1082 |
|
| 1083 |
<Path Compute Request> ::= <TE Tunnel Characteristics> |
| 1084 |
|
| 1085 |
<Path Compute Reply> ::= <TE Computed Path> |
| 1086 |
|
| 1087 |
<TE Tunnel Characteristics> |
| 1088 |
|
| 1089 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span> |
| 1090 |
|
| 1091 |
The ACTN information model is not directly relevant when considering |
| 1092 |
potential security issues. Rather, it defines a set of interfaces |
| 1093 |
for TE networks. The underlying protocols, procedures, and |
| 1094 |
implementations used to exchange the information model described in |
| 1095 |
this document will need to secure the request and control of |
| 1096 |
resources with proper authentication and authorization mechanisms. |
| 1097 |
In addition, the data exchanged over the ACTN interfaces discussed in |
| 1098 |
this document requires verification of data integrity. Backup or |
| 1099 |
redundancies should also be available to restore the affected data to |
| 1100 |
its correct state. |
| 1101 |
|
| 1102 |
Implementations of the ACTN framework will have distributed |
| 1103 |
functional components that will exchange an instantiation that |
| 1104 |
adheres to this information model. Implementations should encrypt |
| 1105 |
data that flows between them, especially when they are implemented at |
| 1106 |
remote nodes and irrespective of whether these data flows are on |
| 1107 |
external or internal network interfaces. The information model may |
| 1108 |
contain customer, application, and network data that, for business or |
| 1109 |
privacy reasons, may be considered sensitive. It should be stored |
| 1110 |
only in an encrypted data store. |
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Lee, et al. Informational [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
The ACTN security discussion is further split into two specific |
| 1122 |
interfaces: |
| 1123 |
|
| 1124 |
o Interface between the CNC and MDSC, CNC-MDSC Interface (CMI) |
| 1125 |
|
| 1126 |
o Interface between the MDSC and PNC, MDSC-PNC Interface (MPI). |
| 1127 |
|
| 1128 |
See the detailed discussion of the CMI and MPI in Sections <a href="#section-9.1">9.1</a> and |
| 1129 |
9.2 (respectively) in [<a href="./rfc8453" title=""Framework for Abstraction and Control of TE Networks (ACTN)"">RFC8453</a>]. |
| 1130 |
|
| 1131 |
The conclusion is that all data models and protocols used to realize |
| 1132 |
the ACTN information model should have rich security features, as |
| 1133 |
discussed in this section. Additional security risks may still |
| 1134 |
exist. Therefore, discussion and applicability of specific security |
| 1135 |
functions and protocols will be better described in documents that |
| 1136 |
are use case and environment specific. |
| 1137 |
|
| 1138 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span> |
| 1139 |
|
| 1140 |
This document has no IANA actions. |
| 1141 |
|
| 1142 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span> |
| 1143 |
|
| 1144 |
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span> |
| 1145 |
|
| 1146 |
[<a id="ref-RFC8453">RFC8453</a>] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for |
| 1147 |
Abstraction and Control of TE Networks (ACTN)", <a href="./rfc8453">RFC 8453</a>, |
| 1148 |
DOI 10.17487/RFC8453, August 2018, |
| 1149 |
<<a href="https://www.rfc-editor.org/info/rfc8453">https://www.rfc-editor.org/info/rfc8453</a>>. |
| 1150 |
|
| 1151 |
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span> |
| 1152 |
|
| 1153 |
[<a id="ref-ACTN-REQ">ACTN-REQ</a>] |
| 1154 |
Lee, Y., Ceccarelli, D., Miyasaka, T., Shin, J., and K. |
| 1155 |
Lee, "Requirements for Abstraction and Control of TE |
| 1156 |
Networks", Work in Progress, |
| 1157 |
<a href="./draft-ietf-teas-actn-requirements-09">draft-ietf-teas-actn-requirements-09</a>, March 2018. |
| 1158 |
|
| 1159 |
[<a id="ref-Path-Compute">Path-Compute</a>] |
| 1160 |
Busi, I., Belotti, S., Lopezalvarez, V., Dios, O., Sharma, |
| 1161 |
A., Shi, Y., Vilata, R., and K. Sethuraman, "Yang model |
| 1162 |
for requesting Path Computation", Work in Progress, |
| 1163 |
<a href="./draft-ietf-teas-yang-path-computation-02">draft-ietf-teas-yang-path-computation-02</a>, June 2018. |
| 1164 |
|
| 1165 |
[<a id="ref-RFC3209">RFC3209</a>] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., |
| 1166 |
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP |
| 1167 |
Tunnels", <a href="./rfc3209">RFC 3209</a>, DOI 10.17487/RFC3209, December 2001, |
| 1168 |
<<a href="https://www.rfc-editor.org/info/rfc3209">https://www.rfc-editor.org/info/rfc3209</a>>. |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Lee, et al. Informational [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
[<a id="ref-RFC3630">RFC3630</a>] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering |
| 1178 |
(TE) Extensions to OSPF Version 2", <a href="./rfc3630">RFC 3630</a>, |
| 1179 |
DOI 10.17487/RFC3630, September 2003, |
| 1180 |
<<a href="https://www.rfc-editor.org/info/rfc3630">https://www.rfc-editor.org/info/rfc3630</a>>. |
| 1181 |
|
| 1182 |
[<a id="ref-RFC4427">RFC4427</a>] Mannie, E., Ed. and D. Papadimitriou, Ed., "Recovery |
| 1183 |
(Protection and Restoration) Terminology for Generalized |
| 1184 |
Multi-Protocol Label Switching (GMPLS)", <a href="./rfc4427">RFC 4427</a>, |
| 1185 |
DOI 10.17487/RFC4427, March 2006, |
| 1186 |
<<a href="https://www.rfc-editor.org/info/rfc4427">https://www.rfc-editor.org/info/rfc4427</a>>. |
| 1187 |
|
| 1188 |
[<a id="ref-RFC5541">RFC5541</a>] Le Roux, JL., Vasseur, JP., and Y. Lee, "Encoding of |
| 1189 |
Objective Functions in the Path Computation Element |
| 1190 |
Communication Protocol (PCEP)", <a href="./rfc5541">RFC 5541</a>, |
| 1191 |
DOI 10.17487/RFC5541, June 2009, |
| 1192 |
<<a href="https://www.rfc-editor.org/info/rfc5541">https://www.rfc-editor.org/info/rfc5541</a>>. |
| 1193 |
|
| 1194 |
[<a id="ref-RFC7471">RFC7471</a>] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. |
| 1195 |
Previdi, "OSPF Traffic Engineering (TE) Metric |
| 1196 |
Extensions", <a href="./rfc7471">RFC 7471</a>, DOI 10.17487/RFC7471, March 2015, |
| 1197 |
<<a href="https://www.rfc-editor.org/info/rfc7471">https://www.rfc-editor.org/info/rfc7471</a>>. |
| 1198 |
|
| 1199 |
[<a id="ref-RFC7926">RFC7926</a>] Farrel, A., Ed., Drake, J., Bitar, N., Swallow, G., |
| 1200 |
Ceccarelli, D., and X. Zhang, "Problem Statement and |
| 1201 |
Architecture for Information Exchange between |
| 1202 |
Interconnected Traffic-Engineered Networks", <a href="https://www.rfc-editor.org/bcp/bcp206">BCP 206</a>, |
| 1203 |
<a href="./rfc7926">RFC 7926</a>, DOI 10.17487/RFC7926, July 2016, |
| 1204 |
<<a href="https://www.rfc-editor.org/info/rfc7926">https://www.rfc-editor.org/info/rfc7926</a>>. |
| 1205 |
|
| 1206 |
[<a id="ref-TE-TOPO">TE-TOPO</a>] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and |
| 1207 |
O. Dios, "YANG Data Model for Traffic Engineering (TE) |
| 1208 |
Topologies", Work in Progress, |
| 1209 |
<a href="./draft-ietf-teas-yang-te-topo-18">draft-ietf-teas-yang-te-topo-18</a>, June 2018. |
| 1210 |
|
| 1211 |
Contributors |
| 1212 |
|
| 1213 |
Haomian Zheng |
| 1214 |
Huawei Technologies |
| 1215 |
Email: [email protected] |
| 1216 |
|
| 1217 |
Xian Zhang |
| 1218 |
Huawei Technologies |
| 1219 |
Email: [email protected] |
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Lee, et al. Informational [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc8454">RFC 8454</a> ACTN Info Model September 2018</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
Authors' Addresses |
| 1234 |
|
| 1235 |
Young Lee (Editor) |
| 1236 |
Huawei Technologies |
| 1237 |
5340 Legacy Drive |
| 1238 |
Plano, TX 75023, USA |
| 1239 |
|
| 1240 |
Phone: (469)277-5838 |
| 1241 |
Email: [email protected] |
| 1242 |
|
| 1243 |
|
| 1244 |
Sergio Belotti (Editor) |
| 1245 |
Nokia |
| 1246 |
Via Trento, 30 |
| 1247 |
Vimercate, Italy |
| 1248 |
|
| 1249 |
Email: [email protected] |
| 1250 |
|
| 1251 |
|
| 1252 |
Dhruv Dhody |
| 1253 |
Huawei Technologies, |
| 1254 |
Divyashree Technopark, Whitefield |
| 1255 |
Bangalore, India |
| 1256 |
|
| 1257 |
Email: [email protected] |
| 1258 |
|
| 1259 |
|
| 1260 |
Daniele Ceccarelli |
| 1261 |
Ericsson |
| 1262 |
Torshamnsgatan,48 |
| 1263 |
Stockholm, Sweden |
| 1264 |
|
| 1265 |
Email: [email protected] |
| 1266 |
|
| 1267 |
|
| 1268 |
Bin Yeong Yoon |
| 1269 |
ETRI |
| 1270 |
|
| 1271 |
Email: [email protected] |
| 1272 |
|
| 1273 |
|
| 1274 |
|
| 1275 |
|
| 1276 |
|
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
Lee, et al. Informational [Page 23] |
| 1285 |
</pre> |