aboutsummaryrefslogtreecommitdiffstats
path: root/lib/diameter/doc/src/notes.xml
diff options
context:
space:
mode:
Diffstat (limited to 'lib/diameter/doc/src/notes.xml')
-rw-r--r--lib/diameter/doc/src/notes.xml209
1 files changed, 111 insertions, 98 deletions
diff --git a/lib/diameter/doc/src/notes.xml b/lib/diameter/doc/src/notes.xml
index 638b6e24b6..82448e7f51 100644
--- a/lib/diameter/doc/src/notes.xml
+++ b/lib/diameter/doc/src/notes.xml
@@ -11,20 +11,21 @@
<header>
<copyright>
<year>2011</year>
-<year>2014</year>
+<year>2016</year>
<holder>Ericsson AB. All Rights Reserved.</holder>
</copyright>
<legalnotice>
-The contents of this file are subject to the Erlang Public License,
-Version 1.1, (the "License"); you may not use this file except in
-compliance with the License. You should have received a copy of the
-Erlang Public License along with this software. If not, it can be
-retrieved online at http://www.erlang.org/.
-
-Software distributed under the License is distributed on an "AS IS"
-basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
-the License for the specific language governing rights and limitations
-under the License.
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
</legalnotice>
@@ -42,12 +43,24 @@ first.</p>
<!-- ===================================================================== -->
-<section><title>diameter 1.9.2.4</title>
+<section><title>diameter 1.11.2</title>
<section><title>Fixed Bugs and Malfunctions</title>
<list>
<item>
<p>
+ Make peer handling more efficient.</p>
+ <p>
+ Inefficient lookup and manipulation of peer lists could
+ result in poor performance when many outgoing requests
+ were sent simultaneously, or when many peers connected
+ simultaneously. Filtering peer lists on realm/host is now
+ also more efficient in many cases.</p>
+ <p>
+ Own Id: OTP-13164</p>
+ </item>
+ <item>
+ <p>
Fix handling of shared peer connections in watchdog state
SUSPECT.</p>
<p>
@@ -60,96 +73,69 @@ first.</p>
</list>
</section>
-
- <section><title>Improvements and New Features</title>
- <list>
- <item>
- <p>
- no</p>
- <p>
- Own Id: OTP-13385</p>
- </item>
- </list>
- </section>
-
</section>
-<section><title>diameter 1.9.2.3</title>
+<section><title>diameter 1.11.1</title>
<section><title>Fixed Bugs and Malfunctions</title>
<list>
<item>
<p>
- Make peer handling more efficient.</p>
+ Fix request table leaks</p>
<p>
- Inefficient lookup and manipulation of peer lists could
- result in poor performance when many outgoing requests
- were sent simultaneously, or when many peers connected
- simultaneously. Filtering peer lists on realm/host is now
- also more efficient in many cases.</p>
+ The End-to-End and Hop-by-Hop identifiers of outgoing
+ Diameter requests are stored in a table in order for the
+ caller to be located when the corresponding answer
+ message is received. Entries were orphaned if the handler
+ was terminated by an exit signal as a consequence of
+ actions taken by callback functions, or if callbacks
+ modified identifiers in retransmission cases.</p>
<p>
- Own Id: OTP-13164</p>
+ Own Id: OTP-13137</p>
</item>
</list>
</section>
</section>
-<section><title>diameter 1.9.2.2</title>
+<section><title>diameter 1.11</title>
<section><title>Fixed Bugs and Malfunctions</title>
<list>
<item>
<p>
- Fix diameter_watchdog function clause.</p>
+ Fix relay encode of nested, Grouped AVPs.</p>
<p>
- OTP-12912 introduced an error with accepting transports
- setting <c>{restrict_connections, false}</c>, causing
- processes to fail when peer connections were terminated.</p>
+ A fault in OTP-12475 caused encode to fail if the first
+ AVP in a Grouped AVP was itself Grouped.</p>
<p>
- Own Id: OTP-12969</p>
+ Own Id: OTP-12879 Aux Id: OTP-12475 </p>
</item>
<item>
<p>
- Fix request table leaks</p>
+ Match acceptable peer addresses case insensitively.</p>
<p>
- The End-to-End and Hop-by-Hop identifiers of outgoing
- Diameter requests are stored in a table in order for the
- caller to be located when the corresponding answer
- message is received. Entries were orphaned if the handler
- was terminated by an exit signal as a consequence of
- actions taken by callback functions, or if callbacks
- modified identifiers in retransmission cases.</p>
+ Regular expressions passed in an 'accept' tuple to
+ diameter_tcp or diameter_sctp inappropriately matched
+ case.</p>
<p>
- Own Id: OTP-13137</p>
+ Own Id: OTP-12902</p>
</item>
- </list>
- </section>
-
-
- <section><title>Improvements and New Features</title>
- <list>
<item>
<p>
- Add service_opt() strict_mbit.</p>
+ Fix diameter_watchdog function clause.</p>
<p>
- There are differing opinions on whether or not reception
- of an arbitrary AVP setting the M-bit is an error. The
- default interpretation is strict: if a command grammar
- doesn't explicitly allow an AVP setting the M-bit then
- reception of such an AVP is regarded as an error. Setting
- <c>{strict_mbit, false}</c> disables this check.</p>
+ OTP-12912 introduced an error with accepting transports
+ setting <c>{restrict_connections, false}</c>, causing
+ processes to fail when peer connections were terminated.</p>
<p>
- Own Id: OTP-12947</p>
+ Own Id: OTP-12969</p>
</item>
</list>
</section>
-</section>
-
-<section><title>diameter 1.9.2.1</title>
- <section><title>Fixed Bugs and Malfunctions</title>
+ <section><title>Improvements and New Features</title>
<list>
<item>
<p>
@@ -164,15 +150,6 @@ first.</p>
</item>
<item>
<p>
- Fix relay encode of nested, Grouped AVPs.</p>
- <p>
- A fault in OTP-12475 caused encode to fail if the first
- AVP in a Grouped AVP was itself Grouped.</p>
- <p>
- Own Id: OTP-12879 Aux Id: OTP-12475 </p>
- </item>
- <item>
- <p>
Improve decode performance.</p>
<p>
The time required to decode a message increased
@@ -183,16 +160,6 @@ first.</p>
</item>
<item>
<p>
- Match acceptable peer addresses case insensitively.</p>
- <p>
- Regular expressions passed in an 'accept' tuple to
- diameter_tcp or diameter_sctp inappropriately matched
- case.</p>
- <p>
- Own Id: OTP-12902</p>
- </item>
- <item>
- <p>
Improve watchdog and statistics performance.</p>
<p>
Inefficient use of timers contributed to poor performance
@@ -203,21 +170,26 @@ first.</p>
</item>
<item>
<p>
- Fix start order of alternate transports.</p>
+ Add service_opt() strict_mbit.</p>
<p>
- A transport configured with diameter:add_transport/2 can
- be passed multiple transport_module/transport_config
- tuples in order to specify alternate configuration,
- modules being attempted in order until one succeeds. This
- is primarily for the connecting case; for example, to
- allow a transport to be configured to first attempt
- connection over SCTP, and then TCP in case SCTP fails.
- Multiple module tuples can be paired with a single config
- tuple, but in this case the start order was reversed
- relative to the order in which the modules were specifed.</p>
+ There are differing opinions on whether or not reception
+ of an arbitrary AVP setting the M-bit is an error. The
+ default interpretation is strict: if a command grammar
+ doesn't explicitly allow an AVP setting the M-bit then
+ reception of such an AVP is regarded as an error. Setting
+ <c>{strict_mbit, false}</c> disables this check.</p>
<p>
- Own Id: OTP-12929</p>
+ Own Id: OTP-12947</p>
</item>
+ </list>
+ </section>
+
+</section>
+
+<section><title>diameter 1.10</title>
+
+ <section><title>Fixed Bugs and Malfunctions</title>
+ <list>
<item>
<p>
Fix decode of Grouped AVPs containing errors.</p>
@@ -266,7 +238,48 @@ first.</p>
suggested single faulty AVP, nested in as many Grouped
containers as required.</p>
<p>
- Own Id: OTP-12930</p>
+ Own Id: OTP-12721</p>
+ </item>
+ <item>
+ <p>
+ Fix SCTP problems on Solaris.</p>
+ <p>
+ The allocation of association ids in Solaris was in
+ conflict with an assumption made in diameter_sctp,
+ resulting in failures when accepting multiple peer
+ connections.</p>
+ <p>
+ Own Id: OTP-12768</p>
+ </item>
+ <item>
+ <p>
+ Fix start order of alternate transports.</p>
+ <p>
+ A transport configured with diameter:add_transport/2 can
+ be passed multiple transport_module/transport_config
+ tuples in order to specify alternate configuration,
+ modules being attempted in order until one succeeds. This
+ is primarily for the connecting case; for example, to
+ allow a transport to be configured to first attempt
+ connection over SCTP, and then TCP in case SCTP fails.
+ Multiple module tuples can be paired with a single config
+ tuple, but in this case the start order was reversed
+ relative to the order in which the modules were specifed.</p>
+ <p>
+ Own Id: OTP-12851</p>
+ </item>
+ </list>
+ </section>
+
+
+ <section><title>Improvements and New Features</title>
+ <list>
+ <item>
+ <p>
+ Change license text from Erlang Public License to Apache
+ Public License v2.</p>
+ <p>
+ Own Id: OTP-12845</p>
</item>
</list>
</section>
@@ -318,7 +331,7 @@ first.</p>
</item>
<item>
<p>
- Don't confuse Result-Code and Experimental-Result</p>
+ Don't confuse Result-Code and Experimental-Result.</p>
<p>
The errors field of a decoded diameter_packet record was
populated with a Result-Code AVP when an