idnits 2.17.1 draft-zcdc-isis-flexe-extention-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 275 has weird spacing: '... Value sub-T...' -- The document date (July 3, 2017) is 2489 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: 'RFC5029' is defined on line 296, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-izh-ccamp-flexe-fwk-03 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Y. Zhu 3 Internet-Draft H. Chen 4 Intended status: Standards Track China Telecom 5 Expires: January 4, 2018 Z. Du 6 M. Chen 7 Huawei 8 July 3, 2017 10 ISIS Extensions for Flexible Ethernet 11 draft-zcdc-isis-flexe-extention-01 13 Abstract 15 This document specifies the extensions to the IS-IS routing protocol 16 to carry and flood Flex Ethernet (FlexE) link state information. The 17 FlexE link state information is necessary for a node or a controller 18 to compute a path that is required to over FlexE links. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 24 document are to be interpreted as described in RFC 2119 [RFC2119]. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on January 4, 2018. 43 Copyright Notice 45 Copyright (c) 2017 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. FlexE Link Advertisement . . . . . . . . . . . . . . . . . . 3 62 3. FlexE Sub-link Advertisement . . . . . . . . . . . . . . . . 6 63 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 64 4.1. FlexE Switching Type . . . . . . . . . . . . . . . . . . 6 65 4.2. FlexE LSP Encoding Type . . . . . . . . . . . . . . . . . 6 66 4.3. FlexE Interface Sub-TLV . . . . . . . . . . . . . . . . . 7 67 5. Security Consideration . . . . . . . . . . . . . . . . . . . 7 68 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 70 7.1. Normative References . . . . . . . . . . . . . . . . . . 7 71 7.2. Informative References . . . . . . . . . . . . . . . . . 7 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 74 1. Introduction 76 Flex Ethernet (FlexE) [I-D.izh-ccamp-flexe-fwk] provides a generic 77 mechanism for supporting a variety of Ethernet MAC rates that may or 78 may not correspond to any existing Ethernet PHY rate. This includes 79 MAC rates that are both greater than (through bonding) and less than 80 (through sub-rate and channelization) the Ethernet PHY rates used to 81 carry Ethernet traffic. 83 FlexE supports interface bonding, a bonded interface is consisted of 84 from 1 to n 100GBASE-R PHYs (other types of PHY will be supported in 85 the future), the bonded interface is called FlexE interface in this 86 document. FlexE also supports interface channelization, a FlexE 87 interface can be channelized into multiple sub-interfaces, the sub- 88 interface is called FlexE sub-interface in the rest of this document. 90 The FlexE mechanism operates using a calendar which assigns 66B block 91 positions on sub-calendars on each PHY of a FlexE interface to each 92 of the FlexE flows. The calendar has a granularity of 5G, and has a 93 length of 20 slots for a 100G interface. Currently, only 100GBASE-R 94 PHY and 5G granularity are supported in FlexE implementation 95 agreement version 1.0 [FlexE], other types (e.g., 200G, 400G) of PHY 96 and granularities (e.g., 25G) will be supported in the future. 98 A FlexE interface has a number of time slots resource. These time 99 slots can be transparent to the up layer application, the up layer 100 application (e.g., RSVP-TE) can just treat the FlexE interface as a 101 normal Ethernet interface, or the time slots can be allocated to a 102 FlexE LSP though RSVP-TE signaling, or the time slots can be 103 allocated to form a FlexE sub-interface though configuration or some 104 dynamic protocols. How to signal the FlexE LSP or configure the 105 FlexE sub-interface is out of the scope of this document. 107 The logical link that connects two FlexE interfaces residing in two 108 adjacent nodes is called FlexE link, and the logical link that 109 connects two FlexE sub-interfaces residing in two adjacent nodes is 110 call FlexE sub-link. 112 More details about FlexE can be found in FlexE framework document 113 [I-D.izh-ccamp-flexe-fwk]. 115 This document defines extensions to ISIS protocol to advertise the 116 FlexE TE link and sub-link state information. 118 2. FlexE Link Advertisement 120 This document re-uses the Interface Switching Capability Descriptor 121 (ISCD) sub-TLV for the advertisement of FlexE link state information. 122 The ISCD is a sub-TLV of the extended IS reachability TLV [RFC5307], 123 it is defined to describes the switching capability of an interface. 124 The following figure (Figure 1) illustrates encoding of the Value 125 field of the ISCD sub-TLV. 127 0 1 2 3 128 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 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | Switching Cap | Encoding | Reserved | 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | Max LSP Bandwidth at priority 0 | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Max LSP Bandwidth at priority 1 | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Max LSP Bandwidth at priority 2 | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Max LSP Bandwidth at priority 3 | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | Max LSP Bandwidth at priority 4 | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | Max LSP Bandwidth at priority 5 | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 | Max LSP Bandwidth at priority 6 | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | Max LSP Bandwidth at priority 7 | 147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 148 | Switching Capability-specific information | 149 | (variable) | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 Figure 1: ISCD sub-TLV 154 To support FlexE link advertisement, new "Switching Cap" and 155 "Encoding" are defined as follows: 157 The Switching Capability (Switching Cap) for FlexE interface is as 158 below: 160 Value Name 161 ----- -------------- 162 TBD1 FlexE-Switching 164 The Encoding Type for FlexE: 166 Value Name 167 ----- -------------- 168 TBD2 FlexE 170 The "Switching Capability-specific information" field for FlexE 171 interface is defined as below. It is referred to as FlexE Interface 172 sub-TLV in this document. 174 0 1 2 3 175 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 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | Type = TBD3 | Length | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | Granularity | Reserved | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | Available Slots at priority 0 | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | Available Slots at priority 1 | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | Available Slots at priority 2 | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | Available Slots at priority 3 | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | Available Slots at priority 4 | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | Available Slots at priority 5 | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | Available Slots at priority 6 | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Available Slots at priority 7 | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 Figure 2: FlexE Interface sub-TLV 200 The Type field is 2 octets in length and the value is TBD3. 202 The Length field is 2 octets in length that indicates the total 203 length of the TLV in octet. 205 The Granularity is 1 octet in length and its value identifies the 206 granularity of the FlexE time slots of a FlexE interface. Current 207 OIF agreement only allows the "5G" granularity, other granularities 208 may be defined in the future. 210 Value Granularity 211 ----- -------------- 212 0 Reserved 213 1 5G 214 2-254 Unassigned 215 255 Reserved 217 For each PHY of a FlexE interface, there are two calendars, one is 218 called Active calendar and the other is called Backup calendar. The 219 two calendars are used to facilitate reconfiguration, for example, 220 FlexE flow resizing can be achieved through calendar updates. More 221 detail about FlexE calendar can be found [FlexE]. 223 Each Available Slots at priority n is 4-octet in length that 224 indicates the maximum number of slots available at priority 'n' on 225 active calendar of the FlexE interface. 227 For a FlexE interface, as said above, 5G granularity is only 228 supported for now, but multiple granularities may be supported in the 229 future. To support this, FlexE Interface sub-TLV can occur multiple 230 times in a ISCD sub-TLV, but for each granularity, only one FlexE 231 Interface sub-TLV can be included and it carries the available time 232 slots of the granularity of the FlexE interface. When multiple FlexE 233 Interface sub-TLVs for the same granularity occur, only the first 234 FlexE Interface sub-TLV is considered to be valid, the rests MUST be 235 ignored. 237 3. FlexE Sub-link Advertisement 239 Through FlexE channelization, a FlexE Link can be sliced into a 240 number of FlexE sub-links, each FlexE sub-link has dedicated 241 bandwidth and is isolated from other FlexE sub-links. A set of FlexE 242 sub-links can be allocated to a specific application/user to form a 243 sliced network. From link characteristic point of view, a FlexE sub- 244 link is same as a real point-2-point link, it can be advertised and 245 used as a normal point-2-point link. 247 4. IANA Considerations 249 4.1. FlexE Switching Type 251 IANA is requested to allocate a new switching type from the 252 "Switching Types" registry of "Generalized Multi-Protocol Label 253 Switching (GMPLS) Signaling Parameters" registry. 255 Value Name Reference 256 ----- --------------- ------------- 257 TBD1 FlexE-Switching This document 259 4.2. FlexE LSP Encoding Type 261 IANA is requested to allocate a new LSP encoding type from the "LSP 262 Encoding Types" registry of "Generalized Multi-Protocol Label 263 Switching (GMPLS) Signaling Parameters" registry. 265 Value Name Reference 266 ----- ------- ------------- 267 TBD2 FlexE This document 269 4.3. FlexE Interface Sub-TLV 271 IANA is requested to create and maintain a new sub-registry, the 272 "Types for sub-TLVs of FlexE Switching Capability Specific 273 Information" registry under the "IS-IS TLV Codepoints" registry. 275 Value sub-TLV Name Reference 276 ----- --------------- ------------- 277 TBD3 FlexE Interface This document 279 5. Security Consideration 281 This document describes a mechanism for advertising FlexE link state 282 information through IS-IS LSPs and does not introduce any new 283 security issues. 285 6. Acknowledgements 287 7. References 289 7.1. Normative References 291 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 292 Requirement Levels", BCP 14, RFC 2119, 293 DOI 10.17487/RFC2119, March 1997, 294 . 296 [RFC5029] Vasseur, JP. and S. Previdi, "Definition of an IS-IS Link 297 Attribute Sub-TLV", RFC 5029, DOI 10.17487/RFC5029, 298 September 2007, . 300 [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions 301 in Support of Generalized Multi-Protocol Label Switching 302 (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, 303 . 305 7.2. Informative References 307 [FlexE] OIF, "Flex Ethernet Implementation Agreement Version 1.0 308 (OIF-FLEXE-01.0)", March 2016. 310 [I-D.izh-ccamp-flexe-fwk] 311 Hussain, I., Valiveti, R., Wang, Q., Andersson, L., Chen, 312 M., and z. zhenghaomian@huawei.com, "GMPLS Routing and 313 Signaling Framework for Flexible Ethernet (FlexE)", draft- 314 izh-ccamp-flexe-fwk-03 (work in progress), June 2017. 316 Authors' Addresses 318 Yongqing Zhu 319 China Telecom 320 109, West Zhongshan Road, Tianhe District, Guangzhou,China 322 Email: zhuyq@gsta.com 324 Huanan Chen 325 China Telecom 326 109, West Zhongshan Road, Tianhe District, Guangzhou,China 328 Email: chenhuanan@gsta.com 330 Zongpeng Du 331 Huawei 333 Email: duzongpeng@huawei.com 335 Mach(Guoyi) Chen 336 Huawei 338 Email: mach.chen@huawei.com