--- 1/draft-ietf-mpls-lsr-mib-05.txt 2006-02-05 00:41:29.000000000 +0100 +++ 2/draft-ietf-mpls-lsr-mib-06.txt 2006-02-05 00:41:30.000000000 +0100 @@ -3,21 +3,21 @@ Expires: January 2001 Arun Viswanathan Force10 Networks, Inc. Thomas D. Nadeau Cisco Systems, Inc. July 2000 MPLS Label Switch Router Management Information Base Using SMIv2 - draft-ietf-mpls-lsr-mib-05.txt + draft-ietf-mpls-lsr-mib-06.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. 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. @@ -457,27 +457,27 @@ (ifTable) contains information on the managed resource's interfaces and that each sub-layer below the internetwork layer of a network interface is considered an interface. Thus, the MPLS interface is represented as an entry in the ifTable. The inter- relation of entries in the ifTable is defined by Interfaces Stack Group defined in [IFMIB]. When using MPLS interfaces, the interface stack table might appear as follows: - +-----------------------------------+ - | MPLS interface ifType = mpls(166) | - +-----------------------------------+ - | Underlying Layer | - +-----------------------------------+ + +----------------------------------------+ + | MPLS-interface ifType = mpls(166) + + +----------------------------------------+ + | Underlying Layer... + + +----------------------------------------+ - In the above diagram, "Underlying Layer" refers to the ifIndex + In the above diagram, "Underlying Layer..." refers to the ifIndex of any interface type, which has been defined for MPLS interworking. Examples include ATM, Frame Relay, Ethernet, etc. 9.1. Support of the MPLS Layer by ifTable Some specific interpretations of ifTable for the MPLS layer follow. Object Use for the MPLS layer @@ -576,21 +576,21 @@ InterfaceIndex, InterfaceIndexOrZero FROM IF-MIB AddressFamilyNumbers FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB InetAddressIPv4, InetAddressIPv6, InetAddressType FROM INET-ADDRESS-MIB; mplsLsrMIB MODULE-IDENTITY - LAST-UPDATED "200007071200Z" -- 07 July 2000 12:00:00 EST + LAST-UPDATED "200007121200Z" -- 12 July 2000 12:00:00 EST ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Cheenu Srinivasan Postal: Tachion Networks, Inc. Monmouth Park Corporate Center I Building C, 185 Monmouth Parkway West Long Branch, NJ 07764 Tel: +1-732-542-7750 x1234 Email: cheenu@tachion.com @@ -611,20 +611,24 @@ DESCRIPTION "This MIB contains managed object definitions for the Multiprotocol Label Switching (MPLS) Router as defined in: Rosen, E., Viswanathan, A., and R. Callon, Multiprotocol Label Switching Architecture, Internet Draft , August 1999." -- Revision history. REVISION + "200007121200Z" -- 12 July 2000 12:00:00 EST + DESCRIPTION + "Seventh draft version. Fix minor compilation errors." + REVISION "200007071200Z" -- 07 July 2000 12:00:00 EST DESCRIPTION "Sixth draft version. Made minor typographical corrections noted from WG mailing list during second working group last call." REVISION "200004261200Z" -- 26 April 2000 12:00:00 EST DESCRIPTION "Fifth draft version. Made minor typographical corrections noted from WG mailing list." @@ -714,21 +716,21 @@ "The number of octets of MPLS data that the stream may send back-to-back without concern for policing." SYNTAX Integer32 (1..2147483647) MplsObjectOwner ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The entity which owns the object in question." SYNTAX INTEGER { other(1), - management(2), + snmp(2), ldp(3), rsvp(4), crldp(5), policyAgent(6), unknown (7) } -- Top level components of this MIB. -- Tables, Scalars @@ -1022,35 +1024,35 @@ mplsInSegmentAddrFamily AddressFamilyNumbers, mplsInSegmentXCIndex Integer32, mplsInSegmentOwner MplsObjectOwner, mplsInSegmentTrafficParamPtr RowPointer, mplsInSegmentRowStatus RowStatus, mplsInSegmentStorageType StorageType } mplsInSegmentIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero - MAX-ACCESS not-accessible + MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique index for an entry in the MplsInSegmentTable. This value represents the interface index for the incoming MPLS interface. A value of zero represents an incoming label from the per-platform label space. In this case, the mplsInSegmentLabel is interpreted to be an MPLS-type label." ::= { mplsInSegmentEntry 1 } mplsInSegmentLabel OBJECT-TYPE SYNTAX MplsLabel - MAX-ACCESS not-accessible + MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The incoming label for this segment." ::= { mplsInSegmentEntry 2 } mplsInSegmentNPop OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION @@ -1289,21 +1292,21 @@ mplsOutSegmentNextHopIpv6Addr InetAddressIPv6, mplsOutSegmentXCIndex Integer32, mplsOutSegmentOwner MplsObjectOwner, mplsOutSegmentTrafficParamPtr RowPointer, mplsOutSegmentRowStatus RowStatus, mplsOutSegmentStorageType StorageType } mplsOutSegmentIndex OBJECT-TYPE SYNTAX Integer32(0..2147483647) - MAX-ACCESS not-accessible + MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This value contains a unique index for this row. While a value of 0 is not valid as an index for this row it can be supplied as a valid value to index mplsXCTable to access entries for which no out- segment has been configured." ::= { mplsOutSegmentEntry 1 } mplsOutSegmentIfIndex OBJECT-TYPE @@ -2347,29 +2351,25 @@ ::= { mplsLsrGroups 12 } mplsSegmentDiscontinuityGroup OBJECT-GROUP OBJECTS { mplsInSegmentPerfDiscontinuityTime, mplsOutSegmentPerfDiscontinuityTime } STATUS current DESCRIPTION "A collection of objects providing information - specific to segment discontinuities." + specific to segment discontinuities.." ::= { mplsLsrGroups 13 } mplsLsrNotificationGroup NOTIFICATION-GROUP - NOTIFICATIONS { mplsInSegmentUp, - mplsInSegmentDown, - mplsOutSegmentUp, - mplsOutSegmentDown, - mplsXCUp, + NOTIFICATIONS { mplsXCUp, mplsXCDown } STATUS current DESCRIPTION "Set of notifications implemented in this module. None is mandatory." ::= { mplsLsrGroups 14 } -- End of MPLS-LSR-MIB END @@ -2406,31 +2406,32 @@ [SNMPv3USM] and the View-based Access Control [SNMPv3VACM] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. There are a number of managed objects in this MIB that may contain information that may be sensitive from a business perspective, in that they represent a customer's interface to the MPLS network. + Allowing uncontrolled access to these objects could result in malicious and unwanted disruptions of network traffic or incorrect configurations for these customers. There are no objects that are particularly sensitive in their own right, such as passwords or monetary amounts. 13. Acknowledgments We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim - Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, and - Vasanthi Thirumalai. + Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, + Vasanthi Thirumalai, Joseph Benoit and Joan Cucchiara. 14. References [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", Internet Draft , August 1999. [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, G., and A. Viswanathan, "A Framework for