[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Network Working Group                                       T. Dreibholz
Internet-Draft                              University of Duisburg-Essen
Intended status: Standards Track                            June 6, 2007
Expires: December 8, 2007


                   Handle Resolution Option for ASAP
               draft-dreibholz-rserpool-asap-hropt-00.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on December 8, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2007).














Dreibholz               Expires December 8, 2007                [Page 1]


Internet-Draft          Handle Resolution Option               June 2007


Abstract

   This document describes the Handle Resolution option for the ASAP
   protocol.















































Dreibholz               Expires December 8, 2007                [Page 2]


Internet-Draft          Handle Resolution Option               June 2007


1.  Introduction

   Reliable Server Pooling defines protocols for providing highly
   available services.  The Aggregate Server Access Protocol (ASAP)
   provides session management and server selection for applications.
   Upon request for a server selection -- denoted as handle resolution
   -- an ENRP server returns a list of selected PE identities.  The
   number of PE identities to be returned is not specified by RSerPool.
   Furthermore the ASAP protocol does not contain a way for letting the
   requesting instance specify it.

   As shown in [7], [9], selecting too many entries does not make sense
   for the application, but on the other hand also result in significant
   processing and network overhead.  Furthermore, it has been shown in
   [8] that the number of requested elements is usually 1, but there are
   application cases where more PE identities have to be returned.  That
   is, there should be a possibility to specify the number of requested
   PE items upon a handle resolution.

1.1.  Scope

   The Handle Resolution option defined in this draft simply defines an
   option to let the PU-side specify the desired number of PE identities
   from the ENRP server.

1.2.  Terminology

   The terms are commonly identified in related work and can be found in
   the Aggregate Server Access Protocol and Endpoint Handlespace
   Redundancy Protocol Common Parameters document ietf-rserpool-common-
   param [4]




















Dreibholz               Expires December 8, 2007                [Page 3]


Internet-Draft          Handle Resolution Option               June 2007


2.  Handle Resolution Option

2.1.  Definition

   The Handle Resolution MAY be used once in an ASAP Handle Resolution
   message sent from a PU to an ENRP server.  It is defined as follows.

       0                   1                   2                   3
       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
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |        Type = 0x803f         |            Length=8            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                             Items                             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Items: 32 bits (unsigned integer)

   Contains the number of PE identities to be selected by the ENRP
   server.  Setting it to 0xffffffff denotes to obtain as many PE
   identities as possible.  A setting of 0 denotes to use the ENRP
   server's default value; this default MUST be used if there is no
   Handle Resolution option given.  The ENRP server SHOULD try to fulfil
   the request for the given number of items.

   Note, that the high-order bits of the type field are set to 10, which
   means "skip this parameter and continue processing" if this parameter
   type is not supported by the ENRP server.  This allows for
   interoperability with old implementations.

2.2.  Reference Implementation

   The reference implementation based on the RSerPool prototype rsplib
   can be found at [6].


















Dreibholz               Expires December 8, 2007                [Page 4]


Internet-Draft          Handle Resolution Option               June 2007


3.  References

3.1.  Normative References

   [1]   Tuexen, M., "Architecture for Reliable Server Pooling",
         draft-ietf-rserpool-arch-12 (work in progress), November 2006.

   [2]   Stewart, R., "Aggregate Server Access Protocol (ASAP)",
         draft-ietf-rserpool-asap-15 (work in progress), January 2007.

   [3]   Stewart, R., "Endpoint Handlespace Redundancy Protocol (ENRP)",
         draft-ietf-rserpool-enrp-15 (work in progress), January 2007.

   [4]   Stewart, R., "Aggregate Server Access Protocol (ASAP) and
         Endpoint Handlespace Redundancy  Protocol (ENRP) Parameters",
         draft-ietf-rserpool-common-param-11 (work in progress),
         October 2006.

   [5]   Tuexen, M. and T. Dreibholz, "Reliable Server Pooling
         Policies", draft-ietf-rserpool-policies-04 (work in progress),
         March 2007.

3.2.  Informative References

   [6]   Dreibholz, T., "Thomas Dreibholz's RSerPool Page",
         URL: http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/.

   [7]   Dreibholz, T., "Reliable Server Pooling -- Evaluation,
         Optimization and Extension of a Novel IETF Architecture", Ph.D.
         Thesis University of Duisburg-Essen, Faculty of Economics,
         Institute for Computer Science and Business Information
         Systems, URL: http://duepublico.uni-duisburg-essen.de/servlets/
         DerivateServlet/Derivate-16326/Dre2006-final.pdf, March 2007.

   [8]   Dreibholz, T. and E. Rathgeb, "On the Performance of Reliable
         Server Pooling Systems", Proceedings of the 30th IEEE Local
         Computer Networks Conference, November 2005.

   [9]   Dreibholz, T. and E. Rathgeb, "Implementing the Reliable Server
         Pooling Framework", Proceedings of the 8th IEEE International
         Conference on Telecommunications, June 2005.

   [10]  Dreibholz, T. and E. Rathgeb, "An Application Demonstration of
         the Reliable Server Pooling Framework", Proceedings of the 24th
         IEEE Infocom, March 2005.






Dreibholz               Expires December 8, 2007                [Page 5]


Internet-Draft          Handle Resolution Option               June 2007


Author's Address

   Thomas Dreibholz
   University of Duisburg-Essen, Institute for Experimental Mathematics
   Ellernstrasse 29
   45326 Essen, Nordrhein-Westfalen
   Germany

   Phone: +49-201-1837637
   Fax:   +49-201-1837673
   Email: dreibh@exp-math.uni-essen.de
   URI:   http://www.exp-math.uni-essen.de/~dreibh/







































Dreibholz               Expires December 8, 2007                [Page 6]


Internet-Draft          Handle Resolution Option               June 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Dreibholz               Expires December 8, 2007                [Page 7]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/