idnits 2.17.1 draft-chen-teas-rsvp-tts-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 -- The document date (December 29, 2016) is 2668 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) == Missing Reference: 'Ta' is mentioned on line 186, but not defined == Missing Reference: 'Tb' is mentioned on line 186, but not defined == Missing Reference: 'INFINITE' is mentioned on line 152, but not defined == Missing Reference: 'Start-time' is mentioned on line 269, but not defined == Missing Reference: 'End-time' is mentioned on line 269, but not defined == Unused Reference: 'RFC2119' is defined on line 428, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 433, but no explicit reference was found in the text == Unused Reference: 'RFC4875' is defined on line 438, but no explicit reference was found in the text == Unused Reference: 'RFC3630' is defined on line 445, but no explicit reference was found in the text == Unused Reference: 'RFC3031' is defined on line 452, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 11 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force H. Chen 3 Internet-Draft Huawei Technologies 4 Intended status: Standards Track M. Toy 5 Expires: July 2, 2017 Verizon 6 V. Liu 7 China Mobile 8 L. Liu 9 Fijitsu 10 December 29, 2016 12 Extensions to MPLS for Temporal LSP 13 draft-chen-teas-rsvp-tts-01.txt 15 Abstract 17 This document specifies extensions to RSVP-TE for creating and 18 maintaining a Traffic Engineering (TE) Label Switched Path (LSP) in a 19 time interval or a sequence of time intervals. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on July 2, 2017. 38 Copyright Notice 40 Copyright (c) 2016 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Conventions Used in This Document . . . . . . . . . . . . . . 3 58 4. Temporal LSP Overview . . . . . . . . . . . . . . . . . . . . 4 59 4.1. Architecture Overview . . . . . . . . . . . . . . . . . . 4 60 4.2. Operations Overview . . . . . . . . . . . . . . . . . . . 4 61 5. TIME INTERVAL Object . . . . . . . . . . . . . . . . . . . . . 5 62 5.1. Absolute TIME INTERVAL Object . . . . . . . . . . . . . . 5 63 5.2. Relative TIME INTERVAL Object . . . . . . . . . . . . . . 6 64 5.3. Recurrent Absolute TIME INTERVAL Object . . . . . . . . . 7 65 5.4. Recurrent Relative TIME INTERVAL Object . . . . . . . . . 8 66 6. Path Message . . . . . . . . . . . . . . . . . . . . . . . . . 9 67 7. Behaviors for Temporal LSP . . . . . . . . . . . . . . . . . . 10 68 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 69 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 70 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 10 71 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 72 11.1. Normative References . . . . . . . . . . . . . . . . . . . 10 73 11.2. Informative References . . . . . . . . . . . . . . . . . . 11 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 76 1. Introduction 78 Once an existing multiprotocol label switching (MPLS) traffic 79 engineering (TE) label switched path (LSP) is set up, it is assumed 80 to carry traffic forever until it is down. When an MPLS TE LSP 81 tunnel is up, it is assumed that the LSP consumes its reserved 82 network resources forever even though the LSP may only use network 83 resources during some period of time. As a result, the network 84 resources are not used efficiently. Moreover, a tunnel service can 85 not be reserved or booked in advance in a period of time. 87 This document specifies extensions to RSVP-TE for creating and 88 maintaining an MPLS TE LSP in a period of time called a time interval 89 or a sequence of time intervals. It is assumed that the LSP carries 90 traffic during this time interval or each of these time intervals. 91 Thus the network resources are efficiently used. More importantly, 92 some new services can be provided. For example, a consumer can book 93 a tunnel service in advance for a given time interval. Tunnel 94 services may be scheduled as requested. 96 2. Terminology 98 A Time Interval: a time period from time Ta to time Tb. 100 LSP: Label Switched Path. An LSP is a P2P (point-to-point) LSP or a 101 P2MP (point-to-multipoiint) LSP. 103 LSP in a time interval: LSP that carries traffic in the time 104 interval. 106 LSP in a sequence of time intervals: LSP that carries traffic in each 107 of the time intervals. 109 Temporal LSP: LSP in a time interval or LSP in a sequence of time 110 intervals. 112 TEDB: Traffic Engineering Database. 114 This document uses terminologies defined in RFC3209 and RFC4875. 116 3. Conventions Used in This Document 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 120 document are to be interpreted as described in RFC2119. 122 4. Temporal LSP Overview 124 This section briefs the architecture for supporting temporal LSPs and 125 some operations on temporal LSPs. 127 4.1. Architecture Overview 129 Based on the existing architecture for supporting TE LSPs, we can 130 extend a few of components to support temporal LSPs. These 131 components include OSPF, CSPF and RSVP-TE. 133 OSPF is extended to distribute and maintain TE inforamtion for a link 134 in a sequence of time intervals. CSPF is extended to compute a path 135 for a temporal LSP based on the TEDB containing TE information for 136 every link in a sequence of time intervals. RSVP-TE is extended to 137 create a temporal LSP and maintain the status of the temporal LSP. 139 4.2. Operations Overview 141 On the ingress of a temporal LSP, a user configures it with a time 142 interval or a sequence of time intervals. A simple time interval is 143 a time interval from start time Ta to end time Tb, which may be 144 represented as [Ta, Tb]. 146 When an LSP is configured with time interval [Ta, Tb], a path 147 satisfying the constraints for the LSP in the time interval is 148 computed and the LSP along the path is set up to carry traffic from 149 Ta to Tb. 151 For time interval from start time Ta to infinite as end time, it may 152 be represented as [Ta, INFINITE]. 154 In addition to simple time intervals, there are recurrent time 155 intervals and elastic time intervals. 157 A recurrent time interval represents a series of repeated simple time 158 intervals. It has a simple time interval such as [Ta, Tb], a number 159 of repeats such as 10 (repeats 10 times), and a repeat cycle/time 160 such as a week (repeats every week). 162 Recurrent time interval "[Ta, Tb] repeats n times with repeat cycle 163 C" represents n+1 simple time intervals as follows: 165 [Ta, Tb], [Ta+C, Tb+C], [Ta+2C, Tb+2C], . . ., [Ta+nC, Tb+nC] 167 When an LSP is configured with a recurrent time interval such as 168 "[Ta, Tb] repeats 10 times with a repeat cycle a week", a path 169 satisfying the constraints for the LSP in each of the simple time 170 intervals (such as 11 simple time intervals) represented by the 171 recurrent time interval is computed and the LSP along the path is set 172 up to carry traffic in each of the simple time intervals. 174 An elastic time interval represents a time period with an elastic 175 range. It has a simple time interval such as [Ta, Tb] with an 176 elastic range such as within -P and Q. 178 Elastic time interval "[Ta, Tb] within -P and Q" means a time period 179 from (Ta+X) to (Tb+X), where -P <= X <= Q, P and Q is an amount of 180 time such as 600 seconds. 182 When an LSP is configured with an elastic time interval such as "[Ta, 183 Tb] within -P and Q", a path is computed such that the path satisfies 184 the constraints for the LSP in the time period from (Ta+X) to (Tb+X) 185 and |X| is the minimum value from -P to Q. That is that [Ta+X, Tb+X] 186 is the time interval closest to [Ta, Tb] within the elastic range. 187 The LSP along the path is set up to carry traffic in the time period 188 from (Ta+X) to (Tb+X). 190 5. TIME INTERVAL Object 192 This section presents a few of TIME-INTERVAL objects, which are the 193 internal representations of time intervals. A Class-Num for the 194 objects is TBD, which is to be assigned by IANA. 196 5.1. Absolute TIME INTERVAL Object 198 The format of an absolute TIME-INTERVAL object body is illustrated 199 below. 201 Class-Name: TIME-INTERVAL, Class-Num: TBD, C-Type = 1 202 0 1 2 3 203 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 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | Start-time | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | End-time | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 o Start-time: The time LSP starts to carry traffic 211 o End-time: The time LSP ends carrying traffic 213 An absolute TIME-INTERVAL object contains a Start-time and an End- 214 time, representing time interval [Start-time, End-time]. All bits in 215 End-time field set to one represents INFINITE. Both of these two 216 times are the times that are synchronized among all network nodes. 218 Thus the clocks on all the nodes MUST be synchronized if an absolute 219 TIME-INTERVAL object is used. The time period represented in an 220 absolute TIME-INTERVAL object is more accurate. 222 5.2. Relative TIME INTERVAL Object 224 The format of a relative TIME-INTERVAL object body is shown below. 226 Class-Name: TIME-INTERVAL, Class-Num: TBD, C-Type = 2 227 0 1 2 3 228 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 229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 230 | Start-time-length | 231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 232 | End-time-length | 233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 o Start-time-length: The time length in seconds from current time 236 to the time LSP starts to carry traffic 237 o End-time-length: The time length in seconds from current time 238 to the time LSP ends carrying traffic 240 A relative TIME-INTERVAL object contains a Start-time-length and an 241 End-time-length, which represents time interval below: 243 [current-time + Start-time-length, current-time + End-time-length] 245 where current-time is the current local time on a node. All bits in 246 End-time-length field set to one represents INFINITE. 248 When a time interval from time Ta to time Tb is configured on a node, 249 these two time lengths are the time lengths that are computed on the 250 node using the current local time as follows. 252 Start-time-length = Ta - current-time; 253 End-time-length = Tb - current-time; 255 For a relative TIME-INTERVAL object, the clocks/times on all the 256 nodes can be different. 258 5.3. Recurrent Absolute TIME INTERVAL Object 260 For a recurrent absolute TIME-INTERVAL object, its body contains a 261 Start-time, an End-time, a Repeat-time-length, a Options field and a 262 Number-repeats field. The format of its body is illustrated below: 264 The Start-time and End-time represents time interval [Start-time, 265 End-time]. The Repeat-time-length represents a repeat cycle/time, 266 which is valid if the Options field is set to indicate the way to 267 repeat is "repeat every Repeat-time-length". The Options field 268 indicates a way to repeat. The Number-repeats indicates the number 269 of repeats of time interval [Start-time, End-time]. 271 Class-Name: TIME-INTERVAL, Class-Num: TBD, C-Type = 3 272 0 1 2 3 273 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 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 | Start-time | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | End-time | 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 | Repeat-time-length | 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 281 | Options | Number-repeats | Reserved(0) | 282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 Start-time: The time LSP starts to carry traffic. 286 End-time: The time LSP ends carrying traffic. 288 Repeat-time-length: The time length in seconds after which LSP 289 starts to carry traffic again for (End-time - Start-time). 291 Options: Indicates a way to repeat. 293 Options = 1: repeat every day; 295 Options = 2: repeat every week; 297 Options = 3: repeat every month; 299 Options = 4: repeat every year; 301 Options = 5: repeat every Repeat-time-length. 303 Number-repeats: The number of repeats. In each of repeats, LSP 304 carries traffic. 306 5.4. Recurrent Relative TIME INTERVAL Object 308 For a recurrent relative TIME-INTERVAL object, the format of its body 309 is illustrated below. it contains a Start-time-length, an End-time- 310 length, a Repeat-time-length, a Options field and a Number-repeats 311 field. 313 The Start-time-length and End-time-length represents time interval 315 [current-time + Start-time-length, current-time + End-time-length] 317 where current-time is a current local time. 319 The Repeat-time-length represents a repeat cycle/time, which is valid 320 if the Options field is set to indicate the way to repeat is "repeat 321 every Repeat-time-length". The Options field indicates a way to 322 repeat. The Number-repeats indicates the number of repeats of the 323 time interval above. 325 Class-Name: TIME-INTERVAL, Class-Num: TBD, C-Type = 4 326 0 1 2 3 327 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 328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 329 | Start-time-length | 330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 331 | End-time-length | 332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 333 | Repeat-time-length | 334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 | Options | Number-repeats | Reserved (0) | 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 Start-time-length: The time length in seconds from a current local 339 time to the time LSP starts to carry traffic. 341 End-time-length: The time length in seconds from a current local 342 time to the time LSP ends carrying traffic. 344 Repeat-time-length: The time length in seconds after which LSP 345 starts to carry traffic again for (End-time-length - Start-time- 346 length). 348 Options: Indicates a way to repeat. 350 Options = 1: repeat every day; 352 Options = 2: repeat every week; 354 Options = 3: repeat every month; 356 Options = 4: repeat every year; 358 Options = 5: repeat every Repeat-time-length. 360 Number-repeats: The number of repeats. In each of repeats, LSP 361 carries traffic. 363 6. Path Message 365 A Path message is enhanced to carry the information about a time 366 interval or a sequence of time intervals through including a time 367 interval list. The format of the message is illustrated below. 369 ::= [ ] 370 [ [ | ] ...] 371 [ ] 372 [ ] 373 [ ] [ ...] 374 [ ] [ ] 375 [ ] [ ... ] 376 [] 377 [