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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rtg area)
Last updated 2015-04-06 (latest revision 2015-02-26)
Replaces draft-khs-forces-lfb-subsidiary-management
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Joel Halpern
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alia Atlas
IESG note Work left over after the forces WG was closed.
Send notices to draft-ietf-forces-lfb-subsidiary-management@ietf.org, draft-ietf-forces-lfb-subsidiary-management.ad@ietf.org, vumip1@gmail.com, hadi@mojatatu.com, draft-ietf-forces-lfb-subsidiary-management.shepherd@ietf.org, ehalep@ece.upatras.gr, "Evangelos Haleplidis
ForCES WG                                                  B. Khasnabish
Internet-Draft                                              ZTE TX, Inc.
Intended status: Standards Track                           E. Haleplidis
Expires: August 29, 2015                            University of Patras
                                                      J. Hadi Salim, Ed.
                                                       Mojatatu Networks
                                                       February 25, 2015

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

Abstract

   Deployment experience has demonstrated the value of using the
   Forwarding and Control Element Separation (ForCES) architecture to
   manage resources other than packet forwarding.  In that spirit, the
   Forwarding Element Manager (FEM) is modelled by creating a Logical
   Functional Block (LFB) to represent its functionality.  We refer to
   this LFB as the FE Configuration (FEC) LFB.  A Control Element (CE)
   that controls a Forwarding Element's (FE) resources can also manage
   its configuration via the FEC LFB.  This document introduces the FEC
   LFB, an LFB that specifies the configuration parameters of an 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 29, 2015.

Copyright Notice

   Copyright (c) 2015 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

Khasnabish, et al.       Expires August 29, 2015                [Page 1]
Internet-Draft      ForCES LFB Subsidiary Management       February 2015

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   5
     1.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Use cases . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  FE integration into an NE . . . . . . . . . . . . . . . .   6
     2.2.  CE associations . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  New LFB class installation  . . . . . . . . . . . . . . .   7
   3.  Applicability statement . . . . . . . . . . . . . . . . . . .   7
     3.1.  FE Integrated . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Virtual FEs . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  FEM . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  FEC Library . . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Frame Definitions . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Datatype Definitions  . . . . . . . . . . . . . . . . . .   8
     4.3.  Metadata Definitions  . . . . . . . . . . . . . . . . . .   8
     4.4.  FEC . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
       4.4.1.  Data Handling . . . . . . . . . . . . . . . . . . . .   9
       4.4.2.  Components  . . . . . . . . . . . . . . . . . . . . .   9
       4.4.3.  Capabilities  . . . . . . . . . . . . . . . . . . . .   9
       4.4.4.  Events  . . . . . . . . . . . . . . . . . . . . . . .   9
   5.  XML for FEC LFB . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  LFB Class Names and LFB Class Identifiers . . . . . . . .  13
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Appendix A.  Appendix . . . . . . . . . . . . . . . . . . . . . .  15
     A.1.  Use of Virtualized ForCES Elements  . . . . . . . . . . .  15
Show full document text