[vnfpool] vnfpool and rserpool

Melinda Shore <melinda.shore@gmail.com> Wed, 23 July 2014 19:49 UTC

Return-Path: <melinda.shore@gmail.com>
X-Original-To: vnfpool@ietfa.amsl.com
Delivered-To: vnfpool@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 2C2CD1A0204 for <vnfpool@ietfa.amsl.com>; Wed, 23 Jul 2014 12:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id YMVsC4t359Mo for <vnfpool@ietfa.amsl.com>; Wed, 23 Jul 2014 12:49:14 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EBEA1A063F for <vnfpool@ietf.org>; Wed, 23 Jul 2014 12:49:14 -0700 (PDT)
Received: by mail-ig0-f170.google.com with SMTP id h3so5733030igd.1 for <vnfpool@ietf.org>; Wed, 23 Jul 2014 12:49:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=MDaOPLW7WYElcGu5kfi9mR4lq5/lW3iWikX5rMiXlHE=; b=wEqO/xm9rofxf/7Zp1RkQOmVQ69G+4ynf9wk2kaUbIc3pz5utUYWg4ISGdoYG0aPSb 3hERWqQ/UIiQwYHSPJL5LNKJj+tfL1oZHAOkMOqqYk7Iv3hDBnvaMGwOjHyj9EeUhdCK KO1iCjnrxQQuJM3V3Nvf/VsqomrGwM+rMwt2iEUltIB/Mgw8rOxqKYFgKuFjgQkf3qcM ESFyCOcGlSn2hq4J656IneetIMHLntkDSvUMN+aIld4ObdQrTLJzTg2b0A5ghMaF+XVK tCZcNThiEQFCkcoevjd92wppAn2/6d0TMtvNKeYZv89kF1ceHCz2LISFXbWeLow5BqJ9 POyw==
X-Received: by with SMTP id p17mr5653476icl.33.1406144952684; Wed, 23 Jul 2014 12:49:12 -0700 (PDT)
Received: from dhcp-9055.meeting.ietf.org (dhcp-9055.meeting.ietf.org. []) by mx.google.com with ESMTPSA id kw1sm15641008igb.2.2014. for <vnfpool@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jul 2014 12:49:12 -0700 (PDT)
Message-ID: <53D011B6.3040708@gmail.com>
Date: Wed, 23 Jul 2014 15:49:10 -0400
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: vnfpool@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/JoMZtXqjGMfD7aUVJ3bmW6liQa4
Subject: [vnfpool] vnfpool and rserpool
X-BeenThere: vnfpool@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for virtual network function resource pooling." <vnfpool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vnfpool/>
List-Post: <mailto:vnfpool@ietf.org>
List-Help: <mailto:vnfpool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jul 2014 19:49:16 -0000

I found yesterday's BOF to be very useful, in terms of clarifying
the scope of the charter proposal and of identifying applicability
considerations in several scenarios.  We plan to get the next
iteration of the charter out next week, with some additional
text about policy.  Many thanks to everybody who participated.

This seems like a good time to post a reminder that we do have
a draft on the applicability of rserpool to the vnfpool problem.
This draft is not intended as a full gap analysis but it does
identify problems that must be addressed by a redundancy model
for VNF reliability, and looks at what is (and is not) provided
by rserpool.  In particular, section 4 says:

    The following features of RSerPool can be used for VNFPOOL:

    o  Pool management.
    o  PE selection with pool policies.
    o  Session management with help of ASAP_BUSINESS_CARD.

    The following features have to be added to RSerPool itself:

    o  Support of TCP including MPTCP as additional/alternative transport
    o  Possibly add some special pool policies?

    The following features have to be provided outside of RSerPool:

    o  State synchronisation for VNFPOOL.
    o  Pool Manager functionality as an RSerPool-based service.

Details are provided by the draft, which is available at:
Please note that the question of which technology to use for
vnfpool is open and will not be resolved until we have a full
set of agreed-upon requirements, and that the rserpool draft
was written as a demonstration of what might be possible with
existing IETF protocols.  We'd love to see similar drafts describing
the applicability of other protocols or technologies.