Debian Codegraph @

rfc1387.html

raw
1 <pre>Network Working Group G. Malkin
2 Request for Comments: 1387 Xylogics, Inc.
3 January 1993
4
5
6 <span class="h1">RIP Version 2 Protocol Analysis</span>
7
8 Status of this Memo
9
10 This memo provides information for the Internet community. It does
11 not specify an Internet standard. Distribution of this memo is
12 unlimited.
13
14 Abstract
15
16 As required by Routing Protocol Criteria (<a href="./rfc1264">RFC 1264</a>), this report
17 documents the key features of the RIP-2 protocol and the current
18 implementation experience.
19
20 Acknowledgements
21
22 The RIP-2 protocol owes much to those who participated in the RIP-2
23 Working Group of the Internet Engineering Task Force (IETF). A
24 special thanks goes to Fred Baker for his help on the MIB, and to
25 Jeffrey Honig for the implementation experience.
26
27 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Protocol Documents</span>
28
29 The RIP-2 protocol description is defined in <a href="./rfc1388">RFC 1388</a> [<a href="#ref-1" title="&quot;RIP Version 2 - Carrying Additional Information&quot;">1</a>]. This memo
30 suggests an update to the "Routing Information Protocol" (<a href="./rfc1058">RFC 1058</a>)
31 [<a href="#ref-3" title="&quot;Routing Information Protocol&quot;">3</a>]. The RIP-2 MIB description is defined in <a href="./rfc1389">RFC 1389</a> [<a href="#ref-2" title="&quot;RIP Version 2 MIB Extension&quot;">2</a>].
32
33 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Key Features</span>
34
35 While RIP-2 shares the same basic algorithms as RIP-1, it supports
36 several new features. They are: routing domains, external route
37 tags, subnet masks, next hop addresses, and authentication.
38
39 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Routing Domains</span>
40
41 Routing domains allow multiple RIP "clouds" to exist over the same
42 physical network. This is a feature requested by several members of
43 the working group. It allows simple policies to be constructed by
44 grouping routers into domains which share routing information.
45
46
47
48
49
50
51
52 <span class="grey">Malkin [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1387">RFC 1387</a> RIP-2 Analysis January 1993</span>
55
56
57 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> External Route Tags</span>
58
59 The route tag field may be used to propagate information acquired
60 from an EGP. The definition of the contents of this field are beyond
61 the scope of this protocol. However, it may be used, for example, to
62 propagate an EGP AS number.
63
64 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> Subnet Masks</span>
65
66 Inclusion of subnet masks was the original intent of opening the RIP
67 protocol for improvement. Subnet mask information makes RIP more
68 useful in a variety of environments and allows the use of variable
69 subnet masks on the network. Subnet masks are also necessary for
70 implementation of "classless" addressing, as the CIDR work proposes.
71
72 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Next Hop Addresses</span>
73
74 Support for next hop addresses allows for optimization of routes in
75 an environment which uses multiple routing protocols. For example,
76 if RIP-2 were being run on a network along with another IGP, and one
77 router ran both protocols, then that router could indicate to the
78 other RIP-2 routers that a better next hop than itself exists for a
79 given destination.
80
81 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a> Authentication</span>
82
83 One significant improvement RIP-2 offers over RIP-1, is the addition
84 of an authentication mechanism. Essentially, it is the same
85 extensible mechanism provided by OSPF. Currently, only a plain-text
86 password is defined for authentication. However, more sophisticated
87 authentication schemes can easily be incorporated as they are
88 defined.
89
90 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a> Multicasting</span>
91
92 RIP-2 packets may be multicast instead of being broadcast. The use
93 of an IP multicast address reduces the load on hosts which do not
94 support routing protocols. It also allows RIP-2 routers to share
95 information which RIP-1 routers cannot hear. This is useful since a
96 RIP-1 router may misinterpret route information because it cannot
97 apply the supplied subnet mask.
98
99 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. RIP-2 MIB</span>
100
101 The MIB for RIP-2 allows for monitoring and control of RIP's
102 operation within the router. In addition to global and per-interface
103 counters and controls, there is are per-peer counters which provide
104 the status of RIP-2 "neighbors".
105
106
107
108 <span class="grey">Malkin [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1387">RFC 1387</a> RIP-2 Analysis January 1993</span>
111
112
113 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Implementations</span>
114
115 Currently, there is one nearly complete implementation of RIP-2. A
116 "gated" implementation is now available with RIP-2, written by
117 Jeffrey Honig at Cornell University. It may be acquired by anonymous
118 FTP from gated.cornell.edu as pub/gated/gated-alpha.tar.Z. It
119 implements multicasting, subnet masks, limited authentication, next-
120 hop, and limited routing domain support. A RIP-2 version of ripquery
121 is also available. The "gated" implementation does not yet support
122 full subsumption rules, full authentication, full routing domains,
123 and the MIB. It has been tested against itself and various RIP-1
124 implementations.
125
126 A second, complete implementation is under development by a vendor
127 who's identity cannot be disclosed at this time.
128
129 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
130
131 [<a id="ref-1">1</a>] Malkin, G., "RIP Version 2 - Carrying Additional Information",
132 <a href="./rfc1388">RFC 1388</a>, Xylogics, Inc., January 1993.
133
134 [<a id="ref-2">2</a>] Malkin, G., and F. Baker, "RIP Version 2 MIB Extension", <a href="./rfc1389">RFC</a>
135 <a href="./rfc1389">1389</a>, Xylogics, Inc., Advanced Computer Communications, January
136 1993.
137
138 [<a id="ref-3">3</a>] Hedrick, C., "Routing Information Protocol", <a href="./rfc1058">RFC 1058</a>, Rutgers
139 University, June 1988.
140
141 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
142
143 Security issues are discussed in <a href="#section-2.5">section 2.5</a>.
144
145 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Author's Address</span>
146
147 Gary Scott Malkin
148 Xylogics, Inc.
149 53 Third Avenue
150 Burlington, MA 01803
151
152 Phone: (617) 272-8140
153 EMail: [email protected]
154
155
156
157
158
159
160
161
162
163
164 Malkin [Page 3]
165 </pre>