--- 1/draft-ietf-mpls-p2mp-te-mib-05.txt 2008-02-14 21:12:13.000000000 +0100 +++ 2/draft-ietf-mpls-p2mp-te-mib-06.txt 2008-02-14 21:12:13.000000000 +0100 @@ -1,23 +1,23 @@ Network Working Group A. Farrel (Editor) INTERNET-DRAFT Old Dog Consulting Updates: RFC3812, RFC4802 Intended Status: Standards Track S. Yasukawa -Created: September 24, 2007 NTT -Expires: March 24, 2008 +Created: February 14, 2008 NTT +Expires: August 24, 2008 T. Nadeau BT Point-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB) module - draft-ietf-mpls-p2mp-te-mib-05.txt + draft-ietf-mpls-p2mp-te-mib-06.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other @@ -74,29 +74,24 @@ 11.1. Normative References .................................... 55 11.2. Informative References .................................. 56 12. Authors' Addresses ........................................... 57 13. Intellectual Property ........................................ 57 14. Full Copyright Statement ..................................... 58 0. Changes Since Previous Revision [This section to be removed before publication as an RFC.] - - Clarify that this MIB module is equally applicable to GMPLS - (Abstract and section 1). - - Add explanation of how backward compatibility is not impacted by - the modification of semantics for objects in the MPLS-TE-STD-MIB. - (Sections 4.2.1 and 4.2.2.) - - Add section 5.2 for transit node example. + - Update author coordinates - Expand conformance statements for read-only and read-create cases. - - Fix smilint warnings. - Typos. + - Add mplsTeP2mpScalarGroup. 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS) traffic engineering (TE). MPLS is defined in [RFC3031] and a signaling protocol for @@ -1247,62 +1242,62 @@ mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId FROM MPLS-TE-STD-MIB -- RFC 3812 IndexInteger, IndexIntegerNextFree FROM DIFFSERV-MIB -- RFC 3289 InetAddress, InetAddressType FROM INET-ADDRESS-MIB -- RFC 4001 ; mplsTeP2mpStdMIB MODULE-IDENTITY - LAST-UPDATED "200709170000Z" -- Setember 17, 2007 + LAST-UPDATED "200802140000Z" -- February 14, 2008 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk Seisho Yasukawa NTT Corporation Email: s.yasukawa@hco.ntt.co.jp Thomas D. Nadeau British Telecom - Email: thomas.nadeau@bt.com + Email: tom.nadeau@bt.com Comments about this document should be emailed directly to the MPLS working group mailing list at mpls@lists.ietf.org" DESCRIPTION - "Copyright (C) The IETF Trust (2007). The initial version of + "Copyright (C) The IETF Trust (2008). The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXXX with the RFC number for this -- document and remove this note. This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in: 1. Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006. 2. Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007." -- Revision history. REVISION - "200709170000Z" -- Setember 17, 2007 + "200802140000Z" -- February 14, 2008 DESCRIPTION "Initial version issued as part of RFC XXXX." -- RFC Editor. Please replace XXXX with the RFC number for this -- document and remove this note. ::= { mplsStdMIB YYY } -- RFC Editor. Please replace YYY with the codepoint issued by IANA -- and remove this note. @@ -2297,21 +2292,22 @@ also be configured using this MIB module. The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE." MODULE -- this module MANDATORY-GROUPS { mplsTeP2mpGeneralGroup, - mplsTeP2mpNotifGroup + mplsTeP2mpNotifGroup, + mplsTeP2mpScalarGroup } -- mplsTeP2mpTunnelTable OBJECT mplsTeP2mpTunnelSubGroupOriginType SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2)} DESCRIPTION "An implementation is only required to support unknown(0), IPv4(1) and IPv6(2) addresses." @@ -2330,20 +2326,21 @@ support for MPLS-TE-P2MP-STD-MIB. Such devices can only be monitored using this MIB module. The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE." MODULE -- this module MANDATORY-GROUPS { mplsTeP2mpGeneralGroup, + mplsTeP2mpScalarGroup, mplsTeP2mpNotifGroup } -- mplsTeP2mpTunnelTable OBJECT mplsTeP2mpTunnelP2mpIntegrity MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTeP2mpTunnelBranchRole @@ -2445,20 +2442,31 @@ mplsTeP2mpNotifGroup NOTIFICATION-GROUP NOTIFICATIONS { mplsTeP2mpTunnelDestUp, mplsTeP2mpTunnelDestDown } STATUS current DESCRIPTION "Notifications implemented in this module." ::= { mplsTeP2mpGroups 2 } + mplsTeP2mpScalarGroup OBJECT-GROUP + OBJECTS { + mplsTeP2mpTunnelConfigured, + mplsTeP2mpTunnelActive, + mplsTeP2mpTunnelTotalMaxHops + } + STATUS current + DESCRIPTION + "Scalar objects needed to implement P2MP MPLS tunnels." + ::= { mplsTeP2mpGroups 3 } + END 8. Security Considerations It is clear that this MIB module is potentially useful for the monitoring of P2MP MPLS TE tunnels. This MIB module can also be used for the configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results. @@ -2674,21 +2682,21 @@ Musashino-Shi, Tokyo 180-8585 Japan Phone: +81 422 59 4769 EMail: s.yasukawa@hco.ntt.co.jp Thomas D. Nadeau BT BT Centre 81 Newgate Street EC1A 7AJ London - Email: thomas.nadeau@bt.com + Email: tom.nadeau@bt.com 13. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be @@ -2702,21 +2710,21 @@ http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. 14. Full Copyright Statement - Copyright (C) The IETF Trust (2007). + Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF