idnits 2.17.1 draft-dreibholz-rserpool-asap-hropt-04.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 (January 7, 2009) is 5580 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-00 == Outdated reference: A later version (-33) exists of draft-dreibholz-rserpool-delay-02 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 January 7, 2009 5 Expires: July 11, 2009 7 Handle Resolution Option for ASAP 8 draft-dreibholz-rserpool-asap-hropt-04.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 July 11, 2009. 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 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. 45 Abstract 47 This document describes the Handle Resolution option for the ASAP 48 protocol. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Handle Resolution Option . . . . . . . . . . . . . . . . . . . 3 57 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. Reference Implementation . . . . . . . . . . . . . . . . . . . 4 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 61 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 64 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 67 1. Introduction 69 Reliable Server Pooling defines protocols for providing highly 70 available services. The Aggregate Server Access Protocol (ASAP) 71 provides session management and server selection for applications. 72 Upon request for a server selection -- denoted as handle resolution 73 -- an ENRP server returns a list of selected PE identities. The 74 number of PE identities to be returned is not specified by RSerPool. 75 Furthermore the ASAP protocol does not contain a way for letting the 76 requesting instance specify it. 78 As shown in [Dre2006], [IJHIT2008], selecting too many entries does 79 not make sense for the application, but on the other hand also result 80 in significant processing and network overhead. Furthermore, it has 81 been shown in [LCN2005] that the number of requested elements is 82 usually 1, but there are application cases where more PE identities 83 have to be returned. That is, there should be a possibility to 84 specify the number of requested PE items upon a handle resolution. 86 1.1. Scope 88 The Handle Resolution option defined in this draft simply defines an 89 option to let the PU-side specify the desired number of PE identities 90 from the ENRP server. 92 1.2. Terminology 94 The terms are commonly identified in related work and can be found in 95 the Aggregate Server Access Protocol and Endpoint Handlespace 96 Redundancy Protocol Common Parameters document RFC 5354 [RFC5354]. 98 1.3. Conventions 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in [RFC2119]. 104 2. Handle Resolution Option 106 2.1. Definition 108 The Handle Resolution MAY be used once in an ASAP Handle Resolution 109 message sent from a PU to an ENRP server. It is defined as follows. 111 0 1 2 3 112 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 113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 | Type = 0x803f | Length=8 | 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 | Items | 117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 Items: 32 bits (unsigned integer) 121 Contains the number of PE identities to be selected by the ENRP 122 server. Setting it to 0xffffffff denotes to obtain as many PE 123 identities as possible. A setting of 0 denotes to use the ENRP 124 server's default value; this default MUST be used if there is no 125 Handle Resolution option given. The ENRP server SHOULD try to fulfil 126 the request for the given number of items. 128 Note, that the high-order bits of the type field are set to 10, which 129 means "skip this parameter and continue processing" if this parameter 130 type is not supported by the ENRP server. This allows for 131 interoperability with old implementations. 133 3. Reference Implementation 135 The RSerPool reference implementation RSPLIB can be found at 136 [RSerPoolPage]. It supports the functionalities defined by 137 [RFC5351], [RFC5352], [RFC5353], [RFC5354] and [RFC5356] as well as 138 the options [I-D.dreibholz-rserpool-delay], 139 [I-D.dreibholz-rserpool-enrp-takeover] and of course the option 140 defined by this document. An introduction to this implementation is 141 provided in [Dre2006]. 143 4. Security Considerations 145 Security considerations for RSerPool systems are described by 146 [RFC5355]. 148 5. IANA Considerations 150 This document does not require additional IANA actions beyond those 151 already identified in the ENRP and ASAP protocol specifications. 153 6. Acknowledgments 155 The author would like to thank Nihad Cosic, Dirk Hoffstadt, Michael 156 Kohnen, Jobin Pulinthanath and Xing Zhou for their support. 158 7. References 160 7.1. Normative References 162 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 163 Requirement Levels", BCP 14, RFC 2119, March 1997. 165 [RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An 166 Overview of Reliable Server Pooling Protocols", RFC 5351, 167 September 2008. 169 [RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 170 "Aggregate Server Access Protocol (ASAP)", RFC 5352, 171 September 2008. 173 [RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. 174 Silverton, "Endpoint Handlespace Redundancy Protocol 175 (ENRP)", RFC 5353, September 2008. 177 [RFC5354] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, 178 "Aggregate Server Access Protocol (ASAP) and Endpoint 179 Handlespace Redundancy Protocol (ENRP) Parameters", 180 RFC 5354, September 2008. 182 [RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M. 183 Holdrege, "Threats Introduced by Reliable Server Pooling 184 (RSerPool) and Requirements for Security in Response to 185 Threats", RFC 5355, September 2008. 187 [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling 188 Policies", RFC 5356, September 2008. 190 7.2. Informative References 192 [RSerPoolPage] 193 Dreibholz, T., "Thomas Dreibholz's RSerPool Page", 194 URL: http://tdrwww.iem.uni-due.de.de/dreibholz/rserpool/. 196 [Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation, 197 Optimization and Extension of a Novel IETF Architecture", 198 Ph.D. Thesis University of Duisburg-Essen, Faculty of 199 Economics, Institute for Computer Science and Business 200 Information Systems, URL: http:// 201 duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/ 202 Derivate-16326/Dre2006-final.pdf, March 2007. 204 [LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of 205 Reliable Server Pooling Systems", Proceedings of the 30th 206 IEEE Local Computer Networks Conference, November 2005. 208 [IJHIT2008] 209 Dreibholz, T. and E. Rathgeb, "An Evalulation of the Pool 210 Maintenance Overhead in Reliable Server Pooling Systems", 211 International Journal of Hybrid Information Technology 212 (IJHIT) Volume 1, Number 2, April 2008. 214 [I-D.dreibholz-rserpool-enrp-takeover] 215 Dreibholz, T. and X. Zhou, "Takeover Suggestion Flag for 216 the ENRP Handle Update Message", 217 draft-dreibholz-rserpool-enrp-takeover-00 (work in 218 progress), December 2008. 220 [I-D.dreibholz-rserpool-delay] 221 Dreibholz, T. and X. Zhou, "Definition of a Delay 222 Measurement Infrastructure and Delay-Sensitive Least-Used 223 Policy for Reliable Server Pooling", 224 draft-dreibholz-rserpool-delay-02 (work in progress), 225 July 2008. 227 Author's Address 229 Thomas Dreibholz 230 University of Duisburg-Essen, Institute for Experimental Mathematics 231 Ellernstrasse 29 232 45326 Essen, Nordrhein-Westfalen 233 Germany 235 Phone: +49-201-1837637 236 Fax: +49-201-1837673 237 Email: dreibh@iem.uni-due.de 238 URI: http://www.iem.uni-due.de/~dreibh/