[forces] Requesting further comments/suggestions on IETF ForCES Logical Function Block (LFB) Subsidiary Management dratf

"B.Khasnabish@ieee.org" <vumip1@gmail.com> Tue, 15 July 2014 17:09 UTC

Return-Path: <vumip1@gmail.com>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E72081A0AC4 for <forces@ietfa.amsl.com>; Tue, 15 Jul 2014 10:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i1M_bHIBKH5f for <forces@ietfa.amsl.com>; Tue, 15 Jul 2014 10:09:40 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFFDB1A0ABB for <forces@ietf.org>; Tue, 15 Jul 2014 10:09:39 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id b13so3778191wgh.10 for <forces@ietf.org>; Tue, 15 Jul 2014 10:09:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=xsY0pCLE8lPgrSYEMEK7FAUl3hf1T2VFsUlCzrmIALs=; b=04Z5Va6OA996a481wEvafxUrb/nqZvvqeMmMd2snmNRExxsZgJNDL/zlOfIFtTjGse Oem37fY2pmw1B58hCn/ZvugJdkjSlathGUQEXMPaPjP2Wp1HN24khVn8MN8HkyM61tfE uBp99HotnhSq+9s+HkqrJYNvIGqQIdbTgcAu1anechDr82qqIlN0hsLO5GyuK/XgjcYV QR7TV6xRL9uE626rGYtoY1rj1MIJfbXzdIQqvSoaU5EtAsRV3yst/XLtes5NM7pcmwbk sRpYE0ufE0XdiqXwrbxATYQGj8ojymGVpb5vNDyINZSjPGgVxJvdToSl3+7Yk7EjHs0f Fndg==
MIME-Version: 1.0
X-Received: by 10.194.20.230 with SMTP id q6mr29576453wje.43.1405444178361; Tue, 15 Jul 2014 10:09:38 -0700 (PDT)
Received: by 10.217.148.67 with HTTP; Tue, 15 Jul 2014 10:09:38 -0700 (PDT)
Date: Tue, 15 Jul 2014 13:09:38 -0400
Message-ID: <CANtnpwjPa_LELo6x4qjtefxL=sFDtzsdJdahJ+KveO0ayvPdPg@mail.gmail.com>
From: "B.Khasnabish@ieee.org" <vumip1@gmail.com>
To: "forces@ietf.org" <forces@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b5d971b00c5dd04fe3e79fd"
Archived-At: http://mailarchive.ietf.org/arch/msg/forces/NS-HDq0egEjlEzLEfbOiUQM6ZO8
Subject: [forces] Requesting further comments/suggestions on IETF ForCES Logical Function Block (LFB) Subsidiary Management dratf
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces/>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2014 17:09:42 -0000

Dear All,

We are planning to release updates to the LFB
Subsidiary Management draft
(
http://datatracker.ietf.org/doc/draft-khs-forces-lfb-subsidiary-management/
)
very soon.

Kindly let us know ASAP if you have any
further comments/suggestions.

Many thanks in advance.

Best.

Draft Authors


+++++++++++++++++++++++++++++++++++++++
Network Working Group                                      B. Khasnabish
Internet-Draft                                              ZTE TX, Inc.
Intended status: Standards Track                           E. Haleplidis
Expires: August 14, 2014                            University of Patras
                                                           J. Hadi Salim
                                                       Mojatatu Networks
                                                       February 10, 2014

     IETF ForCES Logical Function Block (LFB) Subsidiary Management
           draft-khs-forces-lfb-subsidiary-management-00.txt

Abstract

   This document discusses ForCES Logical Function Block (LFB)
   Subsidiary Management (SM).  Note that LFB SM is useful for
   introducing and supporting virtualization of ForCES Network Element
   (NE) including control Element (CE) and Forwarding Element (FE).

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 August 14, 2014.

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

Khasnabish, et al. Expires August 14, 2014 [Page 1]
Internet-Draft IETF ForCES LFB Subsidiary Management February 2014

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Conventions and Definitions . . . . . . . . . . . . . . .   4
   2.  Use of Virtualized ForCES Elements  . . . . . . . . . . . . .   5
     2.1.  Use of Virtualized CEs  . . . . . . . . . . . . . . . . .   5
     2.2.  Use of Virtualized FEs  . . . . . . . . . . . . . . . . .   6
   3.  Potential Scenarios . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Recovery from CE failure  . . . . . . . . . . . . . . . .   6
     3.2.  Recovery from FE failure  . . . . . . . . . . . . . . . .   6
     3.3.  Load Balancing  . . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Scalable/Robust Service Function Chaining . . . . . . . .   6
     3.5.  Orchestration . . . . . . . . . . . . . . . . . . . . . .   6
     3.6.  Generic LFB Lifecycle Management  . . . . . . . . . . . .   6
       3.6.1.  Booting a CE/FE . . . . . . . . . . . . . . . . . . .   7
       3.6.2.  Bootstrapping the Configuration . . . . . . . . . . .   7
       3.6.3.  Runtime Management  . . . . . . . . . . . . . . . . .   7
   4.  Testbed Platform  . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Reference Implementation  . . . . . . . . . . . . . . . . . .   7
   6.  FEM Library . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Frame Definitions . . . . . . . . . . . . . . . . . . . .   7
     6.2.  Datatype Definitions  . . . . . . . . . . . . . . . . . .   7
     6.3.  Metadata Definitions  . . . . . . . . . . . . . . . . . .   8
     6.4.  FEM . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
       6.4.1.  Data Handling . . . . . . . . . . . . . . . . . . . .   8
       6.4.2.  Components  . . . . . . . . . . . . . . . . . . . . .   8
       6.4.3.  Capabilities  . . . . . . . . . . . . . . . . . . . .   9
       6.4.4.  Events  . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  XML for FEM LFB . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     9.1.  LFB Class Names and LFB Class Identifiers . . . . . . . .  13