H3C Technologies H3C S12500 Series Switches - Manual (Page 39)

23
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
• Authentication type—A value of 2 represents plain text authentication, while a value of 3
represents MD5. RFC 1723 defines only plain text authentication. For MD5 authentication
information, see RFC 2453, RIP Version 2.
• 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.
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 VPN
RIP can serve as the IGP running between CE and PE on a BGP/MPLS VPN network. For related
information, see MPLS Configuration Guide.
• RIP FRR
• BFD
RIP periodically sends route updates to neighbors. If no route update 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, when 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
Command
0xFFFF
Authentication (16 octets)
Version Unused
Authentication type
0 7 15 31