High-level VNF Descriptors using NEMO
draft-aranda-nfvrg-recursive-vnf-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-10-13
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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)
NFVRG                                                P. Aranda Gutierrez
Internet-Draft                                                DRL. Lopez
Intended status: Informational                                Telefonica
Expires: April 17, 2017                                       S. Salsano
                                          Univ. of Rome Tor Vergata/CNIT
                                                        October 14, 2016

                 High-level VNF Descriptors using NEMO
                  draft-aranda-nfvrg-recursive-vnf-01

Abstract

   Current efforts in the scope of Network Function Virtualisation(NFV)
   propose YAML-based descriptors for Virtual Network Functions (VNFs)
   and for their composition in Network Services (NS) These descriptors
   are human-readable but hardly understandable by humans.  On the other
   hand, there has been an effort proposed to the IETF to define a
   human-readable (and understandable) representation for networks,
   known as NEMO.  In this draft, we propose a simple extension to NEMO
   to accommodate VNF Descriptors (VNFDs) in a similar manner as inline
   assembly is integrated in higher-level programming languages.

   This approach enables the creation of recursive VNF forwarding graphs
   in Service Descriptors, practically making them recursive.

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 April 17, 2017.

Copyright Notice

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

Aranda Gutierrez, et al. Expires April 17, 2017                 [Page 1]
Internet-Draft         High-level VNFDs with NEMO           October 2016

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology and abbreviations . . . . . . . . . . . . . . . .   3
   3.  Prior art . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Virtual network function descriptors  . . . . . . . . . .   3
       3.1.1.  OpenMANO VNFDs  . . . . . . . . . . . . . . . . . . .   3
       3.1.2.  ETSI MANO VNFDs . . . . . . . . . . . . . . . . . . .   4
     3.2.  NEMO  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Additional requirements on NEMO . . . . . . . . . . . . . . .   8
     4.1.  Referencing VNFDs in a NodeModel  . . . . . . . . . . . .   8
     4.2.  Referencing the network interfaces of a VNF in a
           NodeModel . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.3.  An example  . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
     9.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Currently, there is a lot of on-going activity to deploy NFV in the
   network.  From the point of view of the orchestration, Virtual
   Network Functions are blocks that are deployed in the infrastructure
   as independent units.  Following the reference architectural model
   proposed in [ETSI-NFV-MANO], VNFs provide for one layer of components
   (VNF components(VNFCs)) below, i.e. a set of VNFCs accessible to a
   VNF provider can be composed into VNFs.  However, there is no simple
   way to use existing VNFs as components in VNFs with a higher degree
Show full document text