* anders/diameter/19.1/OTP-13838:
  vsn -> 1.12.1
  Update appup for 19.1
  Fix xmllint errors in documentation
  Remove documentation overkill
  Don't run traffic tests in parallel when {string_decode, true}
  Remove copyright from generated dictionary modules
  Fix dictionary function typo
  Fix dictionary typo in relay example

The SCPT stack has a different behavior in solaris2.10 then in later versions
and linux. Diameter implementation does not support this behavior.

Since the large strings copied between processes cause testcases to fail
randomly.

Option string_decode was added in commit 1590920c.

* anders/diameter/rand/OTP-13664:
  Use rand(3) instead of random(3)

That missed comm_up when something like the following was received on
FreeBSD (for one):

  {sctp,#Port<0.599>,
        {127,0,0,1},
        45455,
        {[{sctp_sndrcvinfo,0,0,[],0,0,0,0,145060462,3}],
         {sctp_assoc_change,comm_up,0,10,10,3}}}

The latter is deprecated in OTP 19.

Listening transports weren't removed, which diameter_reg:subs/0 revealed.

The transport interface documented in diameter_transport(3) is used to
start/stop accepting/connecting transport processes: they're started
with a function call, and told to die with their parent process. In the
accepting case, both diameter_tcp and diameter_sctp start a listening
process when the first accepting transport is started. However, there's
no way for a listening process to find out that that it should stop
listening when transport configuration is removed.

Both diameter_tcp and diameter_sctp have used a timer to terminate the
listening process after all existing accepting processes have died as a
consequence of transport removal. The problem with this is that nothing
stops a new client from connecting before this, and also that no new
transport can succeed in opening the same listening port (eg.
reconfiguration) until the old listener dies.

This commit solves the problem by adding diameter_reg:subscribe/2, to
allow callers to subscribe to messages about added/removed associations.
A call to diameter:add_transport/2 results in a new child process that
registers a term that a listening process subscribes to. Transport
removal results in the death of the child, and the resulting
notification to the listener causes the latter to close its socket and
terminate.

This is still an internal interface, but the subscription mechanism
should probably be made external  (eg. a diameter:subscribe/1 that can
be used to subscribe to specified messages), so that transport modules
other than diameter's own can make use of it. There is no support for
soft upgrade.

Letters are cheap.