Applicability of SUPA
draft-cheng-supa-applicability-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
SUPA                                                            Y. Cheng
Internet-Draft                                              China Unicom
Intended status: Informational                                    D. Liu
Expires: September 14, 2017                                Alibaba Group
                                                                   B. Fu
                                                           China Telecom
                                                                D. Zhang
                                                              Freelancer
                                                              N. Vadrevu
                                                  VN Telecom Consultancy
                                                          March 13, 2017

                         Applicability of SUPA
                   draft-cheng-supa-applicability-01

Abstract

   SUPA will define a generic policy model, an imperative ECA (Event
   Condition Action) policy information model and a declarative (intent-
   based) policy information model which is the extension of the generic
   model, and a set of policy data models which will make use of the
   common concepts defined in the generic model.  This memo will explore
   some typical use cases and demonstrate the applicability of SUPA
   policy models.

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 September 14, 2017.

Copyright Notice

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

Cheng, et al.          Expires September 14, 2017               [Page 1]
Internet-Draft            Applicability of SUPA               March 2017

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Framework . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Network Manager/Controller  . . . . . . . . . . . . . . .   6
   4.  Use Cases of SUPA . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Use Case 1: SNMP blocking . . . . . . . . . . . . . . . .   8
       4.1.1.  Introduction  . . . . . . . . . . . . . . . . . . . .   8
       4.1.2.  Solution Approach . . . . . . . . . . . . . . . . . .   9
     4.2.  Use Case 2: VPC . . . . . . . . . . . . . . . . . . . . .  10
       4.2.1.  Generic . . . . . . . . . . . . . . . . . . . . . . .  10
       4.2.2.  Example 1 . . . . . . . . . . . . . . . . . . . . . .  12
       4.2.3.  Example 2 . . . . . . . . . . . . . . . . . . . . . .  13
     4.3.  Use Case 3: Instant VPN . . . . . . . . . . . . . . . . .  14
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   One of the ways for network service automation is using network
   management and operation software applications.  The applications may
   not be able to directly communicate with each network element; a
   hierarchical and extensible framework should be considered to hide
   the protocol specific and/or vendor specific details, high level
   network and service abstraction, and standardized programming API
Show full document text