idnits 2.17.1 draft-dreibholz-rserpool-nextgen-ideas-00.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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 19, 2013) is 3841 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 4960 (ref. '10') (Obsoleted by RFC 9260) ** Obsolete normative reference: RFC 6824 (ref. '11') (Obsoleted by RFC 8684) == Outdated reference: A later version (-34) exists of draft-dreibholz-rserpool-asap-hropt-13 == Outdated reference: A later version (-33) exists of draft-dreibholz-rserpool-delay-12 == Outdated reference: A later version (-31) exists of draft-dreibholz-rserpool-enrp-takeover-10 == Outdated reference: A later version (-06) exists of draft-zong-vnfpool-problem-statement-01 Summary: 2 errors (**), 0 flaws (~~), 7 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: Informational October 19, 2013 5 Expires: April 22, 2014 7 Ideas for a Next Generation of the Reliable Server Pooling Framework 8 draft-dreibholz-rserpool-nextgen-ideas-00.txt 10 Abstract 12 This document collects some idea for a next generation of the 13 Reliable Server Pooling framework. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on April 22, 2014. 32 Copyright Notice 34 Copyright (c) 2013 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 This document may contain material from IETF Documents or IETF 48 Contributions published or made publicly available before November 49 10, 2008. The person(s) controlling the copyright in some of this 50 material may not have granted the IETF Trust the right to allow 51 modifications of such material outside the IETF Standards Process. 52 Without obtaining an adequate license from the person(s) controlling 53 the copyright in such materials, this document may not be modified 54 outside the IETF Standards Process, and derivative works of it may 55 not be created outside the IETF Standards Process, except to format 56 it for publication as an RFC or to translate it into languages other 57 than English. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 1.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 2 63 1.2. Reliable Server Pooling . . . . . . . . . . . . . . . . . 3 64 1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. What to Change in the Next Generation of RSerPool? . . . . . 3 66 2.1. Security Considerations . . . . . . . . . . . . . . . . . 4 67 2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 4 68 3. Reference Implementation . . . . . . . . . . . . . . . . . . 4 69 4. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 4 70 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 71 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 72 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 73 6.2. Informative References . . . . . . . . . . . . . . . . . 6 74 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 76 1. Introduction 78 1.1. Abbreviations 80 o ASAP: Aggregate Server Access Protocol 82 o ENRP: Endpoint Handlespace Redundancy Protocol 84 o ID: Identifier 86 o MPTCP: Multi-Path Transmission Control Protocol 88 o PE: Pool Element 90 o PR: Pool Registrar 92 o PU: Pool User 94 o RSerPool: Reliable Server Pooling 96 o SCTP: Stream Control Transmission Protocol 97 o TCP: Transmission Control Protocol 99 o VNFPOOL: Virtual Network Function Resource Pooling 101 1.2. Reliable Server Pooling 103 Reliable Server Pooling (RSerPool) has been defined as RFCs in [1], 104 [2], [3], [4], [5], [6], [7], [8]. There is also a detailed 105 introduction provided by [16] as well as lots of further information 106 material on [17]. RSerPool is therefore not introduced in more 107 detail here. 109 1.3. Scope 111 The scope of this document is to collect some ideas of what to update 112 /change for a next generation of the RSerPool framework. It is a 113 result of lessons learned with more than one decade of RSerPool 114 deployment (see also [18], [19], [20]) as well as ongoing discussions 115 on applying RSerPool for Virtual Network Function Resource 116 Pooling (VNFPOOL; as introduced in more detail in [15]). 118 2. What to Change in the Next Generation of RSerPool? 120 o ENRP servers denote the management systems in the context of 121 RSerPool. The term "server" is misleading, since ENRP servers are 122 actually ENRP peers. Literature on RSerPool -- for example [16] 123 -- therefore uses the more accurate term "Pool Registrar" (PR). A 124 future revision of RSerPool should also use this term. (The 125 RSerPool documents did not use "registrar" to avoid confusion with 126 SIP registrars.) 128 o Pool Element Identifiers (PE ID) and Pool Registrar 129 Identifiers (PR ID) are 32-bit random numbers used for the 130 identification of PEs and PRs. Since 64-bit CPUs are standard 131 since quite a long time, these IDs should be extended to 64 bits. 133 o ENRP uses the Internet-16 checksum defined in [9] to detect 134 handlespace inconsistencies. It is trivially possible to extend 135 the underlying algorithm to 32 bits, and the computation is more 136 efficient on today's CPUs. The checksum algorithm should 137 therefore be changed. (The Internet-16 checksum was finally 138 chosen in 2005 after long decisions to avoid any possible patent 139 issues. The trivial extension of Internet-16 to Internet-32 is 140 probably not an issue any more?) 142 o PR failures lead to possible concentration of all PUs and PEs at a 143 single PR. To achieve a better load balancing, the solution ENRP 144 Takeover Suggestion -- as defined in [14] -- should be included in 145 ENRP. 147 o For a Handle Resolution, a PR has to decide on how many PEs to 148 select. Selecting too many ones causes additional overhead (which 149 might be unnecessary), selecting too few ones may cause problems 150 for the applications. The extension Handle Resolution Option -- 151 defined in [12] -- provides a possibility for the PU to specify 152 the amount of PEs to be selected. This possibility should be 153 integrated into ASAP. 155 o RSerPool defines SCTP (defined in [10]) as transport protocol for 156 RSerPool. TCP and particularly Multi-Path TCP (MPTCP; see [11]) 157 should be possible further transport protocols for all RSerPool 158 traffic. SCTP should still be the recommended choice, but 159 allowing TCP/MPTCP could make the deployment much easier. (SCTP 160 is superior, but it lacks of support in operating systems and 161 support by underlying network infrastructure, like firewalls and 162 middleboxes.) 164 2.1. Security Considerations 166 Security considerations for RSerPool can be found in [6]. 168 2.2. IANA Considerations 170 This document introduces no additional considerations for IANA. 172 3. Reference Implementation 174 The RSerPool reference implementation RSPLIB, including example 175 applications, can be found at [17]. It supports the functionalities 176 defined by [2], [3], [4], [5] and [6] as well as the options [12], 177 [14] and [13]. An introduction to this implementation is provided in 178 [16]. 180 4. Testbed Platform 182 NorNet is a large-scale and realistic Internet testbed platform with 183 support for Reliable Server Pooling as well as the underlying 184 transport protocols SCTP and MPTCP. A description of and 185 introduction to NorNet is provided in [20], [21], [22]. Further 186 information can be found on the project website [23] at http:// 187 www.nntb.no. 189 5. Acknowledgments 191 The author would like to thank Randall R. Stewart, Michael Tuexen, 192 Ning Zong for their discussions and support. 194 6. References 196 6.1. Normative References 198 [1] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L., 199 Loughney, J., and M. Stillman, "Requirements for Reliable 200 Server Pooling", RFC 3237, January 2002. 202 [2] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An 203 Overview of Reliable Server Pooling Protocols", RFC 5351, 204 September 2008. 206 [3] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 207 "Aggregate Server Access Protocol (ASAP)", RFC 5352, 208 September 2008. 210 [4] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. 211 Silverton, "Endpoint Handlespace Redundancy Protocol 212 (ENRP)", RFC 5353, September 2008. 214 [5] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 215 "Aggregate Server Access Protocol (ASAP) and Endpoint 216 Handlespace Redundancy Protocol (ENRP) Parameters", RFC 217 5354, September 2008. 219 [6] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M. 220 Holdrege, "Threats Introduced by Reliable Server Pooling 221 (RSerPool) and Requirements for Security in Response to 222 Threats", RFC 5355, September 2008. 224 [7] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 225 Policies", RFC 5356, September 2008. 227 [8] Dreibholz, T. and J. Mulik, "Reliable Server Pooling MIB 228 Module Definition", RFC 5525, April 2009. 230 [9] Braden, R., Borman, D., Partridge, C., and W. Plummer, 231 "Computing the Internet checksum", RFC 1071, September 232 1988. 234 [10] Stewart, R., "Stream Control Transmission Protocol", RFC 235 4960, September 2007. 237 [11] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure, 238 "TCP Extensions for Multipath Operation with Multiple 239 Addresses", RFC 6824, January 2013. 241 [12] Dreibholz, T., "Handle Resolution Option for ASAP", draft- 242 dreibholz-rserpool-asap-hropt-13 (work in progress), July 243 2013. 245 [13] Dreibholz, T. and X. Zhou, "Definition of a Delay 246 Measurement Infrastructure and Delay-Sensitive Least-Used 247 Policy for Reliable Server Pooling", draft-dreibholz- 248 rserpool-delay-12 (work in progress), July 2013. 250 [14] Dreibholz, T. and X. Zhou, "Takeover Suggestion Flag for 251 the ENRP Handle Update Message", draft-dreibholz-rserpool- 252 enrp-takeover-10 (work in progress), July 2013. 254 [15] Zong, N., Dunbar, L., and M. Shore, "Problem Statement for 255 Reliable Virtualized Network Function (VNF)", draft-zong- 256 vnfpool-problem-statement-01 (work in progress), September 257 2013. 259 6.2. Informative References 261 [16] Dreibholz, T., "Reliable Server Pooling - Evaluation, 262 Optimization and Extension of a Novel IETF Architecture", 263 March 2007. 265 [17] Dreibholz, T., "Thomas Dreibholz's RSerPool Page", Online: 266 http://www.iem.uni-due.de/~dreibh/rserpool/, 2013. 268 [18] Dreibholz, T. and E. Rathgeb, "A Powerful Tool-Chain for 269 Setup, Distributed Processing, Analysis and Debugging of 270 OMNeT++ Simulations", Proceedings of the 1st ACM/ICST 271 International Workshop on OMNeT++, ISBN 978-963-9799-20-2, 272 DOI 10.4108/ICST.SIMUTOOLS2008.2990, March 2008. 274 [19] Dreibholz, T., "Evaluation and Optimisation of Multi-Path 275 Transport using the Stream Control Transmission Protocol", 276 March 2012. 278 [20] Dreibholz, T. and E. Gran, "Design and Implementation of 279 the NorNet Core Research Testbed for Multi-Homed Systems", 280 Proceedings of the 3nd International Workshop on Protocols 281 and Applications with Multi-Homing Support (PAMS), Pages 282 1094-1100, ISBN 978-0-7695-4952-1, DOI 10.1109/ 283 WAINA.2013.71, March 2013. 285 [21] Dreibholz, T., "The NorNet Core Testbed - Introduction and 286 Status", Proceedings of the 1st International NorNet Users 287 Workshop (NNUW-1) , September 2013. 289 [22] Dreibholz, T., "The NorNet Core Testbed - An Experiment 290 Tutorial", Proceedings of the 1st International NorNet 291 Users Workshop (NNUW-1) , September 2013. 293 [23] Xiang, J., "NorNet -- A Real-World, Large-Scale Multi- 294 Homing Testbed", 2013. 296 http://www.nntb.no/ 298 Author's Address 300 Thomas Dreibholz 301 Simula Research Laboratory, Network Systems Group 302 Martin Linges vei 17 303 1364 Fornebu, Akershus 304 Norway 306 Phone: +47-6782-8200 307 Fax: +47-6782-8201 308 Email: dreibh@simula.no 309 URI: http://www.iem.uni-due.de/~dreibh/