idnits 2.17.1 draft-chen-idr-bgp-ls-sr-policy-nrp-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (22 April 2022) is 697 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 (-10) exists of draft-bestbar-teas-ns-packet-09 ** Downref: Normative reference to an Informational draft: draft-bestbar-teas-ns-packet (ref. 'I-D.bestbar-teas-ns-packet') == Outdated reference: A later version (-04) exists of draft-dong-idr-sr-policy-nrp-00 == Outdated reference: A later version (-19) exists of draft-ietf-idr-te-lsp-distribution-16 == Outdated reference: A later version (-02) exists of draft-liu-idr-bgp-network-slicing-01 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR R. Chen 3 Internet-Draft D. Zhao 4 Intended status: Standards Track ZTE Corporation 5 Expires: 24 October 2022 22 April 2022 7 SR Policies Extensions for NRP in BGP-LS 8 draft-chen-idr-bgp-ls-sr-policy-nrp-00 10 Abstract 12 This document defines a new TLV which enable the headed to report the 13 configuration and the states of SR policies carrying NRP information 14 by using BPG-LS. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on 24 October 2022. 33 Copyright Notice 35 Copyright (c) 2022 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 40 license-info) in effect on the date of publication of this document. 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. Code Components 43 extracted from this document must include Revised BSD License text as 44 described in Section 4.e of the Trust Legal Provisions and are 45 provided without warranty as described in the Revised BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 51 3. Carrying NRP Sub-TLV in BGP-LS . . . . . . . . . . . . . . . 3 52 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 54 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 55 7. Normative References . . . . . . . . . . . . . . . . . . . . 3 56 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 58 1. Introduction 60 SR Policy is an ordered list of segments (i.e. instructions) that 61 represent a source-routed policy. Packet flows are steered into a SR 62 Policy on a node where it is instantiated called a headend node. The 63 packets steered into an SR Policy carry an ordered list of segments 64 associated with that SR Policy.[I-D.ietf-idr-te-lsp-distribution] 65 describes a mechanism to distribute traffic engineering policy 66 information (SR Policies , TE-LSPs, etc) to external components using 67 BGP-LS. 69 [I-D.bestbar-teas-ns-packet] introduces a Slice-Flow Aggregate as the 70 collection of packets (from one or more IETF network slice traffic 71 streams) that match an NRP Policy selection criteria and are offered 72 the same forwarding treatment. The NRP Policy is used to realize an 73 NRP by instantiating specific control and data plane resources on 74 select topological elements in an IP/MPLS network. The NRP 75 Identifier (NRP-ID) is globally unique within an NRP domain and that 76 can be used in the control or management plane to identify the 77 resources associated with the NRP. 79 Based on the mechanism defined in [I-D.ietf-idr-te-lsp-distribution], 80 this document defines a new TLV which enable the headed to report the 81 configuration and the states of SR policies carrying NRP information 82 by using BPG-LS. 84 2. Requirements Language 86 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 88 document are to be interpreted as described in RFC 2119 [RFC2119]. 90 cloud transport network: It is usually a national or province 91 backbone network to achieve interconnection between multiple regional 92 clouds/core clouds deployed in the country/province. 94 3. Carrying NRP Sub-TLV in BGP-LS 96 [I-D.liu-idr-bgp-network-slicing] and [I-D.dong-idr-sr-policy-nrp] 97 define extensions to BGP in order to advertise NRP in SR policies. 99 In order to collect configuration and states of the NRP SR policies, 100 this document defines a new SR Policy state TLV. 102 The TLV has the following format: 104 0 1 2 3 105 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | Type | Length | Flags | RESERVED | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | NRP ID (4 octets) | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 where: 114 Type: TBD1. 116 Length: 6 octets. 118 Flags: 1 octet of flags. None are defined at this stage. Flags 119 SHOULD be set to zero on transmission and MUST be ignored on receipt. 121 RESERVED: 1 octet of reserved bits. SHOULD be set to zero on 122 transmission and MUST be ignored on receipt. 124 NRP: 4 octet global identifier of Network Resource Partition. 126 4. Acknowledgements 128 TBD. 130 5. IANA Considerations 132 TBD. 134 6. Security Considerations 136 TBD. 138 7. Normative References 140 [I-D.bestbar-teas-ns-packet] 141 Saad, T., Beeram, V. P., Dong, J., Wen, B., Ceccarelli, 142 D., Halpern, J., Peng, S., Chen, R., Liu, X., Contreras, 143 L. M., Rokui, R., and L. Jalil, "Realizing Network Slices 144 in IP/MPLS Networks", Work in Progress, Internet-Draft, 145 draft-bestbar-teas-ns-packet-09, 21 April 2022, 146 . 149 [I-D.dong-idr-sr-policy-nrp] 150 Dong, J., Hu, Z., and R. Pang, "BGP SR Policy Extensions 151 for Network Resource Partition", Work in Progress, 152 Internet-Draft, draft-dong-idr-sr-policy-nrp-00, 3 March 153 2022, . 156 [I-D.ietf-idr-te-lsp-distribution] 157 Previdi, S., Talaulikar, K., Dong, J., Chen, M., Gredler, 158 H., and J. Tantsura, "Distribution of Traffic Engineering 159 (TE) Policies and State using BGP-LS", Work in Progress, 160 Internet-Draft, draft-ietf-idr-te-lsp-distribution-16, 22 161 October 2021, . 164 [I-D.liu-idr-bgp-network-slicing] 165 Yao, L. and P. Shaofu, "BGP Extensions to Support Packet 166 Network Slicing in SR Policy", Work in Progress, Internet- 167 Draft, draft-liu-idr-bgp-network-slicing-01, 15 October 168 2020, . 171 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 172 Requirement Levels", BCP 14, RFC 2119, 173 DOI 10.17487/RFC2119, March 1997, 174 . 176 Authors' Addresses 178 Ran Chen 179 ZTE Corporation 180 Nanjing 181 China 182 Email: chen.ran@zte.com.cn 183 Detao Zhao 184 ZTE Corporation 185 Nanjing 186 China 187 Email: zhao.detao@zte.com.cn