idnits 2.17.1 draft-dreibholz-rserpool-asap-hropt-07.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 contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, 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 (July 2, 2010) is 5040 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-05 == Outdated reference: A later version (-31) exists of draft-dreibholz-rserpool-enrp-takeover-03 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 University of Duisburg-Essen 4 Intended status: Experimental July 2, 2010 5 Expires: January 3, 2011 7 Handle Resolution Option for ASAP 8 draft-dreibholz-rserpool-asap-hropt-07.txt 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 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 January 3, 2011. 32 Copyright Notice 34 Copyright (c) 2010 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 64 1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. Handle Resolution Option . . . . . . . . . . . . . . . . . . . 3 66 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . . 3 67 3. Reference Implementation . . . . . . . . . . . . . . . . . . . 4 68 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 70 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 71 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 72 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 73 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 74 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 76 1. Introduction 78 Reliable Server Pooling defines protocols for providing highly 79 available services. The Aggregate Server Access Protocol (ASAP) 80 provides session management and server selection for applications. 81 Upon request for a server selection -- denoted as handle resolution 82 -- an ENRP server returns a list of selected PE identities. The 83 number of PE identities to be returned is not specified by RSerPool. 84 Furthermore the ASAP protocol does not contain a way for letting the 85 requesting instance specify it. 87 As shown in [Dre2006], [IJAIT2009], [IJHIT2008], selecting too many 88 entries does not make sense for the application, but on the other 89 hand also result in significant processing and network overhead. 90 Furthermore, it has been shown in [LCN2005] that the number of 91 requested elements is usually 1, but there are application cases 92 where more PE identities have to be returned. That is, there should 93 be a possibility to specify the number of requested PE items upon a 94 handle resolution. 96 1.1. Scope 98 The Handle Resolution option defined in this draft simply defines an 99 option to let the PU-side specify the desired number of PE identities 100 from the ENRP server. 102 1.2. Terminology 104 The terms are commonly identified in related work and can be found in 105 the Aggregate Server Access Protocol and Endpoint Handlespace 106 Redundancy Protocol Common Parameters document RFC 5354 [RFC5354]. 108 1.3. Conventions 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 112 document are to be interpreted as described in [RFC2119]. 114 2. Handle Resolution Option 116 2.1. Definition 118 The Handle Resolution MAY be used once in an ASAP Handle Resolution 119 message sent from a PU to an ENRP server. It is defined as follows. 121 0 1 2 3 122 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 123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 124 | Type = 0x803f | Length=8 | 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 | Items | 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 Items: 32 bits (unsigned integer) 131 Contains the number of PE identities to be selected by the ENRP 132 server. Setting it to 0xffffffff denotes to obtain as many PE 133 identities as possible. A setting of 0 denotes to use the ENRP 134 server's default value; this default MUST be used if there is no 135 Handle Resolution option given. The ENRP server SHOULD try to fulfil 136 the request for the given number of items. 138 Note, that the high-order bits of the type field are set to 10, which 139 means "skip this parameter and continue processing" if this parameter 140 type is not supported by the ENRP server. This allows for 141 interoperability with old implementations. 143 3. Reference Implementation 145 The RSerPool reference implementation RSPLIB can be found at 146 [RSerPoolPage]. It supports the functionalities defined by 147 [RFC5351], [RFC5352], [RFC5353], [RFC5354] and [RFC5356] as well as 148 the options [I-D.dreibholz-rserpool-delay], 149 [I-D.dreibholz-rserpool-enrp-takeover] and of course the option 150 defined by this document. An introduction to this implementation is 151 provided in [Dre2006]. 153 4. Security Considerations 155 Security considerations for RSerPool systems are described by 156 [RFC5355]. 158 5. IANA Considerations 160 This document does not require additional IANA actions beyond those 161 already identified in the ENRP and ASAP protocol specifications. 163 6. Acknowledgments 165 The author would like to thank Nihad Cosic, Dirk Hoffstadt, Michael 166 Kohnen, Jobin Pulinthanath and Xing Zhou for their support. 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, March 1997. 175 [RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An 176 Overview of Reliable Server Pooling Protocols", RFC 5351, 177 September 2008. 179 [RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 180 "Aggregate Server Access Protocol (ASAP)", RFC 5352, 181 September 2008. 183 [RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. 184 Silverton, "Endpoint Handlespace Redundancy Protocol 185 (ENRP)", RFC 5353, September 2008. 187 [RFC5354] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 188 "Aggregate Server Access Protocol (ASAP) and Endpoint 189 Handlespace Redundancy Protocol (ENRP) Parameters", 190 RFC 5354, September 2008. 192 [RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M. 193 Holdrege, "Threats Introduced by Reliable Server Pooling 194 (RSerPool) and Requirements for Security in Response to 195 Threats", RFC 5355, September 2008. 197 [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 198 Policies", RFC 5356, September 2008. 200 [I-D.dreibholz-rserpool-delay] 201 Dreibholz, T. and X. Zhou, "Definition of a Delay 202 Measurement Infrastructure and Delay-Sensitive Least-Used 203 Policy for Reliable Server Pooling", 204 draft-dreibholz-rserpool-delay-05 (work in progress), 205 January 2010. 207 [I-D.dreibholz-rserpool-enrp-takeover] 208 Dreibholz, T. and X. Zhou, "Takeover Suggestion Flag for 209 the ENRP Handle Update Message", 210 draft-dreibholz-rserpool-enrp-takeover-03 (work in 211 progress), January 2010. 213 7.2. Informative References 215 [Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation, 216 Optimization and Extension of a Novel IETF Architecture", 217 Ph.D. Thesis University of Duisburg-Essen, Faculty of 218 Economics, Institute for Computer Science and Business 219 Information Systems, URL: http:// 220 duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/ 221 Derivate-16326/Dre2006-final.pdf, March 2007. 223 [IJAIT2009] 224 Dreibholz, T. and E. Rathgeb, "Overview and Evaluation of 225 the Server Redundancy and Session Failover Mechanisms in 226 the Reliable Server Pooling Framework", International 227 Journal on Advances in Internet Technology (IJAIT) Volume 228 2, Number 1, June 2009. 230 [IJHIT2008] 231 Dreibholz, T. and E. Rathgeb, "An Evalulation of the Pool 232 Maintenance Overhead in Reliable Server Pooling Systems", 233 International Journal of Hybrid Information Technology 234 (IJHIT) Volume 1, Number 2, April 2008. 236 [LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of 237 Reliable Server Pooling Systems", Proceedings of the 30th 238 IEEE Local Computer Networks Conference, November 2005. 240 [RSerPoolPage] 241 Dreibholz, T., "Thomas Dreibholz's RSerPool Page", 242 URL: http://tdrwww.iem.uni-due.de.de/dreibholz/rserpool/. 244 Author's Address 246 Thomas Dreibholz 247 University of Duisburg-Essen, Institute for Experimental Mathematics 248 Ellernstrasse 29 249 45326 Essen, Nordrhein-Westfalen 250 Germany 252 Phone: +49-201-1837637 253 Fax: +49-201-1837673 254 Email: dreibh@iem.uni-due.de 255 URI: http://www.iem.uni-due.de/~dreibh/