Internet Classfication
draft-li-intent-classification-00

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)
Internet Engineering Task Force                                    C. Li
Internet-Draft                                             China Telecom
Intended status: Informational                                  Y. Cheng
Expires: September 14, 2017                                 China Unicom
                                                                 T. Peng
                                                                 X. Song
                                                            J. Strassner
                                                     Huawei Technologies
                                                          March 13, 2017

                         Internet Classfication
                   draft-li-intent-classification-00

Abstract

   Intent is an abstract high-level policy used to operate the network
   RFC 7575 [RFC7575].  Intent management system includes an interface
   for users to input requests and an engine to manage the requests.  Up
   to now, there is no commonly agreed interface or model of intent.
   This document describes different ways to classify intent, and an
   associated taxonomy of this classification.

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.

   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

Li, et al.             Expires September 14, 2017               [Page 1]
Internet-Draft           Internet Classfication               March 2017

   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.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  The Policy Continuum  . . . . . . . . . . . . . . . . . . . .   3
   5.  Functional Characteristics and Behavior . . . . . . . . . . .   3
     5.1.  Persistence . . . . . . . . . . . . . . . . . . . . . . .   3
     5.2.  Abstracting Intent Operation  . . . . . . . . . . . . . .   4
     5.3.  Policy Subjects and Policy Targets  . . . . . . . . . . .   4
     5.4.  Policy Scope  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Different SDOs (such as [ANIMA][ONF]) have proposed intent as a
   declarative interface for defining a set of network operations to
   execute.  Although there is no common definition or model of intent
   which are agreed by all SDOs, there are several shared principles:

   o  intent should be declarative, using and depending on as few
      deployment details as possible

   o  intent should provide an easy-to-use interface, and use
      terminology and concepts familiar to its target audience

   o  intent should be vendor-independent and portable across platforms

   o  the intent framework should be able to detect and resolve
      conflicts between multiple intents

   SDOs have different perspectives on what intent is, what set of
   actors it is intended to serve, and how it should be used.  This
   document provides several dimensions to classify intents.
Show full document text