datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

Handle Resolution Option for ASAP
draft-dreibholz-rserpool-asap-hropt-15

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-07-04
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                       T. Dreibholz
Internet-Draft                                Simula Research Laboratory
Intended status: Experimental                              July 04, 2014
Expires: January 5, 2015

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

Abstract

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

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on January 5, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Dreibholz                Expires January 5, 2015                [Page 1]
Internet-Draft          Handle Resolution Option               July 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Handle Resolution Option  . . . . . . . . . . . . . . . . . .   3
     2.1.  Definition  . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Reference Implementation  . . . . . . . . . . . . . . . . . .   3
   4.  Testbed Platform  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

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 [Dre2006], [IJAIT2009], [IJHIT2008], 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 [LCN2005] 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.

Dreibholz                Expires January 5, 2015                [Page 2]
Internet-Draft          Handle Resolution Option               July 2014

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 RFC 5354 [RFC5354].

[include full document text]