draft-ietf-rtgwg-ipfrr-ip-mib-01.txt   draft-ietf-rtgwg-ipfrr-ip-mib-02.txt 
Network Working Group Alia Atlas
Internet-Draft Juniper Networks
Expires: August 23, 2012 A S Kiran Koushik(Ed.)
Cisco Systems Inc.
John Flick(Ed.)
Hewlett-Packard Company
Network Working Group A. Atlas, Ed. March 2012
Internet-Draft Google, Inc.
Expires: August 5, 2006 B. Anderson
Avici Systems, Inc.
D. Fedyk
Nortel Networks
February 2006
IP MIB for IP Fast-Reroute IP MIB for IP Fast-Reroute
draft-ietf-rtgwg-ipfrr-ip-mib-01
draft-ietf-rtgwg-ipfrr-ip-mib-02
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 August 5, 2006. This Internet-Draft will expire on August 23, 2012.
Copyright Notice
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 [RFC5714].
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 Full 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 [I-D.ietf-rtgwg-ipfrr-framework], [I-D.ietf- uses terminology from [RFC5714] and [RFC5286].
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[I-D.ietf-rtgwg-ipfrr-spec-base], the desired local hold-down timer[RFC5286],
whose proper value is 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[RFC5036]. 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[I-D.ietf-ipv6- The ipFrrAltTable extends the inetCidrRouteTable[RFC4292]
rfc2096-update] to provide information about each alternate next-hop to provide information about each alternate next-hop
associated with a primary next-hop used by a route. Statically associated with a primary next-hop used by a route. Statically
configured alternate next-hops associated with primary next-hops can configured alternate next-hops associated with primary next-hops can
be created. be created.
2.3. ipFrrNoAltTable 2.3. ipFrrNoAltTable
The ipFrrNoAltTable extends the inetCidrRouteTable[I-D.ietf-ipv6- The ipFrrNoAltTable extends the inetCidrRouteTable[RFC4292]
rfc2096-update] to provide information about the routes which do not to provide information about the routes which do not
have an alternate next-hop associated with any of the route's primary have an alternate next-hop associated with any of the route's primary
next-hop. The entry provides an explanation for the lack of next-hop. The entry provides an explanation for the lack of
protection. 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]
RowStatus RowStatus
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
InetAddressType, InetAddressType,
InetAddress FROM INET-ADDRESS-MIB -- [RFC3291] InetAddress FROM INET-ADDRESS-MIB -- [RFC4001]
InterfaceIndex FROM IF-MIB -- [RFC2863] InterfaceIndex FROM IF-MIB -- [RFC2863]
ip FROM IP-MIB -- [RFC2011] ip FROM IP-MIB -- [RFC4293]
inetCidrRouteDestType, inetCidrRouteDestType,
inetCidrRouteDest, inetCidrRouteDest,
inetCidrRoutePfxLen, inetCidrRoutePfxLen,
inetCidrRoutePolicy, inetCidrRoutePolicy,
inetCidrRouteNextHopType, inetCidrRouteNextHopType,
inetCidrRouteNextHop FROM IP-FORWARD-MIB inetCidrRouteNextHop FROM IP-FORWARD-MIB
-- [draft-ietf-ipv6-rfc2096-update-07] -- [RFC4292]
; ;
ipFrrMIB MODULE-IDENTITY ipFrrMIB MODULE-IDENTITY
LAST-UPDATED "200502181200Z" -- June 10, 2005 LAST-UPDATED "201203131200Z" -- Mar 13, 2012
ORGANIZATION "draft-ietf-ipfrr-ip-mib-00.txt" ORGANIZATION "draft-ietf-ipfrr-ip-mib-02.txt"
CONTACT-INFO CONTACT-INFO
" Bill Anderson "
Avici Systems, Inc. A S Kiran Koushik
EMail: wanderson@avici.com Cisco Systems Inc.
EMail: kkoushik@cisco.com
Alia Atlas John W Flick
Avici Systems, Inc. Hewlett Packard Company
Email: aatlas@avici.com EMail: john.flick@hp.com
Don Fedyk Alia Atlas
Nortel Networks Juniper Networks
Email: dwfedyk@nortel.com Email: akatlas@juniper.net
" "
DESCRIPTION DESCRIPTION
"IP MIB module for management of IP Fast-Reroute. "IP MIB module for management of IP Fast-Reroute.
Copyright (C) The Internet Society (date). Copyright (C) The Internet Society (date).
This version of this MIB module is part of This version of this MIB module is part of
draft-ietf-rtgwg-ipfrr-ip-mib-00.txt" draft-ietf-rtgwg-ipfrr-ip-mib-00.txt"
REVISION "201203131200Z" -- Mar 13, 2012
DESCRIPTION
"Editorial changes. Added new type to ipFrrAltType."
REVISION "200502181200Z" -- February 18, 2005 REVISION "200502181200Z" -- February 18, 2005
DESCRIPTION DESCRIPTION
"Add Set operations on ipFrrAltTable" "Add Set operations on ipFrrAltTable"
REVISION "200502131200Z" -- February 13, 2005 REVISION "200502131200Z" -- February 13, 2005
DESCRIPTION DESCRIPTION
"Initial version." "Initial version."
::= { ip 999 } -- To be assigned by IANA ::= { ip ZZZ } -- To be assigned by IANA
-- RFC Ed.: replace 999 with actual RFC number -- RFC Ed.: replace 999 with actual RFC number
-- & remove this note -- & remove this note
-- Top level components of this MIB module. -- Top level components of this MIB module.
ipFrrMIBObjects OBJECT IDENTIFIER ::= { ipFrrMIB 1 } ipFrrMIBObjects OBJECT IDENTIFIER ::= { ipFrrMIB 1 }
ipFrrProtectStats OBJECT IDENTIFIER ::= { ipFrrMIBObjects 1 } ipFrrProtectStats OBJECT IDENTIFIER ::= { ipFrrMIBObjects 1 }
-- the IP FRR MIB-Group -- the IP FRR MIB-Group
skipping to change at page 8, line 49 skipping to change at page 8, line 49
ipFrrAltNextHopType OBJECT-TYPE ipFrrAltNextHopType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the ipFrrNextHop address, as defined "The type of the ipFrrNextHop address, as defined
in the InetAddress MIB. in the InetAddress MIB.
Only those address types that may appear in an actual Only those address types that may appear in an actual
routing table are allowed as values of this object." routing table are allowed as values of this object."
REFERENCE "RFC 3291" REFERENCE "RFC 4001"
::= { ipFrrAltEntry 1 } ::= { ipFrrAltEntry 1 }
ipFrrAltNextHop OBJECT-TYPE ipFrrAltNextHop OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the next system along the alternate "The address of the next system along the alternate
route. route.
The type of this address is determined by the value The type of this address is determined by the value
of the ipFrrAltNextHopType." of the ipFrrAltNextHopType."
::= { ipFrrAltEntry 2 } ::= { ipFrrAltEntry 2 }
ipFrrAltIfIndex OBJECT-TYPE ipFrrAltIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value which identifies the local "The ifIndex value which identifies the local
interface through which the next hop of this interface through which the next hop of this
alternate route should be reached." alternate route should be reached."
::= { ipFrrAltEntry 3 } ::= { ipFrrAltEntry 3 }
ipFrrAltType OBJECT-TYPE ipFrrAltType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other (1), -- type not defined other (1), -- type not defined
equalCost (2), -- primary path equalCost (2), -- primary path
loopFree (3), -- loop free alternate loopFree (3), -- loop free alternate
uTurn (4) -- u-turn alternate MRT (4) -- Maximally Redundant Trees
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of alternate which is provided by the "The type of alternate which is provided by the
alternate next-hop. The supported types are as alternate next-hop. The supported types are as
follows: follows:
equalCost : The alternate next-hop is another equalCost : The alternate next-hop is another
primary next-hop. primary next-hop.
loopFree : The shortest route to the destination loopFree : The shortest route to the destination
IP address from the alternate next-hop IP address from the alternate next-hop
does not traverse this system. See does not traverse this system. See
draft-ietf-rtgwg-ipfrr-spec-base-04. draft-ietf-rtgwg-ipfrr-spec-base-04.
uTurn : The alternate next system, which is
indicated by the alternate next-hop, has
itself a primary path that traverses this
system but also has an alternate next-hop
for this route that does not traverse this
system. See
draft-atlas-ip-local-protect-uturn-02.
other : The mechanism by which the alternate next-hop other : The mechanism by which the alternate next-hop
can be used is not specified." can be used is not specified.
MRT : Maximally Redundant Trees, where each
destination has two MRTs associated with it.
These two trees are referred as blue and red
MRTs.
See draft-ietf-rtgwg-mrt-frr-architecture-00.
"
::= { ipFrrAltEntry 4 } ::= { ipFrrAltEntry 4 }
ipFrrAltProtectionAvailable OBJECT-TYPE ipFrrAltProtectionAvailable OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
nodeProtect(0), nodeProtect(0),
linkProtect(1), linkProtect(1),
unknownProtection(2) unknownProtection(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 11, line 47 skipping to change at page 11, line 47
IpFrrNoAltEntry ::= SEQUENCE { IpFrrNoAltEntry ::= SEQUENCE {
ipFrrNoAltCause INTEGER ipFrrNoAltCause INTEGER
} }
ipFrrNoAltCause OBJECT-TYPE ipFrrNoAltCause OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ipFrrUnavailable (1), -- No valid alternate(s) ipFrrUnavailable (1), -- No valid alternate(s)
localAddress (2), -- local/internal address localAddress (2), -- local/internal address
ipFrrDisabled (3), -- Protection not enabled ipFrrDisabled (3), -- Protection not enabled
ipFrrUturnDisabled (4), -- Protection not enabled other (4) -- unknown or other cause
other (5) -- unknown or other cause
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For valid routes without an alternate next-hop, this "For valid routes without an alternate next-hop, this
object enumerates the reason why no protection is object enumerates the reason why no protection is
available. The possibilities are as follows. available. The possibilities are as follows.
ipFrrUnavailable : The supported IP Fast-Reroute ipFrrUnavailable : The supported IP Fast-Reroute
mechanisms could not find a safe mechanisms could not find a safe
alternate next-hop. alternate next-hop.
localAddress : The route represents a local address. localAddress : The route represents a local address.
This system is the destination so no This system is the destination so no
alternate path is possible or necessary. alternate path is possible or necessary.
ipFrrDisabled : Finding of alternate next-hops is ipFrrDisabled : Finding of alternate next-hops is
operationally disabled. operationally disabled.
ipFrrUturnDisabled : Finding of u-turn alternate
next-hops is operationally disabled. No
loop-free alternate could be found. See
draft-atlas-ip-local-protect-uturn-02
other : The reason is unknown or different from those other : The reason is unknown or different from those
specifically enumerated possible causes." specifically enumerated possible causes."
::= { ipFrrNoAltEntry 1 } ::= { ipFrrNoAltEntry 1 }
-- conformance information -- conformance information
ipFrrMIBConformance ipFrrMIBConformance
OBJECT IDENTIFIER ::= { ipFrrMIB 2 } OBJECT IDENTIFIER ::= { ipFrrMIB 2 }
ipFrrMIBCompliances ipFrrMIBCompliances
skipping to change at page 15, line 19 skipping to change at page 15, line 19
ipFrrNodeProtectedRoutes, ipFrrNodeProtectedRoutes,
ipFrrAltIfIndex, ipFrrAltIfIndex,
ipFrrAltType, ipFrrAltType,
ipFrrAltProtectionAvailable, ipFrrAltProtectionAvailable,
ipFrrAltMetric1, ipFrrAltMetric1,
ipFrrAltStatus, ipFrrAltStatus,
ipFrrNoAltCause ipFrrNoAltCause
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entire collection of objects defined in "The entire collection of objects defined in
this MIB for management of IP Fast Reroute ." this MIB for management of IP Fast Reroute ."
::= { ipFrrMIBGroups 1 } ::= { ipFrrMIBGroups 1 }
END END
4. Security Considerations 4. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. The ipFrrAltTable contains routing and network operations. The ipFrrAltTable contains routing and
forwarding information that is critical to the operation of the forwarding information that is critical to the operation of the
network in the event of a local failure. Allowing unauthenticated network in the event of a local failure. Allowing unauthenticated
write access to this table can compromise the validity of the write access to this table can compromise the validity of the
skipping to change at page 16, line 43 skipping to change at page 16, line 43
authentication and privacy). authentication and privacy).
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
[I-D.ietf-ipv6-rfc2096-update] 5.1 Normative References
Wasserman, M. and B. Haberman, "IP Forwarding Table MIB",
draft-ietf-ipv6-rfc2096-update-07 (work in progress),
February 2004.
[I-D.ietf-rtgwg-ipfrr-framework] [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Shand, M. and S. Bryant, "IP Fast Reroute Framework", Requirement Levels", BCP 14, RFC 2119, March 1997.
draft-ietf-rtgwg-ipfrr-framework-05 (work in progress),
March 2006.
[I-D.ietf-rtgwg-ipfrr-spec-base] [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Atlas, A. and A. Zinin, Ed., "Basic Specification for IP MIB", RFC 2863, June 2000.
Fast-Reroute: Loop-free Alternates",
draft-ietf-rtgwg-ipfrr-spec-base-05.txt (work in
progress), February 2006.
[IPFRR-UTURN] [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Atlas, A., Ed., "U-Turn Alternates for IP/LDP Local Schoenwaelder, "Textual Conventions for Internet
Protection", draft-atlas-ip-local-protect-uturn-03.txt Network
(work in progress), February 2006. Addresses", RFC 4001, February 2005.
[RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292,
April 2006.
[RFC4293] Routhier, S., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, April 2006.
[RFC5286] Atlas, A. and A. Zinin, "Basic Specification for IP Fast
Reroute: Loop-Free Alternates", RFC 5286, September 2008.
5.2 Informative References
[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.
[RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and
B. Thomas, "LDP Specification", RFC 3036, January 2001.
[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 [RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas,
Ed., "LDP Specification", RFC 5036, October 2007.
Alia K. Atlas (editor) [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework",
Google, Inc. RFC 5714, January 2010.
1600 Amphitheatre Parkway
Mountain View, CA 94043
USA
Email: akatlas@alum.mit.edu 6. IANA Considerations
Bill Anderson The MIB module in this document uses the following IANA-assigned
Avici Systems, Inc. OBJECT IDENTIFIER value recorded in the SMI Numbers registry.
101 Billerica Avenue
N. Billerica, MA 01862
USA
Phone: +1 978 964 2679 The IANA is requested to assign { ip ZZZ } to the
Email: wanderson@avici.com IPFRR-MIB MIB module specified in this document.
Don Fedyk Editor's Note (to be removed prior to publication): the IANA is
Nortel Networks requested to assign a value for "ZZZ" under
600 Technology Park the ip subtree and to record the assignments in the SMI Numbers
Billerica, MA 01821 registry. When the assignments have been made, the RFC Editor is
asked to replace "ZZZ" (here and in the MIB
modules) with the assigned value and to remove this note.
Authors' Addresses
Alia Atlas
Juniper Networks
10 Technology Park Drive
Westford, MA 01886
USA USA
Phone: +1 978 288 3041 Email: akatlas@juniper.net
Email: dwfedyk@nortel.com
Intellectual Property Statement A S Kiran Koushik (Ed.)
Cisco Systems Inc.
12515 Research Blvd, Bldg 4,
Austin, TX 78759
USA
The IETF takes no position regarding the validity or scope of any Email: kkoushik@cisco.com
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
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any John Flick (Ed.)
assurances of licenses to be made available, or the result of an Hewlett-Packard Company
attempt made to obtain a general license or permission for the use of 8000 Foothills Blvd.
such proprietary rights by implementers or users of this Roseville, CA 95747-5557
specification can be obtained from the IETF on-line IPR repository at USA
http://www.ietf.org/ipr. Email: john.flick@hp.com
The IETF invites any interested party to bring to its attention any Acknowledgements
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.
Disclaimer of Validity The authors would like to acknowledge contributions made by
Bill Anderson and Don Fedyk and thank them.
This document and the information contained herein are provided on an Full Copyright Statement
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
Copyright (C) The Internet Society (2006). This document is subject This document is subject to BCP 78 and the IETF Trust's Legal
to the rights, licenses and restrictions contained in BCP 78, and Provisions Relating to IETF Documents
except as set forth therein, the authors retain all their rights. (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
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s)
controlling the copyright in such materials, this document may not
be modified outside the IETF Standards Process, and derivative
works of it may not be created outside the IETF Standards Process,
except to format it for publication as an RFC or to translate it
into languages other than English.
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. 58 change blocks. 
145 lines changed or deleted 145 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/