Re: [Dime] [RFC3588bis-34] - Host-IP-Address AVP

> >> Yes for the first part and no for the second part.. you are not supposed to send
> >> addresses that you cannot be connected at.
> > 
> > But in general, a Diameter implementation can't reasonably be expected to know which of its IP addresses will be usable by a particular peer.
> 
> A Diameter node is supposed to know which addresses it can bind and
> did bind to. The addresses it might put into host-ip-address do
> not come out of blue.

That is irrelevant.  The problem is that just because the Diameter node has bound to an address, does not imply that it's possible for a specific peer to try and connect to.  

E.g., node A, node B are both behind different firewalls, node A binds to 192.168.1.1, on node B's network, 192.168.1.1 is assigned to a completely different machine.

Do you have a specific suggestion for the algorithm a node should use in selecting which of the nodes addresses are put in the Host-IP-Address field?

> 
> > Best just to treat the field as informational.
> 
> Don't fully agree. In case of TCP I could. In case of SCTP I don't.

For SCTP Host-IP-Address is utterly redundant.  SCTP already supports multi-homing and telling peers of additional addresses (although in practice, I've seen that go hilariously wrong).

Ralph.

> 
> - Jouni
> 
> 
> > 
> > Ralph.
> > 
> > 
> >> 
> >> 
> >> 
> >> - Jouni
> >> 
> >> 
> >>> 
> >>> Ankur Garg
> >>> 
> >> 
> >> _______________________________________________
> >> DiME mailing list
> >> DiME@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dime
> 