RIP-2 final draft
Gary Scott Malkin <gmalkin@xylogics.com> Mon, 27 July 1992 18:42 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa11961;
27 Jul 92 14:42 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa11957;
27 Jul 92 14:42 EDT
Received: from harvard.harvard.edu by NRI.Reston.VA.US id aa15232;
27 Jul 92 14:42 EDT
Received: by harvard.harvard.edu (5.54/a0.25)
(for IETF-archive@nri.reston.va.us) id AA22509; Mon, 27 Jul 92 14:36:46 EDT
Received: by Xylogics.COM (4.12/4.7_jlv1/7/90)
id AA08343; Mon, 27 Jul 92 14:38:21 edt
Received: by Xylogics.COM (4.12/4.7_jlv1/7/90)
id AA04965; Mon, 27 Jul 92 14:36:50 edt
Date: Mon, 27 Jul 92 14:36:50 edt
From: Gary Scott Malkin <gmalkin@xylogics.com>
Message-Id: <9207271836.AA04965@Xylogics.COM>
To: internet-drafts@NRI.Reston.VA.US
Cc: hinden@eng.sun.com, gvaudre@NRI.Reston.VA.US, jrd@thyme.lcs.mit.edu,
ietf-rip@xylogics.com
Subject: RIP-2 final draft
This are the final drafts of the RIP-2 and RIP-2 MIB documents.
As chair of the RIP-2 WG, I would like to submit these documents
into the standards track.
----------------------------------------------------------------------
Gary Malkin Humankind asks: "Why are we here?"
(617) 272-8140 Earth responds: "PLASTIC, morons."
======================================================================
Internet Engineering Task Force G. Malkin
Internet Draft Xylogics
Updates RFC 1058 July 1992
RIP Version 2
Carrying Additional Information
Abstract
This document specifies an extension of the Routing Information
Protocol (RIP), as defined in [1], to expand the amount of useful
information carried in RIP packets and to add a measure of security.
A companion document will define the SNMP MIB objects for RIP-2 [2].
Status of this Memo
This document is an Internet Draft. 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. Internet Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet
Drafts as reference material or to cite them other than as a "working
draft" or "work in progress."
Please check the I-D abstract listing contained in each Internet
Draft directory to learn the current status of this or any other
Internet Draft.
It is intended that this document will be submitted to the IESG for
consideration as a standards document. Distribution of this document
is unlimited.
Acknowledgements
I would like to thank the following for their contributions to this
document: Fred Baker, Noel Chiappa and Vince Fuller.
Expiration: February 16, 1992 [Page 1]
Internet Draft RIP Version 2 July 1992
Table of Contents
1. Justification . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Current RIP . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 3
3.1 Authentication . . . . . . . . . . . . . . . . . . . . . . . 4
3.2 Routing Domain . . . . . . . . . . . . . . . . . . . . . . . 5
3.3 Route Tag . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.4 Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.5 Next Hop . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.6 Multicasting . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1 Compatibility Switch . . . . . . . . . . . . . . . . . . . . 7
4.2 Authentication . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Larger Infinity . . . . . . . . . . . . . . . . . . . . . . . 7
4.4 Addressless Links . . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
Appendicies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
References . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .10
Expiration: February 16, 1992 [Page 2]
Internet Draft RIP Version 2 July 1992
1. Justification
With the advent of OSPF and IS-IS, there are those who believe that
RIP is obsolete. While it is true that the newer IGP routing
protocols are far superior to RIP, RIP does have some advantages.
Primarily, in a small network, RIP has very little overhead in terms
of bandwidth used and configuration and management time. RIP is also
very easy to implement, especially in relation to the newer IGPs.
Additionally, there are many, many more RIP implementations in the
field than OSPF and IS-IS combined. It is likely to remain that way
for some years yet.
Given that RIP will be useful in many environments for some period of
time, it is reasonable to increase RIP's usefulness. This is
especially true since the gain is far greater than the expense of the
change.
2. Current RIP
The current RIP packet contains the minimal amount of information
necessary for routers to route packets through a network. It also
contains a large amount of unused space, owing to its origins.
The current RIP protocol does not consider autonomous systems and
IGP/EGP interactions, subnetting, and authentication since
implementations of these postdate RIP. The lack of subnet masks is a
particularly serious problem for routers since they need a subnet
mask to know how to determine a route. If a RIP route is a network
route (all non-network bits 0), the subnet mask equals the network
mask. However, if some of the non-network bits are set, the router
cannot determine the subnet mask. Worse still, the router cannot
determine if the RIP route is a subnet route or a host route.
Currently, some routers simply choose the subnet mask of the
interface over which the route was learned and determine the route
type from that.
3. Protocol Extensions
This document does not change the RIP protocol per se. Rather, it
provides extensions to the datagram format which allows routers to
share important additional information.
Expiration: February 16, 1992 [Page 3]
Internet Draft RIP Version 2 July 1992
The new RIP datagram format is:
0 1 2 3 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Command (1) | Version (1) | Routing Domain (2) |
+---------------+---------------+-------------------------------+
| Address Family Identifier (2) | Route Tag (2) |
+-------------------------------+-------------------------------+
| IP Address (4) |
+---------------------------------------------------------------+
| Subnet Mask (4) |
+---------------------------------------------------------------+
| Next Hop (4) |
+---------------------------------------------------------------+
| Metric (4) |
+---------------------------------------------------------------+
The Command, Address Family Identifier (AFI), IP Address, and Metric
all have the meanings defined in RFC 1058.
The Version field will specify version number 2 for RIP datagrams
which use authentication or carry information in any of the newly
defined fields.
3.1 Authentication
Since authentication is a per packet function, and since there is
only one 2-byte field available in the packet header, and since any
reasonable authentication scheme will require more than two bytes,
the authentication scheme for RIP version 2 will use the space of an
entire RIP entry. If the Address Family Identifier of the first (and
only the first) entry in the packet is 0xFFFF, then the remainder of
the entry contains the authentication. This means that there can be,
at most, 24 RIP entries in the remainder of the packet. If
authentication is not in use, then no entries in the packet should
have an Address Family Identifier of 0xFFFF. A RIP packet which
contains an authentication entry would have the following format:
0 1 2 3 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Command (1) | Version (1) | Routing Domain (2) |
+---------------+---------------+-------------------------------+
| 0xFFFF | Authentication Type (2) |
+-------------------------------+-------------------------------+
~ Authentication (16) ~
+---------------------------------------------------------------+
Expiration: February 16, 1992 [Page 4]
Internet Draft RIP Version 2 July 1992
Currently, the only Authentication Type is simple password and it
is type 2. The remaining 16 bytes contain the plain text password. If
the password is under 16 bytes, it must be left-justified and
padded to the right with nulls (0x00).
3.2 Routing Domain
The Routing Domain (RD) number is the number of the routing process to
which this update belongs. This field is used to associate the routing
update to a specific routing process on the receiving router. The RD
is needed to allow multiple, independent RIP "clouds" to co-exist on
the same physical wire. This gives administrators the ability to run
multiple, possibly parallel, instances of RIP in order to implement
simple policy. This means that a router operating within one routing
domain, or a set of routing domains, should ignore RIP packets which
belong to another routing domain. RD 0 is the default routing domain.
3.3 Route Tag
The Route Tag (RT) field exists as a support for EGPs. The contents
and use of this field are outside the scope of the this protocol. However,
any RIP system which receives a RIP entry which contains a non-zero
RT value must re-advertise that value. Those routes which have no
RT value must advertise an RT value of zero.
3.4 Subnet mask
The Subnet Mask field contains the subnet mask which is applied to
the IP address to yield the non-host portion of the address. If this
field is zero, then no subnet mask has been included for this entry.
For compatibility with RIP-1, it is necessary that RIP-1 subsumption
(see Appendix B) rules be followed in RIP-2. As a bottom line, a
route which RIP-2 believes is a subnet route may not, under any
circumstances, be viewed by RIP-1 systems as a host route. To achieve
this, the following applies:
1 - On an interface where the RIP-2 update is sent as a multicast, no
subsumption of routes is required. However, if any two network or
subnet routes have the same set of next hops and either:
(a) Have differing subnet masks, and one subnet subsumes the
other, or
(b) Have the same subnet mask, and the two IP Addresses differ
only in the least significant bit for which the Subnet Mask
bit is a 1,
then only one route needs to be advertised. In the former case,
Expiration: February 16, 1992 [Page 5]
Internet Draft RIP Version 2 July 1992
only the less restrictive network mask need be advertised, and in
the latter, the differing bit and its corresponding subnet mask bit
may be zeroed. Clearly, this operation is recursive.
2 - On an interface where a RIP-1 router may hear and operate on the
information, the subsumption rules of RFC 1058 must be obeyed;
information internal to another network number must never be
advertised into another network number, and information about a
more specific subnet may not be advertised where RIP-1 would
consider it a host route. In addition, the automatic subsumption
of routes in (b) above may not occur, as it would reduce route
information available.
RIP-1 compatibility is determined by the compatibility switch defined
in section 4.1.
3.5 Next Hop
The immediate next hop IP address to which packets to the destination
specified by this route entry should be forwarded. Specifying a
value of 0.0.0.0 in this field indicates that routing should be via
the originator of the RIP advertisement. An address specified as
a next hop must, per force, be directly reachable on the logical
subnet over which the advertisement is made.
The purpose of the Next Hop field is to eliminate packets being routed
through extra hops in the system. It is particularly useful when RIP
is not being run on all of the routers on a network. A simple example
is given in Appendix A. Note that Next Hop is an "advisory" field. That
is, if the provided information is ignored, a possibly sub-optimal,
but absolutely valid, route may be taken.
3.6 Multicasting
In order to reduce unnecessary load on those hosts which are not
listening to RIP-2 packets, an IP multicast address will be used for
periodic broadcasts. The IP multicast address is 224.0.0.9. Note that
IGMP is not needed since these are inter-router messages which are not
forwarded.
In order to maintain backwards compatibility, the use of the
multicast address will be configurable, as described in section 4.1. If
multicasting is used, it should be used on all interfaces which support
it.
Expiration: February 16, 1992 [Page 6]
Internet Draft RIP Version 2 July 1992
4. Compatibility
RFC 1058 showed considerable forethought in its explanation of
the handling of version numbers. It specifies that RIP packets of
version 0 are to be discarded, that RIP packets of version 1 are
to be discarded if any Must Be Zero (MBZ) field is non-zero, and that
RIP packets of any version greater than 1 should not be discarded
simply because an MBZ field contains a value other than zero. This
means that the new version of RIP is totally backwards compatible
with existing RIP implementations which adhere to this part of the
specification.
4.1 Compatibility Switch
A compatibility switch is necessary for three reasons. First, there
are implementations of RIP-1 in the field which do not follow RFC
1058 as described above. Second, the use of multicasting would
prevent RIP-1 systems from receiving RIP-2 updates (which may
be a desired feature in some cases). Third, the route subsumption
rules (see section 3.4) differ for RIP-1 and RIP-2 in their handling
of subnet routes.
The switch has three settings: RIP-1, in which only RIP-1 packets
are sent; RIP-1 compatibility, in which RIP-2 packets are broadcast
using RIP-1 subsumption rules; and RIP-2, in which RIP-2 packets are
multicast. The recommended default for this switch is RIP-1 compatibility.
4.2 Authentication
Since an authentication entry is marked with an Address Family
Identifier of 0xFFFF, a RIP-1 system would ignore this entry since
it would belong to an address family other than IP. It should
be noted, therefore, that use of authentication will not prevent
RIP-1 systems from seeing RIP-2 packets. If desired, this may
be done using multicasting, as described in sections 3.6 and 4.1.
4.3 Larger Infinity
While on the subject of compatibility, there is one item which people
have requested: increasing infinity. The primary reason that this
cannot be done is that it would violate backwards compatibility. A
larger infinity would obviously confuse older versions of rip. At
best, they would ignore the route as they would ignore a metric of
16. There was also a proposal to make the Metric a single byte and reuse
the high three bytes, but this would break any implementations which
treat the metric as a long.
Expiration: February 16, 1992 [Page 7]
Internet Draft RIP Version 2 July 1992
4.4 Addressless Links
As in RIP-1, addressless links will not be supported by RIP-2.
5. Security Considerations
The basic RIP protocol is not a secure protocol. To bring RIP-2
in line with more modern routing protocols, an extensible authentication
has been incorporated into the protocol enhancements. The authentication
method is described in section 3.1 of this document.
Expiration: February 16, 1992 [Page 8]
Internet Draft RIP Version 2 July 1992
Appendix A
This is a simple example of the use of the next hop field in a rip entry.
----- ----- ----- ----- ----- -----
|IR1| |IR2| |IR3| |XR1| |XR2| |XR3|
--+-- --+-- --+-- --+-- --+-- --+--
| | | | | |
--+-------+-------+---------------+-------+-------+--
<-------------RIP-2------------->
Assume that IR1, IR2, and IR3 are all "internal" routers which are
under one administration (e.g. a campus) which has elected to use
RIP-2 as its IGP. XR1, XR2, and XR3, on the other hand, are under
separate administration (e.g. a regional network, of which the campus
is a member) and are using some other routing protocol (e.g. OSPF).
XR1, XR2, and XR3 exchange routing information among themselves such
that they know that the best routes to networks N1 and N2 are via
XR1, to N3, N4, and N5 are via XR2, and to N6 and N7 are via XR3. By
setting the Next Hop field correctly (to XR2 for N3/N4/N5, to XR3 for
N6/N7), only XR1 need exchange RIP-2 routes with IR1/IR2/IR3 for
routing to occur without additional hops through XR1. Without the
Next Hop (for example, if RIP-1 were used) it would be necessary for
XR2 and XR3 to also participate in the RIP-2 protocol to eliminate
extra hops.
Appendix B
Route subsumption is basic to IP routing. The idea is to reduce the
amount of information other routers need to know in order to route
packets correctly. Here are generic and specific examples.
Consider the subnets A.B.C.0 and A.B.D.0, where D = C + 1. It would
only be necessary to advertise A.B.C.0 with a subnet mask one bit
shorter.
Consider the following specific example:
Address Mask Next hop
----------------------------------------
191.154.88.0 255.255.255.0 191.154.3.8 Subnet route 1
191.154.89.0 255.255.255.0 191.154.3.8 Subnet route 2
----------------------------------------
191.154.88.0 255.255.254.0 191.154.3.8 Advertised route
Expiration: February 16, 1992 [Page 9]
Internet Draft RIP Version 2 July 1992
References
[1] Hedrick, C., Routing Information Protocol, Request For Comments
(RFC) 1058, Rutgers University, June 1988.
[2] Malkin, G., and F. Baker, draft-ietf-ripv2-mibext-01.txt,
Xylogics, ACC, May 8, 1992.
Author's Address
Gary Scott Malkin
Xylogics, Inc.
53 Third Avenue
Burlington, MA 01803
Phone: (617) 272-8140
EMail: gmalkin@Xylogics.COM
Expiration: February 16, 1992 [Page 10]
======================================================================
Internet Draft RIP 2 MIB Extension July 1992
RIP Version 2 MIB Extension
July 6, 1992
Gary Malkin
Xylogics, Inc.
53 Third Avenue
Burlington, MA 01803
gmalkin@Xylogics.COM
Fred Baker
Advanced Computer Communications
315 Bollay Drive
Santa Barbara, California 93117-6014
fbaker@acc.com
_1. _S_t_a_t_u_s _o_f _t_h_i_s _M_e_m_o
This document is an Internet Draft. 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. Internet Drafts may be updated, replaced, or obsoleted
by other documents at any time. It is not appropriate to use
Internet Drafts as reference material or to cite them other
than as a "working draft" or "work in progress."
Please check the I-D abstract listing contained in each
Internet Draft directory to learn the current status of this
or any other Internet Draft.
It is intended that this document will be submitted to the
IESG for consideration as a standards document. Distribution
of this document is unlimited.
Please send comments to ietf-rip@xylogics.com.
Malkin and Baker Expires: 31Jan92 [Page 1]
Internet Draft RIP 2 MIB Extension July 1992
_2. _A_b_s_t_r_a_c_t
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management
protocols in TCP/IP-based internets. In particular, it
defines objects for managing RIP Version 2.
This memo does not specify a standard for the Internet
community.
_3. _T_h_e _N_e_t_w_o_r_k _M_a_n_a_g_e_m_e_n_t _F_r_a_m_e_w_o_r_k
The Internet-standard Network Management Framework consists of
three components. They are:
RFC 1155 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management.
RFC 1212 defines a more concise description mechanism, which
is wholly consistent with the SMI.
RFC 1156 which defines MIB-I, the core set of managed objects
for the Internet suite of protocols. RFC 1213 defines MIB-II,
an evolution of MIB-I based on implementation experience and
new operational requirements.
RFC 1157 which defines the SNMP, the protocol used for network
access to managed objects.
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
_4. _O_b_j_e_c_t_s
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the
MIB are defined using the subset of Abstract Syntax Notation
One (ASN.1) [7] defined in the SMI. In particular, each
object has a name, a syntax, and an encoding. The name is an
object identifier, an administratively assigned name, which
specifies an object type. The object type together with an
object instance serves to uniquely identify a specific
Malkin and Baker Expires: 31Jan92 [Page 2]
Internet Draft RIP 2 MIB Extension July 1992
instanciation of the object. For human convenience, we often
use a textual string, termed the OBJECT DESCRIPTOR, to also
refer to the object type.
The syntax of an object type defines the abstract data
structure corresponding to that object type. The ASN.1
language is used for this purpose. However, the SMI [3]
purposely restricts the ASN.1 constructs which may be used.
These restrictions are explicitly made for simplicity.
The encoding of an object type is simply how that object type
is represented using the object type's syntax. Implicitly
tied to the notion of an object type's syntax and encoding is
how the object type is represented when being transmitted on
the network.
The SMI specifies the use of the basic encoding rules of ASN.1
[8], subject to the additional requirements imposed by the
SNMP.
_4._1. _F_o_r_m_a_t _o_f _D_e_f_i_n_i_t_i_o_n_s
Section 6 contains contains the specification of all object
types contained in this MIB module. The object types are
defined using the conventions defined in the SMI, as amended
by the extensions specified in [9].
_5. _O_v_e_r_v_i_e_w
_5._1. _T_e_x_t_u_a_l _C_o_n_v_e_n_t_i_o_n_s
Several new data types are introduced as a textual convention
in this MIB document. These textual conventions enhance the
readability of the specification and can ease comparison with
other specifications if appropriate. It should be noted that
the introduction of the these textual conventions has no
effect on either the syntax nor the semantics of any managed
objects. The use of these is merely an artifact of the
explanatory method used. Objects defined in terms of one of
these methods are always encoded by means of the rules that
define the primitive type. Hence, no changes to the SMI or
the SNMP are necessary to accommodate these textual
Malkin and Baker Expires: 31Jan92 [Page 3]
Internet Draft RIP 2 MIB Extension July 1992
conventions which are adopted merely for the convenience of
readers and writers in pursuit of the elusive goal of clear,
concise, and unambiguous MIB documents.
The new data types are: Validation (the standard "set to
invalid causes deletion" type), and RouteTag. The RouteTag
type represents the contents of the Route Tag field in the
packet header or route entry.
_5._2. _S_t_r_u_c_t_u_r_e _o_f _M_I_B
The RIP-2 MIB contains global counters useful for detecting
the deleterious effects of RIP incompatibilities, an
"interfaces" table which contains interface-specific
statistics and configuration information, and an optional
"neighbor" table containing information that may be helpful in
debugging neighbor relationships. Like the protocol itself,
this MIB takes great care to preserve compatibility with RIP-1
systems, and controls for monitoring and controlling system
interactions.
Malkin and Baker Expires: 31Jan92 [Page 4]
Internet Draft RIP 2 MIB Extension July 1992
_6. _D_e_f_i_n_i_t_i_o_n_s
RFCRIP2-MIB DEFINITIONS ::= BEGIN
IMPORTS
experimental, Counter, TimeTicks, IpAddress
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212;
-- RIP-2 Management Information Base
-- Note: IANA has a special curse that it utters over
-- people who install the following OID in their systems...
rip2 OBJECT IDENTIFIER ::= { experimental 1234 }
-- the RouteTag type represents the contents of the
-- Route Tag field in the packet header or route entry.
RouteTag ::= OCTET STRING (SIZE (2))
-- the Validation type is used for the variable that deletes
-- an entry from a table, and ALWAYS takes at least these values:
Validation ::= INTEGER { valid (1), invalid (2) }
Malkin and Baker Expires: 31Jan92 [Page 5]
Internet Draft RIP 2 MIB Extension July 1992
-- The RIP 2 Globals Group.
-- Implementation of this group is mandatory for systems that
-- implement RIP-2.
-- These counters are intended to facilitate debugging quickly
-- changing routes or failing neighbors
rip2GlobalGroup OBJECT IDENTIFIER ::= { rip2 1 }
rip2GlobalRouteChanges OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of changes made to the IP Route Da-
tabase by RIP."
::= { rip2GlobalGroup 1 }
rip2GlobalQueries OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of responses sent to RIP queries
from other systems."
::= { rip2GlobalGroup 2 }
Malkin and Baker Expires: 31Jan92 [Page 6]
Internet Draft RIP 2 MIB Extension July 1992
-- RIP Interfaces Groups
-- Implementation of these Groups is mandatory for systems that
-- implement RIP-2.
-- Since RIP versions 1 and 2 do not deal with addressless links,
-- it is assumed that RIP "interfaces" are subnets within a
-- routing domain.
-- The RIP Interface Status Table.
rip2IfStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF Rip2IfStatEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of subnets which require separate
status monitoring in RIP."
::= { rip2 2 }
rip2IfStatEntry OBJECT-TYPE
SYNTAX Rip2IfStatEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A Single Routing Domain in a single Subnet."
INDEX { rip2IfStatAddress }
::= { rip2IfStatTable 1 }
Rip2IfStatEntry ::=
SEQUENCE {
rip2IfStatAddress
IpAddress,
rip2IfStatRcvBadPackets
Counter,
rip2IfStatRcvBadRoutes
Counter,
rip2IfStatSentUpdates
Counter,
rip2IfStatStatus
Validation
}
Malkin and Baker Expires: 31Jan92 [Page 7]
Internet Draft RIP 2 MIB Extension July 1992
rip2IfStatAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP Address of this system on the indicated
subnet."
::= { rip2IfStatEntry 1 }
rip2IfStatRcvBadPackets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of RIP response packets received by
the RIP process which were subsequently dis-
carded for any reason (e.g. a version 0 packet,
or an unknown command type)."
::= { rip2IfStatEntry 2 }
rip2IfStatRcvBadRoutes OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of routes, in valid RIP packets,
which were ignored for any reason (e.g. unknown
address family, or invalid metric)."
::= { rip2IfStatEntry 3 }
rip2IfStatSentUpdates OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of triggered RIP updates actually
sent on this interface. This explicitly does
NOT include full updates sent containing new
information."
::= { rip2IfStatEntry 4 }
Malkin and Baker Expires: 31Jan92 [Page 8]
Internet Draft RIP 2 MIB Extension July 1992
rip2IfStatStatus OBJECT-TYPE
SYNTAX Validation
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Writing invalid has the effect of deleting
this interface."
DEFVAL { valid }
::= { rip2IfStatEntry 5 }
Malkin and Baker Expires: 31Jan92 [Page 9]
Internet Draft RIP 2 MIB Extension July 1992
-- The RIP Interface Configuration Table.
rip2IfConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF Rip2IfConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of subnets which require separate con-
figuration in RIP."
::= { rip2 3 }
rip2IfConfEntry OBJECT-TYPE
SYNTAX Rip2IfConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A Single Routing Domain in a single Subnet."
INDEX { rip2IfConfAddress }
::= { rip2IfConfTable 1 }
Rip2IfConfEntry ::=
SEQUENCE {
rip2IfConfAddress
IpAddress,
rip2IfConfDomain
RouteTag,
rip2IfConfAuthType
INTEGER,
rip2IfConfAuthKey
OCTET STRING (SIZE(0..16)),
rip2IfConfSend
INTEGER,
rip2IfConfReceive
INTEGER,
rip2IfConfDefaultMetric
INTEGER,
rip2IfConfStatus
Validation
}
Malkin and Baker Expires: 31Jan92 [Page 10]
Internet Draft RIP 2 MIB Extension July 1992
rip2IfConfAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP Address of this system on the indicated
subnet."
::= { rip2IfConfEntry 1 }
rip2IfConfDomain OBJECT-TYPE
SYNTAX RouteTag
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Value inserted into the Routing Domain field
of all RIP packets sent on this interface."
DEFVAL { 0 }
::= { rip2IfConfEntry 2 }
rip2IfConfAuthType OBJECT-TYPE
SYNTAX INTEGER {
noAuthentication (1),
simplePassword (2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The type of Authentication used on this inter-
face."
DEFVAL { noAuthentication }
::= { rip2IfConfEntry 3 }
Malkin and Baker Expires: 31Jan92 [Page 11]
Internet Draft RIP 2 MIB Extension July 1992
rip2IfConfAuthKey OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..16))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The value to be used as the Authentication Key
whenever the corresponding instance of
rip2IfConfAuthType has the value simplePass-
word. A modification of the corresponding in-
stance of rip2IfConfAuthType does not modify
the rip2IfConfAuthKey value.
If a string shorter than 16 octets is supplied,
it will be left-justified and padded to 16 oc-
tets, on the right, with nulls (0x00).
Reading this object always results in an OCTET
STRING of length zero; authentication may not
be bypassed by reading the MIB object."
DEFVAL { ''h }
::= { rip2IfConfEntry 4 }
rip2IfConfSend OBJECT-TYPE
SYNTAX INTEGER {
doNotSend (1),
ripVersion1 (2),
rip1Compatible (3),
ripVersion2 (4)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"What the router sends on this interface.
ripVersion1 implies sending RIP updates compli-
ant with RFC 1058. rip1Compatible implies
broadcasting RIP-2 updates using RFC 1058 route
subsumption rules. ripVersion2 implies multi-
casting RIP-2 updates."
DEFVAL { rip1Compatible }
::= { rip2IfConfEntry 5 }
Malkin and Baker Expires: 31Jan92 [Page 12]
Internet Draft RIP 2 MIB Extension July 1992
rip2IfConfReceive OBJECT-TYPE
SYNTAX INTEGER {
rip1 (1),
rip2 (2),
rip1OrRip2 (3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This indicates which version of RIP updates
are to be accepted. Note that rip2 and
rip1OrRip2 implies reception of multicast pack-
ets."
DEFVAL { rip1OrRip2 }
::= { rip2IfConfEntry 6 }
rip2IfConfDefaultMetric OBJECT-TYPE
SYNTAX INTEGER ( 0..15 )
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable indicates what metric is to be
used as a default route in RIP updates ori-
ginated on this interface. A value of zero in-
dicates that no default route should be ori-
ginated; in this case, a default route via
another router may be propagated."
::= { rip2IfConfEntry 7 }
rip2IfConfStatus OBJECT-TYPE
SYNTAX Validation
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Writing invalid has the effect of deleting
this interface."
DEFVAL { valid }
::= { rip2IfConfEntry 8 }
Malkin and Baker Expires: 31Jan92 [Page 13]
Internet Draft RIP 2 MIB Extension July 1992
-- Peer Table
-- The RIP Peer Group
-- Implementation of this Group is Optional
-- This group provides information about active peer
-- relationships intended to assist in debugging.
rip2PeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Rip2PeerEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of RIP Peers."
::= { rip2 4 }
rip2PeerEntry OBJECT-TYPE
SYNTAX Rip2PeerEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information regarding a single routing peer."
INDEX { rip2PeerAddress, rip2PeerDomain }
::= { rip2PeerTable 1 }
Rip2PeerEntry ::=
SEQUENCE {
rip2PeerAddress
IpAddress,
rip2PeerDomain
RouteTag,
rip2PeerLastUpdate
TimeTicks,
rip2PeerVersion
INTEGER,
rip2PeerRcvBadPackets
Counter,
rip2PeerRcvBadRoutes
Counter
}
Malkin and Baker Expires: 31Jan92 [Page 14]
Internet Draft RIP 2 MIB Extension July 1992
rip2PeerAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP Address of the Peer System."
::= { rip2PeerEntry 1 }
rip2PeerDomain OBJECT-TYPE
SYNTAX RouteTag
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value in the Routing Domain field in RIP
packets received from the peer."
::= { rip2PeerEntry 2 }
rip2PeerLastUpdate OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of sysUpTime when the most recent
RIP update was received from this system."
::= { rip2PeerEntry 3 }
rip2PeerVersion OBJECT-TYPE
SYNTAX INTEGER ( 0..255 )
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The RIP version number in the header of the
last RIP packet received."
::= { rip2PeerEntry 4 }
Malkin and Baker Expires: 31Jan92 [Page 15]
Internet Draft RIP 2 MIB Extension July 1992
rip2PeerRcvBadPackets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of RIP response packets from this
peer discarded as invalid."
::= { rip2PeerEntry 5 }
rip2PeerRcvBadRoutes OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of routes from this peer that were
ignored because the entry format was invalid."
::= { rip2PeerEntry 6 }
END
Malkin and Baker Expires: 31Jan92 [Page 16]
Internet Draft RIP 2 MIB Extension July 1992
_7. _A_c_k_n_o_w_l_e_d_g_e_m_e_n_t_s
This document was produced by the RIP 2 Working Group.
In addition, the comments of the following individuals are
also acknowledged: Keith McCloghrie and Frank Kastenholz.
Malkin and Baker Expires: 31Jan92 [Page 17]
Internet Draft RIP 2 MIB Extension July 1992
_8. _R_e_f_e_r_e_n_c_e_s
[1] V. Cerf, IAB Recommendations for the Development of
Internet Network Management Standards. Internet Working
Group Request for Comments 1052. Network Information
Center, SRI International, Menlo Park, California,
(April, 1988).
[2] V. Cerf, Report of the Second Ad Hoc Network Management
Review Group, Internet Working Group Request for Comments
1109. Network Information Center, SRI International,
Menlo Park, California, (August, 1989).
[3] M.T. Rose and K. McCloghrie, Structure and Identification
of Management Information for TCP/IP-based internets,
Internet Working Group Request for Comments 1155.
Network Information Center, SRI International, Menlo
Park, California, (May, 1990).
[4] K. McCloghrie and M.T. Rose, Management Information Base
for Network Management of TCP/IP-based internets,
Internet Working Group Request for Comments 1156.
Network Information Center, SRI International, Menlo
Park, California, (May, 1990).
[5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin,
Simple Network Management Protocol, Internet Working
Group Request for Comments 1157. Network Information
Center, SRI International, Menlo Park, California, (May,
1990).
[6] M.T. Rose (editor), Management Information Base for
Network Management of TCP/IP-based internets, Internet
Working Group Request for Comments 1158. Network
Information Center, SRI International, Menlo Park,
California, (May, 1990).
[7] Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax
Notation One (ASN.1), International Organization for
Standardization. International Standard 8824, (December,
1987).
[8] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules
Malkin and Baker Expires: 31Jan92 [Page 18]
Internet Draft RIP 2 MIB Extension July 1992
for Abstract Notation One (ASN.1), International
Organization for Standardization. International Standard
8825, (December, 1987).
[9] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB
Definitions, Request for Comments 1212, Internet
Engineering Task Force, (March, 1991).
Malkin and Baker Expires: 31Jan92 [Page 19]
Internet Draft RIP 2 MIB Extension July 1992
Table of Contents
1 Status of this Memo ................................... 1
2 Abstract .............................................. 2
3 The Network Management Framework ...................... 2
4 Objects ............................................... 2
4.1 Format of Definitions ............................... 3
5 Overview .............................................. 3
5.1 Textual Conventions ................................. 3
5.2 Structure of MIB .................................... 4
6 Definitions ........................................... 5
6.1 Global Counters ..................................... 6
6.2 RIP Interface Tables ................................ 7
6.3 Peer Table .......................................... 14
7 Acknowledgements ...................................... 17
8 References ............................................ 18
Malkin and Baker Expires: 31Jan92 [Page 20]
- RIP-2 final draft Gary Scott Malkin
- RIP-2 final draft Bob Hinden