Network Working Group Bharat M Gaonkar Internet Draft Praveen Ananthasankaran Intended status: Experimental Sudhin Jacob Expires: January 2017 Juniper Networks Giuseppe Fioccola Telecom Italia July 5,2016 Yang Data Model for Loss Measurement draft-jacpra-lime-yang-ais-01 Abstract This document presents a YANG Data model for Alarm Indication Signal. The YANG Model presented in this document extends the generic YANG Data Model for AIS to support OAM fault management. 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 December 2, 2016. Copyright Notice Copyright (c) 2016 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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions and Terminology . . . . . . . . . . . . . . . 5 2.1.Terminology . . . . . . . . . . . . . . . . . . . . . . .5 3.YANG Extension . . . . . . . . . . . . . . . . . . . . . ..6 4.IANA Considerations . . . . . . . . . . . . . . . . . . . .6 5.Security Considerations . . . . . . . . . . . . . . . . . .6 6. References . . . . . . . . . . . . . . . . . . . . 7 6.1. Normative References . . . . . . . . . . . . . . 7 Appendix A. Appendix......................................8 Authors' Addresses ........................................8 1. Introduction Generic OAM Yang model [GENYANGGOAM] presents Generic Yang data model for all OAM technologies.In this document we extend the YANG model defined in [GENYANGGOAM] with AIS alarm indication singal.Details are provided in section 4 below. 2. Conventions and Terminology 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 [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 The terminology for describing YANG data models is found in [RFC6020]. 2.1. Terminology MP - Maintenance Point [8021.Q] MEP - Maintenance End Point [RFC7174] [8021Q] [RFC6371] MIP - Maintenance Intermediate Point [RFC7174] [8021.Q] [RFC6371] MA - Maintenance Association [8021.Q] [RFC7174] MD - Maintenance Domain [8021.Q] OAM - Operations, Administration, and Maintenance [RFC6291] 3.1. MEP Configuration Extension 3.1.1. AIS Configuration This section describes a set of data definitions ais configuration. This set of data defintions augment the MEP configuration defined in the Generic YANG OAM model with parameters related to AIS and define the role of MEP and measurement method of the AIS. module: ietf-gen-oam-ais augment /goam:domains/goam:domain/goam:MAs/goam:MA/goam:MEP: +--rw oam-ais boolean +--rw interval int8 +--rw priority int8 +--rw client-meg-level int8 +--rw drop-eligible Boolean +--ro transmit-status boolean +--ro receive-status boolean +--ro transmit-counter yang:counter32 +--ro receive-counter yang:counter32 +--ro last-received-mac-address yang:mac-address +--ro ma-name yang:ma-name +--ro md-name yang:md-name +--ro hostname yang:hostname +--ro fault-type int8 +--ro mep-id uint16 file "ietf-gen-oam-ais.yang" module ietf-gen-oam-ais { namespace "urn:ietf:params:xml:ns:yang:ietf-gen-oam-ais"; prefix goamais; import ietf-gen-oam { prefix goam; } import ietf-yang-types { prefix yang; } organization "IETF LIME (Layer Independent OAM Management in Multi-Layer Environment) Working Group"; contact "sudhin jacob sjacob@juniper.net."; description "This YANG module defines generic ais Expires December 25, 2016."; revision 2016-06-25 { description "Initial revision."; reference "draft-jacpra-lime-yang-ais"; } container oam-ais { description "This set of data definitions covers the proactive OAM Fault Management Alarm Indication Signal function. leaf enabled { type boolean; default false; description "This attribute specifies whether transmission is enabled. The value 'true' indicates AIS transmission is enabled. The value 'false' indicates AIS transmission is disabled."; leaf interval { type int8; default one-second; description "This attribute specifies the AIS transmission period 1s or 1m"; } leaf priority { type int8; description "This attribute specifies the priority of frames with AIS information. If AIS is supported, the default value for the CoS for AIS frame MUST be the value which yields the lowest frame loss performance for this EVC."; } leaf client-meg-level { type int8; default 0; description "The MEG/Maintenance Domain Level of the Client AIS PDU (transmitted level)."; } leaf drop-eligible { type boolean; default false; description "This attribute specifies the eligibility of frames with ETH-AIS information to be discarded when congestion conditions are encountered.The value 'true' indicates frames are eligible to be discarded.The value 'false' indicates frames are not eligible to be discarded. This attribute may be constrained to read-only in some implementations"; leaf transmit-status { type boolean; config false; description "This attribute specifies the current AIS transmission status of the MEP.The value 'true' indicates AIS frames are currently being transmitted by the MEP.The value 'false' indicates AIS frames are not currently being transmitted by the MEP."; } leaf receive-status { type boolean; config false; description "This attribute specifies the current AIS receive status of the MEP. The value 'true' indicates an AIS PDU has been received and 3.5 times the interval defined in the PDU has not yet passed, otherwise it is 'false'."; } leaf transmit-counter { type yang:zero-based-counter32; config false; description "This attribute contains the count of the total number of AIS messages sent by the MEP. The count is incremented every time an AIS PDU is transmitted by the MEP."; } leaf receive-counter { type yang:counter32; config false; description "This attribute contains the count of the total number of AIS messages received by the MEP. The count is incremented every time an AIS PDU is received by the MEP."; } leaf last-received-mac-address { type yang:mac-address; config false; description "The source MAC Address Field of last AIS received by the MEP. If no AIS PDU has been received by the NE the MAC address is set to all zeros."; } leaf ma-name { type yang:ma-name; config false; description "The ma name where the fault is detected"; } leaf md-name { type yang:md-name; config false; description "The md name where the fault is detected."; } leaf hostname { type yang:hostname; config false; description "The hostname of the device where fault is detected."; } leaf fault-type { type int8; config false; description "The type of fault the value 1 means adjacency loss 2 means errored ccm 3 means cross connect ccm"; } leaf mep-id { type uint16; config false; description "The mep id of the device where the fault was detected "; } } } 4.0 Security Considerations NA 5.0 IANA Considerations NA 6.0 References 6.1. Normative References [GENYANGGOAM] Senevirathne , T. and Q. Wu, "Generic YANG Data Model for Operations, Administration, and Maintenance (OAM)", ID https://tools.ietf.org/pdf/draft-ietf-lime-yang-oam-model-05.pdf [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119,DOI 10.17487/RFC2119, March 1997, . 8.2. Informative References [IEEE802.1Q] "Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks", IEEE Std 802.1Q-2011, August 2011. Appendix A. Appendix Authors' Addresses Sudhin Jacob Juniper Networks Bangalore Email: sjacob@juniper.net Praveen Ananthasankaran Juniper Networks Bangalore Email: panantha@juniper.net Bharat M Gaonkar Juniper Networks Bangalore Email: gbharat@juniper.net Giuseppe Fioccola Telecom Italia giuseppe.fioccola@telecomitalia.it