Traffic Engineering (TE) and Service Mapping Yang Model
draft-ietf-teas-te-service-mapping-yang-02

Document Type Active Internet-Draft (teas WG)
Last updated 2019-09-09
Replaces draft-lee-teas-te-service-mapping-yang
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Yang Validation 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-l1csm-te-service-mapping@2019-09-09.yang
- Yang catalog entry for ietf-l2sm-te-service-mapping@2019-09-09.yang
- Yang catalog entry for ietf-l3sm-te-service-mapping@2019-09-09.yang
- Yang catalog entry for ietf-te-service-mapping-types@2019-09-09.yang
- Yang impact analysis for draft-ietf-teas-te-service-mapping-yang
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TEAS Working Group                                           Y. Lee, Ed.
Internet-Draft                                                      SKKU
Intended status: Standards Track                           D. Dhody, Ed.
Expires: March 12, 2020                                      G. Fioccola
                                                              Q. Wu, Ed.
                                                     Huawei Technologies
                                                           D. Ceccarelli
                                                                Ericsson
                                                             J. Tantsura
                                                                  Apstra
                                                       September 9, 2019

        Traffic Engineering (TE) and Service Mapping Yang Model
               draft-ietf-teas-te-service-mapping-yang-02

Abstract

   This document provides a YANG data model to map customer service
   models (e.g., the L3VPN Service Model (L3SM)) to Traffic Engineering
   (TE) models (e.g., the TE Tunnel or the Virtual Network (VN) model).
   This model is referred to as TE Service Mapping Model and is
   applicable generically to the operator's need for seamless control
   and management of their VPN services with TE tunnel support.

   The model is principally used to allow monitoring and diagnostics of
   the management systems to show how the service requests are mapped
   onto underlying network resource and TE 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 https://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 March 12, 2020.

Lee, et al.              Expires March 12, 2020                 [Page 1]
Internet-Draft             TE Service Mapping             September 2019

Copyright Notice

   Copyright (c) 2019 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
   (https://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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Tree diagram  . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Prefixes in Data Node Names . . . . . . . . . . . . . . .   4
   2.  TE and Service Related Parameters . . . . . . . . . . . . . .   5
     2.1.  VN/Tunnel Selection Requirements  . . . . . . . . . . . .   5
     2.2.  Availability Requirement  . . . . . . . . . . . . . . . .   6
   3.  YANG Modeling Approach  . . . . . . . . . . . . . . . . . . .   7
     3.1.  Forward Compatibility . . . . . . . . . . . . . . . . . .   8
   4.  L3VPN Architecture in the ACTN Context  . . . . . . . . . . .   8
     4.1.  Service Mapping . . . . . . . . . . . . . . . . . . . . .  11
     4.2.  Site Mapping  . . . . . . . . . . . . . . . . . . . . . .  11
   5.  Applicability of TE-Service Mapping in Generic context  . . .  12
   6.  YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  L3SM  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     6.2.  L2SM  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.3.  L1CSM . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  YANG Data Models  . . . . . . . . . . . . . . . . . . . . . .  15
     7.1.  ietf-te-service-mapping-types . . . . . . . . . . . . . .  15
     7.2.  ietf-l3sm-te-service-mapping  . . . . . . . . . . . . . .  21
     7.3.  ietf-l2sm-te-service-mapping  . . . . . . . . . . . . . .  23
     7.4.  ietf-l1csm-te-service-mapping . . . . . . . . . . . . . .  25
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  27
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  28
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  29
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  29
Show full document text