LDP keychain authentication can be configured to improve the security of a connection used by an LDP session. LDP authentication is configured on LSRs at both ends of an LDP session.
To help improve LDP session security, keychain authentication can be configured for a TCP connection over which an LDP session has been established.
During keychain authentication, a group of passwords are defined in the format of a password string, and each password is assigned a specified encryption and decryption algorithm such as MD5 or secure hash algorithm-1 (SHA-1) and configured with a validity period. When sending or receiving a packet, the system selects a valid password. Within the validity period of the password, the system uses the encryption algorithm matching the password to encrypt the packet before sending it out, or uses the decryption algorithm matching the password to decrypt the packet before accepting it. In addition, the system automatically uses a new password after the previous password expires, minimizing password decryption risks.
You can configure either LDP MD5 authentication or LDP keychain authentication based on their separate characteristics:
Keychain authentication and MD5 authentication cannot be both configured on a single LDP peer.
system-view
mpls ldp
authentication key-chain peer peer-id name keychain-name
By default, LDP keychain authentication is not performed between LDP peers.
Configuring LDP keychain authentication leads to reestablishment of an LDP session and deletes the LSP associated with the LDP session.