Prepare releaseOTP_R16B01

1 files changed, 223 insertions, 0 deletions

diff --git a/lib/diameter/doc/src/notes.xml b/lib/diameter/doc/src/notes.xml
index ad61f12b5b..e750b56f1e 100644
--- a/lib/diameter/doc/src/notes.xml
+++ b/lib/diameter/doc/src/notes.xml
@@ -42,6 +42,229 @@ first.</p>
 
 <!-- ===================================================================== -->
 
+<section><title>diameter 1.4.2</title>
+
+    <section><title>Fixed Bugs and Malfunctions</title>
+      <list>
+        <item>
+          <p>
+	    Fix handling of 5014 (INVALID_AVP_LENGTH) errors.</p>
+          <p>
+	    This was in some cases reported as 3009
+	    (INVALID_AVP_BITS).</p>
+          <p>
+	    Note that the correction is partially implemented in
+	    modules generated by diameterc(1): a dictionary file must
+	    be recompiled for the correction to apply to any messages
+	    it defines.</p>
+          <p>
+	    Own Id: OTP-11007</p>
+        </item>
+        <item>
+          <p>
+	    Fix faulty capitalization in release notes.</p>
+          <p>
+	    Diameter = the protocol.<br/> diameter = the Erlang
+	    application.</p>
+          <p>
+	    Own Id: OTP-11014</p>
+        </item>
+        <item>
+          <p>
+	    Fix watchdog memory leak.</p>
+          <p>
+	    Entries were not removed from a service-specific ets
+	    table, causing them to be orphaned at connection
+	    reestablishment for listening transports, and
+	    diameter:remove_transport/2 for both listening and
+	    connecting transports.</p>
+          <p>
+	    The fault was introduced by OTP-10692 in diameter-1.4.1
+	    (R16B).</p>
+          <p>
+	    Own Id: OTP-11019 Aux Id: OTP-10692 </p>
+        </item>
+        <item>
+          <p>
+	    Fix decode failure on AVP Length &lt; 8.</p>
+          <p>
+	    The failure caused the message in question to be
+	    discarded.</p>
+          <p>
+	    Own Id: OTP-11026</p>
+        </item>
+        <item>
+          <p>
+	    Respect Host-IP-Address configuration.</p>
+          <p>
+	    Addresses returned from a transport module were always
+	    used to populate Host-IP-Address AVP's in an outgoing
+	    CER/CEA, which precluded the sending of a VIP address.
+	    Transport addresses are now only used if Host-IP-Address
+	    is unspecified.</p>
+          <p>
+	    Own Id: OTP-11045</p>
+        </item>
+        <item>
+          <p>
+	    Fix mkdir race.</p>
+          <p>
+	    Install could fail if examples/code and examples/dict
+	    were created in parallel. Noticed on FreeBSD.</p>
+          <p>
+	    Own Id: OTP-11051</p>
+        </item>
+        <item>
+          <p>
+	    Fix recognition of 5001 on mandatory AVP's.</p>
+          <p>
+	    An AVP setting the M-bit was not regarded as erroneous if
+	    it was defined in the dictionary in question and its
+	    container (message or Grouped AVP) had an 'AVP' field.
+	    It's now regarded as a 5001 error (AVP_UNSUPPORTED), as
+	    in the case that the AVP is not defined.</p>
+          <p>
+	    Note that the correction is partially implemented in
+	    modules generated by diameterc(1): a dictionary file must
+	    be recompiled for the correction to apply to any messages
+	    it defines.</p>
+          <p>
+	    Own Id: OTP-11087</p>
+        </item>
+        <item>
+          <p>
+	    Fix setting of Failed-AVP on handle_request
+	    {answer_message, 5xxx} return.</p>
+          <p>
+	    Failed-AVP was never in the outgoing answer-message. It
+	    is now set with the AVP from the first entry with the
+	    specified Result-Code in the errors field of the incoming
+	    diameter_packet, if found.</p>
+          <p>
+	    Own Id: OTP-11092</p>
+        </item>
+        <item>
+          <p>
+	    Fix watchdog function_clause</p>
+          <p>
+	    A listening transport on a service that allowed multiple
+	    connections to the same peer could result in a
+	    function_clause error in module diameter_watchdog. The
+	    resulting crash was harmless but unseemly.</p>
+          <p>
+	    Thanks to Aleksander Nycz.</p>
+          <p>
+	    Own Id: OTP-11115</p>
+        </item>
+        <item>
+          <p>
+	    Fix population of Failed-AVP.</p>
+          <p>
+	    In cases in which diameter populated this AVP, many
+	    values were sent instead of one as suggested by RFC 6733.
+	    This was partially corrected by OTP-11007.</p>
+          <p>
+	    Own Id: OTP-11127 Aux Id: OTP-11007 </p>
+        </item>
+        <item>
+          <p>
+	    Fix list-valued Vendor-Specific-Application-Id config</p>
+          <p>
+	    R16B (specifically, OTP-10760) broke the handling of such
+	    configuration, resulting in a function clause error if
+	    the list was not of length 3, and faulty interpretation
+	    of the list's contents otherwise. Only record-valued
+	    configuration was properly interpreted.</p>
+          <p>
+	    Own Id: OTP-11165</p>
+        </item>
+      </list>
+    </section>
+
+
+    <section><title>Improvements and New Features</title>
+      <list>
+        <item>
+          <p>
+	    Allow peer connections to be shared between Erlang nodes
+	    for the purpose of sending outgoing requests.</p>
+          <p>
+	    A diameter_app(3) pick_peer/4 callback gets a list of
+	    remote candidates as argument, allowing a callback on one
+	    node to select a transport connection established on
+	    another node. The service_opt() share_peers controls the
+	    extent to which local connections are shared with remote
+	    nodes. The service_opt() use_shared_peers controls the
+	    extent to which connections shared from remote nodes are
+	    utilized on the local node.</p>
+          <p>
+	    Own Id: OTP-9610</p>
+        </item>
+        <item>
+          <p>
+	    Allow listening diameter_{tcp,sctp} transports to be
+	    configured with remote addresses.</p>
+          <p>
+	    Option 'accept' allows remote addresses to be configured
+	    as tuples or regular expressions. Remote addresses are
+	    matched against the configured values at connection
+	    establishment, any non-matching address causing the
+	    connection to be aborted.</p>
+          <p>
+	    Own Id: OTP-10893</p>
+        </item>
+        <item>
+          <p>
+	    Detect more transport_opt() configuration errors at
+	    diameter:add_transport/2.</p>
+          <p>
+	    Many errors would previously not be detected until
+	    transport start, diameter:add_transport/2 returning 'ok'
+	    but transport connections failing to be established. An
+	    error tuple is now returned.</p>
+          <p>
+	    Own Id: OTP-10972</p>
+        </item>
+        <item>
+          <p>
+	    Make explicit local address configuration optional in
+	    diameter_tcp:start/3.</p>
+          <p>
+	    The default address (as determined by gen_tcp) is now
+	    used when a local address is not explicitly configured.</p>
+          <p>
+	    Own Id: OTP-10986</p>
+        </item>
+        <item>
+          <p>
+	    Improve handling of unrecognized service options.</p>
+          <p>
+	    Such options were silently ignored by
+	    diameter:start_service/2. An error tuple is now returned.</p>
+          <p>
+	    Own Id: OTP-11017</p>
+        </item>
+        <item>
+          <p>
+	    Don't send default Inband-Security-Id in CER/CEA.</p>
+          <p>
+	    RFC 6733 recommends against the use of
+	    Inband-Security-Id. Only send a value that differs from
+	    the default, NO_INBAND_SECURITY = 0.</p>
+          <p>
+	    Own Id: OTP-11050</p>
+        </item>
+        <item>
+          <p>
+	    Make spawn options for request processes configurable.</p>
+          <p>
+	    Own Id: OTP-11060</p>
+        </item>
+      </list>
+    </section>
+
+</section>
+
 <section><title>diameter 1.4.1.1</title>
 
     <section><title>Fixed Bugs and Malfunctions</title>