idnits 2.17.1 draft-ietf-tsvwg-sctp-failover-13.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 (September 1, 2015) is 3154 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) ** Obsolete normative reference: RFC 4960 (Obsoleted by RFC 9260) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Y. Nishida 3 Internet-Draft GE Global Research 4 Intended status: Standards Track P. Natarajan 5 Expires: March 4, 2016 Cisco Systems 6 A. Caro 7 BBN Technologies 8 P. Amer 9 University of Delaware 10 K. Nielsen 11 Ericsson 12 September 1, 2015 14 SCTP-PF: Quick Failover Algorithm in SCTP 15 draft-ietf-tsvwg-sctp-failover-13.txt 17 Abstract 19 SCTP supports multi-homing. However, when the failover operation 20 specified in RFC4960 is followed, there can be significant delay and 21 performance degradation in the data transfer path failover. To 22 overcome this problem this document specifies a quick failover 23 algorithm (SCTP-PF) based on the introduction of a Potentially Failed 24 (PF) state in SCTP Path Management. 26 The document also specifies a dormant state operation of SCTP. This 27 dormant state operation is required to be followed by an SCTP-PF 28 implementation, but it may equally well be applied by a standard 29 RFC4960 SCTP implementation. 31 Additionally, the document introduces an alternative switchback 32 operation mode called Primary Path Switchover that will be beneficial 33 in certain situations. This mode of operation applies to both a 34 standard RFC4960 SCTP implementation as well as to a SCTP-PF 35 implementation. 37 The procedures defined in the document require only minimal 38 modifications to the RFC4960 specification. The procedures are 39 sender-side only and do not impact the SCTP receiver. 41 Status of This Memo 43 This Internet-Draft is submitted in full conformance with the 44 provisions of BCP 78 and BCP 79. 46 Internet-Drafts are working documents of the Internet Engineering 47 Task Force (IETF). Note that other groups may also distribute 48 working documents as Internet-Drafts. The list of current Internet- 49 Drafts is at http://datatracker.ietf.org/drafts/current/. 51 Internet-Drafts are draft documents valid for a maximum of six months 52 and may be updated, replaced, or obsoleted by other documents at any 53 time. It is inappropriate to use Internet-Drafts as reference 54 material or to cite them other than as "work in progress." 56 This Internet-Draft will expire on March 4, 2016. 58 Copyright Notice 60 Copyright (c) 2015 IETF Trust and the persons identified as the 61 document authors. All rights reserved. 63 This document is subject to BCP 78 and the IETF Trust's Legal 64 Provisions Relating to IETF Documents 65 (http://trustee.ietf.org/license-info) in effect on the date of 66 publication of this document. Please review these documents 67 carefully, as they describe your rights and restrictions with respect 68 to this document. Code Components extracted from this document must 69 include Simplified BSD License text as described in Section 4.e of 70 the Trust Legal Provisions and are provided without warranty as 71 described in the Simplified BSD License. 73 Table of Contents 75 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 76 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4 77 3. SCTP with Potentially Failed Destination State (SCTP-PF) . . 4 78 3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 4 79 3.2. Specification of the SCTP-PF Procedures . . . . . . . . . 5 80 4. Dormant State Operation . . . . . . . . . . . . . . . . . . . 9 81 4.1. SCTP Dormant State Procedure . . . . . . . . . . . . . . 10 82 5. Primary Path Switchover . . . . . . . . . . . . . . . . . . . 11 83 6. Suggested SCTP Protocol Parameter Values . . . . . . . . . . 12 84 7. Socket API Considerations . . . . . . . . . . . . . . . . . . 12 85 7.1. Support for the Potentially Failed Path State . . . . . . 13 86 7.2. Peer Address Thresholds (SCTP_PEER_ADDR_THLDS) Socket 87 Option . . . . . . . . . . . . . . . . . . . . . . . . . 14 88 7.3. Exposing the Potentially Failed Path State 89 (SCTP_EXPOSE_POTENTIALLY_FAILED_STATE) Socket Option . . 15 90 8. Security Considerations . . . . . . . . . . . . . . . . . . . 16 91 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 92 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 93 11. Proposed Change of Status (to be Deleted before Publication) 17 94 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 95 12.1. Normative References . . . . . . . . . . . . . . . . . . 17 96 12.2. Informative References . . . . . . . . . . . . . . . . . 17 97 Appendix A. Discussions of Alternative Approaches . . . . . . . 18 98 A.1. Reduce Path.Max.Retrans (PMR) . . . . . . . . . . . . . . 18 99 A.2. Adjust RTO related parameters . . . . . . . . . . . . . . 19 100 Appendix B. Discussions for Path Bouncing Effect . . . . . . . . 20 101 Appendix C. SCTP-PF for SCTP Single-homed Operation . . . . . . 20 102 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 104 1. Introduction 106 The Stream Control Transmission Protocol (SCTP) specified in 107 [RFC4960] supports multi-homing at the transport layer. SCTP's 108 multi-homing features include failure detection and failover 109 procedures to provide network interface redundancy and improved end- 110 to-end fault tolerance. In SCTP's current failure detection 111 procedure, the sender must experience Path.Max.Retrans (PMR) number 112 of consecutive failed timer-based retransmissions on a destination 113 address before detecting a path failure. Until detecting the path 114 failure, the sender continues to transmit data on the failed path. 115 The prolonged time in which [RFC4960] SCTP continues to use a failed 116 path severely degrades the performance of the protocol. To address 117 this problem, this document specifies a quick failover algorithm 118 (SCTP-PF) based on the introduction of a new Potentially Failed (PF) 119 path state in SCTP path management. The performance deficiencies of 120 the [RFC4960] failover operation, and the improvements obtainable 121 from the introduction of a Potentially Failed state in SCTP, were 122 proposed and documented in [NATARAJAN09] for Concurrent Multipath 123 Transfer SCTP [IYENGAR06]. 125 While SCTP-PF can accelerate failover process and improve 126 performance, the risks that an SCTP endpoint enters in dormant state 127 where all destination addresses are inactive can be increased. 128 [RFC4960] leaves the protocol operation during dormant state to 129 implementations and encourages to avoid entering the state as much as 130 possible by careful tuning of the Path.Max.Retrans (PMR) and 131 Association.Max.Retrans (AMR) parameters. We specify a dormant state 132 operation for SCTP-PF which makes SCTP-PF provide the same disruption 133 tolerance as [RFC4960] despite that the dormant state may be entered 134 more quickly. The dormant state operation may equally well be 135 applied by an [RFC4960] implementation and will here serve to provide 136 added fault tolerance for situations where the tuning of the 137 Path.Max.Retrans (PMR) and Association.Max.Retrans (AMR) parameters 138 fail to provide adequate prevention of the entering of the dormant 139 state. 141 The operation after the recovery of a failed path equally well 142 impacts the performance of the protocol. With the procedures 143 specified in [RFC4960] SCTP will, after a failover from the primary 144 path, switch back to use the primary path for data transfer as soon 145 as this path becomes available again. From a performance perspective 146 such a forced switchback of the data transmission path can be 147 suboptimal as the CWND towards the original primary destination 148 address has to be rebuilt once data transfer resumes, [CARO02]. As 149 an optional alternative to the switchback operation of [RFC4960], 150 this document specifies an alternative Primary Path Switchover 151 procedure which avoid such forced switchbacks of the data transfer 152 path. The Primary Path Switchover operation was originally proposed 153 in [CARO02]. 155 While SCTP-PF primarily is motivated by a desire to improve the 156 multi-homed operation, the feature applies also to SCTP single-homed 157 operation. Here the algorithm serves to provide increased failure 158 detection on idle associations, whereas the failover or switchback 159 aspects of the algorithm will not be activated. This is discussed in 160 more detail in Appendix C. 162 A brief description of the motivation for the introduction of the 163 Potentially Failed state including a discussion of alternative 164 approaches to mitigate the deficiencies of the [RFC4960] failover 165 operation are given in the Appendices. Discussion of path bouncing 166 effects that might be caused by frequent switchover, are also 167 provided there. 169 2. Conventions and Terminology 171 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 172 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 173 document are to be interpreted as described in [RFC2119]. 175 3. SCTP with Potentially Failed Destination State (SCTP-PF) 177 3.1. Overview 179 To minimize the performance impact during failover, the sender should 180 avoid transmitting data to a failed destination address as early as 181 possible. In the [RFC4960] SCTP path management scheme, the sender 182 stops transmitting data to a destination address only after the 183 destination address is marked inactive. This process takes a 184 significant amount of time as it requires the error counter of the 185 destination address to exceed the Path.Max.Retrans (PMR) threshold. 186 The issue cannot simply be mitigated by lowering of the PMR threshold 187 because this may result in spurious failure detection and unnecessary 188 prevention of the usage of a preferred primary path as well as it, 189 due to the coupled tuning of the Path.Max.Retrans (PMR) and the 190 Association.Max.Retrans (AMR) parameter values in [RFC4960], may 191 result in compromisation of the fault tolerance of SCTP. 193 The solution provided in this document is to extend the SCTP path 194 management scheme of [RFC4960] by the addition of the Potentially 195 Failed (PF) state as an intermediate state in between the active and 196 inactive state of a destination address in the [RFC4960] path 197 management scheme, and let the failover of data transfer away from a 198 destination address be driven by the entering of the PF state instead 199 of by the entering of the inactive state. Thereby SCTP may perform 200 quick failover without compromising the overall fault tolerance of 201 [RFC4960] SCTP. At the same time, RTO-based HEARTBEAT probing is 202 initiated towards a destination address once it enters PF state. 203 Thereby SCTP may quickly ascertain whether network connectivity 204 towards the destination address is broken or whether the failover was 205 spurious. In the case where the failover was spurious data transfer 206 may quickly resume towards the original destination address. 208 The new failure detection algorithm assumes that loss detected by a 209 timeout implies either severe congestion or network connectivity 210 failure and it assumes that by default a destination address is 211 classified as PF already at the occurrence of one first timeout. 213 3.2. Specification of the SCTP-PF Procedures 215 The SCTP-PF operation is specified as follows: 217 1. The sender maintains a new tunable SCTP Protocol Parameter 218 called PotentiallyFailed.Max.Retrans (PFMR). The PFMR defines 219 the new intermediate PF threshold on the destination address 220 error counter at exceed of which the destination address is 221 classified as PF. The RECOMMENDED value of PFMR is 0, but other 222 values MAY be used. Setting PFMR larger to or equal to 223 Path.Max.Retrans (PMR) does not result in definition of a PF 224 threshold for the destination address. I.e., the destination 225 address will not be classified as PF prior to reaching inactive 226 state. 228 2. The error counter of an active destination address is 229 incremented as specified in [RFC4960]. This means that the 230 error counter of the destination address will be incremented 231 each time the T3-rtx timer expires, or each time a HEARTBEAT 232 chunk is sent when idle and not acknowledged within an RTO. 233 When the value in the destination address error counter exceeds 234 PFMR, the endpoint MUST mark the destination address as in the 235 PF state. 237 3. The PFMR threshold defines the point the destination address no 238 longer is considered a good candidate for data transmission and 239 a SCTP-PF sender SHOULD NOT send data to destination addresses 240 in PF state when alternative destination addresses in active 241 state are available. Specifically this means that: 243 i When there is outbound data to send and the destination 244 address presently used for data transmission is in PF state, 245 the sender SHOULD choose a destination address in active 246 state, if one exists, and failover to deploy this destination 247 address for data transmission. 249 ii When retransmitting data that has timed out and the sender 250 thus by [RFC4960], section 6.4.1, should attempt to pick a 251 new destination address for data retransmission, the sender 252 SHOULD choose an alternate destination transport address in 253 active state if one exists. 255 iii When there is outbound data to send and the SCTP user 256 explicitly requests to send data to a destination address in 257 PF state, the sender SHOULD send the data to an alternate 258 destination address in active state if one exists. 260 When choosing among multiple destination addresses in active 261 state the following considerations are given: 263 A. An SCTP sender should comply with [RFC4960], section 6.4.1, 264 principles of choosing most divergent source-destination 265 pairs compared with, for i.: the destination address in PF 266 state that it performs a failover from, and for ii.: the 267 destination address towards which the data timed out. Rules 268 for picking the most divergent source-destination pair are 269 an implementation decision and are not specified within this 270 document. 272 B. A SCTP-PF sender MAY choose to send data to a destination 273 address in PF state, even if destination addresses in active 274 state exist, have the SCTP-PF sender other means of 275 information available that disqualifies the destination 276 address in active state from being preferred. However, the 277 discussion of such mechanisms is outside of the scope of the 278 SCTP-PF operation specified in this document. 280 In all cases, the sender MUST NOT change the state of chosen 281 destination address, whether this state be active or PF, and it 282 MUST NOT clear the error counter of the destination address as a 283 result of choosing the destination address for data 284 transmission. 286 4. When the destination addresses are all in PF state or some in PF 287 state and some in inactive state, the sender MUST choose one 288 destination address in PF state and transmit or retransmit data 289 to this destination address using the following rules: 291 A. The sender SHOULD choose the destination in PF state with 292 the lowest error count (fewest consecutive timeouts) for 293 data transmission and transmit or retransmit data to this 294 destination. 296 B. When there are multiple destination addresses in PF state 297 with same error count, the sender should let the choice 298 among the multiple destination addresses in PF state with 299 equal error count be based on the [RFC4960], section 6.4.1, 300 principles of choosing most divergent source-destination 301 pairs when executing (potentially consecutive) 302 retransmission. Rules for picking the most divergent 303 source-destination pair are an implementation decision and 304 are not specified within this document. 306 C. A sender MAY choose to deploy other strategies than the 307 above when choosing among multiple destinations in PF state 308 have the SCTP-PF sender other means of information available 309 that qualifies a particular destination address for being 310 used. The SCTP-PF protocol operation specified in this 311 document makes no assumption of the existence of such other 312 means of information and specifies for the above as the 313 default operation of an SCTP-PF sender. 315 The sender MUST NOT change the state and the error counter of 316 any destination address regardless of whether it has been chosen 317 for transmission or not. 319 5. The HB.interval of the Path Heartbeat function of [RFC4960] MUST 320 be ignored for destination addresses in PF state. Instead 321 HEARTBEAT chunks are sent to destination addresses in PF state 322 once per RTO. HEARTBEAT chunks SHOULD be sent to destination 323 addresses in PF state, but the sending of HEARTBEATS MUST honor 324 whether the Path Heartbeat function (Section 8.3 of [RFC4960]) 325 is enabled for the destination address or not. I.e., if the 326 Path Heartbeat function is disabled for the destination address 327 in question, HEARTBEATS MUST NOT be sent. Note that when 328 Heartbeat function is disabled, it may take longer to transition 329 a destination address in PF state back to active state. 331 6. HEARTBEATs are sent when a destination address reaches the PF 332 state. When a HEARTBEAT chunk is not acknowledged within the 333 RTO, the sender increments the error counter and exponentially 334 backs off the RTO value. If the error counter is less than PMR, 335 the sender transmits another packet containing the HEARTBEAT 336 chunk immediately after timeout expiration on the previous 337 HEARTBEAT. When data is being transmitted to a destination 338 address in the PF state, the transmission of a HEARTBEAT chunk 339 MAY be omitted in case receipt of a SACK of or a T3-rtx timer 340 expiration on the outstanding data can provide equivalent 341 information, such as a case where the data chunk has transmitted 342 to a single destination. Likewise, the timeout of a HEARTBEAT 343 chunk MAY be ignored if data is outstanding towards the 344 destination address. 346 7. When the sender receives a HEARTBEAT ACK from a HEARTBEAT sent 347 to a destination address in PF state, the sender SHOULD clear 348 the error counter of the destination address and transition the 349 destination address back to active state. When the sender 350 resumes data transmission on a destination address after a 351 transition of the destination address from PF to active state, 352 it MUST do this following the prescriptions of Section 7.2 of 353 [RFC4960]. In a situation where a HEARTBEAT ACK arrives while 354 there is data outstanding towards the destination address to 355 which the HEARTBEAT was sent, then an implementation MAY choose 356 to not have the HEARTBEAT ACK reset the error counter, but have 357 the error counter reset await the fate of the outstanding data 358 transmission. This situation can happen when data is sent to a 359 destination address in PF state. 361 8. Additional (PMR - PFMR) consecutive timeouts on a destination 362 address in PF state confirm the path failure, upon which the 363 destination address transitions to the inactive state. As 364 described in [RFC4960], the sender (i) SHOULD notify the ULP 365 about this state transition, and (ii) transmit HEARTBEAT chunks 366 to the inactive destination address at a lower HB.interval 367 frequency as described in Section 8.3 of [RFC4960] (when the 368 Path Heartbeat function is enabled for the destination address). 370 9. Acknowledgments for chunks that have been transmitted to 371 multiple destinations (i.e., a chunk which has been 372 retransmitted to a different destination address than the 373 destination address to which the chunk was first transmitted) 374 SHOULD NOT clear the error count for an inactive destination 375 address and SHOULD NOT transition a destination address in PF 376 state back to active state, since a sender cannot disambiguate 377 whether the ACK was for the original transmission or the 378 retransmission(s). A SCTP sender MAY apply a different approach 379 for the error count handling based on unequivocally information 380 on which destination (including multiple destination addresses) 381 the chunk reached. This document makes no reference to what 382 such unequivocally information could consist of, neither how 383 such unequivocally information could be obtained. The design of 384 such an alternative approach is left to implementations. 386 10. Acknowledgments for data chunks that has been transmitted to one 387 destination address only MUST clear the error counter for the 388 destination address and MUST transition a destination address in 389 PF state back to active state. This situation can happen when 390 new data is sent to a destination address in the PF state. It 391 can also happen in situations where the destination address is 392 in the PF state due to the occurrence of a spurious T3-rtx timer 393 and acknowledgments start to arrive for data sent prior to 394 occurrence of the spurious T3-rtx and data has not yet been 395 retransmitted towards other destinations. This document does 396 not specify special handling for detection of or reaction to 397 spurious T3-rtx timeouts, e.g., for special operation vis-a-vis 398 the congestion control handling or data retransmission operation 399 towards a destination address which undergoes a transition from 400 active to PF to active state due to a spurious T3-rtx timeout. 401 But it is noted that this is an area which would benefit from 402 additional attention, experimentation and specification for 403 single-homed SCTP as well as for multi-homed SCTP protocol 404 operation. 406 11. When all destination addresses are in inactive state, and SCTP 407 protocol operation thus is said to be in dormant state, the 408 prescriptions given in Section 4 shall be followed. 410 12. The SCTP stack SHOULD provide the ULP with the means to expose 411 the PF state of its destinations as well as the means to notify 412 of state transitions from active to PF, and vice-versa. However 413 it is recommended that an SCTP stack implementing SCTP-PF also 414 allows for that the ULP is kept ignorant of the PF state of its 415 destinations and the associated state transition. For this 416 reason it is recommended that an SCTP stack implementing SCTP-PF 417 also should provide the ULP with the means to suppress exposure 418 of PF state and the associated state transitions. 420 4. Dormant State Operation 422 In a situation with complete disruption of the communication in 423 between the SCTP Endpoints, the aggressive HEARTBEAT transmissions of 424 SCTP-PF on destination addresses in PF state may make the association 425 enter dormant state faster than a standard [RFC4960] SCTP 426 implementation given the same setting of Path.Max.Retrans (PMR) and 427 Association.Max.Retrans (AMR). For example, an SCTP association with 428 two destination addresses typically would reach dormant state in half 429 the time of an [RFC4960] SCTP implementation in such situations. 430 This is because a SCTP PF sender will send HEARTBEATS and data 431 retransmissions in parallel with RTO intervals when there are 432 multiple destinations addresses in PF state. This argument presumes 433 that RTO << HB.interval of [RFC4960]. With the design goal that 434 SCTP-PF shall provide the same level of disruption tolerance as an 435 [RFC4960] SCTP implementation with the same Path.Max.Retrans (PMR) 436 and Association.Max.Retrans (AMR) setting, we prescribe for that an 437 SCTP-PF implementation SHOULD operate as described below in 438 Section 4.1 during dormant state. 440 An SCTP-PF implementation MAY choose a different dormant state 441 operation than the one described below in Section 4.1 provided that 442 the solution chosen does not compromise the fault tolerance of the 443 SCTP-PF operation. 445 The below prescription for SCTP-PF dormant state handling SHOULD NOT 446 be coupled to the value of the PFMR, but solely to the activation of 447 SCTP-PF logic in an SCTP implementation. 449 It is noted that the below dormant state operation is considered to 450 provide added disruption tolerance also for an [RFC4960] SCTP 451 implementation, and that it can be sensible for an [RFC4960] SCTP 452 implementation to follow this mode of operation. For an [RFC4960] 453 SCTP implementation the continuation of data transmission during 454 dormant state makes the fault tolerance of SCTP be more robust 455 towards situations where some, or all, alternative paths of an SCTP 456 association approach, or reach, inactive state prior to that the 457 primary path used for data transmission observes trouble. 459 4.1. SCTP Dormant State Procedure 461 a. When the destination addresses are all in inactive state and data 462 is available for transfer, the sender MUST choose one destination 463 and transmit data to this destination address. 465 b. The sender MUST NOT change the state of the chosen destination 466 address (it remains in inactive state) and it MUST NOT clear the 467 error counter of the destination address as a result of choosing 468 the destination address for data transmission. 470 c. The sender SHOULD choose the destination in inactive state with 471 the lowest error count (fewest consecutive timeouts) for data 472 transmission. When there are multiple destinations with same 473 error count in inactive state, the sender SHOULD attempt to pick 474 the most divergent source - destination pair from the last source 475 - destination pair where failure was observed. Rules for picking 476 the most divergent source-destination pair are an implementation 477 decision and are not specified within this document. To support 478 differentiation of inactive destination addresses based on their 479 error count SCTP will need to allow for increment of the 480 destination address error counters up to some reasonable limit 481 above PMR+1, thus changing the prescriptions of [RFC4960], 482 section 8.3, in this respect. The exact limit to apply is not 483 specified in this document but it is considered reasonable to 484 require for such to be an order of magnitude higher than the PMR 485 value. A sender MAY choose to deploy other strategies that the 486 strategy defined by here. The strategy to prioritize the last 487 active destination address, i.e., the destination address with 488 the fewest error counts is optimal when some paths are 489 permanently inactive, but suboptimal when a path instability is 490 transient. 492 5. Primary Path Switchover 494 The objective of the Primary Path Switchover operation is to allow 495 the SCTP sender to continue data transmission on a new working path 496 even when the old primary destination address becomes active again. 497 This is achieved by having SCTP perform a switch over of the primary 498 path to the new working path if the error counter of the primary path 499 exceeds a certain threshold. This mode of operation can be applied 500 not only to SCTP-PF implementations, but also to [RFC4960] 501 implementations. 503 The Primary Path Switchover operation requires only sender side 504 changes. The details are: 506 1. The sender maintains a new tunable parameter, called 507 Primary.Switchover.Max.Retrans (PSMR). For SCTP-PF 508 implementations, the PSMR MUST be set greater or equal to the 509 PFMR value. For [RFC4960] implementations the PSMR MUST be set 510 greater or equal to the PMR value. Implementations MUST reject 511 any other values of PSMR. 513 2. When the path error counter on a set primary path exceeds PSMR, 514 the SCTP implementation MUST autonomously select and set a new 515 primary path. 517 3. The primary path selected by the SCTP implementation MUST be the 518 path which at the given time would be chosen for data transfer. 519 A previously failed primary path can be used as data transfer 520 path as per normal path selection when the present data transfer 521 path fails. 523 4. For SCTP-PF, the recommended value of PSMR is PFMR when Primary 524 Path Switchover operation mode is used. This means that no 525 forced switchback to a previously failed primary path is 526 performed. An SCTP-PF implementation of Primary Path Switchover 527 MUST support the setting of PSMR = PFMR. A SCTP-PF 528 implementation of Primary Path Switchover MAY support setting of 529 PSMR > PFMR. 531 5. For [RFC4960] SCTP, the recommended value of PSMR is PMR when 532 Primary Path Switchover is used. This means that no forced 533 switchback to a previously failed primary path is performed. A 534 [RFC4960] SCTP implementation of Primary Path Switchover MUST 535 support the setting of PSMR = PMR. An [RFC4960] SCTP 536 implementation of Primary Path Switchover MAY support larger 537 settings of PSMR > PMR. 539 6. It MUST be possible to disable the Primary Path Switchover 540 operation and obtain the standard switchback operation of 541 [RFC4960]. 543 The manner of switch over operation that is most optimal in a given 544 scenario depends on the relative quality of a set primary path versus 545 the quality of alternative paths available as well as it depends on 546 the extent to which it is desired for the mode of operation to 547 enforce traffic distribution over a number of network paths. I.e., 548 load distribution of traffic from multiple SCTP associations may be 549 sought to be enforced by distribution of the set primary paths with 550 [RFC4960] switchback operation. However as [RFC4960] switchback 551 behavior is suboptimal in certain situations, especially in scenarios 552 where a number of equally good paths are available, an SCTP 553 implementation MAY support also, as alternative behavior, the Primary 554 Path Switchover mode of operation and MAY enable it based on users' 555 requests. 557 For an SCTP implementation that implements the Primary Path 558 Switchover operation, this specification RECOMMENDS that the standard 559 RFC4960 switchback operation is retained as the default operation. 561 6. Suggested SCTP Protocol Parameter Values 563 This document does not alter the [RFC4960] value RECOMMENDATIONS for 564 the SCTP Protocol Parameters defined in [RFC4960]. 566 The following protocol parameter is RECOMMENDED: 568 PotentiallyFailed.Max.Retrans (PFMR) - 0 570 7. Socket API Considerations 572 This section describes how the socket API defined in [RFC6458] is 573 extended to provide a way for the application to control and observe 574 the SCTP-PF behavior as well as the Primary Path Switchover function. 576 Please note that this section is informational only. 578 A socket API implementation based on [RFC6458] is, by means of the 579 existing SCTP_PEER_ADDR_CHANGE event, extended to provide the event 580 notification when a peer address enters or leaves the potentially 581 failed state as well as the socket API implementation is extended to 582 expose the potentially failed state of a peer address in the existing 583 SCTP_GET_PEER_ADDR_INFO structure. 585 Furthermore, two new read/write socket options for the level 586 IPPROTO_SCTP and the name SCTP_PEER_ADDR_THLDS and 587 SCTP_EXPOSE_POTENTIALLY_FAILED_STATE are defined as described below. 588 The first socket option is used to control the values of the PFMR and 589 PSMR parameters described in Section 3 and in Section 5. The second 590 one controls the exposition of the potentially failed path state. 592 Support for the SCTP_PEER_ADDR_THLDS and 593 SCTP_EXPOSE_POTENTIALLY_FAILED_STATE socket options need also to be 594 added to the function sctp_opt_info(). 596 7.1. Support for the Potentially Failed Path State 598 As defined in [RFC6458], the SCTP_PEER_ADDR_CHANGE event is provided 599 if the status of a peer address changes. In addition to the state 600 changes described in [RFC6458], this event is also provided, if a 601 peer address enters or leaves the potentially failed state. The 602 notification as defined in [RFC6458] uses the following structure: 604 struct sctp_paddr_change { 605 uint16_t spc_type; 606 uint16_t spc_flags; 607 uint32_t spc_length; 608 struct sockaddr_storage spc_aaddr; 609 uint32_t spc_state; 610 uint32_t spc_error; 611 sctp_assoc_t spc_assoc_id; 612 } 614 [RFC6458] defines the constants SCTP_ADDR_AVAILABLE, 615 SCTP_ADDR_UNREACHABLE, SCTP_ADDR_REMOVED, SCTP_ADDR_ADDED, and 616 SCTP_ADDR_MADE_PRIM to be provided in the spc_state field. This 617 document defines in addition to that the new constant 618 SCTP_ADDR_POTENTIALLY_FAILED, which is reported if the affected 619 address becomes potentially failed. 621 The SCTP_GET_PEER_ADDR_INFO socket option defined in [RFC6458] can be 622 used to query the state of a peer address. It uses the following 623 structure: 625 struct sctp_paddrinfo { 626 sctp_assoc_t spinfo_assoc_id; 627 struct sockaddr_storage spinfo_address; 628 int32_t spinfo_state; 629 uint32_t spinfo_cwnd; 630 uint32_t spinfo_srtt; 631 uint32_t spinfo_rto; 632 uint32_t spinfo_mtu; 633 }; 635 [RFC6458] defines the constants SCTP_UNCONFIRMED, SCTP_ACTIVE, and 636 SCTP_INACTIVE to be provided in the spinfo_state field. This 637 document defines in addition to that the new constant 638 SCTP_POTENTIALLY_FAILED, which is reported if the peer address is 639 potentially failed. 641 7.2. Peer Address Thresholds (SCTP_PEER_ADDR_THLDS) Socket Option 643 Applications can control the SCTP-PF behavior by getting or setting 644 the number of consecutive timeouts before a peer address is 645 considered potentially failed or unreachable. The same socket option 646 is used by applications to set and get the number of timeouts before 647 the primary path is changed automatically by the Primary Path 648 Switchover function. This socket option uses the level IPPROTO_SCTP 649 and the name SCTP_PEER_ADDR_THLDS. 651 The following structure is used to access and modify the thresholds: 653 struct sctp_paddrthlds { 654 sctp_assoc_t spt_assoc_id; 655 struct sockaddr_storage spt_address; 656 uint16_t spt_pathmaxrxt; 657 uint16_t spt_pathpfthld; 658 uint16_t spt_pathcpthld; 659 }; 661 spt_assoc_id: This parameter is ignored for one-to-one style 662 sockets. For one-to-many style sockets the application may fill 663 in an association identifier or SCTP_FUTURE_ASSOC. It is an error 664 to use SCTP_{CURRENT|ALL}_ASSOC in spt_assoc_id. 666 spt_address: This specifies which peer address is of interest. If a 667 wild card address is provided, this socket option applies to all 668 current and future peer addresses. 670 spt_pathmaxrxt: Each peer address of interest is considered 671 unreachable, if its path error counter exceeds spt_pathmaxrxt. 673 spt_pathpfthld: Each peer address of interest is considered 674 Potentially Failed, if its path error counter exceeds 675 spt_pathpfthld. 677 spt_pathcpthld: Each peer address of interest is not considered the 678 primary remote address anymore, if its path error counter exceeds 679 spt_pathcpthld. Using a value of 0xffff disables the selection of 680 a new primary peer address. If an implementation does not support 681 the automatically selection of a new primary address, it should 682 indicate an error with errno set to EINVAL if a value different 683 from 0xffff is used in spt_pathcpthld. For SCTP-PF, the setting 684 of spt_pathcpthld < spt_pathpfthld should be rejected with errno 685 set to EINVAL. For [RFC4960] SCTP, the setting of spt_pathcpthld 686 < spt_pathmaxrxt should be rejected with errno set to EINVAL. A 687 SCTP-PF implementation MAY support only setting of spt_pathcpthld 688 = spt_pathpfthld and spt_pathcpthld = 0xffff and a [RFC4960] SCTP 689 implementation MAY support only setting of spt_pathcpthld = 690 spt_pathmaxrxt and spt_pathcpthld = 0xffff. In these cases SCTP 691 shall reject setting of other values with errno set to EINVAL. 693 7.3. Exposing the Potentially Failed Path State 694 (SCTP_EXPOSE_POTENTIALLY_FAILED_STATE) Socket Option 696 Applications can control the exposure of the potentially failed path 697 state in the SCTP_PEER_ADDR_CHANGE event and the 698 SCTP_GET_PEER_ADDR_INFO as described in Section 7.1. The default 699 value is implementation specific. 701 This socket option uses the level IPPROTO_SCTP and the name 702 SCTP_EXPOSE_POTENTIALLY_FAILED_STATE. 704 The following structure is used to control the exposition of the 705 potentially failed path state: 707 struct sctp_assoc_value { 708 sctp_assoc_t assoc_id; 709 uint32_t assoc_value; 710 }; 712 assoc_id: This parameter is ignored for one-to-one style sockets. 713 For one-to-many style sockets the application may fill in an 714 association identifier or SCTP_FUTURE_ASSOC. It is an error to 715 use SCTP_{CURRENT|ALL}_ASSOC in assoc_id. 717 assoc_value: The potentially failed path state is exposed if and 718 only if this parameter is non-zero. 720 8. Security Considerations 722 Security considerations for the use of SCTP and its APIs are 723 discussed in [RFC4960] and [RFC6458]. 725 The logic introduced by this document does not impact existing SCTP 726 messages on the wire. Also, this document does not introduce any new 727 SCTP messages on the wire that require new security considerations. 729 SCTP-PF makes SCTP not only more robust during primary path failure/ 730 congestion but also more vulnerable to network connectivity/ 731 congestion attacks on the primary path. SCTP-PF makes it easier for 732 an attacker to trick SCTP to change data transfer path, since the 733 duration of time that an attacker needs to compromise the network 734 connectivity is much shorter than [RFC4960]. However, SCTP-PF does 735 not constitute a significant change in the duration of time and 736 effort an attacker needs to keep SCTP away from the primary path. 737 With the standard switchback operation [RFC4960] SCTP resumes data 738 transfer on its primary path as soon as the next HEARTBEAT succeeds. 740 On the other hand, usage of the Primary Path Switchover mechanism, 741 does change the treat analysis. This is because attackers can force 742 a permanent change of the data transfer path by blocking the primary 743 path until the switchover of the primary path is triggered by the 744 Primary Path Switchover algorithm. This especially will be the case 745 when the Primary Path Switchover is used together with SCTP-PF with 746 the particular setting of PSMR = PFMR = 0, as Primary Path Switchover 747 here happens already at the first RTO timeout experienced. Users of 748 the Primary Path Switchover mechanism should be aware of this fact. 750 The event notification of path state transfer from active to 751 potentially failed state and vice versa gives attackers an increased 752 possibility to generate more local events. However, it is assumed 753 that event notifications are rate-limited in the implementation to 754 address this threat. 756 9. IANA Considerations 758 This document does not create any new registries or modify the rules 759 for any existing registries managed by IANA. 761 10. Acknowledgements 763 The authors wish to thank Michael Tuexen for his many invaluable 764 comments and for his very substantial support with the making of this 765 document. 767 11. Proposed Change of Status (to be Deleted before Publication) 769 Initially this work looked to entail some changes of the Congestion 770 Control (CC) operation of SCTP and for this reason the work was 771 proposed as Experimental. These intended changes of the CC operation 772 have since been judged to be irrelevant and are no longer part of the 773 specification. As the specification entails no other potential 774 harmful features, consensus exists in the WG to bring the work 775 forward as PS. 777 Initially concerns have been expressed about the possibility for the 778 mechanism to introduce path bouncing with potential harmful network 779 impacts. These concerns are believed to be unfounded. This issue is 780 addressed in Appendix B. 782 It is noted that the feature specified by this document is 783 implemented by multiple SCTP SW implementations and furthermore that 784 various variants of the solution have been deployed in Tel co 785 signaling environments for several years with good results. 787 12. References 789 12.1. Normative References 791 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 792 Requirement Levels", BCP 14, RFC 2119, 793 DOI 10.17487/RFC2119, March 1997, 794 . 796 [RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", 797 RFC 4960, DOI 10.17487/RFC4960, September 2007, 798 . 800 12.2. Informative References 802 [CARO02] Caro Jr., A., Iyengar, J., Amer, P., Heinz, G., and R. 803 Stewart, "A Two-level Threshold Recovery Mechanism for 804 SCTP", Tech report, CIS Dept, University of Delaware , 7 805 2002. 807 [CARO04] Caro Jr., A., Amer, P., and R. Stewart, "End-to-End 808 Failover Thresholds for Transport Layer Multi homing", 809 MILCOM 2004 , 11 2004. 811 [CARO05] Caro Jr., A., "End-to-End Fault Tolerance using Transport 812 Layer Multi homing", Ph.D Thesis, University of Delaware , 813 1 2005. 815 [FALLON08] 816 Fallon, S., Jacob, P., Qiao, Y., Murphy, L., Fallon, E., 817 and A. Hanley, "SCTP Switchover Performance Issues in WLAN 818 Environments", IEEE CCNC 2008, 1 2008. 820 [GRINNEMO04] 821 Grinnemo, K-J. and A. Brunstrom, "Performance of SCTP- 822 controlled failovers in M3UA-based SIGTRAN networks", 823 Advanced Simulation Technologies Conference , 4 2004. 825 [IYENGAR06] 826 Iyengar, J., Amer, P., and R. Stewart, "Concurrent 827 Multipath Transfer using SCTP Multihoming over Independent 828 End-to-end Paths.", IEEE/ACM Trans on Networking 14(5), 10 829 2006. 831 [JUNGMAIER02] 832 Jungmaier, A., Rathgeb, E., and M. Tuexen, "On the use of 833 SCTP in failover scenarios", World Multiconference on 834 Systemics, Cybernetics and Informatics , 7 2002. 836 [NATARAJAN09] 837 Natarajan, P., Ekiz, N., Amer, P., and R. Stewart, 838 "Concurrent Multipath Transfer during Path Failure", 839 Computer Communications , 5 2009. 841 [RFC6458] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V. 842 Yasevich, "Sockets API Extensions for the Stream Control 843 Transmission Protocol (SCTP)", RFC 6458, 844 DOI 10.17487/RFC6458, December 2011, 845 . 847 Appendix A. Discussions of Alternative Approaches 849 This section lists alternative approaches for the issues described in 850 this document. Although these approaches do not require to update 851 RFC4960, we do not recommend them from the reasons described below. 853 A.1. Reduce Path.Max.Retrans (PMR) 855 Smaller values for Path.Max.Retrans shorten the failover duration and 856 in fact this is recommended in some research results [JUNGMAIER02] 857 [GRINNEMO04] [FALLON08]. However to significantly reduce the 858 failover time it is required to go down (as with PFMR) to 859 Path.Max.Retrans=0 and with this setting SCTP switches to another 860 destination address already on a single timeout which may result in 861 spurious failover. Spurious failover is a problem in [RFC4960] SCTP 862 as the transmission of HEARTBEATS on the left primary path, unlike in 863 SCTP-PF, is governed by 'HB.interval' also during the failover 864 process. 'HB.interval' is usually set in the order of seconds 865 (recommended value is 30 seconds) and when the primary path becomes 866 inactive, the next HEARTBEAT may be transmitted only many seconds 867 later. Indeed as recommended, only 30 secs later. Meanwhile, the 868 primary path may since long have recovered, if it needed recovery at 869 all (indeed the failover could be truly spurious). In such 870 situations, post failover, an endpoint is forced to wait in the order 871 of many seconds before the endpoint can resume transmission on the 872 primary path and furthermore once it returns on the primary path the 873 CWND needs to be rebuild anew - a process which the throughput 874 already have had to suffer from on the alternate path. Using a 875 smaller value for 'HB.interval' might help this situation, but it 876 would result in a general waste of bandwidth as such more frequent 877 HEARTBEATING would take place also when there are no observed 878 troubles. The bandwidth overhead may be diminished by having the ULP 879 use a smaller 'HB.interval' only on the path which at any given time 880 is set to be the primary path, but this adds complication in the ULP. 882 In addition, smaller Path.Max.Retrans values also affect the 883 'Association.Max.Retrans' value. When the SCTP association's error 884 count exceeds Association.Max.Retrans threshold, the SCTP sender 885 considers the peer endpoint unreachable and terminates the 886 association. Section 8.2 in [RFC4960] recommends that 887 Association.Max.Retrans value should not be larger than the summation 888 of the Path.Max.Retrans of each of the destination addresses. Else 889 the SCTP sender considers its peer reachable even when all 890 destinations are INACTIVE and to avoid this dormant state operation, 891 [RFC4960] SCTP implementation SHOULD reduce Association.Max.Retrans 892 accordingly whenever it reduces Path.Max.Retrans. However, smaller 893 Association.Max.Retrans value compromises the fault tolerance of SCTP 894 as it increases the chances of association termination during minor 895 congestion events. 897 A.2. Adjust RTO related parameters 899 As several research results indicate, we can also shorten the 900 duration of failover process by adjusting RTO related parameters 901 [JUNGMAIER02] [FALLON08]. During failover process, RTO keeps being 902 doubled. However, if we can choose smaller value for RTO.max, we can 903 stop the exponential growth of RTO at some point. Also, choosing 904 smaller values for RTO.initial or RTO.min can contribute to keep the 905 RTO value small. 907 Similar to reducing Path.Max.Retrans, the advantage of this approach 908 is that it requires no modification to the current specification, 909 although it needs to ignore several recommendations described in the 910 Section 15 of [RFC4960]. However, this approach requires to have 911 enough knowledge about the network characteristics between end 912 points. Otherwise, it can introduce adverse side-effects such as 913 spurious timeouts. 915 The significant issue with this approach, however, is that even if 916 the RTO.max is lowered to an optimal low value, then as long as the 917 Path.Max.Retrans is kept at the [RFC4960] recommended value, the 918 reduction of the RTO.max doesn't reduce the failover time 919 sufficiently enough to prevent severe performance degradation during 920 failover. 922 Appendix B. Discussions for Path Bouncing Effect 924 The methods described in the document can accelerate the failover 925 process. Hence, they might introduce the path bouncing effect where 926 the sender keeps changing the data transmission path frequently. 927 This sounds harmful to the data transfer, however several research 928 results indicate that there is no serious problem with SCTP in terms 929 of path bouncing effect [CARO04] [CARO05]. 931 There are two main reasons for this. First, SCTP is basically 932 designed for multipath communication, which means SCTP maintains all 933 path related parameters (CWND, ssthresh, RTT, error count, etc) per 934 each destination address. These parameters cannot be affected by 935 path bouncing. In addition, when SCTP migrates the data transfer to 936 another path, it starts with the minimal or the initial CWND. Hence, 937 there is little chance for packet reordering or duplicating. 939 Second, even if all communication paths between the end-nodes share 940 the same bottleneck, the SCTP-PF results in a behavior already 941 allowed by [RFC4960]. 943 Appendix C. SCTP-PF for SCTP Single-homed Operation 945 For a single-homed SCTP association the only tangible effect of the 946 activation of SCTP-PF operation is enhanced failure detection in 947 terms of potential notification of the PF state of the sole 948 destination address as well as, for idle associations, more rapid 949 entering, and notification, of inactive state of the destination 950 address and more rapid end-point failure detection. It is believed 951 that neither of these effects are harmful, provided adequate dormant 952 state operation is implemented, and furthermore that they may be 953 particularly useful for applications that deploys multiple SCTP 954 associations for load balancing purposes. The early notification of 955 the PF state may be used for preventive measures as the entering of 956 the PF state can be used as a warning of potential congestion. 957 Depending on the PMR value, the aggressive HEARTBEAT transmission in 958 PF state may speed up the end-point failure detection (exceed of AMR 959 threshold on the sole path error counter) on idle associations in 960 case where relatively large HB.interval value compared to RTO (e.g. 961 30secs) is used. 963 Authors' Addresses 965 Yoshifumi Nishida 966 GE Global Research 967 2623 Camino Ramon 968 San Ramon, CA 94583 969 USA 971 Email: nishida@wide.ad.jp 973 Preethi Natarajan 974 Cisco Systems 975 510 McCarthy Blvd 976 Milpitas, CA 95035 977 USA 979 Email: prenatar@cisco.com 981 Armando Caro 982 BBN Technologies 983 10 Moulton St. 984 Cambridge, MA 02138 985 USA 987 Email: acaro@bbn.com 989 Paul D. Amer 990 University of Delaware 991 Computer Science Department - 434 Smith Hall 992 Newark, DE 19716-2586 993 USA 995 Email: amer@udel.edu 996 Karen E. E. Nielsen 997 Ericsson 998 Kistavaegen 25 999 Stockholm 164 80 1000 Sweden 1002 Email: karen.nielsen@tieto.com