TRILL OAM MIB
draft-ietf-trill-oam-mib-02
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7784.
|
|
|---|---|---|---|
| Authors | Deepak Kumar , Samer Salam , Tissa Senevirathne | ||
| Last updated | 2015-01-23 (Latest revision 2014-12-12) | ||
| Replaces | draft-deepak-trill-oam-mib | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Donald E. Eastlake 3rd | ||
| Shepherd write-up | Show Last changed 2014-12-22 | ||
| IESG | IESG state | Became RFC 7784 (Proposed Standard) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Alia Atlas | ||
| Send notices to | d3e3e3@gmail.com, trill-chairs@ietf.org, trill@ietf.org |
draft-ietf-trill-oam-mib-02
Internet Draft TRILL OAM MIB December 12, 2014 STATUS current DESCRIPTION "Trill OAM MEP Flow Configuration objects group." ::= { trillOamMibGroups 2 } trillOamPtrTableGroup OBJECT-GROUP OBJECTS { trillOamMepPtrHC, trillOamMepPtrFlag, trillOamMepPtrErrorCode, trillOamMepPtrTerminalMep, trillOamMepPtrLastEgressId, trillOamMepPtrIngress, trillOamMepPtrIngressMac, trillOamMepPtrIngressPortIdSubtype, trillOamMepPtrIngressPortId, trillOamMepPtrEgress, trillOamMepPtrEgressMac, trillOamMepPtrEgressPortIdSubtype, trillOamMepPtrEgressPortId, trillOamMepPtrChassisIdSubtype, trillOamMepPtrChassisId, trillOamMepPtrOrganizationSpecificTlv, trillOamMepPtrNextHopNicknames } STATUS current DESCRIPTION "Trill OAM MEP PTR objects group." ::= { trillOamMibGroups 3 } trillOamMtrTableGroup OBJECT-GROUP OBJECTS { trillOamMepMtrFlag, trillOamMepMtrErrorCode, trillOamMepMtrLastEgressId, trillOamMepMtrIngress, trillOamMepMtrIngressMac, trillOamMepMtrIngressPortIdSubtype, trillOamMepMtrIngressPortId, trillOamMepMtrEgress, trillOamMepMtrEgressMac, trillOamMepMtrEgressPortIdSubtype, trillOamMepMtrEgressPortId, trillOamMepMtrChassisIdSubtype, trillOamMepMtrChassisId, trillOamMepMtrOrganizationSpecificTlv, trillOamMepMtrNextHopNicknames, trillOamMepMtrReceiverAvailability, Kumar et al. Expires June 15, 2015 [Page 43] Internet Draft TRILL OAM MIB December 12, 2014 trillOamMepMtrReceiverCount } STATUS current DESCRIPTION "Trill OAM MEP MTR objects group." ::= { trillOamMibGroups 4 } trillOamMepDbGroup OBJECT-GROUP OBJECTS { trillOamMepDbFlowIndex, trillOamMepDbFlowEntropy, trillOamMepDbFlowState, trillOamMepDbFlowFailedOkTime, trillOamMepDbRbridgeName, trillOamMepDbLastGoodSeqNum } STATUS current DESCRIPTION "Trill OAM MEP DB objects group." ::= { trillOamMibGroups 5 } trillOamNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { trillOamFaultAlarm } STATUS current DESCRIPTION "Objects for Notification Group" ::= { trillOamMibGroups 6 } -- ****************************************************************** -- TRILL OAM MIB Module Compliance statements -- ****************************************************************** trillOamMibCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for the TRILL OAM MIB." MODULE -- this module MANDATORY-GROUPS { trillOamMepMandatoryGroup, trillOamMepFlowCfgTableGroup, trillOamPtrTableGroup, trillOamMtrTableGroup, trillOamMepDbGroup, trillOamNotificationGroup } Kumar et al. Expires June 15, 2015 [Page 44] Internet Draft TRILL OAM MIB December 12, 2014 ::= { trillOamMibCompliances 1 } -- Compliance requirement for read-only implementation. trillOamMibReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementation that only provide read-only support for TRILL-OAM-MIB. Such devices can be monitored but cannot be configured using this MIB module " MODULE -- this module MANDATORY-GROUPS { trillOamMepMandatoryGroup, trillOamMepFlowCfgTableGroup, trillOamPtrTableGroup, trillOamMtrTableGroup, trillOamMepDbGroup, trillOamNotificationGroup } -- trillOamMepTable OBJECT trillOamMepTxLbmDestRName MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxLbmHC MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxLbmReplyModeOob MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTransmitLbmReplyIp MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxLbmFlowEntropy MIN-ACCESS read-only DESCRIPTION "Write access is not required." Kumar et al. Expires June 15, 2015 [Page 45] Internet Draft TRILL OAM MIB December 12, 2014 OBJECT trillOamMepTxPtmDestRName MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxPtmHC MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxPtmReplyModeOob MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTransmitPtmReplyIp MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxPtmFlowEntropy MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxPtmStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxPtmResultOK MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxPtmMessages MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxPtmSeqNumber MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxMtmTree MIN-ACCESS read-only DESCRIPTION Kumar et al. Expires June 15, 2015 [Page 46] Internet Draft TRILL OAM MIB December 12, 2014 "Write access is not required." OBJECT trillOamMepTxMtmHC MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxMtmReplyModeOob MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTransmitMtmReplyIp MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxMtmFlowEntropy MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxMtmStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxMtmResultOK MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxMtmMessages MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxMtmSeqNumber MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepTxMtmScopeList MIN-ACCESS read-only DESCRIPTION "Write access is not required." Kumar et al. Expires June 15, 2015 [Page 47] Internet Draft TRILL OAM MIB December 12, 2014 -- trillOamMepFlowCfgTable OBJECT trillOamMepFlowCfgFlowEntropy MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepFlowCfgDestRName MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepFlowCfgFlowHC MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT trillOamMepFlowCfgRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { trillOamMibCompliances 2 } END 8. Security Considerations This MIB relates to a system that will provide network connectivity and packet forwarding services. As such, improper manipulation of the objects represented by this MIB may result in denial of service to a large number of end-users. There are number of management objects defined in this MIB module with a MAX-ACCESS clause of read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have negative effect on sensitivity/vulnerability are described below. Some of the readable objects in this MIB module (objects with a MAC- ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control GET and/or NOTIFY access to these objects and possibly to encrypt the values of these objects when sending them over the network via SNMP. Kumar et al. Expires June 15, 2015 [Page 48] Internet Draft TRILL OAM MIB December 12, 2014 SNMP version prior to SNMPv3 did not include adequate security. Even if the network itself is secure, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanism (for authentication and privacy). Further, deployment of SNMP version prior to SNMPv3 is NOT RECOMMENDED. Instead, deployment of SNMPv3 with cryptographic security enabled is RECOMMENDED. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give only those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them access to the objects. 9. IANA Considerations The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER value recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER value ---------------------------------------- trillOamMIB { mib-2 xxx } Editor's Note (to be removed prior to publication): the IANA is requested to assign a value for "xxx" under the 'mib-2' subtree and to record the assignment in the SMI Numbers registry. When the assignment has been made, the RFC Editor is asked to replace "XXX" (here and in the MIB module) with the assigned value and to remove this note. 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. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Kumar et al. Expires June 15, 2015 [Page 49] Internet Draft TRILL OAM MIB December 12, 2014 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC6325] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and A. Ghanwani, "Routing Bridges (RBridges): Base Protocol Specification", RFC 6325, July 2011, <http://www.rfc-editor.org/info/rfc6325>. [RFC7172] Eastlake 3rd, D., Zhang, M., Agarwal, P., Perlman, R., and D. Dutt, "Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling", RFC 7172, May 2014, <http://www.rfc-editor.org/info/rfc7172>. [TRILL-FM] Senevirathne, T., et.al., "TRILL Fault Management", draft-ietf-trill-oam-fm, Work in Progress. 10.2. Informative References [802.1Q] IEEE, "IEEE Standard for Local and metropolitan area networks - Media Access Control (MAC) Bridges and Virtual Bridge Local Area Networks", IEEE Std 802.1Q-2011, 31 August 2011. [RFC3410] Case, J., Mundy, R., Partain, D., and B.Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC6905] Senevirathne, T., Bond, D., Aldrin, S., Li, Y., and R. Watve, "Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)", RFC 6905, March 2013. [RFC7174] Salam, S., Senevirathne, T., Aldrin, S., and D. Eastlake 3rd, "Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) Framework", RFC 7174, May 2014, <http://www.rfc- editor.org/info/rfc7174>. 11. Acknowledgments Kumar et al. Expires June 15, 2015 [Page 50] Internet Draft TRILL OAM MIB December 12, 2014 We wish to thank members of the IETF TRILL WG for their comments and suggestions. Detailed comments were provided by Sam Aldrin, and Donald Eastlake. 12. Copyright and Disclaimer Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Authors' Addresses Deepak Kumar Cisco 510 McCarthy Blvd, Milpitas, CA 95035, USA Kumar et al. Expires June 15, 2015 [Page 51] Internet Draft TRILL OAM MIB December 12, 2014 Phone : +1 408-853-9760 Email: dekumar@cisco.com Samer Salam Cisco 595 Burrard St. Suite 2123 Vancouver, BC V7X 1J1, Canada Email: ssalam@cisco.com Tissa Senevirathne Cisco 375 East Tasman Drive San Jose, CA 95134, USA Email: tsenevir@cisco.com Kumar et al. Expires June 15, 2015 [Page 52]