Network Working Group A. Atlas, Ed.
Internet-Draft B. Anderson
Expires: August 21, 2005 Avici Systems, Inc.
D. Fedyk
Nortel Networks
February 20, 2005
IP MIB for IP Fast-Reroute
draft-atlas-rtgwg-ipfrr-ip-mib-01
Status of this Memo
This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. 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 become aware will be disclosed, in accordance with
RFC 3668.
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.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 21, 2005.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This draft 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 relevant for IP routes
using IP Fast-Reroute [IPFRR].
Atlas, et al. Expires August 21, 2005 [Page 1]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 The SNMP Management Framework . . . . . . . . . . . . . . 3
2. Brief Description of MIB Objects . . . . . . . . . . . . . . . 4
2.1 ipFrrProtectStats Group . . . . . . . . . . . . . . . . . 4
2.2 ipFrrAltTable . . . . . . . . . . . . . . . . . . . . . . 4
2.3 ipFrrNoAltTable . . . . . . . . . . . . . . . . . . . . . 4
3. IP Fast-Reroute MIB Module Definitions . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 16
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . 19
Atlas, et al. Expires August 21, 2005 [Page 2]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
1. Introduction
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community. In particular, it defines the managed objects used for IP
routes and interfaces in relation to IP Fast-Reroute. This document
uses terminology from [FRAMEWORK], [IPFRR] and [IPFRR-UTURN].
Current work is underway to define mechanisms for determining
alternate paths for traffic to use when the original path becomes
unavailable due to a local failure. The alternate next-hops can be
computed in the context of any IGP.
There are certain configuration attributes for IP Fast-Reroute that
should be configured to enable IP Fast Reroute in the context of the
IGP. These configuration attributes of IP Fast-Reroute are not
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 the desired local hold-down timer[IPFRR], 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
alternate next-hops computed by IP Fast-Reroute. An example would be
MPLS traffic whose path is configured via LDP[RFC3036]. The
additional details (for example, outgoing MPLS label) pertaining to
alternate next-hops that are required by such traffic are not covered
by this MIB module.
An IP route may be reachable via multiple primary next-hops which
provide equal-cost paths. Where IP Fast-Reroute is enabled, each
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.
1.1 The SNMP Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
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
[RFC2580].
Atlas, et al. Expires August 21, 2005 [Page 3]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
2. Brief Description of MIB Objects
This MIB module consists of five global objects, organized into the
ipFrrProtectStats group, and two tables.
2.1 ipFrrProtectStats Group
The global objects in this group provide summary information related
to protection for all IP routes. The information available includes
counts of all routes, of all protected routes, of all unprotected
routes, of all routes which are protected against a link failure, and
of all routes which are protected against a node failure.
2.2 ipFrrAltTable
The ipFrrAltTable extends the inetCidrRouteTable[RFC2096-update] to
provide information about each alternate next-hop associated with a
primary next-hop used by a route. Statically configured alternate
next-hops associated with primary next-hops can be created.
2.3 ipFrrNoAltTable
The ipFrrNoAltTable extends the inetCidrRouteTable[RFC2096-update] to
provide information about the routes which do not have an alternate
next-hop associated with any of the route's primary next-hop. The
entry provides an explanation for the lack of protection.
Atlas, et al. Expires August 21, 2005 [Page 4]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
3. IP Fast-Reroute MIB Module Definitions
IPFRR-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Gauge32,
Integer32 FROM SNMPv2-SMI -- [RFC2578]
RowStatus
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
InetAddressType,
InetAddressPrefixLength,
InetAddress FROM INET-ADDRESS-MIB -- [RFC3291]
ifIndex,
InterfaceIndex FROM IF-MIB -- [RFC2863]
ip FROM IP-MIB -- [RFC2011]
inetCidrRouteDestType,
inetCidrRouteDest,
inetCidrRoutePfxLen,
inetCidrRoutePolicy,
inetCidrRouteNextHopType,
inetCidrRouteNextHop FROM IP-FORWARD-MIB
-- [draft-ietf-ipv6-rfc2096-update-07]
;
ipFrrMIB MODULE-IDENTITY
LAST-UPDATED "200502181200Z" -- February 18, 2005
ORGANIZATION "draft-atlas-ipfrr-ip-mib-01.txt"
CONTACT-INFO
" Bill Anderson
Avici Systems, Inc.
EMail: wanderson@avici.com
Alia Atlas
Avici Systems, Inc.
Email: aatlas@avici.com
Don Fedyk
Atlas, et al. Expires August 21, 2005 [Page 5]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
Nortel Networks
Email: dwfedyk@nortel.com
"
DESCRIPTION
"IP MIB module for management of IP Fast-Reroute.
Copyright (C) The Internet Society (date).
This version of this MIB module is part of
draft-atlas-rtgwg-ipfrr-ip-mib-00.txt"
REVISION "200502181200Z" -- February 18, 2005
DESCRIPTION
"Add Set operations on ipFrrAltTable"
REVISION "200502131200Z" -- February 13, 2005
DESCRIPTION
"Initial version."
::= { ip 999 } -- To be assigned by IANA
-- RFC Ed.: replace 999 with actual RFC number
-- & remove this note
-- Top level components of this MIB module.
ipFrrMIBObjects OBJECT IDENTIFIER ::= { ipFrrMIB 1 }
ipFrrProtectStats OBJECT IDENTIFIER ::= { ipFrrMIBObjects 1 }
-- the IP FRR MIB-Group
-- A collection of objects providing summarized information
-- about the protection availability and type of alternate paths
-- provided by IP Fast-Reroute mechanisms.
ipFrrTotalRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of valid routes known by this entity."
::= { ipFrrProtectStats 1 }
ipFrrUnprotectedRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of valid routes known by this entity
which do not have an alternate next-hop associated
with any primary next-hop."
Atlas, et al. Expires August 21, 2005 [Page 6]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
::= { ipFrrProtectStats 2 }
ipFrrProtectedRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes known by this entity
which have at least one alternate next-hop."
::= { ipFrrProtectStats 3 }
ipFrrLinkProtectedRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes known by this entity
for which all alternate next-hops provide link
protection for their associated primary next-hops."
::= { ipFrrProtectStats 4 }
ipFrrNodeProtectedRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes known by this entity
for which all alternate next-hops provide node
protection for their associated primary next-hops."
::= { ipFrrProtectStats 5 }
-- the IP FRR Alternate MIB-Group
--
-- The ipFrrAltTable extends the inetCidrRouteTable to indicate
-- the alternate next-hop(s) associated with each primary
-- next-hop. The additional indices (ipFrrAltNextHopType and
-- ipFrrAltNextHop ) allow for multiple alternate paths for a
-- given primary next-hop.
ipFrrAltTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpFrrAltEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This entity's IP Fast Reroute Alternates table."
::= { ipFrrMIBObjects 2 }
ipFrrAltEntry OBJECT-TYPE
Atlas, et al. Expires August 21, 2005 [Page 7]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
SYNTAX IpFrrAltEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing information on a particular route,
one of its particular (primary) next-hops and one of
the associated alternate next-hops.
Implementers need to be aware that if the total
number of elements (octets or sub-identifiers) in
inetCidrRouteDest, inetCidrRoutePolicy,
inetCidrRouteNextHop, and ipFrrAltNextHop exceeds 107
then OIDs of column instances in this table will have
more than 128 sub-identifiers and cannot be accessed
using SNMPv1, SNMPv2c, or SNMPv3."
INDEX { inetCidrRouteDestType,
inetCidrRouteDest,
inetCidrRoutePfxLen,
inetCidrRoutePolicy,
inetCidrRouteNextHopType,
inetCidrRouteNextHop,
ipFrrAltNextHopType,
ipFrrAltNextHop
}
::= { ipFrrAltTable 1 }
IpFrrAltEntry ::= SEQUENCE {
ipFrrAltNextHopType InetAddressType,
ipFrrAltNextHop InetAddress,
ipFrrAltIfIndex InterfaceIndex,
ipFrrAltType INTEGER,
ipFrrAltProtectionAvailable BITS,
ipFrrAltMetric1 Integer32,
ipFrrAltStatus RowStatus
}
ipFrrAltNextHopType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The type of the ipFrrNextHop address, as defined
in the InetAddress MIB.
Only those address types that may appear in an actual
routing table are allowed as values of this object."
REFERENCE "RFC 3291"
Atlas, et al. Expires August 21, 2005 [Page 8]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
::= { ipFrrAltEntry 1 }
ipFrrAltNextHop OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the next system along the alternate
route.
The type of this address is determined by the value
of the ipFrrAltNextHopType."
::= { ipFrrAltEntry 2 }
ipFrrAltIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The ifIndex value which identifies the local
interface through which the next hop of this
alternate route should be reached."
::= { ipFrrAltEntry 3 }
ipFrrAltType OBJECT-TYPE
SYNTAX INTEGER {
other (1), -- type not defined
equalCost (2), -- primary path
loopFree (3), -- loop free alternate
uTurn (4) -- u-turn alternate
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of alternate which is provided by the
alternate next-hop. The supported types are as
follows:
equalCost : The alternate next-hop is another
primary next-hop.
loopFree : The shortest route to the destination
IP address from the alternate next-hop
does not traverse this system.
uTurn : The alternate next system, which is
indicated by the alternate next-hop, has
itself a primary path that traverses this
Atlas, et al. Expires August 21, 2005 [Page 9]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
system but also has an alternate next-hop
for this route that does not traverse this
system.
other : The mechanism by which the alternate next-hop
can be used is not specified."
::= { ipFrrAltEntry 4 }
ipFrrAltProtectionAvailable OBJECT-TYPE
SYNTAX BITS {
nodeProtect(0),
linkProtect(1),
unknownProtection(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the scope of protection for
which this alternate next-hop can provide failure
protection. The alternate next-hop should provide
one or more of node-protection and link-protection.
If the protection provided by the alternate next-hop
is unknown, then only unknownProtection should be
specified. Specifying uknownProtection with any
other type of protection is not supported. "
::= { ipFrrAltEntry 5 }
ipFrrAltMetric1 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This is the primary routing metric for this
alternate path to the destination IP address.
If the alternate path metric is unknown, the value
should be set to -1."
::= { ipFrrAltEntry 6 }
ipFrrAltStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The row status variable, used according to
row installation and removal conventions."
::= { ipFrrAltEntry 7 }
Atlas, et al. Expires August 21, 2005 [Page 10]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
-- the IP FRR No Alternate MIB-Group
--
-- The ipFrrNoAltTable extends the inetCidrRouteTable
-- to indicate which routes are unprotected and the reason
-- why. The indices do not include the primary next-hop because
-- the lack of protection is for the route. This allows easy
-- access to the set of unprotected routes that would be
-- affected by a local failure of their primary next-hop.
ipFrrNoAltTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpFrrNoAltEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This entity's IP Fast Reroute Unprotected Routes
table."
::= { ipFrrMIBObjects 3 }
ipFrrNoAltEntry OBJECT-TYPE
SYNTAX IpFrrNoAltEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing the reason why a route does not
have an alternate next-hop. The existence of an
entry for a route indicates that there is no
alternate next-hop."
INDEX { inetCidrRouteDestType,
inetCidrRouteDest,
inetCidrRoutePfxLen
}
::= { ipFrrNoAltTable 1 }
IpFrrNoAltEntry ::= SEQUENCE {
ipFrrNoAltCause INTEGER
}
ipFrrNoAltCause OBJECT-TYPE
SYNTAX INTEGER {
ipFrrUnavailable (1), -- No valid alternate(s)
localAddress (2), -- local/internal address
ipFrrDisabled (3), -- Protection not enabled
ipFrrUturnDisabled (4), -- Protection not enabled
other (5) -- unknown or other cause
}
MAX-ACCESS read-only
STATUS current
Atlas, et al. Expires August 21, 2005 [Page 11]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
DESCRIPTION
"For valid routes without an alternate next-hop, this
object enumerates the reason why no protection is
available. The possibilities are as follows.
ipFrrUnavailable : The supported IP Fast-Reroute
mechanisms could not find a safe
alternate next-hop.
localAddress : The route represents a local address.
This system is the destination so no
alternate path is possible or necessary.
ipFrrDisabled : Finding of alternate next-hops is
operationally disabled.
ipFrrUturnDisabled : Finding of u-turn alternate
next-hops is operationally disabled. No
loop-free alternate could be found.
other : The reason is unknown or different from those
specifically enumerated possible causes."
::= { ipFrrNoAltEntry 1 }
-- conformance information
ipFrrMIBConformance
OBJECT IDENTIFIER ::= { ipFrrMIB 2 }
ipFrrMIBCompliances
OBJECT IDENTIFIER ::= { ipFrrMIBConformance 1 }
ipFrrMIBGroups
OBJECT IDENTIFIER ::= { ipFrrMIBConformance 2 }
-- compliance statements
ipFrrMIBCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"Minimum requirements to state conformity
to this MIB. Supporting only IP v4 addresses
This is deprecated in favor of
ipFrrMIBInetCompliance
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
Atlas, et al. Expires August 21, 2005 [Page 12]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
expressed in OBJECT clause form in this description:
OBJECT inetCidrRouteDestType
SYNTAX InetAddressType { ipv4(1), ipv4z(3) }
MIN-ACCESS read-only
DESCRIPTION
A (deprecated) complying implementation at this
level is required to support IPv4 addresses only.
This compliance level is defined so an
implementation only needs to support the addresses
it actually supports on the device.
OBJECT inetCidrRouteNextHopType
SYNTAX InetAddressType { ipv4(1), ipv4z(3) }
MIN-ACCESS read-only
DESCRIPTION
A (deprecated) complying implementation at this
level is required to support IPv4 addresses only.
This compliance level is defined so an
implementation only needs to support the addresses
it actually supports on the device.
OBJECT ipFrrAltNextHopType
SYNTAX InetAddressType { ipv4(1), ipv4z(3) }
MIN-ACCESS read-only
DESCRIPTION
A (deprecated) complying implementation at this
level is required to support IPv4 addresses only.
This compliance level is defined so an
implementation only needs to support the
addresses it actually supports on the device.
"
MODULE -- this module
MANDATORY-GROUPS { ipFrrBasicGroup }
::= { ipFrrMIBCompliances 1 }
ipFrrMIBInetCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Full conformity to this MIB."
MODULE -- this module
MANDATORY-GROUPS { ipFrrBasicGroup }
OBJECT apsConfigRowStatus
SYNTAX INTEGER { active(1) }
WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
Atlas, et al. Expires August 21, 2005 [Page 13]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
DESCRIPTION
"Support for createAndWait and notInService is not
required."
::= { ipFrrMIBCompliances 2 }
ipFrrReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"When this MIB is implemented without support for
read-create (i.e. in read-only mode), then that
implementation can claim read-only compliance. In that
case, ipFrrAlt group can be monitored but cannot be
configured with this MIB."
MODULE
MANDATORY-GROUPS { ipFrrBasicGroup }
OBJECT ipFrrAltIfIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT ipFrrAltType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT ipFrrAltProtectionAvailable
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT ipFrrAltMetric1
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT ipFrrAltStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { ipFrrMIBCompliances 3 }
-- units of conformance
Atlas, et al. Expires August 21, 2005 [Page 14]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
ipFrrBasicGroup OBJECT-GROUP
OBJECTS {ipFrrTotalRoutes,
ipFrrUnprotectedRoutes,
ipFrrProtectedRoutes,
ipFrrLinkProtectedRoutes,
ipFrrNodeProtectedRoutes,
ipFrrAltIfIndex,
ipFrrAltType,
ipFrrAltProtectionAvailable,
ipFrrAltMetric1,
ipFrrAltStatus,
ipFrrNoAltCause
}
STATUS current
DESCRIPTION
"The entire collection of objects defined in
this MIB for management of IP Fast Reroute ."
::= { ipFrrMIBGroups 1 }
END
Atlas, et al. Expires August 21, 2005 [Page 15]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
4. Security Considerations
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
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 a negative effect on
network operations. The ipFrrAltTable contains routing and
forwarding information that is critical to the operation of the
network in the event of a local failure. Allowing unauthenticated
write access to this table can compromise the validity of the
alternate forwarding information.
Some of the readable objects in this MIB module (i.e. objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET access to these objects and possibly to even encrypt
the values of these objects when sending them over the network via
SNMP.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET 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 mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. 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 access to
the objects only to those principals (users) that have legitimate
rights to indeed GET them.
5 References
[FRAMEWORK]
Shand, M., "IP Fast Reroute Framework",
draft-ietf-rtgwg-ipfrr-framework-02.txt (work in
progress), October 2004.
[IPFRR] Atlas, A., "Basic Specification for IP Fast-Reroute:
Loop-free Alternates",
draft-ietf-rtgwg-ipfrr-spec-base-02.txt (work in
Atlas, et al. Expires August 21, 2005 [Page 16]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
progress), January 2005.
[IPFRR-UTURN]
Atlas, A., "U-Turn Alternates for IP/LDP Local
Protection", draft-atlas-ip-local-protect-uturn-02.txt
(work in progress), February 2005.
[RFC2096] Baker, F., "IP Forwarding Table MIB", RFC 2096, January
1997.
[RFC2096-update]
Haberman, B., "IP Forwarding Table MIB",
draft-ietf-ipv6-rfc2096-update-07.txt (work in progress),
February 2004.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
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
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,
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
Atlas, et al. Expires August 21, 2005 [Page 17]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
Authors' Addresses
Alia K. Atlas (editor)
Avici Systems, Inc.
101 Billerica Avenue
N. Billerica, MA 01862
USA
Phone: +1 978 964 2070
EMail: aatlas@avici.com
Bill Anderson
Avici Systems, Inc.
101 Billerica Avenue
N. Billerica, MA 01862
USA
Phone: +1 978 964 2679
EMail: wanderson@avici.com
Don Fedyk
Nortel Networks
600 Technology Park
Billerica, MA 01821
USA
Phone: +1 978 288 3041
EMail: dwfedyk@nortel.com
Atlas, et al. Expires August 21, 2005 [Page 18]
Internet-Draft draft-atlas-rtgwg-ipfrr-ip-mib-01 February 2005
Intellectual Property Statement
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
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
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.
Disclaimer of Validity
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 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) The Internet Society (2005). 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.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Atlas, et al. Expires August 21, 2005 [Page 19]