NEMO (NEtwork MOdeling) Language
draft-xia-sdnrg-nemo-language-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-07-04
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)
SDNRG                                                        Y. Xia, Ed.
Internet-Draft                                             S. Jiang, Ed.
Intended status: Standards Track                            T. Zhou, Ed.
Expires: January 5, 2015                                        S. Hares
                                            Huawei Technologies Co., Ltd
                                                            July 4, 2014

                    NEMO (NEtwork MOdeling) Language
                    draft-xia-sdnrg-nemo-language-00

Abstract

   The North-Bound Interface (NBI), located between the network control
   plane and the applications, is essential to enable the application
   innovations and nourish the eco-system of SDN.

   While most of the NBIs are provided in the form of API, this document
   proposes the NEtwork MOdeling (NEMO) language which is anther NBI
   fashion.  Concept, model and syntax are introduced in the document.

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 January 5, 2015.

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

Xia, et al.              Expires January 5, 2015                [Page 1]
Internet-Draft          NEtwork MOdeling Language              July 2014

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Related work  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  The NEMO Language overview  . . . . . . . . . . . . . . . . .   5
     4.1.  Network Model of the NEMO Language  . . . . . . . . . . .   5
     4.2.  Primitives  . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  The NEMO Language Examples  . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   While SDN (Software Defined Network) is becoming one of the most
   important directions of network evolution, the essence of SDN is to
   make the network more flexible and easy to use.  The North-Bound
   Interface (NBI), located between the control plane and the
   applications, is essential to enable the application innovations and
   nourish the eco-system of SDN by abstracting the network
   capabilities/information and opening the abstract/logic network to
   applications.

   The NBI is usually provided in the form of API (Application
   Programming Interface).  Different vendors provide self-defined API
   sets.  Each API set, such as OnePK from Cisco and OPS from Huawei,
   often contains hundreds of specific APIs.  Diverse APIs without
   consistent style are hard to remember and use, and nearly impossible
   to be standardized.

   Most of those APIs are designed by network domain experts, who are
   used to thinking from the network system perspective.  The interface
   designer does not know how the users will use the device and exposes
   information details as much as possible.  It enables better control
   of devices, but leaves huge burden of selecting useful information to
   users without well training.  Since the NBI is used by network users,
   a more appropriate design is to think from the user perspective and
   abstract the network from the top down.
   [I-D.sdnrg-service-description-language] describe the requirements
   for a service description language and the design considerations.

Xia, et al.              Expires January 5, 2015                [Page 2]
Show full document text