CER will not handle IP Addresses on the AVPs

[SummaNetworks]

If the CER message received contains IP addresses, those are ignored to generate the information for the Peer, and the FQDN is used instead. When the CER contains IP addresses, those shall be used to construct the Peer IP information. The Peer shall have a list of IPs, as to allow multiple paths.

[ammendonca]

Hi @SummaNetworks,

I think you should be referring to the Host-IP-Address AVP, which the CER and/or the CEA must include with their available IP addresses (in case of SCTP).

These AVPs should be treated mostly as informational, for logging/admin purposes, as those addresses are likely not reachable through other interfaces (eg: we may receive a 192.168.1.123 address, and although we might have a network interface in that range, might not be the same private network). It may even happen to connect to another Diameter peer on those new IP addresses, and this might be a security issue.

I think the best approach is to handle those IPs as informational, and if the admin wants to add them to the list of IPs to use, then do so manually. Also from this DIME Mailing List Thread on the same subject, this has been the conclusion.