Which (autoconfig) you should either not be using on
servers, or you
should be configuring your software properly to select the correct
outbound address.
that's a bizarre statement. the distinction between a client
and a server is an artificial one. either autoconfig is
useful for all kinds of machines, or it's almost useless.
You are correct when talking about IP networks in general,
however Jeroen is talking about the public Internet, not
IP networks in general.
Of course another way to make this less bizarre is to stop
using the word "server" to refer to two different things.
Jeroen is saying that an IPv6 devices that wishes to
advertise its IPv6 address for the purposes of receiving
SMTP connection requests, should not be configured in
such a way that its IPv6 host ID is randomly assigned.
Of course you could try to dynamically update your reverse
DNS to match the random host IDs but that creates corner
cases and race conditions which can be entirely avoided just
by making the publicly visible IPv6 address a static one.
Jeroen further pointed out that there is no reason for
an interface, which has been assigned a random host ID,
to suffer with only one address because IPv6 makes it
straightforward to have multiple addresses on an interface.
BTW, I do agree with your general viewpoint of Internet
email architecture; it is horribly ugly and broken.
--Michael Dillon
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf