Requirements and Architecture of Carrier IP Service Models
draft-li-opsawg-carrier-ip-service-model-req-arch-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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)
Network Working Group                                              Z. Li
Internet-Draft                                                    Huawei
Intended status: Informational                                    Q. Sun
Expires: September 14, 2017                                China Telecom
                                                                Y. Zheng
                                                            China Unicom
                                                          March 13, 2017

       Requirements and Architecture of Carrier IP Service Models
          draft-li-opsawg-carrier-ip-service-model-req-arch-01

Abstract

   Service Model is a fundamental building block for a controller's
   North-Bound Interface (NBI).  Defining a service model for different
   multi-layered and heterogeneous networks is a complicated work and
   may require lots of consideration since different model users may
   have different perspective and concerns.

   This document proposes the requirements and architecture for service
   models to facilitate future work.  This document does not attempt to
   provide a detailed description of all the architectural components,
   but rather it describes a set of building blocks, requirements,
   architecture and guidelines from which models may be constructed.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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.

Li, et al.             Expires September 14, 2017               [Page 1]
Internet-Draft   Req & Arch of Carrier IP Service Models      March 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
   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Considerations  . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Generic Scenarios Oriented  . . . . . . . . . . . . . . .   6
     4.2.  Network-Functional Level Abstract . . . . . . . . . . . .   6
     4.3.  Multi-Level Openness Required . . . . . . . . . . . . . .   6
   5.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Base Network Models . . . . . . . . . . . . . . . . . . .   7
       5.1.1.  Topology Model  . . . . . . . . . . . . . . . . . . .   7
       5.1.2.  Inventory Model . . . . . . . . . . . . . . . . . . .   7
       5.1.3.  Resource Model  . . . . . . . . . . . . . . . . . . .   7
     5.2.  Service Models  . . . . . . . . . . . . . . . . . . . . .   7
       5.2.1.  VPN Service Models  . . . . . . . . . . . . . . . . .   8
       5.2.2.  Service Flow Models . . . . . . . . . . . . . . . . .   9
       5.2.3.  Tunnel Service Models . . . . . . . . . . . . . . . .   9
       5.2.4.  IP Flow Service Models  . . . . . . . . . . . . . . .   9
     5.3.  Supporting Models . . . . . . . . . . . . . . . . . . . .   9
       5.3.1.  QoS Profile . . . . . . . . . . . . . . . . . . . . .   9
   6.  Architecture of Network Models  . . . . . . . . . . . . . . .   9
     6.1.  Principles of Architecture  . . . . . . . . . . . . . . .  10
       6.1.1.  Hierarchical Architecture . . . . . . . . . . . . . .  10
Show full document text