idnits 2.17.1 draft-dreibholz-rserpool-enrp-takeover-09.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 (January 2, 2013) is 4132 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-11 == Outdated reference: A later version (-33) exists of draft-dreibholz-rserpool-delay-10 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: July 6, 2013 Hainan University 6 January 2, 2013 8 Takeover Suggestion Flag for the ENRP Handle Update Message 9 draft-dreibholz-rserpool-enrp-takeover-09.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 July 6, 2013. 33 Copyright Notice 35 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Takeover Suggestion Flag . . . . . . . . . . . . . . . . . . . 3 55 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . . 4 56 3. Reference Implementation . . . . . . . . . . . . . . . . . . . 4 57 4. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . . 4 58 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 59 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 60 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 62 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 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 110 2.1. Definition 112 In this subsection, only the differences to the ENRP_HANDLE_UPDATE 113 message defined in [RFC5353] are explained. The following figure 114 shows the ENRP_HANDLE_UPDATE message: 116 0 1 2 3 117 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 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | Type = 0x04 |0|0|0|0|0|0|0|T| Message Length | 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | Sending Server's ID | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Receiving Server's ID | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | Update Action | (reserved) | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 : Pool Handle Parameter : 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 : Pool Element Parameter : 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 T flag: 1 bit (boolean) 134 If set, the receiving ENRP server is suggested to take over the PE 135 specified by the Pool Handle and Pool Element Parameters. It is 136 RECOMMENDED for the receiving ENRP server to perform this takeover if 137 it has the resources to do so. 139 3. Reference Implementation 141 The RSerPool reference implementation RSPLIB can be found at 142 [RSerPoolPage]. It supports the functionalities defined by 143 [RFC5351], [RFC5352], [RFC5353], [RFC5354] and [RFC5356] as well as 144 the options [I-D.dreibholz-rserpool-asap-hropt], 145 [I-D.dreibholz-rserpool-delay] and of course the option defined by 146 this document. An introduction to this implementation is provided in 147 [Dre2006]. 149 4. Testbed Platform 151 A large-scale and realistic Internet testbed platform with support 152 for the multi-homing feature of the underlying SCTP protocol is 153 NorNet. A description of NorNet is provided in [PAMS2013-NorNet], 154 some further information can be found on the project website 155 [NorNet-Website]. 157 5. Security Considerations 159 Security considerations for RSerPool systems are described by 160 [RFC5355]. 162 6. IANA Considerations 164 This document does not require additional IANA actions beyond those 165 already identified in the ENRP and ASAP protocol specifications. 167 7. References 169 7.1. Normative References 171 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 172 Requirement Levels", BCP 14, RFC 2119, March 1997. 174 [RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An 175 Overview of Reliable Server Pooling Protocols", RFC 5351, 176 September 2008. 178 [RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 179 "Aggregate Server Access Protocol (ASAP)", RFC 5352, 180 September 2008. 182 [RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. 183 Silverton, "Endpoint Handlespace Redundancy Protocol 184 (ENRP)", RFC 5353, September 2008. 186 [RFC5354] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 187 "Aggregate Server Access Protocol (ASAP) and Endpoint 188 Handlespace Redundancy Protocol (ENRP) Parameters", 189 RFC 5354, September 2008. 191 [RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M. 192 Holdrege, "Threats Introduced by Reliable Server Pooling 193 (RSerPool) and Requirements for Security in Response to 194 Threats", RFC 5355, September 2008. 196 [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 197 Policies", RFC 5356, September 2008. 199 [I-D.dreibholz-rserpool-asap-hropt] 200 Dreibholz, T., "Handle Resolution Option for ASAP", 201 draft-dreibholz-rserpool-asap-hropt-11 (work in progress), 202 July 2012. 204 [I-D.dreibholz-rserpool-delay] 205 Dreibholz, T. and X. Zhou, "Definition of a Delay 206 Measurement Infrastructure and Delay-Sensitive Least-Used 207 Policy for Reliable Server Pooling", 208 draft-dreibholz-rserpool-delay-10 (work in progress), 209 July 2012. 211 7.2. Informative References 213 [AINA2009] 214 Zhou, X., Dreibholz, T., Fa, F., Du, W., and E. Rathgeb, 215 "Evaluation and Optimization of the Registrar Redundancy 216 Handling in Reliable Server Pooling Systems", Proceedings 217 of the IEEE 23rd International Conference on Advanced 218 Information Networking and Applications (AINA), Pages 256- 219 262, ISBN 978-0-7695-3638-5, DOI 10.1109/AINA.2009.25, 220 May 2009. 222 [Dre2006] Dreibholz, T., "Reliable Server Pooling - Evaluation, 223 Optimization and Extension of a Novel IETF Architecture", 224 March 2007. 226 [IJHIT2008] 227 Dreibholz, T. and E. Rathgeb, "An Evaluation of the Pool 228 Maintenance Overhead in Reliable Server Pooling Systems", 229 SERSC International Journal on Hybrid Information 230 Technology (IJHIT), Volume 1, Number 2, Pages 17-32, 231 ISSN 1738-9968, April 2008. 233 [RSerPoolPage] 234 Dreibholz, T., "Thomas Dreibholz's RSerPool Page", 2012. 236 [NorNet-Website] 237 Xiang, J., "NorNet -- A Programmable Testbed for 238 Measurements and Experimental Networking Research", 2013. 240 [PAMS2013-NorNet] 241 Dreibholz, T. and E. Gran, "Design and Implementation of 242 the NorNet Core Research Testbed for Multi-Homed Systems", 243 Proceedings of the 3nd International Workshop on Protocols 244 and Applications with Multi-Homing Support (PAMS) , 245 March 2013. 247 Authors' Addresses 249 Thomas Dreibholz 250 Simula Research Laboratory, Network Systems Group 251 Martin Linges vei 17 252 1364 Fornebu, Akershus 253 Norway 255 Phone: +47-6782-8200 256 Fax: +47-6782-8201 257 Email: dreibh@simula.no 258 URI: http://www.iem.uni-due.de/~dreibh/ 260 Xing Zhou 261 Hainan University, College of Information Science and Technology 262 Renmin Avenue 58 263 570228 Haikou, Hainan 264 China 266 Phone: +86-898-66279141 267 Email: zhouxing@hainu.edu.cn