H3C Technologies H3C S7500E Series Switches - Manual (Page 40)

3-5
z 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.
z RFC 1723 only defines plain text authentication. For information about MD5 authentication, see
RFC 2453 “RIP Version 2”.
z With RIPv1, you can configure the authentication mode in interface view. However, the
configuration will not take effect because RIPv1 does not support authentication.
Supported RIP Features
The current implementation supports the following RIP features.
z RIPv1 and RIPv2
z RIP multi-instance.
RIP can serve as the IGP running between CE and PE on a BGP/MPLS VPN network. For related
information, see MPLS L3VPN Configuration in the MPLS Configuration Guide.
z 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, when BFD detects a broken link, RIP can
quickly age out the unreachable route, thus avoiding interference to other services.
Protocols and Standards
z RFC 1058: Routing Information Protocol
z RFC 1723: RIP Version 2 - Carrying Additional Information
z RFC 1721: RIP Version 2 Protocol Analysis
z RFC 1722: RIP Version 2 Protocol Applicability Statement
z RFC 1724: RIP Version 2 MIB Extension
z RFC 2082: RIPv2 MD5 Authentication
z RFC 2091: Triggered Extensions to RIP to Support Demand Circuits
z RFC 2453: RIP Version 2
Configuring RIP Basic Functions
Configuration Prerequisites
Before configuring RIP basic functions, complete the following tasks.
z Configure the link layer protocol.