idnits 2.17.1 draft-liu-idr-bgp-network-slicing-01.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([I-D.peng-teas-network-slicing]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 111: '... SHOULD be set to zero on transmissi...' RFC 2119 keyword, line 113: '... reserved bits. SHOULD be set to zero...' RFC 2119 keyword, line 114: '...transmission and MUST be ignored on re...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 15, 2020) is 1289 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) == Unused Reference: 'I-D.zch-lsr-isis-network-slicing' is defined on line 168, but no explicit reference was found in the text == Outdated reference: A later version (-26) exists of draft-ietf-idr-segment-routing-te-policy-09 == Outdated reference: A later version (-22) exists of draft-ietf-spring-segment-routing-policy-08 == Outdated reference: A later version (-04) exists of draft-peng-teas-network-slicing-03 Summary: 2 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Group Yao. Liu 3 Internet-Draft Shaofu. Peng 4 Intended status: Standards Track ZTE Corporation 5 Expires: April 18, 2021 October 15, 2020 7 BGP Extensions to Support Packet Network Slicing in SR Policy 8 draft-liu-idr-bgp-network-slicing-01 10 Abstract 12 [I-D.peng-teas-network-slicing] defines a unified TN-slice 13 identifier, AII(administrative instance identifier), to indicate the 14 topology, computing, storage resources of the dedicated virtual 15 network for both intra-domain and inter-domain network slicing 16 scenarios. This document defines extensions to BGP in order to 17 advertise AII in SR policies. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 18, 2021. 36 Copyright Notice 38 Copyright (c) 2020 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. SR policy with AII . . . . . . . . . . . . . . . . . . . . . 2 55 3. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 60 6.2. Informative References . . . . . . . . . . . . . . . . . 4 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 For a packet network, network slicing requires the underlying network 66 to support partitioning of the network resources to provide the 67 client with dedicated (private) networking, computing, and storage 68 resources drawn from a shared pool. 70 [I-D.peng-teas-network-slicing] defines a unified TN-slice 71 identifier, AII(administrative instance identifier), to indicate the 72 topology, computing, storage resources of the dedicated virtual 73 network for both intra-domain and inter-domain network slicing 74 scenarios, and how to compute SR-BE or SR-TE path according to TN- 75 slice Identifier combined with other creteria. 77 [I-D.ietf-spring-segment-routing-policy] details the concepts of SR 78 Policy and steering into an SR 79 Policy.[I-D.ietf-idr-segment-routing-te-policy] specifies the way to 80 use BGP to distribute one or more of the candidate paths of an SR 81 Policy to the headend of that policy. 83 This document defines extensions to BGP in order to advertise AII in 84 SR-TE policies. 86 2. SR policy with AII 88 To distinguish forwarding behavior of different virtual networks, 89 each segment lists in SR policy need to be computed within the scope 90 of TN-slice identified by AII. As AII has global significance, all 91 segments of the same segment list can share a single AII. This 92 document defines a new AII sub-TLV in Segment List Sub-TLV to 93 indicate which slice this segment list belongs to, 94 0 1 2 3 95 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 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 97 | Type=TBD1 | Length | Flags | RESERVED | 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | AII | 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 Figure 1: AII sub-TLV in Segment List Sub-TLV 104 where: 106 o Type: TBD1 108 o Length: 6 110 o Flags: 1 octet of flags. None are defined at this stage. Flags 111 SHOULD be set to zero on transmission and MUST be ignored on receipt. 113 o RESERVED: 1 octet of reserved bits. SHOULD be set to zero on 114 transmission and MUST be ignored on receipt. 116 o AII: Identifies the TN-slice (AII) information corresponding to the 117 segment list. 119 3. Operations 121 The operations about advertisement and reception of SR policy can 122 refer to [I-D.ietf-idr-segment-routing-te-policy]. Typically, a 123 controller or a PCE can compute SR path taking acount of AII 124 criteria, so that the SR path can be limited in the scope of TN-slice 125 identified by AII. The AII information contained in Segment List 126 Sub-TLV can help the headend to translate the segment to AII related 127 SID, if the Segment Sub-TLV has not provided optional SID 128 information. 130 Even if Segment Sub-TLV has provided valid SID information, it is 131 also beneficial for the headend to know which slice this path belongs 132 to, according to the AII information contained in Segment List Sub- 133 TLV. 135 4. Security Considerations 137 Procedures and protocol extensions defined in this document do not 138 affect the security considerations discussed in 139 [I-D.ietf-idr-segment-routing-te-policy]. 141 5. IANA Considerations 143 TBD 145 6. References 147 6.1. Normative References 149 [I-D.ietf-idr-segment-routing-te-policy] 150 Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P., 151 Rosen, E., Jain, D., and S. Lin, "Advertising Segment 152 Routing Policies in BGP", draft-ietf-idr-segment-routing- 153 te-policy-09 (work in progress), May 2020. 155 [I-D.ietf-spring-segment-routing-policy] 156 Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and 157 P. Mattes, "Segment Routing Policy Architecture", draft- 158 ietf-spring-segment-routing-policy-08 (work in progress), 159 July 2020. 161 [I-D.peng-teas-network-slicing] 162 Peng, S., Chen, R., Mirsky, G., and F. Qin, "Packet 163 Network Slicing using Segment Routing", draft-peng-teas- 164 network-slicing-03 (work in progress), February 2020. 166 6.2. Informative References 168 [I-D.zch-lsr-isis-network-slicing] 169 Zhu, Y., Chen, R., Peng, S., and F. Qin, "IS-IS Extensions 170 to Support Transport Network Slices using Segment 171 Routing", draft-zch-lsr-isis-network-slicing-06 (work in 172 progress), September 2020. 174 Authors' Addresses 176 Liu Yao 177 ZTE Corporation 178 No. 50 Software Ave, Yuhuatai Distinct 179 Nanjing 180 China 182 Email: liu.yao71@zte.com.cn 183 Peng Shaofu 184 ZTE Corporation 185 No. 50 Software Ave, Yuhuatai Distinct 186 Nanjing 187 China 189 Email: peng.shaofu@zte.com.cn