Ideas for a Next Generation of the Reliable Server Pooling Framework
draft-dreibholz-rserpool-nextgen-ideas-08

Document Type Active Internet-Draft (individual)
Last updated 2017-08-06
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       T. Dreibholz
Internet-Draft                                Simula Research Laboratory
Intended status: Informational                           August 06, 2017
Expires: February 7, 2018

  Ideas for a Next Generation of the Reliable Server Pooling Framework
             draft-dreibholz-rserpool-nextgen-ideas-08.txt

Abstract

   This document collects some idea for a next generation of the
   Reliable Server Pooling framework.

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 February 7, 2018.

Copyright Notice

   Copyright (c) 2017 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 February 7, 2018                [Page 1]
Internet-Draft       RSerPool Next Generation Ideas          August 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Reliable Server Pooling . . . . . . . . . . . . . . . . .   2
     1.3.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  What to Change in the Next Generation of RSerPool?  . . . . .   3
     2.1.  Security Considerations . . . . . . . . . . . . . . . . .   4
     2.2.  IANA Considerations . . . . . . . . . . . . . . . . . . .   4
   3.  Reference Implementation  . . . . . . . . . . . . . . . . . .   4
   4.  Testbed Platform  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

1.1.  Abbreviations

   o  ASAP: Aggregate Server Access Protocol

   o  ENRP: Endpoint Handlespace Redundancy Protocol

   o  ID: Identifier

   o  MPTCP: Multi-Path Transmission Control Protocol

   o  PE: Pool Element

   o  PR: Pool Registrar

   o  PU: Pool User

   o  RSerPool: Reliable Server Pooling

   o  SCTP: Stream Control Transmission Protocol

   o  TCP: Transmission Control Protocol

   o  VNFPOOL: Virtual Network Function Resource Pooling

1.2.  Reliable Server Pooling

   Reliable Server Pooling (RSerPool) has been defined as RFCs in [1],
   [2], [3], [4], [5], [6], [7], [8].  There is also a detailed
   introduction provided by [16] as well as lots of further information

Dreibholz               Expires February 7, 2018                [Page 2]
Internet-Draft       RSerPool Next Generation Ideas          August 2017

   material on [22].  RSerPool is therefore not introduced in more
   detail here.

1.3.  Scope

   The scope of this document is to collect some ideas of what to
   update/change for a next generation of the RSerPool framework.  It is
   a result of lessons learned with more than one decade of RSerPool
   deployment (see also [17], [18], [19]) as well as ongoing discussions
   on applying RSerPool for Virtual Network Function Resource
   Pooling (VNFPOOL; as introduced in more detail in [15]).

2.  What to Change in the Next Generation of RSerPool?

   o  ENRP servers denote the management systems in the context of
      RSerPool.  The term "server" is misleading, since ENRP servers are
Show full document text