--- 1/draft-ietf-bfd-mpls-mib-05.txt 2015-04-24 01:14:55.585504058 -0700 +++ 2/draft-ietf-bfd-mpls-mib-06.txt 2015-04-24 01:14:55.633505234 -0700 @@ -1,26 +1,26 @@ Network Working Group INTERNET-DRAFT Sam Aldrin -Intended Status: Standards Track Huawei Technologies -Expires: July 01, 2015 M.Venkatesan - Dell Inc. +Intended Status: Standards Track Google, Inc. +Expires: October 26, 2015 M.Venkatesan + Dell, Inc. Kannan KV Sampath Redeem Software Thomas D. Nadeau Brocade - December 28, 2014 + April 24, 2015 BFD Management Information Base (MIB) extensions for MPLS and MPLS-TP Networks - draft-ietf-bfd-mpls-mib-05 + draft-ietf-bfd-mpls-mib-06 Abstract This draft defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it extends the BFD Management Information Base and describes the managed objects for modeling Bidirectional Forwarding Detection (BFD) protocol for MPLS and MPLS-TP networks. Status of this Memo @@ -37,25 +37,25 @@ 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 July 01, 2015. + This Internet-Draft will expire on October 26, 2015. Copyright Notice - Copyright (c) 2014 IETF Trust and the persons identified as the + Copyright (c) 2015 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 @@ -63,21 +63,21 @@ Table of Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1 Conventions used in this document . . . . . . . . . . . . . 3 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 - 5.1. Extensions to the BFD session table (bfdSessionTable) . . . 4 + 5.1. Extensions to the BFD session table (bfdSessTable) . . . . 4 5.2. Example of BFD session configuration . . . . . . . . . . . 6 5.2.1 Example of BFD Session configuration for MPLS TE tunnel . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.2.2 Example of BFD Session configuration for ME of MPLS-TP TE tunnel . . . . . . . . . . . . . . . . . . . . . . . 7 5.3. BFD objects for session performance counters . . . . . . . 9 6. BFD-EXT-STD-MIB Module Definition . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 18 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 20 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 @@ -123,23 +123,23 @@ 3.1 Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119]. 3.2 Terminology This document adopts the definitions, acronyms and mechanisms - described in [BFD], [BFD-1HOP], [BFD-MH], [RFC5884], [RFC6428]. - Unless otherwise stated, the mechanisms described therein will not be - re-described here. + described in [RFC5880], [RFC5881], [RFC5883], [RFC7130], [RFC5884], + and [RFC6428]. Unless otherwise stated, the mechanisms described + therein will not be re-described here. 4. Acronyms BFD: Bidirectional Forwarding Detection CC: Continuity Check CV: Connectivity Verification IP: Internet Protocol LDP: Label Distribution Protocol LOC: Loss Of Continuity LSP: Label Switching Path @@ -156,21 +156,21 @@ RDI: Remote Defect Indication TE: Traffic Engineering TP: Transport Profile 5. Brief description of MIB Objects The objects described in this section support the functionality described in documents [RFC5884] and [RFC6428]. The objects are defined as an extension to the BFD base MIB defined by [RFC7331]. -5.1. Extensions to the BFD session table (bfdSessionTable) +5.1. Extensions to the BFD session table (bfdSessTable) The BFD session table used to identify a BFD session between a pair of nodes, as defined in [RFC7331], is extended with managed objects to achieve the required functionality in MPLS and MPLS-TP networks as described below: 1. SessionRole - Active/Passive role specification for the BFD session configured on the node. Either end of a BFD session can be configured as Active/Passive to determine which end starts transmitting the BFD control packets. @@ -307,22 +307,22 @@ -- In the above OID example: -- 100 -> Tunnel Index -- 1 -> Tunnel instance -- 3221225985 -> Ingress LSR Id 192.0.2.1 -- 3221225987 -> Egress LSR Id 192.0.2.3 bfdMplsSessMapPointer = mplsTunnelName.100.1.3221225985.3221225987, bfdSessRowStatus = createAndGo } - Similarly BFD session would be configured on the tail-end of - the tunnel. Creating the above row will trigger + Similarly, the BFD session would be configured on the tail-end + of the tunnel. Creating the above row will trigger the bootstrapping of the session using LSP Ping and its subsequent establishment over the path by de-multiplexing of the control packets using the BFD session discriminators. 5.2.2 Example of BFD Session configuration for ME of MPLS-TP TE tunnel This example considers the OAM identifiers configuration on a head-end LSR to manage and monitor a co-routed bidirectional MPLS tunnel. Only relevant objects which are applicable for IP based OAM @@ -390,33 +390,33 @@ ... -- Indicates that the BFD session is to monitor -- a ME of an MPLS-TP TE tunnel bfdMplsSessMapType = mep(6), bfdMplsSessMapPointer = mplsOamIdMeName.1.1.1, bfdSessRowStatus = createAndGo } - Similarly BFD session would be configured on the tail-end of + Similarly, the BFD session would be configured on the tail-end of the tunnel and creating the above row will trigger the bootstrapping of the session using LSP Ping and its subsequent establishment over the path by de-multiplexing of the control packets using the BFD session discriminators. 5.3. BFD objects for session performance counters [RFC7331] defines BFD Session Performance Table - (bfdSessionPerfTable), for collecting per-session BFD performance - counters, as an extension to the bfdSessionTable. + (bfdSessPerfTable), for collecting per-session BFD performance + counters, as an extension to the bfdSessTable. - The bfdSessionPerfTable is extended with the performance counters + The bfdSessPerfTable is extended with the performance counters to collect Mis-connectivity Defect, Loss of Continuity Defect and RDI (Remote Defect Indication) counters. 1. bfdMplsSessPerfMisDefCount - Mis-connectivity defect count for this BFD session. 2. bfdMplsSessPerfLocDefCount - Loss of continuity defect count for this BFD session. 3. bfdMplsSessPerfRdiInCount - Total number of RDI messages received for this BFD session. 4. bfdMplsSessPerfRdiOutCount - Total number of RDI messages sent @@ -430,57 +430,59 @@ Counter32, zeroDotZero FROM SNMPv2-SMI -- [RFC2578] RowPointer,TruthValue,TEXTUAL-CONVENTION FROM SNMPv2-TC -- [RFC2579] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] bfdSessIndex - FROM BFD-STD-MIB; + FROM BFD-STD-MIB; -- [RFC7331] bfdMplsMib MODULE-IDENTITY - LAST-UPDATED "201406270000Z" -- June 27 2014 + LAST-UPDATED "201504190000Z" -- April 19, 2015 ORGANIZATION "IETF Bidirectional Forwarding Detection Working Group" CONTACT-INFO " Sam Aldrin - Huawei Technologies - 2330 Central Express Way, - Santa Clara, CA 95051, USA + Google, Inc. + 1600 Amphitheatre Parkway + Mountain View, CA + USA Email: aldrin.ietf@gmail.com Venkatesan Mahalingam Dell Inc. 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com Kannan KV Sampath Redeem Software India Email: kannankvs@gmail.com Thomas D. Nadeau Email: tnadeau@lucidvision.com" DESCRIPTION - " Copyright (c) 2014 IETF Trust and the persons identified + " Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This MIB module is an initial version containing objects to provide a proactive mechanism to detect faults using BFD for MPLS and MPLS-TP networks." - REVISION "201406270000Z" -- June 27 2014 + REVISION "201504190000Z" -- April 19, 2015 DESCRIPTION - -- RFC Ed.: RFC-editor pls fill in xxxx + "BFD MIB objects for MPLS paths" + -- RFC Ed.: RFC-editor pls fill in XXX ::= { mib-2 XXX } -- XXX to be replaced with correct value -- RFC Ed.: assigned by IANA -- ------------------------------------------------------------ -- groups in the MIB -- ------------------------------------------------------------ bfdMplsObjects OBJECT IDENTIFIER ::= { bfdMplsMib 0 } bfdMplsConformance OBJECT IDENTIFIER ::= { bfdMplsMib 1 } @@ -524,21 +527,23 @@ DESCRIPTION "This table is an extension to the bfdSessTable for configuring BFD sessions for MPLS or MPLS-TP paths." ::= { bfdMplsObjects 1 } bfdMplsSessEntry OBJECT-TYPE SYNTAX BfdMplsSessEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A row in this table extends a row in bfdSessTable." + "A row in this table extends a row in bfdSessTable + and note that not all of the objects defined in + bfdSessTable are used for MPLS BFD sessions." INDEX { bfdSessIndex } ::= { bfdMplsSessTable 1 } BfdMplsSessEntry ::= SEQUENCE { bfdMplsSessRole INTEGER, bfdMplsSessMode INTEGER, bfdMplsSessTmrNegotiate TruthValue, bfdMplsSessMapType SessionMapTypeTC, bfdMplsSessMapPointer RowPointer, bfdMplsSessMisConnectivityDefectAction DefectActionTC, @@ -550,40 +555,39 @@ active(1), passive(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies whether the system is playing the active(1) role or the passive(2) role for this BFD session." REFERENCE - "RFC 5880, Section 6.1" + "Bidirectional Forwarding Detection, RFC 5880, + Section 6.1" DEFVAL { active } ::= { bfdMplsSessEntry 1 } - bfdMplsSessMode OBJECT-TYPE SYNTAX INTEGER { cc(1), cv(2) - } MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies whether the BFD session is running in Continuity Check(CC) or the Connectivity Verification(CV) mode." REFERENCE - "1.RFC6428, Proactive Connectivity Verification, - Continuity Check and Remote Defect Indication - for MPLS Transport Profile." + "Proactive Connectivity Verification, Continuity Check + and Remote Defect Indication for MPLS Transport Profile, + RFC 6428." DEFVAL { cc } ::= { bfdMplsSessEntry 2 } bfdMplsSessTmrNegotiate OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies if timer negotiation is required for the BFD session. When set to false, timer negotiation is @@ -628,21 +632,27 @@ path associated with this BFD session. If this object points to a conceptual row instance in a table consistent with bfdMplsSessMapType but this instance does not currently exist then no valid path is associated with this session entry. If this object contains zeroDotZero then no valid path is associated with this BFD session entry till it is populated with a valid pointer consistent with - the value of bfdMplsSessMapType as explained above." + the value of bfdMplsSessMapType as explained above. + + When the bfdSessRowStatus is active, this object value + change would lead to set failure and the bfdSessRowStatus + should be in notReady or notInService state in order to + change the value of this object. + " REFERENCE "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)Management Information Base (MIB), [RFC3812]. 2. Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB), [RFC3813]. 3. Pseudowire (PW) Management Information Base (MIB, [RFC5601]. 4. MPLS-TP Operations, Administration, and Management @@ -931,52 +940,52 @@ "XXX" here and in the MIB module) with the assigned value and to remove this note.] 9. References 9.1 Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. - [BFD] Katz, D. and D. Ward, "Bidirectional Forwarding + [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, + "Structure of Management Information Version 2 (SMIv2)", + STD 58, RFC 2578, April 1999. + + [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, + "Textual Conventions for SMIv2", STD 58, RFC 2579, April + 1999. + + [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, + "Conformance Statements for SMIv2", STD 58, RFC 2580, + April 1999. + + [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, June 2010. - [BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding + [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June 2010. - [BFD-MH] Katz, D. and D. Ward, "Bidirectional Forwarding + [RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD) for Multihop Paths", RFC 5883, - June 2010. + June 2010 [RFC5884] Aggarwal, R. et.al., "Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)", RFC 5884, June 2010 [RFC6428] Allan, D., Swallow, G., Drake, J., "Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile", RFC 6428, November 2011. - [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, - "Structure of Management Information Version 2 (SMIv2)", - STD 58, RFC 2578, April 1999. - - [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, - "Textual Conventions for SMIv2", STD 58, RFC 2579, April - 1999. - - [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, - "Conformance Statements for SMIv2", STD 58, RFC 2580, - April 1999. - 9.2 Informative References [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction and Applicability Statement for Internet Standard Management Framework", RFC 3410, December 2002. [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model(USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. @@ -1005,43 +1014,48 @@ Protocol (SNMP)", RFC 5592, June 2009. [RFC5601] T. Nadeau, Ed., D. Zelig, Ed., "Pseudowire (PW) Management Information Base (MIB)", RFC 5601, July 2009. [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, July 2011. + [RFC7130] Bhatia, M., Chen, M., Boutros, S., Binderberger, M., and + J. Haas, "Bidirectional Forwarding Detection (BFD) on + Link Aggregation Group (LAG) Interfaces", RFC 7130, + February 2014. + [RFC7331] T. Nadeau, Z. Ali, N. Akiya "BFD Management Information Base", RFC 7331, August 2014. [MPLS-OAM-ID-STD-MIB] Sam Aldrin, M.Venkatesan, Kannan KV Sampath, Thomas D. Nadeau, Sami Boutros, Ping Pan, "MPLS-TP Operations, Administration, and Management (OAM) Identifiers Management Information Base (MIB)", ID - draft-ietf-mpls-tp-oam-id-mib-06, - December 2014. + draft-ietf-mpls-tp-oam-id-mib-08, + February 2015. 10. Acknowledgments The authors would like to thank Jeffrey Haas, Mukund Mani, Lavanya Srivatsa, Muly Ilan and John Salloway for their valuable comments. 11. Authors' Addresses - Sam Aldrin - Huawei Technologies - 2330 Central Express Way, - Santa Clara, CA 95051, USA + Google, Inc. + 600 Amphitheatre Parkway + Mountain View, CA + USA Email: aldrin.ietf@gmail.com Venkatesan Mahalingam Dell Inc. 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com Kannan KV Sampath Redeem Software