idnits 2.17.1 draft-dreibholz-rserpool-enrp-takeover-27.txt: -(260): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding 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: ---------------------------------------------------------------------------- == There are 2 instances of lines with non-ascii characters in the document. 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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (21 March 2022) is 738 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-33) exists of draft-dreibholz-rserpool-asap-hropt-29 == Outdated reference: A later version (-32) exists of draft-dreibholz-rserpool-delay-28 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Dreibholz 3 Internet-Draft SimulaMet 4 Intended status: Experimental X. Zhou 5 Expires: 22 September 2022 Hainan University 6 21 March 2022 8 Takeover Suggestion Flag for the ENRP Handle Update Message 9 draft-dreibholz-rserpool-enrp-takeover-27 11 Abstract 13 This document describes the Takeover Suggestion Flag for the 14 ENRP_HANDLE_UPDATE message of the ENRP protocol. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on 22 September 2022. 33 Copyright Notice 35 Copyright (c) 2022 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 40 license-info) in effect on the date of publication of this document. 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. Code Components 43 extracted from this document must include Revised BSD License text as 44 described in Section 4.e of the Trust Legal Provisions and are 45 provided without warranty as described in the Revised BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 52 1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Takeover Suggestion Flag . . . . . . . . . . . . . . . . . . 3 54 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Reference Implementation . . . . . . . . . . . . . . . . . . 4 56 4. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 4 57 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 58 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 61 7.2. Informative References . . . . . . . . . . . . . . . . . 5 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 64 1. Introduction 66 Reliable Server Pooling as described in [3] defines protocols for 67 providing highly available services. The management component used 68 for pool administration is denoted as ENRP Server or Pool Registrar 69 (PR). Since a single ENRP server constitutes a single point of 70 failure, there must be multiple ENRP servers. Servers, denoted as 71 Pool Elements (PE), use an arbitrary ENRP server for registration 72 into the pool. The chosen ENRP server becomes the Home ENRP Server, 73 also denoted as Home PR (PR-H), of the PE. It is responsible for 74 making the PE identity known to the other ENRP servers (by using 75 ENRP_HANDLE_UPDATE messages) and also to monitor the PE health (by 76 using keep-alive messages). 78 As shown in [11], the following scenario leads to unbalanced ENRP 79 server workload: consider a set of multiple ENRP servers with one 80 subset being unreliable (for example, their network connection has 81 problems) and some reliable ENRP servers. After a while, the 82 reliable ENRP server will get the home ENRP server role for almost 83 all of the PEs, which results in high workload for this ENRP server. 84 Since the home ENRP server role is more computation-intensive (as 85 shown by [13]), this leads to highly unbalanced workload for large 86 RSerPool setups. This unbalanced workload remains, even when the 87 unreliable ENRP servers become reliable again (for example, when the 88 network problems have been solved). 90 1.1. Scope 92 The Takeover Suggestion Flag defined in this draft defines a flag for 93 the ENRP_HANDLE_UPDATE message. If the flag is set, the receiving 94 ENRP server is suggested to take over the PE specified in the 95 ENRP_HANDLE_UPDATE message. 97 1.2. Terminology 99 The terms are commonly identified in related work and can be found in 100 the RSerPool Overview document RFC 5351 [3]. 102 1.3. Conventions 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 106 "OPTIONAL" in this document are to be interpreted as described in BCP 107 14 [1] [2] when, and only when, they appear in all capitals, as shown 108 here. 110 2. Takeover Suggestion Flag 112 2.1. Definition 114 In this subsection, only the differences to the ENRP_HANDLE_UPDATE 115 message defined in [5] are explained. The following figure shows the 116 ENRP_HANDLE_UPDATE message: 118 0 1 2 3 119 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 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | Type = 0x04 |0|0|0|0|0|0|0|T| Message Length | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Sending Server's ID | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | Receiving Server's ID | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 | Update Action | (reserved) | 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 : Pool Handle Parameter : 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 : Pool Element Parameter : 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 T flag: 1 bit (boolean) 135 If set, the receiving ENRP server is suggested to take over the PE 136 specified by the Pool Handle and Pool Element Parameters. It is 137 RECOMMENDED for the receiving ENRP server to perform this takeover if 138 it has the resources to do so. 140 3. Reference Implementation 142 The RSerPool reference implementation RSPLIB can be found at [15]. 143 It supports the functionalities defined by [3], [4], [5], [6] and [8] 144 as well as the options [9], [10] and of course the option defined by 145 this document. An introduction to this implementation is provided in 146 [12]. 148 4. Testbed Platform 150 A large-scale and realistic Internet testbed platform with support 151 for the multi-homing feature of the underlying SCTP protocol is 152 NorNet. A description of NorNet is provided in [14], some further 153 information can be found on the project website [16]. 155 5. Security Considerations 157 Security considerations for RSerPool systems are described by [7]. 159 6. IANA Considerations 161 This document does not require additional IANA actions beyond those 162 already identified in the ENRP and ASAP protocol specifications. 164 7. References 166 7.1. Normative References 168 [1] Bradner, S., "Key words for use in RFCs to Indicate 169 Requirement Levels", BCP 14, RFC 2119, 170 DOI 10.17487/RFC2119, March 1997, 171 . 173 [2] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 174 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 175 May 2017, . 177 [3] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An 178 Overview of Reliable Server Pooling Protocols", RFC 5351, 179 DOI 10.17487/RFC5351, September 2008, 180 . 182 [4] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 183 "Aggregate Server Access Protocol (ASAP)", RFC 5352, 184 DOI 10.17487/RFC5352, September 2008, 185 . 187 [5] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. 188 Silverton, "Endpoint Handlespace Redundancy Protocol 189 (ENRP)", RFC 5353, DOI 10.17487/RFC5353, September 2008, 190 . 192 [6] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 193 "Aggregate Server Access Protocol (ASAP) and Endpoint 194 Handlespace Redundancy Protocol (ENRP) Parameters", 195 RFC 5354, DOI 10.17487/RFC5354, September 2008, 196 . 198 [7] Stillman, M., Ed., Gopal, R., Guttman, E., Sengodan, S., 199 and M. Holdrege, "Threats Introduced by Reliable Server 200 Pooling (RSerPool) and Requirements for Security in 201 Response to Threats", RFC 5355, DOI 10.17487/RFC5355, 202 September 2008, . 204 [8] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 205 Policies", RFC 5356, DOI 10.17487/RFC5356, September 2008, 206 . 208 [9] Dreibholz, T., "Handle Resolution Option for ASAP", Work 209 in Progress, Internet-Draft, draft-dreibholz-rserpool- 210 asap-hropt-29, 6 September 2021, 211 . 214 [10] Dreibholz, T. and X. Zhou, "Definition of a Delay 215 Measurement Infrastructure and Delay-Sensitive Least-Used 216 Policy for Reliable Server Pooling", Work in Progress, 217 Internet-Draft, draft-dreibholz-rserpool-delay-28, 6 218 September 2021, . 221 7.2. Informative References 223 [11] Zhou, X., Dreibholz, T., Fa, F., Du, W., and E. P. 224 Rathgeb, "Evaluation and Optimization of the Registrar 225 Redundancy Handling in Reliable Server Pooling Systems", 226 Proceedings of the IEEE 23rd International Conference on 227 Advanced Information Networking and 228 Applications (AINA) Pages 256-262, ISBN 978-0-7695-3638-5, 229 DOI 10.1109/AINA.2009.25, 26 May 2009, 230 . 233 [12] Dreibholz, T., "Reliable Server Pooling – Evaluation, 234 Optimization and Extension of a Novel IETF Architecture", 235 7 March 2007, . 239 [13] Dreibholz, T. and E. P. Rathgeb, "An Evaluation of the 240 Pool Maintenance Overhead in Reliable Server Pooling 241 Systems", SERSC International Journal on Hybrid 242 Information Technology (IJHIT) Number 2, Volume 1, Pages 243 17-32, ISSN 1738-9968, April 2008, . 247 [14] Dreibholz, T. and E. G. Gran, "Design and Implementation 248 of the NorNet Core Research Testbed for Multi-Homed 249 Systems", Proceedings of the 3nd International Workshop on 250 Protocols and Applications with Multi-Homing 251 Support (PAMS) Pages 1094-1100, ISBN 978-0-7695-4952-1, 252 DOI 10.1109/WAINA.2013.71, 27 March 2013, 253 . 257 [15] Dreibholz, T., "Thomas Dreibholz's RSerPool Page", 2022, 258 . 260 [16] Dreibholz, T., "NorNet – A Real-World, Large-Scale Multi- 261 Homing Testbed", 2022, . 263 Authors' Addresses 265 Thomas Dreibholz 266 Simula Metropolitan Centre for Digital Engineering 267 Pilestredet 52 268 0167 Oslo 269 Norway 270 Email: dreibh@simula.no 271 URI: https://www.simula.no/people/dreibh 273 Xing Zhou 274 Hainan University, College of Information Science and Technology 275 Renmin Avenue 58 276 570228 Haikou 277 Hainan, 278 China 279 Phone: +86-898-66279141 280 Email: zhouxing@hainu.edu.cn