* anders/diameter/20.3/OTP-14946:
  vsn -> 2.1.4
  Update appup for 20.3
  Update service_info examples in doc
  Fix inaccurate comment

* anders/diameter/terminate/ERIERL-124:
  Fix handling of SUSPECT connections at service termination

* anders/diameter/reg/OTP-14839:
  Fix diameter_reg:subscribe/2 remove notification

A peer_fsm process can be started long before a connection is
established in the listening case. The time reported in a 'peer' tuple
in service_info is of connection establishment.

A peer connection in watchdog state SUSPECT is represented by a peer
table entry in diameter_service, but not by a request table entry in
diameter_peer, so diameter_service:terminate/2 could result in failures
like this:

exception error: no match of right hand side value []
  in function diameter_traffic:peer_down/1 (base/diameter_traffic.erl, line 141)
  in call from lists:foldl/3 (lists.erl, line 1263)
  in call from ets:do_foldl/4 (ets.erl, line 611)
  in call from ets:foldl/3 (ets.erl, line 600)
  in call from diameter_service:terminate/2 (base/diameter_service.erl, line 557)
  in call from gen_server:try_terminate/3 (gen_server.erl, line 648)
  in call from gen_server:terminate/10 (gen_server.erl, line 833)
  in call from gen_server:handle_msg/6 (gen_server.erl, line 679)

Commit fae8ca0c broke notification by removing table elements before
matching for them, causing diameter_tcp/sctp listening processes to
live on after diameter:remove_transport/2.

Commit 58091992 added diameter_reg:subscribe/2, and commit 5ca5fb71
started using it for listener exit.

Only change is doc.

* anders/diameter/decode/OTP-14684:
  vsn -> 2.1.2
  Update appup for ERIERL-14684

The options map wasn't updated after the AVP was identified, with
the resulting consequences for M-bit interpretation.