Internet Draft Deepak Kumar T. Senevirathne Norman Finn Samer Salam CISCO Liang Xia Weiguo Hao Huawei Category: Standard Track Expires October 2017 March 31, 2017 YANG Data Model for TRILL Operations, Administration, and Maintenance (OAM) draft-ietf-trill-yang-oam-05.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 May 04, 2016. 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 Kumar, Deepak Expires October 2, 2017 [Page 1] Internet Draft TRILL OAM YANG March 31, 2017 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. Abstract This document presents YANG Data model for TRILL OAM. It extends the Generic YANG model for OAM defined in with TRILL technology specifics. Table of Contents. Kumar, Deepak Expires October 2, 2017 [Page 2] Internet Draft TRILL OAM YANG March 31, 2017 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . . 3 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 3. Architecture of OAM YANG Model and Relationship to TRILL OAM . 4 4. TRILL extensions to Generic YANG Model . . . . . . . . . . . . 4 4.1 MEP Address . . . . . . . . . . . . . . . . . . . . . . . . 5 4.2 Flow Entropy . . . . . . . . . . . . . . . . . . . . . . . . 5 4.3 Context-id . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.5 RPC definition . . . . . . . . . . . . . . . . . . . . . . . 5 5. OAM data hierarchy . . . . . . . . . . . . . . . . . . . . . . 6 6. OAM YANG module . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Base Mode for TRILL OAM . . . . . . . . . . . . . . . . . . . . 19 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 10.1. Normative References . . . . . . . . . . . . . . . . . . 20 10.2. Informative References . . . . . . . . . . . . . . . . . 20 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 1. Introduction Fault Management for TRILL is defined in [TRILLOAMFM]. TRILL Fault Management utilizes the [8021Q] CFM model and extends CFM with technology specific details. Those technology specific extensions are flow-entropy for multipath support, MEP addressing on TRILL identifiers, and so on. The extensions are explained in detail in [TRILLOAMFM]. In this document, we extend the YANG model defined in [GENYANGOAM] with TRILL OAM specifics. 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]. In this document, these words will appear with that interpretation only when in ALL CAPS. Lower case uses of these words are not to be interpreted as carrying RFC-2119 significance. 2.1. Terminology CCM - Continuity Check Message [8021Q] ECMP - Equal Cost Multipath LBM - Loopback Message [8021Q] MP - Maintenance Point [8021Q] MEP - Maintenance End Point [RFC7174] [8021Q] [RFC6371] Kumar, Deepak Expires October 2, 2017 [Page 3] Internet Draft TRILL OAM YANG March 31, 2017 MIP - Maintenance Intermediate Point [RFC7174] [8021Q] [RFC6371] MA - Maintenance Association [8021Q] [RFC7174] MD - Maintenance Domain [8021Q] MTV - Multi-destination Tree Verification Message OAM - Operations, Administration, and Maintenance [RFC6291] TRILL - Transparent Interconnection of Lots of Links [RFC6325] 3. Architecture of OAM YANG Model and Relationship to TRILL OAM +-+-+-+-+-+ | CO | |OAM YANG | +-+-+-+-+-+ | O | +--------------------------------------------------+ | | | | +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ | TRILL | | NVO3 | | MPLS-TP | . . .| foo | |OAM YANG | |OAM YANG | |OAM YANG | |OAM YANG | +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ | | | | +----------------------------------------------------+ | Uniform API | +----------------------------------------------------+ Figure 1 Relationship of TRILL OAM YANG model to Generic Connection Oriented OAM YANG model 4. TRILL extensions to Generic YANG Model The Technology parameter is defined in the [GENYANGOAM] as an identity. This allows easy extension of the YANG model by other technologies. Technology-specific extensions are applied only when the Technology parameter is set to the specific type. "trill" is defined as an identity that augments the base "technology-types". identity trill { base goam:technology-types; description "trill type"; } Figure 2 Trill identity type. Kumar, Deepak Expires October 2, 2017 [Page 4] Internet Draft TRILL OAM YANG March 31, 2017 4.1 MEP Address In TRILL, the MEP address is the 2 octet RBridge Nickname. In [GENYANGOAM] MEP address is defined as a combination choice and case statement. We augment this to include TRILL RBridge nickname. augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:mep- address" { case mep-address-trill { leaf mep-address-trill { when "/goam:domains/goam:domain/goam:technology='trill'"; type tril-rb-nickname; } } } Figure 3 Augment MEP address 4.2 Flow Entropy In TRILL, flow-entropy is defined as a 96 octet field. [GENYANGOAM] defines a placeholder for flow-entropy. This allows other technologies to easily augment that to include technology-specific augmentations. Below figure depicts an example of augmenting flow- entropy to include TRILL flow-entropy. augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:flow-entropy" { case flow-entropy-trill { leaf flow-entropy-trill { type flow-entropy-trill; } } } Figure 4 TRILL flow-entropy 4.3 Context-id In TRILL, context-id is either 12 bit VLAN identifier or 24 bit fine- grained label. [GENYANGOAM] 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 TRILL context-id. augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:context-id" { case context-id-vlan { leaf context-id-vlan { type vlan; } } case context-id-fgl { leaf context-id-fgl { type fgl; } } } Figure 5 TRILL context-id 4.5 RPC definition The rpc model facilitates issuing commands to a NETCONF server (in this case to the device that needs to execute the OAM command) and obtaining a response. Grouping statement command-ext-trill defines the input extensions for TRILL. Kumar, Deepak Expires October 2, 2017 [Page 5] Internet Draft TRILL OAM YANG March 31, 2017 Continuity-check (CCM)[RFC7455]], continuity-verification (LBM/LBR)[RFC7455], and traceroute (PTM/PTR)[RFC7455] are defined in Generic Lime Model[GENYANGOAM]. Multicast Tree Verification (MTV) [RFC7455] rpc command, defined in TRILL YANG model, is TRILL specific and allows to verify connectivity as well as data-plane and control-plane integrity of TRILL multicast forwarding. 5. OAM data hierarchy The complete data hierarchy related to the 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 :. 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: ietf-trill-oam augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:mep-address: +--:(mep-address-trill) +--rw mep-address-trill? tril-rb-nickname augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:connectivity-context: +--:(connectivity-context-vlan) | +--rw connectivity-context-vlan? vlan +--:(connectivity-context-fgl) +--rw connectivity-context-fgl? fgl augment /goam:domains/goam:domain/goam:MAs/goam:MA: +--rw flow-entropy-trill? flow-entropy-trill augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP: +--rw flow-entropy-trill? flow-entropy-trill augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:session: Kumar, Deepak Expires October 2, 2017 [Page 6] Internet Draft TRILL OAM YANG March 31, 2017 +--rw flow-entropy-trill? flow-entropy-trill augment /goam:continuity-check/goam:input: +---- (out-of-band)? | +--:(ipv4-address) | | +---- ipv4-address? inet:ipv4-address | +--:(ipv6-address) | | +---- ipv6-address? inet:ipv6-address | +--:(trill-nickname) | +---- trill-nickname? tril-rb-nickname +---- diagnostic-vlan? boolean augment /goam:continuity-check/goam:input: +---- flow-entropy-trill? flow-entropy-trill augment /goam:continuity-check/goam:output: +---- upstream-rbridge? tril-rb-nickname +---- next-hop-rbridge* tril-rb-nickname augment /goam:continuity-verification/goam:input: +---- (out-of-band)? | +--:(ipv4-address) | | +---- ipv4-address? inet:ipv4-address | +--:(ipv6-address) | | +---- ipv6-address? inet:ipv6-address | +--:(trill-nickname) | +---- trill-nickname? tril-rb-nickname +---- diagnostic-vlan? boolean augment /goam:continuity-verification/goam:input: +---- flow-entropy-trill? flow-entropy-trill augment /goam:continuity-verification/goam:output: +--:(monitor-stats-resp) | +---- tx-packt-count? oam-counter32 | +---- rx-packet-count? oam-counter32 | +---- min-delay? oam-counter32 | +---- average-delay? oam-counter32 | +---- max-delay? oam-counter32 +---- upstream-rbridge? tril-rb-nickname +---- next-hop-rbridge* tril-rb-nickname augment /goam:traceroute/goam:input: +---- (out-of-band)? | +--:(ipv4-address) | | +---- ipv4-address? inet:ipv4-address | +--:(ipv6-address) | | +---- ipv6-address? inet:ipv6-address | +--:(trill-nickname) | +---- trill-nickname? tril-rb-nickname +---- diagnostic-vlan? boolean augment /goam:traceroute/goam:input: +---- flow-entropy-trill? flow-entropy-trill augment /goam:traceroute/goam:output/goam:response: +--:(monitor-stats-ext) Kumar, Deepak Expires October 2, 2017 [Page 7] Internet Draft TRILL OAM YANG March 31, 2017 | +---- tx-packt-count? oam-counter32 | +---- rx-packet-count? oam-counter32 | +---- min-delay? oam-counter32 | +---- average-delay? oam-counter32 | +---- max-delay? oam-counter32 +---- upstream-rbridge? tril-rb-nickname +---- next-hop-rbridge* tril-rb-nickname rpcs: +---x mtv +---w input | +---w technology identityref | +---w MD-name-string MD-name-string | +---w MA-name-string? MA-name-string | +---w (out-of-band)? | | +--:(ipv4-address) | | | +---w ipv4-address? inet:ipv4-address | | +--:(ipv6-address) | | | +---w ipv6-address? inet:ipv6-address | | +--:(trill-nickname) | | +---w trill-nickname? tril-rb-nickname | +---w diagnostic-vlan? boolean | +---w (flow-entropy)? | | +--:(flow-entropy-null) | | | +---w flow-entropy-null? empty | | +--:(flow-entropy-trill) | | +---w flow-entropy-trill? flow-entropy-trill | +---w max-hop-count? uint8 | +---w type? identityref | +---w scope* tril-rb-nickname | +---w ecmp-choice? enumeration | +---w outgoing-interfaces* [interface] | | +---w interface if:interface-ref | +---w source-mep | | +---w (mep-address)? | | | +--:(mac-address) | | | | +---w mac-address? yang:mac-address | | | +--:(ipv4-address) | | | | +---w ipv4-address? inet:ipv4-address | | | +--:(ipv6-address) | | | +---w ipv6-address? inet:ipv6-address | | +---w mep-id? tril-rb-nickname | +---w destination-mep | +---w (mep-address)? | | +--:(mac-address) | | | +---w mac-address? yang:mac-address | | +--:(ipv4-address) | | | +---w ipv4-address? inet:ipv4-address | | +--:(ipv6-address) Kumar, Deepak Expires October 2, 2017 [Page 8] Internet Draft TRILL OAM YANG March 31, 2017 | | +---w ipv6-address? inet:ipv6-address | +---w mep-id? tril-rb-nickname +--ro output +--ro response* [mep-address mep-id] +--ro hop-count? uint8 +--ro mep-id tril-rb-nickname +--ro mep-address tril-rb-nickname +--ro next-hop-rbridge* tril-rb-nickname +--ro upstream-rbridge? tril-rb-nickname +--ro multicast-receiver-count? uint32 +--ro tx-packt-count? oam-counter32 +--ro rx-packet-count? oam-counter32 +--ro min-delay? oam-counter32 +--ro average-delay? oam-counter32 +--ro max-delay? oam-counter32 6. OAM YANG module file "ietf-trill-oam.yang" module ietf-trill-oam { namespace "urn:ietf:params:xml:ns:yang:ietf-trill-oam"; prefix trilloam; import ietf-conn-oam { prefix goam; } import ietf-inet-types { prefix inet; } import ietf-interfaces { prefix if; } import ietf-yang-types { prefix yang; } organization "IETF TRILL Working Group"; contact " WG List: mailto:trill@ietf.org Editor: Deepak Kumar dekumar@cisco.com"; description "This YANG module defines the configuration for TRILL, OAM Fault Management statistics and rpc"; revision 2016-07-17 { Kumar, Deepak Expires October 2, 2017 [Page 9] Internet Draft TRILL OAM YANG March 31, 2017 description "Initial revision."; reference "draft-ietf-trill-yang-oam"; } identity trill { base goam:technology-types; description "trill type"; } typedef oam-counter32 { type yang:zero-based-counter32; description "defines 32 bit counter for OAM"; } typedef tril-rb-nickname { type uint16; description "Trill Rbridge Nickname"; } typedef flow-entropy-trill { type binary { length "1..96"; } description "Flow entropy as defined in RFC7455"; } typedef vlan { type uint16 { range "0..4095"; } description "Vlan Identifier."; } typedef fgl { type uint32; description "Fine Grain Label"; } identity trill-mtv { base goam:command-sub-type; description Kumar, Deepak Expires October 2, 2017 [Page 10] Internet Draft TRILL OAM YANG March 31, 2017 "identfies this command as multicast tree verification comand"; } identity trill-ping { base goam:command-sub-type; description "identifies the command as TRILL Loopback Request"; } identity trill-trace-route { base goam:command-sub-type; description "identifies the command as TRILL Pathtrace Request."; } grouping command-ext-trill { description "group the rpc command extensions for trill"; choice out-of-band { case ipv4-address { leaf ipv4-address { type inet:ipv4-address; description "ip version 4 address of the device where out of band reply should be sent."; } } case ipv6-address { leaf ipv6-address { type inet:ipv6-address; description "ip version 6 address of the device where out of band reply should be sent."; } } case trill-nickname { leaf trill-nickname { type tril-rb-nickname; description "TRILL Rbridge Nickname of the device where out of band reply should be sent."; } } description "presence of this node indicate out of band request needed"; } leaf diagnostic-vlan { type boolean; Kumar, Deepak Expires October 2, 2017 [Page 11] Internet Draft TRILL OAM YANG March 31, 2017 description "indicates whether to include diagnostic VLAN/fgl TLV or not in the request. actual value is the VLAN/FGL specified in the command"; } } grouping monitor-stats-trill { leaf tx-packt-count { type oam-counter32; description "Transmitted Packet count"; } leaf rx-packet-count { type oam-counter32; description "Received packet count, zero for one way message (CCM)."; } leaf min-delay { type oam-counter32; units milliseconds; description "Delay is specified in milliseconds, zero for one way message (CCM)."; } leaf average-delay { type oam-counter32; units millisecond; description "average delay in milliseconds, zero for one way message (CCM)."; } leaf max-delay { type oam-counter32; units millisecond; description "Maximum delay in milliseconds, zero for one way message (CCM)."; } description "Monitor Statistics"; } augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:mep-address" { case mep-address-trill { leaf mep-address-trill { when "/goam:domains/goam:domain/goam:technology='trill'" { description Kumar, Deepak Expires October 2, 2017 [Page 12] Internet Draft TRILL OAM YANG March 31, 2017 "Technology TRILL"; } type tril-rb-nickname; description "MEP Address TRILL Rbridge Nickname."; } } description "Extend Generic OAM Maintenance Point Address."; } augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:connectivity-context" { case connectivity-context-vlan { leaf connectivity-context-vlan { type vlan; description "Connectivity context Vlan Identifier."; } } case connectivity-context-fgl { leaf connectivity-context-fgl { type fgl; description "connectivity context Fine Grain Label."; } } description "Extends connectivity context."; } augment "/goam:domains/goam:domain/goam:MAs/goam:MA" { leaf flow-entropy-trill { type flow-entropy-trill; description "connectivity context flow entropy."; } description "Extends Flow Entropy."; } augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP" { leaf flow-entropy-trill { type flow-entropy-trill; description "Flow Entropy TRILL"; } description Kumar, Deepak Expires October 2, 2017 [Page 13] Internet Draft TRILL OAM YANG March 31, 2017 "Extends Flow Entropy defined under Generic OAM MEP."; } augment "/goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP/goam:session" { leaf flow-entropy-trill { type flow-entropy-trill; description "Flow Entropy TRILL"; } description "Extends Flow Entropy defined under Generic OAM Session."; } augment "/goam:continuity-check/goam:input" { uses command-ext-trill; description "Extends continuity check input."; } augment "/goam:continuity-check/goam:input" { leaf flow-entropy-trill { type flow-entropy-trill; description "Flow Entropy TRILL"; } description "Extends continuity check input Flow entropy."; } augment "/goam:continuity-check/goam:output" { description "adds trill specific items on the response"; leaf upstream-rbridge { type tril-rb-nickname; description "Trill Rbridge nickname."; } leaf-list next-hop-rbridge { type tril-rb-nickname; description "nickname of the next hop RBRdige"; } } augment "/goam:continuity-verification/goam:input" { uses command-ext-trill; description "Extends continuity check input."; } augment "/goam:continuity-verification/goam:input" { Kumar, Deepak Expires October 2, 2017 [Page 14] Internet Draft TRILL OAM YANG March 31, 2017 leaf flow-entropy-trill { type flow-entropy-trill; description "Flow Entropy TRILL"; } description "Extends continuity check input Flow entropy."; } augment "/goam:continuity-verification/goam:output" { description "adds trill specific items on the response"; case monitor-stats-resp { uses monitor-stats-trill; } leaf upstream-rbridge { type tril-rb-nickname; description "Trill Rbridge nickname."; } leaf-list next-hop-rbridge { type tril-rb-nickname; description "nickname of the next hop RBRdige"; } } augment "/goam:traceroute/goam:input" { uses command-ext-trill; description "Extends path disovery Input."; } augment "/goam:traceroute/goam:input" { leaf flow-entropy-trill { type flow-entropy-trill; description "Flow entropy TRILL."; } description "Extends path discovery input flow entropy."; } augment "/goam:traceroute/goam:output/goam:response" { description "adds trill specific items on the response"; case monitor-stats-ext { uses monitor-stats-trill; } Kumar, Deepak Expires October 2, 2017 [Page 15] Internet Draft TRILL OAM YANG March 31, 2017 leaf upstream-rbridge { type tril-rb-nickname; description "Upstream Rbridge nickname."; } leaf-list next-hop-rbridge { type tril-rb-nickname; description "nickname of the next hop RBRdige"; } } rpc mtv { description "Generates Trace-route and return response. Starts with TTL of one and increment by one at each hop. Untill destination reached or TTL reach max valune"; input { uses goam:maintenance-domain-id { description "Specifies the MA-domain"; } uses goam:ma-identifier { description "identfies the Maintenance association"; } uses command-ext-trill { description "defines extensions needed for trill. We are using this structure so mtv command is in line with ping and trace-route"; } choice flow-entropy { case flow-entropy-null { leaf flow-entropy-null { type empty; description "Empty flow entropy"; } } case flow-entropy-trill { leaf flow-entropy-trill { type flow-entropy-trill; description "Flow Entroy TRILL"; } } Kumar, Deepak Expires October 2, 2017 [Page 16] Internet Draft TRILL OAM YANG March 31, 2017 description "Flow Entropy choices."; } leaf max-hop-count { type uint8; default "255"; description "Defines maximum value of hop count"; } leaf type { type identityref { base goam:command-sub-type; } description "defines different command types"; } leaf-list scope { type tril-rb-nickname; description "This list contain rbridges that needed to respond Empty list indicate all Rbridges needed to respond"; reference "RFC7455"; } leaf ecmp-choice { type enumeration { enum "ecmp-use-platform-hash" { value 0; description "Use Platform hashing to send packet on specified interface."; } enum "ecmp-use-round-robin" { value 1; description "Use round robin hashing."; } } description "Ecmp Choice enumeration."; } list outgoing-interfaces { key "interface"; leaf interface { Kumar, Deepak Expires October 2, 2017 [Page 17] Internet Draft TRILL OAM YANG March 31, 2017 type if:interface-ref; description "Interface"; } description "List of Outgoing Interface."; } container source-mep { uses goam:mep-address; description "Source MEP Container."; leaf mep-id { type tril-rb-nickname; description "Trill Rbridge Nickname"; } } container destination-mep { uses goam:mep-address; leaf mep-id { type tril-rb-nickname; description "MEP Identifier."; } description "Destination MEP Identifier."; } } output { list response { key "mep-address mep-id"; leaf hop-count { type uint8; description "unsigned integer 1-255"; } leaf mep-id { type tril-rb-nickname; description "Maintenance Endpoint Identifier."; } leaf mep-address { type tril-rb-nickname; description "Maintenance Endpoint Address."; } leaf-list next-hop-rbridge { type tril-rb-nickname; Kumar, Deepak Expires October 2, 2017 [Page 18] Internet Draft TRILL OAM YANG March 31, 2017 description "list of downstream rbridges. There is no perticular order"; } leaf upstream-rbridge { type tril-rb-nickname; description "Upstream Rbridge Nickname."; } leaf multicast-receiver-count { type uint32; description "number of ports that are interested in this multicast stream"; } uses monitor-stats-trill; description "Output list."; } } } } 7. Base Mode for TRILL OAM The Base Mode defines default configuration that MUST be present in the devices that comply with this document. Base Mode allows users to have a zero-touch experience. Details of TRILL Base Mode for OAM are defined in RFC7455 Appendix B. 8. Security Considerations There are no security considerations relevant to this document. 9. IANA Considerations This document registers the following namespace URI in the IETF XML registry. URI:urn:ietf:params:xml:ns:yang:ietf-trill-oam Kumar, Deepak Expires October 2, 2017 [Page 19] Internet Draft TRILL OAM YANG March 31, 2017 10. References 10.1. Normative References [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. [RFC7174] Salam, S., et.al., "Transparent Interconnect of Lots of Links (TRILL) OAM Framework", May, 2014. [RFC7455] Senevirathne, T., et.al, "Transparent Interconnect of Lots of Links(TRILL): Fault Management", March, 2015 10.2. Informative References [RFC7174] TRILL OAM Framework [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. [RFC6325] Perlman, R., et.al., "Routing Bridges (RBridges): Base Protocol Specification", RFC 6325, July 2011. [GENYANGOAM] Senevirathne, T., et.al., "YANG Data Model for Operations, Administration and Maintenance (OAM)", Work in Progress, March, 2014. 11. Acknowledgments Giles Heron came up with the idea of developing a YANG model as a way of creating a unified OAM API set (interface), work in this document is largely an inspiration of that. Alexander Clemm provided many valuable tips, comments and remarks that helped to refine the YANG model presented in this document. Kumar, Deepak Expires October 2, 2017 [Page 20] Internet Draft TRILL OAM YANG March 31, 2017 Authors' Addresses Authors' Addresses Tissa Senevirathne CISCO Systems 375 East Tasman Drive. San Jose, CA 95134 USA. Phone: 408-853-2291 Email: tsenevir@cisco.com Norman Finn CISCO Systems 510 McCarthy Blvd Milpitas, CA 95035. Email: nfinn@cisco.com Deepak Kumar CISCO Systems 510 McCarthy Blvd Milpitas, CA 95035. Email: dekumar@cisco.com Samer Salam CISCO Systems 595 Burrard St. Suite 2123 Vancouver, BC V7X 1J1, Canada Email: ssalam@cisco.com Liang Xia Huawei technologies Email: frank.xialiang@huawei.com Weiguo Hao Huawei Technologies 101 Software Avenue Nanjing 210012, China Email: haoweiguo@huawei.com Kumar, Deepak Expires October 2, 2017 [Page 21]