draft-ietf-rtgwg-ipfrr-ip-mib-00.txt   draft-ietf-rtgwg-ipfrr-ip-mib-01.txt 
Network Working Group A. Atlas, Ed. Network Working Group A. Atlas, Ed.
Internet-Draft B. Anderson Internet-Draft Google, Inc.
Expires: December 19, 2005 Avici Systems, Inc. Expires: August 5, 2006 B. Anderson
Avici Systems, Inc.
D. Fedyk D. Fedyk
Nortel Networks Nortel Networks
June 17, 2005 February 2006
IP MIB for IP Fast-Reroute IP MIB for IP Fast-Reroute
draft-ietf-rtgwg-ipfrr-ip-mib-00 draft-ietf-rtgwg-ipfrr-ip-mib-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 19, 2005. This Internet-Draft will expire on August 5, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This draft defines a portion of the Management Information Base (MIB) This draft defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects relevant for IP routes In particular, it describes managed objects relevant for IP routes
using IP Fast-Reroute [IPFRR]. using IP Fast-Reroute [IPFRR].
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 The SNMP Management Framework . . . . . . . . . . . . . . 3 1.1. The SNMP Management Framework . . . . . . . . . . . . . . 3
2. Brief Description of MIB Objects . . . . . . . . . . . . . . . 4 2. Brief Description of MIB Objects . . . . . . . . . . . . . . . 4
2.1 ipFrrProtectStats Group . . . . . . . . . . . . . . . . . 4 2.1. ipFrrProtectStats Group . . . . . . . . . . . . . . . . . 4
2.2 ipFrrAltTable . . . . . . . . . . . . . . . . . . . . . . 4 2.2. ipFrrAltTable . . . . . . . . . . . . . . . . . . . . . . 4
2.3 ipFrrNoAltTable . . . . . . . . . . . . . . . . . . . . . 4 2.3. ipFrrNoAltTable . . . . . . . . . . . . . . . . . . . . . 4
3. IP Fast-Reroute MIB Module Definitions . . . . . . . . . . . . 5 3. IP Fast-Reroute MIB Module Definitions . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 16 4. Security Considerations . . . . . . . . . . . . . . . . . . . 16
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . . . 19
1. Introduction 1. Introduction
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it defines the managed objects used for IP community. In particular, it defines the managed objects used for IP
routes and interfaces in relation to IP Fast-Reroute. This document routes and interfaces in relation to IP Fast-Reroute. This document
uses terminology from [FRAMEWORK], [IPFRR] and [IPFRR-UTURN]. uses terminology from [I-D.ietf-rtgwg-ipfrr-framework], [I-D.ietf-
rtgwg-ipfrr-spec-base] and [IPFRR-UTURN].
Current work is underway to define mechanisms for determining Current work is underway to define mechanisms for determining
alternate paths for traffic to use when the original path becomes alternate paths for traffic to use when the original path becomes
unavailable due to a local failure. The alternate next-hops can be unavailable due to a local failure. The alternate next-hops can be
computed in the context of any IGP. computed in the context of any IGP.
There are certain configuration attributes for IP Fast-Reroute that There are certain configuration attributes for IP Fast-Reroute that
should be configured to enable IP Fast Reroute in the context of the should be configured to enable IP Fast Reroute in the context of the
IGP. These configuration attributes of IP Fast-Reroute are not IGP. These configuration attributes of IP Fast-Reroute are not
covered by this MIB module. Examples include whether IP Fast-Reroute covered by this MIB module. Examples include whether IP Fast-Reroute
is enabled on a network region (i.e. an OSPF area or IS-IS level) and is enabled on a network region (i.e. an OSPF area or IS-IS level) and
the desired local hold-down timer[IPFRR], whose proper value is the desired local hold-down timer[I-D.ietf-rtgwg-ipfrr-spec-base],
dependent upon the size of the network region. whose proper value is dependent upon the size of the network region.
It is possible for traffic other than IP to depend upon and use the It is possible for traffic other than IP to depend upon and use the
alternate next-hops computed by IP Fast-Reroute. An example would be alternate next-hops computed by IP Fast-Reroute. An example would be
MPLS traffic whose path is configured via LDP[RFC3036]. The MPLS traffic whose path is configured via LDP[RFC3036]. The
additional details (for example, outgoing MPLS label) pertaining to additional details (for example, outgoing MPLS label) pertaining to
alternate next-hops that are required by such traffic are not covered alternate next-hops that are required by such traffic are not covered
by this MIB module. by this MIB module.
An IP route may be reachable via multiple primary next-hops which An IP route may be reachable via multiple primary next-hops which
provide equal-cost paths. Where IP Fast-Reroute is enabled, each provide equal-cost paths. Where IP Fast-Reroute is enabled, each
primary next-hop will be protected by one or more alternate next- primary next-hop will be protected by one or more alternate next-
hops. Such an alternate next-hop may itself be a primary next-hop. hops. Such an alternate next-hop may itself be a primary next-hop.
1.1 The SNMP Management Framework 1.1. The SNMP Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Brief Description of MIB Objects 2. Brief Description of MIB Objects
This MIB module consists of five global objects, organized into the This MIB module consists of five global objects, organized into the
ipFrrProtectStats group, and two tables. ipFrrProtectStats group, and two tables.
2.1 ipFrrProtectStats Group 2.1. ipFrrProtectStats Group
The global objects in this group provide summary information related The global objects in this group provide summary information related
to protection for all IP routes. The information available includes to protection for all IP routes. The information available includes
counts of all routes, of all protected routes, of all unprotected counts of all routes, of all protected routes, of all unprotected
routes, of all routes which are protected against a link failure, and routes, of all routes which are protected against a link failure, and
of all routes which are protected against a node failure. of all routes which are protected against a node failure.
2.2 ipFrrAltTable 2.2. ipFrrAltTable
The ipFrrAltTable extends the inetCidrRouteTable[RFC2096-update] to The ipFrrAltTable extends the inetCidrRouteTable[I-D.ietf-ipv6-
provide information about each alternate next-hop associated with a rfc2096-update] to provide information about each alternate next-hop
primary next-hop used by a route. Statically configured alternate associated with a primary next-hop used by a route. Statically
next-hops associated with primary next-hops can be created. configured alternate next-hops associated with primary next-hops can
be created.
2.3 ipFrrNoAltTable 2.3. ipFrrNoAltTable
The ipFrrNoAltTable extends the inetCidrRouteTable[RFC2096-update] to The ipFrrNoAltTable extends the inetCidrRouteTable[I-D.ietf-ipv6-
provide information about the routes which do not have an alternate rfc2096-update] to provide information about the routes which do not
next-hop associated with any of the route's primary next-hop. The have an alternate next-hop associated with any of the route's primary
entry provides an explanation for the lack of protection. next-hop. The entry provides an explanation for the lack of
protection.
3. IP Fast-Reroute MIB Module Definitions 3. IP Fast-Reroute MIB Module Definitions
IPFRR-MIB DEFINITIONS ::= BEGIN IPFRR-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Gauge32, Gauge32,
Integer32 FROM SNMPv2-SMI -- [RFC2578] Integer32 FROM SNMPv2-SMI -- [RFC2578]
skipping to change at page 16, line 45 skipping to change at page 16, line 45
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET them. rights to indeed GET them.
5. References 5. References
[FRAMEWORK] [I-D.ietf-ipv6-rfc2096-update]
Shand, M., "IP Fast Reroute Framework", Wasserman, M. and B. Haberman, "IP Forwarding Table MIB",
draft-ietf-rtgwg-ipfrr-framework-02.txt (work in draft-ietf-ipv6-rfc2096-update-07 (work in progress),
progress), October 2004. February 2004.
[IPFRR] Atlas, A., "Basic Specification for IP Fast-Reroute: Loop-
free Alternates", draft-ietf-rtgwg-ipfrr-spec-base-04.txt
(work in progress), June 2005.
[IPFRR-UTURN] [I-D.ietf-rtgwg-ipfrr-framework]
Atlas, A., "U-Turn Alternates for IP/LDP Local Shand, M. and S. Bryant, "IP Fast Reroute Framework",
Protection", draft-atlas-ip-local-protect-uturn-02.txt draft-ietf-rtgwg-ipfrr-framework-05 (work in progress),
(work in progress), February 2005. March 2006.
[RFC2096] Baker, F., "IP Forwarding Table MIB", RFC 2096, [I-D.ietf-rtgwg-ipfrr-spec-base]
January 1997. Atlas, A. and A. Zinin, Ed., "Basic Specification for IP
Fast-Reroute: Loop-free Alternates",
draft-ietf-rtgwg-ipfrr-spec-base-05.txt (work in
progress), February 2006.
[RFC2096-update] [IPFRR-UTURN]
Haberman, B., "IP Forwarding Table MIB", Atlas, A., Ed., "U-Turn Alternates for IP/LDP Local
draft-ietf-ipv6-rfc2096-update-07.txt (work in progress), Protection", draft-atlas-ip-local-protect-uturn-03.txt
February 2004. (work in progress), February 2006.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and
B. Thomas, "LDP Specification", RFC 3036, January 2001. B. Thomas, "LDP Specification", RFC 3036, January 2001.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 3291, May 2002.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
Authors' Addresses Authors' Addresses
Alia K. Atlas (editor) Alia K. Atlas (editor)
Avici Systems, Inc. Google, Inc.
101 Billerica Avenue 1600 Amphitheatre Parkway
N. Billerica, MA 01862 Mountain View, CA 94043
USA USA
Phone: +1 978 964 2070 Email: akatlas@alum.mit.edu
Email: aatlas@avici.com
Bill Anderson Bill Anderson
Avici Systems, Inc. Avici Systems, Inc.
101 Billerica Avenue 101 Billerica Avenue
N. Billerica, MA 01862 N. Billerica, MA 01862
USA USA
Phone: +1 978 964 2679 Phone: +1 978 964 2679
Email: wanderson@avici.com Email: wanderson@avici.com
skipping to change at page 19, line 41 skipping to change at page 19, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 25 change blocks. 
58 lines changed or deleted 53 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/