idnits 2.17.1 draft-dreibholz-rserpool-asap-hropt-25.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 seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 10, 2019) is 1682 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-33) exists of draft-dreibholz-rserpool-delay-23 == Outdated reference: A later version (-31) exists of draft-dreibholz-rserpool-enrp-takeover-21 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). 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 September 10, 2019 5 Expires: March 13, 2020 7 Handle Resolution Option for ASAP 8 draft-dreibholz-rserpool-asap-hropt-25 10 Abstract 12 This document describes the Handle Resolution option for the ASAP 13 protocol. 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 https://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 March 13, 2020. 32 Copyright Notice 34 Copyright (c) 2019 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 (https://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 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2 51 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 52 1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Handle Resolution Option . . . . . . . . . . . . . . . . . . 3 54 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Reference Implementation . . . . . . . . . . . . . . . . . . 3 56 4. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 4 57 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 58 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 60 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 62 8.2. Informative References . . . . . . . . . . . . . . . . . 5 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 65 1. Introduction 67 Reliable Server Pooling defines protocols for providing highly 68 available services. The Aggregate Server Access Protocol (ASAP) 69 provides session management and server selection for applications. 70 Upon request for a server selection -- denoted as handle resolution 71 -- an ENRP server returns a list of selected PE identities. The 72 number of PE identities to be returned is not specified by RSerPool. 73 Furthermore the ASAP protocol does not contain a way for letting the 74 requesting instance specify it. 76 As shown in [Dre2006], [IJAIT2009], [IJHIT2008], selecting too many 77 entries does not make sense for the application, but on the other 78 hand also result in significant processing and network overhead. 79 Furthermore, it has been shown in [LCN2005] that the number of 80 requested elements is usually 1, but there are application cases 81 where more PE identities have to be returned. That is, there should 82 be a possibility to specify the number of requested PE items upon a 83 handle resolution. 85 1.1. Scope 87 The Handle Resolution option defined in this draft simply defines an 88 option to let the PU-side specify the desired number of PE identities 89 from the ENRP server. 91 1.2. Terminology 93 The terms are commonly identified in related work and can be found in 94 the Aggregate Server Access Protocol and Endpoint Handlespace 95 Redundancy Protocol Common Parameters document RFC 5354 [RFC5354]. 97 1.3. Conventions 99 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 100 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 101 document are to be interpreted as described in [RFC2119]. 103 2. Handle Resolution Option 105 2.1. Definition 107 The Handle Resolution MAY be used once in an ASAP Handle Resolution 108 message sent from a PU to an ENRP server. It is defined as follows. 110 0 1 2 3 111 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 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | Type = 0x803f | Length=8 | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | Items | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 Items: 32 bits (unsigned integer) 120 Contains the number of PE identities to be selected by the ENRP 121 server. Setting it to 0xffffffff denotes to obtain as many PE 122 identities as possible. A setting of 0 denotes to use the ENRP 123 server's default value; this default MUST be used if there is no 124 Handle Resolution option given. The ENRP server SHOULD try to fulfil 125 the request for the given number of items. 127 Note, that the high-order bits of the type field are set to 10, which 128 means "skip this parameter and continue processing" if this parameter 129 type is not supported by the ENRP server. This allows for 130 interoperability with old implementations. 132 3. Reference Implementation 134 The RSerPool reference implementation RSPLIB can be found at 135 [RSerPool-Website]. It supports the functionalities defined by 136 [RFC5351], [RFC5352], [RFC5353], [RFC5354] and [RFC5356] as well as 137 the options [I-D.dreibholz-rserpool-delay], 138 [I-D.dreibholz-rserpool-enrp-takeover] and of course the option 139 defined by this document. An introduction to this implementation is 140 provided in [Dre2006]. 142 4. Testbed Platform 144 A large-scale and realistic Internet testbed platform with support 145 for the multi-homing feature of the underlying SCTP protocol is 146 NorNet. A description of NorNet is provided in [PAMS2013-NorNet], 147 some further information can be found on the project website 148 [NorNet-Website]. 150 5. Security Considerations 152 Security considerations for RSerPool systems are described by 153 [RFC5355]. 155 6. IANA Considerations 157 This document does not require additional IANA actions beyond those 158 already identified in the ENRP and ASAP protocol specifications. 160 7. Acknowledgments 162 The author would like to thank Nihad Cosic, Dirk Hoffstadt, Michael 163 Kohnen, Jobin Pulinthanath and Xing Zhou for their support. 165 8. References 167 8.1. Normative References 169 [I-D.dreibholz-rserpool-delay] 170 Dreibholz, T. and X. Zhou, "Definition of a Delay 171 Measurement Infrastructure and Delay-Sensitive Least-Used 172 Policy for Reliable Server Pooling", draft-dreibholz- 173 rserpool-delay-23 (work in progress), March 2019. 175 [I-D.dreibholz-rserpool-enrp-takeover] 176 Dreibholz, T. and X. Zhou, "Takeover Suggestion Flag for 177 the ENRP Handle Update Message", draft-dreibholz-rserpool- 178 enrp-takeover-21 (work in progress), March 2019. 180 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 181 Requirement Levels", BCP 14, RFC 2119, 182 DOI 10.17487/RFC2119, March 1997, 183 . 185 [RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An 186 Overview of Reliable Server Pooling Protocols", RFC 5351, 187 DOI 10.17487/RFC5351, September 2008, 188 . 190 [RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 191 "Aggregate Server Access Protocol (ASAP)", RFC 5352, 192 DOI 10.17487/RFC5352, September 2008, 193 . 195 [RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. 196 Silverton, "Endpoint Handlespace Redundancy Protocol 197 (ENRP)", RFC 5353, DOI 10.17487/RFC5353, September 2008, 198 . 200 [RFC5354] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 201 "Aggregate Server Access Protocol (ASAP) and Endpoint 202 Handlespace Redundancy Protocol (ENRP) Parameters", 203 RFC 5354, DOI 10.17487/RFC5354, September 2008, 204 . 206 [RFC5355] Stillman, M., Ed., Gopal, R., Guttman, E., Sengodan, S., 207 and M. Holdrege, "Threats Introduced by Reliable Server 208 Pooling (RSerPool) and Requirements for Security in 209 Response to Threats", RFC 5355, DOI 10.17487/RFC5355, 210 September 2008, . 212 [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 213 Policies", RFC 5356, DOI 10.17487/RFC5356, September 2008, 214 . 216 8.2. Informative References 218 [Dre2006] Dreibholz, T., "Reliable Server Pooling - Evaluation, 219 Optimization and Extension of a Novel IETF Architecture", 220 March 2007, . 224 [IJAIT2009] 225 Dreibholz, T. and E. Rathgeb, "Overview and Evaluation of 226 the Server Redundancy and Session Failover Mechanisms in 227 the Reliable Server Pooling Framework", International 228 Journal on Advances in Internet Technology (IJAIT) Number 229 1, Volume 2, Pages 1-14, ISSN 1942-2652, June 2009, 230 . 233 [IJHIT2008] 234 Dreibholz, T. and E. Rathgeb, "An Evaluation of the Pool 235 Maintenance Overhead in Reliable Server Pooling Systems", 236 SERSC International Journal on Hybrid Information 237 Technology (IJHIT) Number 2, Volume 1, Pages 17-32, 238 ISSN 1738-9968, April 2008, . 242 [LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of 243 Reliable Server Pooling Systems", Proceedings of the IEEE 244 Conference on Local Computer Networks (LCN) 30th 245 Anniversary Pages 200-208, ISBN 0-7695-2421-4, 246 DOI 10.1109/LCN.2005.98, November 2005, 247 . 250 [NorNet-Website] 251 Dreibholz, T., "NorNet - A Real-World, Large-Scale Multi- 252 Homing Testbed", Online: https://www.nntb.no/, 2019, 253 . 255 [PAMS2013-NorNet] 256 Dreibholz, T. and E. Gran, "Design and Implementation of 257 the NorNet Core Research Testbed for Multi-Homed Systems", 258 Proceedings of the 3nd International Workshop on Protocols 259 and Applications with Multi-Homing Support (PAMS) Pages 260 1094-1100, ISBN 978-0-7695-4952-1, 261 DOI 10.1109/WAINA.2013.71, March 2013, 262 . 266 [RSerPool-Website] 267 Dreibholz, T., "Thomas Dreibholz's RSerPool Page", 268 Online: https://www.uni-due.de/~be0001/rserpool/, 2019, 269 . 271 Author's Address 272 Thomas Dreibholz 273 Simula Metropolitan Centre for Digital Engineering 274 Pilestredet 52 275 0167 Oslo, Oslo 276 Norway 278 Phone: +47-6782-8200 279 Fax: +47-6782-8201 280 Email: dreibh@simula.no 281 URI: https://www.simula.no/people/dreibh