idnits 2.17.1 draft-dreibholz-rserpool-asap-hropt-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. 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 (July 5, 2009) is 5409 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-31) exists of draft-dreibholz-rserpool-enrp-takeover-01 == Outdated reference: A later version (-33) 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 July 5, 2009 5 Expires: January 6, 2010 7 Handle Resolution Option for ASAP 8 draft-dreibholz-rserpool-asap-hropt-05.txt 10 Status of this Memo 12 This Internet-Draft is submitted to IETF in full conformance with the 13 provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on January 6, 2010. 33 Copyright Notice 35 Copyright (c) 2009 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 in effect on the date of 40 publication of this document (http://trustee.ietf.org/license-info). 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. 44 Abstract 46 This document describes the Handle Resolution option for the ASAP 47 protocol. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Handle Resolution Option . . . . . . . . . . . . . . . . . . . 3 56 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Reference Implementation . . . . . . . . . . . . . . . . . . . 4 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 59 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 60 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 61 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 63 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 Reliable Server Pooling defines protocols for providing highly 69 available services. The Aggregate Server Access Protocol (ASAP) 70 provides session management and server selection for applications. 71 Upon request for a server selection -- denoted as handle resolution 72 -- an ENRP server returns a list of selected PE identities. The 73 number of PE identities to be returned is not specified by RSerPool. 74 Furthermore the ASAP protocol does not contain a way for letting the 75 requesting instance specify it. 77 As shown in [Dre2006], [IJHIT2008], selecting too many entries does 78 not make sense for the application, but on the other hand also result 79 in significant processing and network overhead. Furthermore, it has 80 been shown in [LCN2005] that the number of requested elements is 81 usually 1, but there are application cases where more PE identities 82 have to be returned. That is, there should be a possibility to 83 specify the number of requested PE items upon a 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 [RSerPoolPage]. 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. Security Considerations 144 Security considerations for RSerPool systems are described by 145 [RFC5355]. 147 5. IANA Considerations 149 This document does not require additional IANA actions beyond those 150 already identified in the ENRP and ASAP protocol specifications. 152 6. Acknowledgments 154 The author would like to thank Nihad Cosic, Dirk Hoffstadt, Michael 155 Kohnen, Jobin Pulinthanath and Xing Zhou for their support. 157 7. References 159 7.1. Normative References 161 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 162 Requirement Levels", BCP 14, RFC 2119, March 1997. 164 [RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An 165 Overview of Reliable Server Pooling Protocols", RFC 5351, 166 September 2008. 168 [RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 169 "Aggregate Server Access Protocol (ASAP)", RFC 5352, 170 September 2008. 172 [RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. 173 Silverton, "Endpoint Handlespace Redundancy Protocol 174 (ENRP)", RFC 5353, September 2008. 176 [RFC5354] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 177 "Aggregate Server Access Protocol (ASAP) and Endpoint 178 Handlespace Redundancy Protocol (ENRP) Parameters", 179 RFC 5354, September 2008. 181 [RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M. 182 Holdrege, "Threats Introduced by Reliable Server Pooling 183 (RSerPool) and Requirements for Security in Response to 184 Threats", RFC 5355, September 2008. 186 [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 187 Policies", RFC 5356, September 2008. 189 7.2. Informative References 191 [RSerPoolPage] 192 Dreibholz, T., "Thomas Dreibholz's RSerPool Page", 193 URL: http://tdrwww.iem.uni-due.de.de/dreibholz/rserpool/. 195 [Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation, 196 Optimization and Extension of a Novel IETF Architecture", 197 Ph.D. Thesis University of Duisburg-Essen, Faculty of 198 Economics, Institute for Computer Science and Business 199 Information Systems, URL: http:// 200 duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/ 201 Derivate-16326/Dre2006-final.pdf, March 2007. 203 [LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of 204 Reliable Server Pooling Systems", Proceedings of the 30th 205 IEEE Local Computer Networks Conference, November 2005. 207 [IJHIT2008] 208 Dreibholz, T. and E. Rathgeb, "An Evalulation of the Pool 209 Maintenance Overhead in Reliable Server Pooling Systems", 210 International Journal of Hybrid Information Technology 211 (IJHIT) Volume 1, Number 2, April 2008. 213 [I-D.dreibholz-rserpool-enrp-takeover] 214 Dreibholz, T. and X. Zhou, "Takeover Suggestion Flag for 215 the ENRP Handle Update Message", 216 draft-dreibholz-rserpool-enrp-takeover-01 (work in 217 progress), January 2009. 219 [I-D.dreibholz-rserpool-delay] 220 Dreibholz, T. and X. Zhou, "Definition of a Delay 221 Measurement Infrastructure and Delay-Sensitive Least-Used 222 Policy for Reliable Server Pooling", 223 draft-dreibholz-rserpool-delay-03 (work in progress), 224 January 2009. 226 Author's Address 228 Thomas Dreibholz 229 University of Duisburg-Essen, Institute for Experimental Mathematics 230 Ellernstrasse 29 231 45326 Essen, Nordrhein-Westfalen 232 Germany 234 Phone: +49-201-1837637 235 Fax: +49-201-1837673 236 Email: dreibh@iem.uni-due.de 237 URI: http://www.iem.uni-due.de/~dreibh/