RFC 3588:Diameter Base Protocol
RFC-Ref

IP address


Click on the red underlined text to get to the source

... Direction (in or out) Source and destination IP address (possibly masked) Protocol Source and destination port ...
... IP version must be present in the packet that was used in describing the IP address. To test for a particular IP version, the bits ...
... Direction (in or out) Source and destination IP address (possibly masked) Protocol Source and destination port ...


... connections to span multiple interfaces and multiple IP addresses, the Capabilities-Exchange-Request message MUST contain one Host ...
... Address AVP for each potential IP address that MAY be locally used when transmitting Diameter ...
... connections to span multiple interfaces, hence, multiple IP addresses, the Capabilities-Exchange-Answer message MUST contain one Host ...
... IP-Address AVP for each potential IP address that MAY be locally used when transmitting Diameter ...
... to inform a Diameter peer of the sender's IP address. All source addresses that a Diameter node expects to use with SCTP ...


... identifier in the request is saved, and replaced with a locally unique value. The source of the request is also saved, which includes the IP address, port and protocol. ...


... configured. A statically configured Diameter peer would require that either the IP address or the fully qualified domain name (FQDN ...


... identification data. However, when used in conformant implementations, each ID Payload MUST carry a single IP address and a single non-zero port number ...
... non-zero port number, and MUST NOT use the IP Subnet or IP Address Range formats. This allows the Phase 2 security association ...
... pre-shared keys are configured with Diameter peers, who are identified by their IP address (Main Mode), or possibly their FQDN (Aggressive Mode). As a result, it is necessary for the set of ...



Google
Web
RFC-Ref