idnits 2.17.1 draft-sw-detnet-network-slice-mapping-yang-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 19 instances of too long lines in the document, the longest one being 33 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 2022) is 706 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-20) exists of draft-ietf-detnet-yang-16 == Outdated reference: A later version (-25) exists of draft-ietf-teas-ietf-network-slices-10 ** Downref: Normative reference to an Informational draft: draft-ietf-teas-ietf-network-slices (ref. 'I-D.ietf-teas-ietf-network-slices') ** Downref: Normative reference to an Informational RFC: RFC 7960 ** Downref: Normative reference to an Informational RFC: RFC 8938 ** Downref: Normative reference to an Informational RFC: RFC 9055 Summary: 5 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DetNet Working Group X. Song 3 Internet-Draft H. Wu 4 Intended status: Standards Track ZTE Corp. 5 Expires: 3 November 2022 May 2022 7 YANG Data Model for DetNet Mapping with Network Slice 8 draft-sw-detnet-network-slice-mapping-yang-00 10 Abstract 12 This document considers the applicability of Deterministic Networking 13 (DetNet) mapping with network slice in the context of IP/MPLS 14 network. It identifies the mapping requirements and YANG data models 15 being defined by the IETF to support the deployment. 17 Existing data models are identified for deterministic networking, 18 this document outlines the applicability of DetNet for network 19 slicing. It also identifies the features for necessity of mapping 20 network slicing with DetNet and indicates where the DetNet YANG might 21 be extended. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on 2 November 2022. 40 Copyright Notice 42 Copyright (c) 2022 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 47 license-info) in effect on the date of publication of this document. 48 Please review these documents carefully, as they describe your rights 49 and restrictions with respect to this document. Code Components 50 extracted from this document must include Revised BSD License text as 51 described in Section 4.e of the Trust Legal Provisions and are 52 provided without warranty as described in the Revised BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 59 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 60 2.3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 61 3. Applicability of DetNet to Network Slice . . . . . . . . . . 4 62 3.1. Problem Statement . . . . . . . . . . . . . . . . . . . . 4 63 3.2. Use Case . . . . . . . . . . . . . . . . . . . . . . . . 4 64 3.3. Modes of IETF Network Slice Selection . . . . . . . . . . 5 65 4. Mapping DetNet with Network Slice . . . . . . . . . . . . . . 5 66 4.1. Mapping Requirements . . . . . . . . . . . . . . . . . . 6 67 4.2. Mapping Process . . . . . . . . . . . . . . . . . . . . . 6 68 5. YANG Modeling Approach . . . . . . . . . . . . . . . . . . . 7 69 6. YANG Data Tree . . . . . . . . . . . . . . . . . . . . . . . 8 70 6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 8 71 6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 8 72 7. YANG Data Model . . . . . . . . . . . . . . . . . . . . . . . 8 73 7.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 8 74 7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 12 75 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 76 9. Security Considerations . . . . . . . . . . . . . . . . . . . 14 77 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 15 78 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 79 11.1. Normative References . . . . . . . . . . . . . . . . . . 15 80 11.2. Informative References . . . . . . . . . . . . . . . . . 16 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 83 1. Introduction 85 Deterministic Networking (DetNet) is a service that can be offered by 86 a network to DetNet flows. As defined in [RFC8655], DetNet flows 87 provide deterministic services with guaranteed performance such as 88 end-to-end delay and low packet loss rate for unicast or multicast 89 data streams. DetNet assumes that the management controller can 90 complete the path selection for the resources required by the service 91 as to how to provide the guarantee of the underlying network 92 resources to meet the requirement. 94 As specified in 3GPP TS 28.530, network slicing is a paradigm where 95 logical networks/partitions are created, with appropriate isolation, 96 resources and optimized topology to serve a purpose or service 97 category (e.g. use case/traffic category, or for MNO internal 98 reasons) or customers (logical system created "on demand"). 99 [I-D.ietf-teas-ietf-network-slices] provides the definition of 100 network slice in the context of IETF network, the main 101 characteristics, necessary components and interfaces for the general 102 framework and realization involved of IETF Network Slice. This 103 document provides the applicability of DetNet to Network Slice in the 104 context of IETF. 106 2. Conventions 108 2.1. Requirements Language 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 112 "OPTIONAL" in this document are to be interpreted as described in BCP 113 14 [RFC2119] [RFC8174] when, and only when, they appear in all 114 capitals, as shown here. 116 2.2. Terminology 118 Refer to [RFC8655], [RFC8938] and 119 [I-D.ietf-teas-ietf-network-slices], for the key terms used in this 120 document. 122 The terminology for describing YANG data models is found in 123 [RFC7960]. 125 2.3. Abbreviations 127 DetNet: Deterministic Networking 129 IETF NS: IETF Network Slice 131 MPLS: Multi-Protocol Label Switching 133 NETCONF: Network Configuration Protocol 135 NRP: Network Resource Partition 137 PREOF: Packet Replication, Elimination, and Ordering Functions 139 SDP: Service Demarcation Point 141 SLE: Service Level Expectation 143 SLO: Service Level Objective 144 SSH: transport Secure Shell 146 TLS: Transport Layer Security 148 3. Applicability of DetNet to Network Slice 150 3.1. Problem Statement 152 DetNet is a service that provides a reliable or available service to 153 DetNet flows through dedicating network resources such as link 154 bandwidth, buffer space to DetNet individual flow or DetNet 155 aggregation flows. To realize this object the management and control 156 plane of DetNet needs support DetNet flow (including App-layer, 157 service-layer and forwarding-layer flow) instantiation, resource 158 reservation and allocation, path computation and route steering. In 159 data plane DetNet supports packet replication, elimination and 160 ordering function to reduce packet loss rate and jitter performance. 161 Refer to [RFC8655] and [RFC8938], DetNet PREOF function for service 162 protection in order to reduce packet loss and jitter performance. 163 Except service protection, the necessary resource reservation and 164 allocation are feasible to eliminate packet congestion and avoiding 165 packet loss; optimization for path computation needs be based on a 166 set of constraints of some specific network requirements. To realize 167 resource reservation and path computation it's recommended to use 168 existing technologies, such as RSVP-TE, BGP, SR, etc. From the 169 discussion on network slicing at IETF TEAS WG we know that the 170 resource guarantee of a specific service requires the closed-loop 171 management of resource exposure, resource reservation, resource 172 occupation, resource optimization and other aspects, and the existing 173 technology may not be enough to support that. 175 Refer to [I-D.ietf-teas-ietf-network-slices] the network slicing 176 technology can provide necessary network resources to meet the 177 service requirements of users while realizing the SLO/SLE 178 requirements for user services. By applying network slicing 179 technology to DetNet, resource guarantee can be achieved for 180 deterministic networking services. On the other hand, network 181 slicing with ultra-high reliability or ultra-low latency guarantee 182 requires the processing of packets with the help of DetNet-specific 183 queuing technology. 185 3.2. Use Case 187 Refer to [RFC8578] provides DetNet use cases which include DetNet 188 applied to Network Slicing described in section 10: 190 * Resource isolation across slices. 192 * Deterministic services within slices. 194 With the applicability of DetNet to Network Slice, not only the 195 network capability (such as end-to-end latency, bounded jitter and 196 low packet loss ratio) the DetNet concerns be satisfied, but also the 197 necessary network resource reserved and allocated the IETF Network 198 Slice concerns to be supported. There are also limitations for 199 DetNet applied to Network Slicing, e.g., mainly used for latency- 200 sensitive service, only support P2P and P2MP connectivity, etc. The 201 resolve for these limitations are out of the scope of this document. 202 This document mainly outlines the applicability of DetNet to Network 203 Slice for latency-sensitive service. 205 3.3. Modes of IETF Network Slice Selection 207 This document provides three modes of IETF Network Slice selection 208 operations as associated with DetNet follows. Additional modes may 209 be defined in the future. 211 * New IETF Network Slice Binding - A customer may request a DetNet 212 service with requirements guarantee, e.g., end-to-end latency, 213 latency variation, jitter, etc. To satisfy the customer's 214 requirements on network resource it's recommended to bind DetNet 215 flows with an IETF Network Slice instance. The YANG model 216 described in Section 5 of this document provides the mapping 217 between DetNet flows with anew IETF Network Slice. 219 * IETF Network Slice Sharing - A customer may request a DetNet 220 service with requirement guarantee where a new IETF Network Slice 221 do not need to be created but be shared with other multiple DetNet 222 flows. The mapping YANG model described in Section 5 of this 223 document provides the mapping between DetNet flows with an IETF 224 Network Slice in use. No modification of the properties of an 225 IETF Network Slice is allowed in this mode. 227 * IETF Network Slice Modification - This mode allows the 228 modification of the properties of the existing IETF Network Slice 229 (e.g., bandwidth, latency, etc.). 231 IETF Network Slice Mapping Template - A policy profile which contains 232 network constraints and optimization criteria is used for mapping 233 DetNet flows to one/more certain IETF Network Slice instance. 235 4. Mapping DetNet with Network Slice 236 4.1. Mapping Requirements 238 DetNet service is per flow (including app-layer, service-layer and 239 forwarding-layer flow), performs traffic processing based on the 240 identification for flow/flow aggregation. Differences in IETF 241 Network Slice service are considered in terms of Network Resource 242 Partition. [I-D.bestbar-teas-ns-packet] introduces a mechanism to 243 associate Network Resource Partition (NRP) with Slice-Flow Aggregate. 244 If DetNet applied to IETF Network Slice, the DetNet-flow/flow 245 aggregation is considered as the slice-flow/flow aggregation over the 246 underlying NRP. 248 Requirements for Network Slice mapping with deterministic networking 249 services: 251 * The mapping of deterministic services with underlying network 252 slice resources is necessary. It may include: 254 - Service endpoint mapping between DetNet Edge Node and IETF 255 Network Slice SDP. 257 - Access service mapping between DetNet UNI and IETF Network 258 Slice AC. 260 - Instance mapping between DetNet-flow/flow aggregations with 261 IETF Network Slice. 263 * The creation request for network slice instance to be bounded with 264 one specific deterministic flow/flow aggregation instances should 265 be supported. 267 * The sharing of network slice instance for one or more 268 deterministic flow/flow aggregation instances SHOULD be supported. 270 * Configurations for a new network slice instance to provide 271 necessary underlying resource to deterministic services is 272 necessary. 274 * Modification for an existing network slice instance applied to one 275 or more DetNet flow SHOULD be supported. 277 4.2. Mapping Process 279 * APP-flow packets is instantiated as DetNet service awareness flow. 281 * If there is an existing IETF Network Slice instance which 282 satisfies the network resource requirements of the DetNet 283 customer. After check the feasibility of the IETF Network Slice 284 instance bound to DetNet flows, request mapping DetNet-flow/flow 285 aggregations with IETF Network Slice instance. 287 * If there is no IETF Network Slice available, a new IETF Network 288 Slice instance creation is required. 290 * The mapping of DetNet flow with IETF Network Slice is configured 291 and stored in management plane. The mapping policy of DetNet flow 292 associated with underlying network resource partition (NRP) is 293 programmed to the DetNet or IETF Network Slice Nodes (such as SDP, 294 P nodes, etc.) through YANG data models. 296 * In data plane, the DetNet or IETF Network Slice Nodes complete the 297 identification of deterministic service flows (such as IP 6-tuple, 298 MPLS labels, etc.) and correspond with one specific network slice 299 instance , realize the slice awareness of DetNet flow/flow 300 aggregation. Through the network resource occupation of hop-by- 301 hop nodes along the path, network resources required by the 302 deterministic networking service flow is guaranteed. 304 5. YANG Modeling Approach 306 This section provides how the DetNet and IETF Network Slice Service 307 mapping parameters are supported using augmentation of the existing 308 DetNet service models (i.e., [I-D.ietf-detnet-yang]). It identifies 309 the YANG data models being defined by the IETF to support this 310 deployment architecture and specific scenarios relevant for Service 311 Providers. 313 The below figure shows the modeling approach of the Augmented DetNet 314 Model. 316 +--------------+ +----------------------+ 317 | DetNet |o-------| | 318 +--------------+ augment| | 319 | | 320 +--------------+ |Augmented DetNet Model| 321 | DetNet & NS |------->| | 322 | Mapping Types| import | | 323 +--------------+ | | 324 +----------------------+ 326 Figure 1: Modeling approach 328 6. YANG Data Tree 330 6.1. Service Mapping Types 332 module: ietf-ns-detnet-mapping-types 333 +--rw ns-mapping-templates 334 +--rw ns-mapping-template* [id] 335 +--rw id string 336 +--rw description? string 337 +--rw map-type? identityref 338 +--rw ns-slo-ref? 339 ->/ns:slice-template/ns-slo-sle-templates/id 341 6.2. Service Models 343 module: ietf-ns-detnet-service-mapping 344 augment /dnet:detnet:detnet/service:sub-layer 345 /service:sub-layer: 346 +--rw ns-detnet-mapping 347 +--rw ns-mapping 348 +--rw map-type? identityref 349 +--rw ns-id string 350 +--rw ns-mapping-template-ref? 351 -> /nsdmt:ns-mapping-templates/ns-mapping-template/id 352 {template}? 354 7. YANG Data Model 356 7.1. Service Mapping Types 358 file "ietf-ns-detnet-mapping-types@2022-03-07.yang" 359 module ietf-ns-detnet-mapping-types { 360 yang-version 1.1; 361 namespace 362 "urn:ietf:params:xml:ns:yang:ietf-ns-detnet-mapping-types"; 363 prefix nsdmt; 365 import ietf-network-slice { 366 prefix ietf-ns; 367 reference 368 "I-D.ietf-teas-ietf-network-slice-nbi-yang-01: A YANG Data Model for the IETF Network Slice"; 369 } 371 organization 372 "IETF DetNet Working Group"; 373 contact 374 "WG Web: 375 WG List: 377 Editor: Xueyan Song 378 379 Editor: Haisheng Wu 380 "; 381 description 382 "This module contains a YANG module for IETF Network Slice & Detnet mapping 383 parameters. 385 Copyright (c) 2022 IETF Trust and the persons identified as 386 authors of the code. All rights reserved. 388 Redistribution and use in source and binary forms, with or 389 without modification, is permitted pursuant to, and subject to 390 the license terms contained in, the Revised BSD License set 391 forth in Section 4.c of the IETF Trust's Legal Provisions 392 Relating to IETF Documents 393 (https://trustee.ietf.org/license-info). 395 This version of this YANG module is part of RFC XXXX; see the 396 RFC itself for full legal notices."; 398 revision 2022-03-27 { 399 description 400 "Initial revision."; 401 reference 402 "RFC XXXX: YANG Data Model for DetNet Mapping with Network Slice"; 403 } 405 /* 406 * Features 407 */ 409 feature template { 410 description 411 "Support Network Slice mapping templates."; 412 } 414 /* 415 * Identity for map-type 416 */ 418 identity map-type { 419 description 420 "Base identity from which specific map types are derived."; 421 } 422 identity new { 423 base map-type; 424 description 425 "The new Network Slice are binded to the service."; 426 } 428 identity select { 429 base map-type; 430 description 431 "The Detnet service selects an existing Network Slice with no 432 modification."; 433 } 435 identity modify { 436 base map-type; 437 description 438 "The Detnet service selects an existing Network Slice and allows to modify 439 the properties of the Network Slice (e.g., SLO)"; 440 } 442 identity none { 443 base map-type; 444 description 445 "The Detnet service is not mapped to any underlying Network Slice"; 446 } 448 /* 449 * Typedef 450 */ 452 typedef ns-mapping-template-id { 453 type string; 454 description 455 "Identifier for Network Slice mapping template."; 456 } 458 /* 459 * Groupings 460 */ 462 grouping ns-ref { 463 description 464 "The reference to Network Slice."; 466 leaf ns-mapping-slice-id{ 467 type int; 468 description 469 "Identifier for a Network Slice." 470 }; 472 leaf ns-mapping-template-ref { 473 if-feature "template"; 474 type leafref { 475 path "/nsdmt:ns-mapping-templates/" 476 + "nsdmt:ns-mapping-template/nsdmt:id"; 477 } 478 description 479 "An identifier to the Network Slice Mapping Template where the Network Slice 480 constraints and optimization criteria are specified."; 481 } 482 } 484 grouping ns-mapping { 485 description 486 "Mapping between Services and network-slice"; 487 container ns-mapping { 488 description 489 "Mapping between Services and network-slice"; 490 leaf map-type { 491 type identityref { 492 base map-type; 493 } 494 description 495 "Isolation Requirements"; 496 } 497 uses ns-ref; 498 } 499 } 501 //grouping 503 container ns-mapping-templates { 504 description 505 "The network-slice constraints and optimization criteria"; 506 list ns-mapping-template { 507 key "id"; 508 leaf id { 509 type ns-mapping-template-id; 510 description 511 "Identification of the Template to be used."; 512 } 513 leaf description { 514 type string; 515 description 516 "Description of the template."; 517 } 518 leaf map-type { 519 type identityref { 520 base map-type; 521 } 522 must "0 = derived-from-or-self(.,'none')" { 523 error-message "The map-type must be other than " 524 + "none"; 525 } 526 description 527 "Map type for Network Slice creation/ 528 selection."; 529 } 530 leaf ns-slo-ref{ 531 type leafref { 532 path "/ns:ns-slo-sle-templates/ns-slo-sle-template/id"; 533 } 535 description 536 "List for templates."; 537 } 538 } 539 } 540 542 7.2. Service Models 544 file "ietf-ns-detnet-service-mapping@2022-03-27.yang" 545 module ietf-ns-detnet-service-mapping { 546 yang-version 1.1; 547 namespace 548 "urn:ietf:params:xml:ns:yang:ietf-ns-detnet-service-mapping"; 549 prefix detnet-nssm; 551 import ietf-ns-detnet-mapping-types { 552 prefix nsdmt; 553 reference 554 "RFC XXXX: YANG Data Model for DetNet Mapping with Network Slice"; 555 } 556 import ietf-detnet { 557 prefix dnet; 558 reference 559 "draft-ietf-detnet-yang-16.txt: YANG Data Model for Detnet"; 560 } 562 organization 563 "IETF DetNet Working Group"; 565 contact 566 "WG Web: 567 WG List: 569 Editor: Xueyan Song 570 571 Editor: Haisheng Wu 572 "; 574 description 575 "This module contains a YANG module for the mapping of DetNet to the Network Slice. 577 Copyright (c) 2022 IETF Trust and the persons identified as 578 authors of the code. All rights reserved. 580 Redistribution and use in source and binary forms, with or 581 without modification, is permitted pursuant to, and subject to 582 the license terms contained in, the Revised BSD License set 583 forth in Section 4.c of the IETF Trust's Legal Provisions 584 Relating to IETF Documents 585 (https://trustee.ietf.org/license-info). 587 This version of this YANG module is part of RFC XXXX; see the 588 RFC itself for full legal notices."; 590 revision 2022-03-27 { 591 description 592 "Initial revision."; 593 reference 594 "RFC XXXX: YANG Data Model for DetNet Mapping with Network Slice"; 595 } 597 /* 598 * Augmentation to Detnet 599 */ 601 augment "/dnet:detnet:detnet/service:sub-layer" 602 + "/service:sub-layer" { 603 description 604 "Detnet augmented to include Network Slice parameters and mapping"; 605 container ns-detnet-mapping { 606 presence "Indicates Detnet service to Network Slice mapping"; 607 description 608 "Container to augment detnet to Network Slice parameters and mapping"; 609 uses nsdmt:ns-mapping; 611 } 612 } 614 //augment 616 } 617 619 8. IANA Considerations 621 This document requests the IANA to register the following URIs in the 622 "IETF XML Registry" [RFC3688]. 624 URI: urn:ietf:params:xml:ns:yang: ietf-ns-detnet-mapping-types 625 Registrant Contact: The IESG. 626 XML: N/A, the requested URI is an XML namespace. 628 URI: urn:ietf:params:xml:ns:yang:ietf-ns-detnet-service-mapping 629 Registrant Contact: The IESG. 630 XML: N/A, the requested URI is an XML namespace. 632 This document requests the IANA to register the following YANG 633 modules in the YANG Module Names registry [RFC7950]. 635 Name: ietf-ns-detnet-mapping-types 636 Namespace: urn:ietf:params:xml:ns:yang: ietf-ns-detnet-mapping-types 637 Prefix: nsdmt 638 Reference: [This.I-D] 640 Name: ietf-ns-detnet-service-mapping 641 Namespace: urn:ietf:params:xml:ns:yang: ietf-ns-detnet-service-mapping 642 Prefix: detnet-nssm 643 Reference: [This.I-D] 645 9. Security Considerations 647 Security considerations for DetNet are covered in the DetNet 648 Architecture [RFC8655] and DetNet Security Considerations [RFC9055] 650 The YANG data model specified in this document defines a schema for 651 mapping of DetNet with IETF Network Slice via NETCONF [RFC6241] or 652 RESTCONF [RFC8040]. For NETCONF to support secure transport Secure 653 Shell (SSH) [RFC6242] is mandatory. For RESTCONF to support secure 654 transport TLS [RFC8446] is mandatory. 656 10. Acknowledgement 658 The authors appreciate Peng Shaofu and Liu Aihua for useful 659 discussions and motivations for this work. 661 11. References 663 11.1. Normative References 665 [I-D.ietf-detnet-yang] 666 Geng, X., Ryoo, Y., Fedyk, D., Rahman, R., and Z. Li, 667 "Deterministic Networking (DetNet) YANG Model", Work in 668 Progress, Internet-Draft, draft-ietf-detnet-yang-16, 5 669 February 2022, . 672 [I-D.ietf-teas-ietf-network-slices] 673 Farrel, A., Drake, J., Rokui, R., Homma, S., Makhijani, 674 K., Contreras, L. M., and J. Tantsura, "Framework for IETF 675 Network Slices", Work in Progress, Internet-Draft, draft- 676 ietf-teas-ietf-network-slices-10, 27 March 2022, 677 . 680 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 681 Requirement Levels", BCP 14, RFC 2119, 682 DOI 10.17487/RFC2119, March 1997, 683 . 685 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 686 DOI 10.17487/RFC3688, January 2004, 687 . 689 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 690 and A. Bierman, Ed., "Network Configuration Protocol 691 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 692 . 694 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 695 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 696 . 698 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 699 RFC 7950, DOI 10.17487/RFC7950, August 2016, 700 . 702 [RFC7960] Martin, F., Ed., Lear, E., Ed., Draegen, T., Ed., Zwicky, 703 E., Ed., and K. Andersen, Ed., "Interoperability Issues 704 between Domain-based Message Authentication, Reporting, 705 and Conformance (DMARC) and Indirect Email Flows", 706 RFC 7960, DOI 10.17487/RFC7960, September 2016, 707 . 709 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 710 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 711 . 713 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 714 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 715 May 2017, . 717 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 718 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 719 . 721 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 722 "Deterministic Networking Architecture", RFC 8655, 723 DOI 10.17487/RFC8655, October 2019, 724 . 726 [RFC8938] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., and S. 727 Bryant, "Deterministic Networking (DetNet) Data Plane 728 Framework", RFC 8938, DOI 10.17487/RFC8938, November 2020, 729 . 731 [RFC9055] Grossman, E., Ed., Mizrahi, T., and A. Hacker, 732 "Deterministic Networking (DetNet) Security 733 Considerations", RFC 9055, DOI 10.17487/RFC9055, June 734 2021, . 736 [TS_28.530] 737 3GPP, "Management and orchestration; Concepts, use cases 738 and requirements", 739 . 742 11.2. Informative References 744 [I-D.bestbar-teas-ns-packet] 745 Saad, T., Beeram, V. P., Dong, J., Wen, B., Ceccarelli, 746 D., Halpern, J., Peng, S., Chen, R., Liu, X., Contreras, 747 L. M., Rokui, R., and L. Jalil, "Realizing Network Slices 748 in IP/MPLS Networks", Work in Progress, Internet-Draft, 749 draft-bestbar-teas-ns-packet-10, 5 May 2022, 750 . 753 [RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases", 754 RFC 8578, DOI 10.17487/RFC8578, May 2019, 755 . 757 Authors' Addresses 759 Xueyan Song 760 ZTE Corp. 761 Nanjing 762 China 763 Phone: +86 25 88013062 764 Email: song.xueyan2@zte.com.cn 766 Haisheng Wu 767 ZTE Corp. 768 Nanjing 769 China 770 Email: wu.haisheng@zte.com.cn