IP MIB for IP Fast-Reroute
draft-ietf-rtgwg-ipfrr-ip-mib-03
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (rtgwg WG)
|
|
Last updated |
|
2014-05-27
|
|
Replaces |
|
draft-atlas-rtgwg-ipfrr-ip-mib
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Routing Area Working Group A. Atlas
Internet-Draft Juniper Networks
Intended status: Standards Track K. Koushik
Expires: November 28, 2014 Cisco Systems
J. Flick
Hewlett-Packard
S. Litkowski
Orange
May 27, 2014
IP MIB for IP Fast-Reroute
draft-ietf-rtgwg-ipfrr-ip-mib-03
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 [RFC5714]
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on November 28, 2014.
Atlas, et al. Expires November 28, 2014 [Page 1]
Internet-Draft ipfrr-mib May 2014
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. The SNMP Management Framework . . . . . . . . . . . . . . 3
2. Brief description of MIB Objects . . . . . . . . . . . . . . 3
2.1. ipFrrProtectStats Group . . . . . . . . . . . . . . . . . 3
2.2. ipFrrInstanceTable . . . . . . . . . . . . . . . . . . . 4
2.3. ipFrrIfTable . . . . . . . . . . . . . . . . . . . . . . 4
2.4. ipFrrProtectStatsTable . . . . . . . . . . . . . . . . . 4
2.5. ipFrrAltTable . . . . . . . . . . . . . . . . . . . . . . 4
2.6. ipFrrNoAltTable . . . . . . . . . . . . . . . . . . . . . 4
3. IP Fast-Reroute MIB Module Definitions . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 23
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.1. Normative References . . . . . . . . . . . . . . . . . . 25
7.2. Informative References . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
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 [RFC5714] and [RFC5286].
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.
Atlas, et al. Expires November 28, 2014 [Page 2]
Internet-Draft ipfrr-mib May 2014
There are certain configuration attributes for IP Fast-Reroute that
Show full document text