idnits 2.17.1 draft-dreibholz-rserpool-asap-hropt-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 (January 5, 2010) is 5196 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-30) exists of draft-dreibholz-rserpool-enrp-takeover-01 == Outdated reference: A later version (-32) exists of draft-dreibholz-rserpool-delay-03 Summary: 1 error (**), 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 January 5, 2010 5 Expires: July 9, 2010 7 Handle Resolution Option for ASAP 8 draft-dreibholz-rserpool-asap-hropt-06.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 to IETF 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), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 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 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on July 9, 2010. 38 Copyright Notice 40 Copyright (c) 2010 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 58 1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Handle Resolution Option . . . . . . . . . . . . . . . . . . . 3 60 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . . 3 61 3. Reference Implementation . . . . . . . . . . . . . . . . . . . 4 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 64 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 67 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 1. Introduction 72 Reliable Server Pooling defines protocols for providing highly 73 available services. The Aggregate Server Access Protocol (ASAP) 74 provides session management and server selection for applications. 75 Upon request for a server selection -- denoted as handle resolution 76 -- an ENRP server returns a list of selected PE identities. The 77 number of PE identities to be returned is not specified by RSerPool. 78 Furthermore the ASAP protocol does not contain a way for letting the 79 requesting instance specify it. 81 As shown in [Dre2006], [IJHIT2008], selecting too many entries does 82 not make sense for the application, but on the other hand also result 83 in significant processing and network overhead. Furthermore, it has 84 been shown in [LCN2005] that the number of requested elements is 85 usually 1, but there are application cases where more PE identities 86 have to be returned. That is, there should be a possibility to 87 specify the number of requested PE items upon a handle resolution. 89 1.1. Scope 91 The Handle Resolution option defined in this draft simply defines an 92 option to let the PU-side specify the desired number of PE identities 93 from the ENRP server. 95 1.2. Terminology 97 The terms are commonly identified in related work and can be found in 98 the Aggregate Server Access Protocol and Endpoint Handlespace 99 Redundancy Protocol Common Parameters document RFC 5354 [RFC5354]. 101 1.3. Conventions 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in [RFC2119]. 107 2. Handle Resolution Option 109 2.1. Definition 111 The Handle Resolution MAY be used once in an ASAP Handle Resolution 112 message sent from a PU to an ENRP server. It is defined as follows. 114 0 1 2 3 115 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 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | Type = 0x803f | Length=8 | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | Items | 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 Items: 32 bits (unsigned integer) 124 Contains the number of PE identities to be selected by the ENRP 125 server. Setting it to 0xffffffff denotes to obtain as many PE 126 identities as possible. A setting of 0 denotes to use the ENRP 127 server's default value; this default MUST be used if there is no 128 Handle Resolution option given. The ENRP server SHOULD try to fulfil 129 the request for the given number of items. 131 Note, that the high-order bits of the type field are set to 10, which 132 means "skip this parameter and continue processing" if this parameter 133 type is not supported by the ENRP server. This allows for 134 interoperability with old implementations. 136 3. Reference Implementation 138 The RSerPool reference implementation RSPLIB can be found at 139 [RSerPoolPage]. It supports the functionalities defined by 140 [RFC5351], [RFC5352], [RFC5353], [RFC5354] and [RFC5356] as well as 141 the options [I-D.dreibholz-rserpool-delay], 142 [I-D.dreibholz-rserpool-enrp-takeover] and of course the option 143 defined by this document. An introduction to this implementation is 144 provided in [Dre2006]. 146 4. Security Considerations 148 Security considerations for RSerPool systems are described by 149 [RFC5355]. 151 5. IANA Considerations 153 This document does not require additional IANA actions beyond those 154 already identified in the ENRP and ASAP protocol specifications. 156 6. Acknowledgments 158 The author would like to thank Nihad Cosic, Dirk Hoffstadt, Michael 159 Kohnen, Jobin Pulinthanath and Xing Zhou for their support. 161 7. References 163 7.1. Normative References 165 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 166 Requirement Levels", BCP 14, RFC 2119, March 1997. 168 [RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An 169 Overview of Reliable Server Pooling Protocols", RFC 5351, 170 September 2008. 172 [RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 173 "Aggregate Server Access Protocol (ASAP)", RFC 5352, 174 September 2008. 176 [RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. 177 Silverton, "Endpoint Handlespace Redundancy Protocol 178 (ENRP)", RFC 5353, September 2008. 180 [RFC5354] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 181 "Aggregate Server Access Protocol (ASAP) and Endpoint 182 Handlespace Redundancy Protocol (ENRP) Parameters", 183 RFC 5354, September 2008. 185 [RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M. 186 Holdrege, "Threats Introduced by Reliable Server Pooling 187 (RSerPool) and Requirements for Security in Response to 188 Threats", RFC 5355, September 2008. 190 [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 191 Policies", RFC 5356, September 2008. 193 7.2. Informative References 195 [RSerPoolPage] 196 Dreibholz, T., "Thomas Dreibholz's RSerPool Page", 197 URL: http://tdrwww.iem.uni-due.de.de/dreibholz/rserpool/. 199 [Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation, 200 Optimization and Extension of a Novel IETF Architecture", 201 Ph.D. Thesis University of Duisburg-Essen, Faculty of 202 Economics, Institute for Computer Science and Business 203 Information Systems, URL: http:// 204 duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/ 205 Derivate-16326/Dre2006-final.pdf, March 2007. 207 [LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of 208 Reliable Server Pooling Systems", Proceedings of the 30th 209 IEEE Local Computer Networks Conference, November 2005. 211 [IJHIT2008] 212 Dreibholz, T. and E. Rathgeb, "An Evalulation of the Pool 213 Maintenance Overhead in Reliable Server Pooling Systems", 214 International Journal of Hybrid Information Technology 215 (IJHIT) Volume 1, Number 2, April 2008. 217 [I-D.dreibholz-rserpool-enrp-takeover] 218 Dreibholz, T. and X. Zhou, "Takeover Suggestion Flag for 219 the ENRP Handle Update Message", 220 draft-dreibholz-rserpool-enrp-takeover-01 (work in 221 progress), January 2009. 223 [I-D.dreibholz-rserpool-delay] 224 Dreibholz, T. and X. Zhou, "Definition of a Delay 225 Measurement Infrastructure and Delay-Sensitive Least-Used 226 Policy for Reliable Server Pooling", 227 draft-dreibholz-rserpool-delay-03 (work in progress), 228 January 2009. 230 Author's Address 232 Thomas Dreibholz 233 University of Duisburg-Essen, Institute for Experimental Mathematics 234 Ellernstrasse 29 235 45326 Essen, Nordrhein-Westfalen 236 Germany 238 Phone: +49-201-1837637 239 Fax: +49-201-1837673 240 Email: dreibh@iem.uni-due.de 241 URI: http://www.iem.uni-due.de/~dreibh/