SFC Netmod Liang Xia Internet Draft Qin Wu Intended status: Informational Huawei Expires: April 2015 October 25, 2014 YANG Data Model for SFC Operations, Administration, and Maintenance (OAM) draft-xia-sfc-yang-oam-00.txt 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), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on April 25, 2009. 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 to this document. Code Components extracted from this document must include Simplified BSD License text as described in Xia & Wu Expires April 23, 2015 [Page 1] Internet-Draft SFC OAM YANG Model October 2014 Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Abstract This draft defines YANG data model for SFC OAM. It extends from the basic YANG data model for Layer independent OAM Management defined in [I-D.tissa-lime-yang-oam-model] and [I-D.wang-lime-rpc-yang-oam- management] with SFC technology specifics. It includes SFC OAM related configuration, state, and RPC information data. Table of Contents 1. Introduction ................................................ 2 2. Conventions used in this document ........................... 3 2.1. Terminology ............................................ 3 3. SFC Extensions to LIME YANG Model ........................... 4 3.1. MEP Address ............................................ 4 3.2. Context-id ............................................. 6 3.3. SFC Layer For RPC - Path Discovery ..................... 7 4. SFC OAM YANG Data Hierarchy ................................. 8 5. SFC OAM YANG Module ........................................ 16 6. Security Considerations .................................... 37 7. IANA Considerations ........................................ 37 8. References ................................................. 37 8.1. Normative References .................................. 37 8.2. Informative References ................................ 37 9. Acknowledgments ............................................ 38 1. Introduction YANG [RFC6020] is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF) [RFC6241], NETCONF remote procedure calls (RPC), and NETCONF notifications. This draft defines the YANG data model for Service Function Chaining (SFC) [SFCPS] OAM. The SFC OAM YANG module involves the OAM configuration, RPCs and notifications, etc. Currently, [I-D.tissa-lime-yang-oam-model] and [I-D.wang-lime-rpc- yang-oam-management] propose a basic YANG data model for Layer independent OAM Management that can be applied to various network technologies. So, SFC OAM YANG data model can directly extend them with SFC technology specifics. It can bring some obvious benefits Xia & Wu Expires April 25, 2015 [Page 2] Internet-Draft SFC OAM YANG Model October 2014 such as unified format, reusable parts, and correlation of defects, faults, network failure at different layers. By referring to the SFC technology specific YANG data model for various SFC components defined in [SFCYANG], this draft defines the SFC OAM YANG data model as an augmentation to the basic YANG model defined in [I-D.tissa-lime-yang-oam-model] and [I-D.wang-lime-rpc- yang-oam-management]. Note that SFC OAM mechanisms are not yet defined or standardized although some of the basic concepts and functions (e.g., fault detection, fault localization, performance measurement, etc) may be similar to traditional OAM mechanisms. This draft should get alignment with the latest development SFC OAM mechanisms. 2. Conventions used in this document 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]. The following terms are defined in [RFC6241] and are not redefined here: o client o configuration data o server o state data The following terms are defined in [RFC6020] and are not redefined here: o augment o data model o data node The terminology for describing YANG data models is found in [RFC6020]. 2.1. Terminology MP - Maintenance Point [8021Q] Xia & Wu Expires April 25, 2015 [Page 3] Internet-Draft SFC OAM YANG Model October 2014 MEP - Maintenance End Point [8021Q] [RFC6371] MIP - Maintenance Intermediate Point [8021Q] [RFC6371] MEG - Maintenance Entity Group [Y1731] [RFC6371] ME - Maintenance Entity [Y.1731] [RFC6371] MD - Maintenance Domain [8021Q] OAM - Operations, Administration, and Maintenance [RFC6291] LIME - Layer Independent OAM Management [I-D.tissa-lime-yang-oam- model] [I-D.wang-lime-rpc-yang-oam-management] SF - Service Function [SFCYANG] SFC - Service Function Chaining [SFCYANG] SFF - Service Function Forwarder [SFCYANG] 3. SFC Extensions to LIME YANG Model A new Technology parameter of SFC is defined here for the purpose of identifying the SFC specific YANG model extension: identity SFC { base goam:technology-types; description "SFC type"; } Figure 1 SFC identity type Only when the Technology parameter is set to the "SFC" value, the SFC specific extensions are applied. 3.1. MEP Address In SFC, either the SF on service function layer or SF/SFF on SFC forwarding layer can be MEP/MIP. A MEP/MIP cannot be identified without specifying service function path. Therefore the MEP/MIP address can only be identified by SF/SFF address plus service Xia & Wu Expires April 25, 2015 [Page 4] Internet-Draft SFC OAM YANG Model October 2014 function path id. In [I-D.tissa-lime-yang-oam-model] and [I-D.wang- lime-rpc-yang-oam-management], MEP/MIP address is defined using a combination of choice and case statement. We augment this to include SFC specific SF/SFF address plus service function path id. augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:mep- address" { case sf-mep-ref { description "Service function (or service function forwarder) address plus service function path id to identify one SFC MEP. A SFC MP can be a service function or service function forwarder!" leaf sf-mep-ref { when "/goam:domains/goam:domain/goam:technology='sfc'"; type sfc-sf:service-function-ref; } leaf sfp-mep-ref { when "/goam:domains/goam:domain/goam:technology='sfc'"; type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { description "Service function address plus service function path id identify one SFC MEP. A SFC MP can be a service function or service function forwarder!" leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; Xia & Wu Expires April 25, 2015 [Page 5] Internet-Draft SFC OAM YANG Model October 2014 } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } Figure 2 Augment SFC MEP address 3.2. Context-id In SFC, context-id is the service function path id. [I-D.tissa-lime- yang-oam-model] and [I-D.wang-lime-rpc-yang-oam-management] defines a placeholder for context-id. This allows other technologies to easily augment that to include technology specific extensions. The snippet below depicts an example of augmenting context-id to include the SFC context-id. augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:context- id" { case context-id-sfc { leaf context-id-sfp { type sfc-sfp:service-function-path-ref; } } } Figure 3 Augment SFC Context-id Xia & Wu Expires April 25, 2015 [Page 6] Internet-Draft SFC OAM YANG Model October 2014 3.3. SFC Layer For RPC - Path Discovery Path discovery is used to discover the path that specific service traverses in the network. For SFC, it can be used on both service function layer and SFC forwarding layer depending on what is the desired degree of path information. typedef SFC-layer { type enumeration { enum "Service function layer" { value 0; } enum "SFC forwarding layer" { value 1; } } } augment "/goam:path-discovery/goam:input" { description "adds SFC specific items on the input"; leaf path-discovery-layer { type SFC-layer; description "Identifying which SFC layer to run path discovery"; Xia & Wu Expires April 25, 2015 [Page 7] Internet-Draft SFC OAM YANG Model October 2014 } } Figure 4 Augment SFC SFC-layer for path discovery 4. SFC OAM YANG Data Hierarchy The complete data hierarchy related to the SFC OAM YANG model is presented below. The following notations are used within the data tree and carry the meaning as noted below. Each node is printed as: is one of: + for current x for deprecated o for obsolete is one of: rw for configuration data ro for non-configuration data -x for rpcs -n for notifications is the name of the node If the node is augmented into the tree from another module, its name is printed as :. Xia & Wu Expires April 25, 2015 [Page 8] Internet-Draft SFC OAM YANG Model October 2014 is one of: ? for an optional leaf or choice ! for a presence container * for a leaf-list or list [] for a list's keys is the name of the type for leafs and leaf-lists module: sfc-oam augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:context-id: +--:(context-id-sfc) +--rw context-id-sfp? sfc-sfp:service-function-path-ref augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:mep-address: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:session/goa m:destination-mep-address: +--:(sf-mep-ref) Xia & Wu Expires April 25, 2015 [Page 9] Internet-Draft SFC OAM YANG Model October 2014 | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:session/goa m:context-id: +--:(context-id-sfc) +--rw context-id-sfp? sfc-sfp:service-function-path-ref augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:remote- MEP/goam:mep-address: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:contiuity-check/goam:input/goam:context-id: +--:(context-id-sfc) +--rw context-id-sfp? sfc-sfp:service-function-path-ref augment /goam:contiuity-check/goam:input/goam:source-mep/goam:mep- addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref Xia & Wu Expires April 25, 2015 [Page 10] Internet-Draft SFC OAM YANG Model October 2014 +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:contiuity-check/goam:input/goam:destination-mep/goam: mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:contiuity-check/goam:output/goam:source-mep/goam:mep- addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:contiuity-check/goam:output/goam:destination-mep/goam: mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) Xia & Wu Expires April 25, 2015 [Page 11] Internet-Draft SFC OAM YANG Model October 2014 | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:contiuity-verification/goam:input/goam:context-id: +--:(context-id-sfc) +--rw context-id-sfp? sfc-sfp:service-function-path-ref augment /goam:connectity-verification/goam:input/goam:source- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:connectity-verification/goam:input/goam:destination- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:connectity-verification/goam:output/goam:source- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref Xia & Wu Expires April 25, 2015 [Page 12] Internet-Draft SFC OAM YANG Model October 2014 | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:connectity-verification/goam:output/goam:destination- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:path-discovery/goam:input/goam:context-id: +--:(context-id-sfc) +--rw context-id-sfp? sfc-sfp:service-function-path-ref augment /goam:path-discovery/goam:input/goam:source-mep/goam:mep- addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:path-discovery/goam:input/goam:destination- mep/goam:mep-addr: Xia & Wu Expires April 25, 2015 [Page 13] Internet-Draft SFC OAM YANG Model October 2014 +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:path-discovery/goam:output/goam:source-mep/goam:mep- addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:path-discovery/goam:output/goam:destination- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:path-discovery/goam:input: +--ro:path-discovery-layer SFC-layer augment /goam:performance-measurement/goam:input/goam:context-id: Xia & Wu Expires April 25, 2015 [Page 14] Internet-Draft SFC OAM YANG Model October 2014 +--:(context-id-sfc) +--rw context-id-sfp? sfc-sfp:service-function-path-ref augment /goam:performance-measurement/goam:input/goam:source- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:performance-measurement/goam:input/goam:destination- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:performance-measurement/goam:output/goam:source- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref Xia & Wu Expires April 25, 2015 [Page 15] Internet-Draft SFC OAM YANG Model October 2014 +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref augment /goam:performance-measurement/goam:output/goam:destination- mep/goam:mep-addr: +--:(sf-mep-ref) | +--rw sf-mep-ref sfc-sf:service-function-ref | +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref +--:(sff-mep-ref) | +--rw sff-mep-ref sfc-sff:service-function-forwarder-ref +--rw sfp-mep-ref? sfc-sfp:service-function-path-ref Figure 5 Data hierarchy of SFC OAM 5. SFC OAM YANG Module file "xxx.yang" module trill-oam { namespace "urn:huawei:params:xml:ns:yang:sfc-oam"; prefix sfcoam; import ietf-management-oam { prefix goam; } import ietf-inet-types { prefix inet; } import ietf-interfaces { prefix if; Xia & Wu Expires April 25, 2015 [Page 16] Internet-Draft SFC OAM YANG Model October 2014 } import service-function { prefix sfc-sf; } import service-function-path { prefix sfc-sfp; } import service-function-forwarder { prefix sfc-sff; } revision 2014-09-04 { description "Initial revision."; } identity sfc { base goam:technology-types; description "sfc type"; } typedef SFC-layer { type enumeration { Xia & Wu Expires April 25, 2015 [Page 17] Internet-Draft SFC OAM YANG Model October 2014 enum "Service function layer" { value 0; } enum "SFC forwarding layer" { value 1; } } } augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:context-id" { case context-id-sfc { leaf context-id-sfp { type sfc-sfp:service-function-path-ref; } } } augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:mep- address" { case sf-mep-ref { description Xia & Wu Expires April 25, 2015 [Page 18] Internet-Draft SFC OAM YANG Model October 2014 "Service function (or service function forwarder) address plus service function path id identify one SFC MEP. A SFC MP can be a service function or service function forwarder!" leaf sf-mep-ref { when "/goam:domains/goam:domain/goam:technology='sfc'"; type sfc-sf:service-function-ref; } leaf sfp-mep-ref { when "/goam:domains/goam:domain/goam:technology='sfc'"; type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { description "Service function address plus service function path id identify one SFC MEP. A SFC MP can be a service function or service function forwarder!" leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } Xia & Wu Expires April 25, 2015 [Page 19] Internet-Draft SFC OAM YANG Model October 2014 augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:session/go am:destination-mep-address" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:session/go am:context-id" { case context-id-sfc { leaf context-id-sfp { Xia & Wu Expires April 25, 2015 [Page 20] Internet-Draft SFC OAM YANG Model October 2014 type sfc-sfp:service-function-path-ref; } } } augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:remote- MEP/goam:mep-address" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } Xia & Wu Expires April 25, 2015 [Page 21] Internet-Draft SFC OAM YANG Model October 2014 //SFC extension of contiuity-check part augment "/goam:contiuity-check/goam:input/goam:context-id" { case context-id-sfc { leaf context-id-sfp { type sfc-sfp:service-function-path-ref; } } } augment "/goam:contiuity-check/goam:input/goam:source-mep/goam: mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; Xia & Wu Expires April 25, 2015 [Page 22] Internet-Draft SFC OAM YANG Model October 2014 } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:contiuity-check/goam:input/goam:destination-mep/goam: mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } Xia & Wu Expires April 25, 2015 [Page 23] Internet-Draft SFC OAM YANG Model October 2014 } augment "/goam:contiuity-check/goam:output/goam:source-mep/goam: mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:contiuity-check/goam:output/goam:destination- mep/goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { Xia & Wu Expires April 25, 2015 [Page 24] Internet-Draft SFC OAM YANG Model October 2014 type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } //SFC extension of connectity-verification part augment "/goam:contiuity-verification/goam:input/goam:context-id" { case context-id-sfc { leaf context-id-sfp { type sfc-sfp:service-function-path-ref; } } Xia & Wu Expires April 25, 2015 [Page 25] Internet-Draft SFC OAM YANG Model October 2014 } augment "/goam:connectity-verification/goam:input/goam:source- mep/goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:connectity-verification/goam:input/goam:destination- mep /goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { Xia & Wu Expires April 25, 2015 [Page 26] Internet-Draft SFC OAM YANG Model October 2014 type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:connectity-verification/goam:output/goam:source- mep/goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } Xia & Wu Expires April 25, 2015 [Page 27] Internet-Draft SFC OAM YANG Model October 2014 } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:connectity- verification/goam:output/goam:destination-mep/goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } Xia & Wu Expires April 25, 2015 [Page 28] Internet-Draft SFC OAM YANG Model October 2014 leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } //SFC extension of path-discovery part augment "/goam:path-discovery/goam:input/goam:context-id" { case context-id-sfc { leaf context-id-sfp { type sfc-sfp:service-function-path-ref; } } } augment "/goam:path-discovery/goam:input/goam:source-mep/goam:mep- addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } Xia & Wu Expires April 25, 2015 [Page 29] Internet-Draft SFC OAM YANG Model October 2014 } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:path-discovery/goam:input/goam:destination-mep/goam: mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } Xia & Wu Expires April 25, 2015 [Page 30] Internet-Draft SFC OAM YANG Model October 2014 leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:path-discovery/goam:output/goam:source-mep/goam:mep- addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } Xia & Wu Expires April 25, 2015 [Page 31] Internet-Draft SFC OAM YANG Model October 2014 } augment "/goam:path-discovery/goam:output/goam:destination-mep/goam: mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:path-discovery/goam:input" { description "adds SFC specific items on the input"; Xia & Wu Expires April 25, 2015 [Page 32] Internet-Draft SFC OAM YANG Model October 2014 leaf path-discovery-layer { type SFC-layer; description "Identifying which SFC layer to run path discovery"; } } //SFC extension of performance-measurement part augment "/goam:performance-measurement/goam:input/goam:context-id" { case context-id-sfc { leaf context-id-sfp { type sfc-sfp:service-function-path-ref; } } } augment "/goam:performance-measurement/goam:input/goam:source- mep/goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } Xia & Wu Expires April 25, 2015 [Page 33] Internet-Draft SFC OAM YANG Model October 2014 leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:performance-measurement/goam:input/goam:destination- mep/goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { Xia & Wu Expires April 25, 2015 [Page 34] Internet-Draft SFC OAM YANG Model October 2014 leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } augment "/goam:performance-measurement/goam:output/goam:source- mep/goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { Xia & Wu Expires April 25, 2015 [Page 35] Internet-Draft SFC OAM YANG Model October 2014 type sfc-sfp:service-function-path-ref; } } } augment "/goam:performance- measurement/goam:output/goam:destination-mep/goam:mep-addr" { case sf-mep-ref { leaf sf-mep-ref { type sfc-sf:service-function-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } case sff-mep-ref { leaf sff-mep-ref { type sfc-sff:service-function-forwarder-ref; } leaf sfp-mep-ref { type sfc-sfp:service-function-path-ref; } } } Xia & Wu Expires April 25, 2015 [Page 36] Internet-Draft SFC OAM YANG Model October 2014 Figure 6 YANG module of SFC OAM 6. Security Considerations TBD 7. IANA Considerations This document registers the following namespace URI in the IETF XML registry. URI:TBD 8. References 8.1. Normative References [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [2] Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, Internet Mail Consortium and Demon Internet Ltd., November 1997. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2234] Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, Internet Mail Consortium and Demon Internet Ltd., November 1997. [8021Q] IEEE, "Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks", IEEE Std 802.1Q-2011, August, 2011. 8.2. Informative References [Y1731] ITU, "OAM functions and mechanisms for Ethernet based networks", ITU-T G.8013/Y.1731, July, 2011 [RFC6291] Andersson, L., et.al., "Guidelines for the use of the "OAM" Acronym in the IETF" RFC 6291, June 2011. Xia & Wu Expires April 25, 2015 [Page 37] Internet-Draft SFC OAM YANG Model October 2014 [I-D.tissa-lime-yang-oam-model] Senevirathne , T. and Q. Wu, "YANG Data Model for Generic Operations, Administration, and Maintenance (OAM)", Work in Progress, October 2014. [I-D.wang-lime-rpc-yang-oam-management] Wang, Z., " Additional RPC definitions to Generic YANG Data Model for layer Independent OAM Management ", Work in Progress, October, 2014. [SFCYANG] Penno, R., et.al., "Yang Data Model for Service Function Chaining", Work in Progress, September, 2014. 9. Acknowledgments This document was prepared using 2-Word-v2.0.template.dot. Authors' Addresses Liang Xia Huawei Email: Frank.xialiang@huawei.com Qin Wu Huawei Email: Bill.wu@huawei.com Xia & Wu Expires April 25, 2015 [Page 38]