F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices Appendix Protocol Reference-6PW100

RIPv2 authentication message format

RIPv2 sets the AFI field of the first route entry to 0xFFFF to identify authentication information.

Figure 3 RIPv2 authentication message

• Authentication type—A value of 2 represents plain text authentication, while a value of 3

represents MD5.

• Authentication—Authentication data, including password information when plain text

authentication is adopted or including key ID, MD5 authentication data length and sequence

number when MD5 authentication is adopted.

RFC 1723 only defines plain text authentication. For information about MD5 authentication, see RFC

2453.

Supported RIP features

RIP supports the following features:

• RIPv1 and RIPv2

• RIP for MPLS VPNs

• 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

• RFC 2091, Triggered Extensions to RIP to Support Demand Circuits

• RFC 2453, RIP Version 2

Command

0xFFFF

Authentication (16 octets)

Version Unused

Authentication type

0715 31