Supported Rip Features; Protocols And Standards - HP MSR2000 series Configuration Manual

Next hop—If set to 0.0.0.0, it indicates that the originator of the route is the best next hop.
•
Otherwise, it indicates a next hop better than the originator of the route.
RIPv2 authentication message format
RIPv2 sets the AFI field of the first route entry to 0xFFFF to identify authentication information.
Figure 8 RIPv2 authentication message
0
Command
Authentication Type—A value of 2 represents simple authentication. A value of 3 represents MD5.
•
RFC 1723 only defines simple authentication. For more information about MD5 authentication, see
RFC 2453, RIP Version 2.
Authentication—Authentication data, including password information when simple authentication
•
is adopted or including key ID, MD5 authentication data length and sequence number when MD5
authentication is adopted.
NOTE:
Even though with RIPv1, you can configure the authentication mode in interface view, the configuration
will not take effect because RIPv1 does not support authentication.

Supported RIP features

The current implementation supports the following RIP features:
RIPv1 and RIPv2
•
RIP support for multi-VPN-instance
•
• RIP FRR
BFD
•
RIP periodically sends route update requests to neighbors. If no route update response for a route is
received within the specified interval, RIP considers the route unreachable. This mechanism cannot detect
link faults quickly. After BFD is configured for RIP, and BFD detects a broken link, RIP can quickly age out
the unreachable route, thus avoiding interference to other services.

Protocols and standards

RFC 1058, Routing Information Protocol
•
• RFC 1723, RIP Version 2 - Carrying Additional Information
RFC 1721, RIP Version 2 Protocol Analysis
•
RFC 1722, RIP Version 2 Protocol Applicability Statement
•
RFC 1724, RIP Version 2 MIB Extension
•
RFC 2082, RIPv2 MD5 Authentication
•
7
Version
0xFFFF
Authentication (16 octets)
15
Unused
Authentication type
23
31