idnits 2.17.1 draft-dreibholz-rserpool-enrp-takeover-16.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 (July 18, 2016) is 2836 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-34) exists of draft-dreibholz-rserpool-asap-hropt-18 == Outdated reference: A later version (-33) exists of draft-dreibholz-rserpool-delay-17 Summary: 0 errors (**), 0 flaws (~~), 3 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 Simula Research Laboratory 4 Intended status: Experimental X. Zhou 5 Expires: January 19, 2017 Hainan University 6 July 18, 2016 8 Takeover Suggestion Flag for the ENRP Handle Update Message 9 draft-dreibholz-rserpool-enrp-takeover-16.txt 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 http://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 January 19, 2017. 33 Copyright Notice 35 Copyright (c) 2016 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 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Takeover Suggestion Flag . . . . . . . . . . . . . . . . . . 3 55 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. Reference Implementation . . . . . . . . . . . . . . . . . . 4 57 4. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 4 58 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 59 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 60 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 62 7.2. Informative References . . . . . . . . . . . . . . . . . 5 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 65 1. Introduction 67 Reliable Server Pooling as described in [RFC5351] defines protocols 68 for providing highly available services. The management component 69 used for pool administration is denoted as ENRP Server or Pool 70 Registrar (PR). Since a single ENRP server constitutes a single 71 point of failure, there must be multiple ENRP servers. Servers, 72 denoted as Pool Elements (PE), use an arbitrary ENRP server for 73 registration into the pool. The chosen ENRP server becomes the Home 74 ENRP Server, also denoted as Home PR (PR-H), of the PE. It is 75 responsible for making the PE identity known to the other ENRP 76 servers (by using ENRP_HANDLE_UPDATE messages) and also to monitor 77 the PE health (by using keep-alive messages). 79 As shown in [AINA2009], the following scenario leads to unbalanced 80 ENRP server workload: consider a set of multiple ENRP servers with 81 one subset being unreliable (for example, their network connection 82 has problems) and some reliable ENRP servers. After a while, the 83 reliable ENRP server will get the home ENRP server role for almost 84 all of the PEs, which results in high workload for this ENRP server. 85 Since the home ENRP server role is more computation-intensive (as 86 shown by [IJHIT2008]), this leads to highly unbalanced workload for 87 large RSerPool setups. This unbalanced workload remains, even when 88 the unreliable ENRP servers become reliable again (for example, when 89 the network problems have been solved). 91 1.1. Scope 93 The Takeover Suggestion Flag defined in this draft defines a flag for 94 the ENRP_HANDLE_UPDATE message. If the flag is set, the receiving 95 ENRP server is suggested to take over the PE specified in the 96 ENRP_HANDLE_UPDATE message. 98 1.2. Terminology 100 The terms are commonly identified in related work and can be found in 101 the RSerPool Overview document RFC 5351 [RFC5351]. 103 1.3. Conventions 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in [RFC2119]. 109 2. Takeover Suggestion Flag 111 2.1. Definition 113 In this subsection, only the differences to the ENRP_HANDLE_UPDATE 114 message defined in [RFC5353] are explained. The following figure 115 shows the ENRP_HANDLE_UPDATE message: 117 0 1 2 3 118 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 119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 120 | Type = 0x04 |0|0|0|0|0|0|0|T| Message Length | 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 | Sending Server's ID | 123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 124 | Receiving Server's ID | 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 | Update Action | (reserved) | 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 : Pool Handle Parameter : 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 : Pool Element Parameter : 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 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 143 [RSerPool-Website]. It supports the functionalities defined by 144 [RFC5351], [RFC5352], [RFC5353], [RFC5354] and [RFC5356] as well as 145 the options [I-D.dreibholz-rserpool-asap-hropt], 146 [I-D.dreibholz-rserpool-delay] and of course the option defined by 147 this document. An introduction to this implementation is provided in 148 [Dre2006]. 150 4. Testbed Platform 152 A large-scale and realistic Internet testbed platform with support 153 for the multi-homing feature of the underlying SCTP protocol is 154 NorNet. A description of NorNet is provided in [PAMS2013-NorNet], 155 some further information can be found on the project website 156 [NorNet-Website]. 158 5. Security Considerations 160 Security considerations for RSerPool systems are described by 161 [RFC5355]. 163 6. IANA Considerations 165 This document does not require additional IANA actions beyond those 166 already identified in the ENRP and ASAP protocol specifications. 168 7. References 170 7.1. Normative References 172 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 173 Requirement Levels", BCP 14, RFC 2119, 174 DOI 10.17487/RFC2119, March 1997, 175 . 177 [RFC5351] 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 [RFC5352] 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 [RFC5353] 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 [RFC5354] 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 [RFC5355] 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 [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 205 Policies", RFC 5356, DOI 10.17487/RFC5356, September 2008, 206 . 208 [I-D.dreibholz-rserpool-asap-hropt] 209 Dreibholz, T., "Handle Resolution Option for ASAP", draft- 210 dreibholz-rserpool-asap-hropt-18 (work in progress), 211 January 2016. 213 [I-D.dreibholz-rserpool-delay] 214 Dreibholz, T. and X. Zhou, "Definition of a Delay 215 Measurement Infrastructure and Delay-Sensitive Least-Used 216 Policy for Reliable Server Pooling", draft-dreibholz- 217 rserpool-delay-17 (work in progress), January 2016. 219 7.2. Informative References 221 [AINA2009] 222 Zhou, X., Dreibholz, T., Fa, F., Du, W., and E. Rathgeb, 223 "Evaluation and Optimization of the Registrar Redundancy 224 Handling in Reliable Server Pooling Systems", Proceedings 225 of the IEEE 23rd International Conference on Advanced 226 Information Networking and Applications (AINA) Pages 227 256-262, ISBN 978-0-7695-3638-5, DOI 10.1109/AINA.2009.25, 228 May 2009, . 232 [Dre2006] Dreibholz, T., "Reliable Server Pooling - Evaluation, 233 Optimization and Extension of a Novel IETF Architecture", 234 March 2007, . 238 [IJHIT2008] 239 Dreibholz, T. and E. Rathgeb, "An Evaluation of the Pool 240 Maintenance Overhead in Reliable Server Pooling Systems", 241 SERSC International Journal on Hybrid Information 242 Technology (IJHIT) Number 2, Volume 1, Pages 17-32, 243 ISSN 1738-9968, April 2008, . 247 [PAMS2013-NorNet] 248 Dreibholz, T. and E. Gran, "Design and Implementation of 249 the NorNet Core Research Testbed for Multi-Homed Systems", 250 Proceedings of the 3nd International Workshop on Protocols 251 and Applications with Multi-Homing Support (PAMS) Pages 252 1094-1100, ISBN 978-0-7695-4952-1, 253 DOI 10.1109/WAINA.2013.71, March 2013, 254 . 258 [RSerPool-Website] 259 Dreibholz, T., "Thomas Dreibholz's RSerPool Page", 260 Online: http://www.iem.uni-due.de/~dreibh/rserpool/, 2016, 261 . 263 [NorNet-Website] 264 Dreibholz, T., "NorNet -- A Real-World, Large-Scale Multi- 265 Homing Testbed", Online: https://www.nntb.no/, 2016, 266 . 268 Authors' Addresses 270 Thomas Dreibholz 271 Simula Research Laboratory, Network Systems Group 272 Martin Linges vei 17 273 1364 Fornebu, Akershus 274 Norway 276 Phone: +47-6782-8200 277 Fax: +47-6782-8201 278 Email: dreibh@simula.no 279 URI: http://www.iem.uni-due.de/~dreibh/ 280 Xing Zhou 281 Hainan University, College of Information Science and Technology 282 Renmin Avenue 58 283 570228 Haikou, Hainan 284 China 286 Phone: +86-898-66279141 287 Email: zhouxing@hainu.edu.cn 288 URI: http://www.hainu.edu.cn/stm/xinxi/2011330/10409758.shtml