From b6dc1a844eab061d0a7153d46e7e68296f15a504 Mon Sep 17 00:00:00 2001 From: Erlang/OTP Date: Tue, 4 Oct 2011 12:06:58 +0200 Subject: Prepare release --- lib/diameter/doc/src/notes.xml | 129 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 129 insertions(+) (limited to 'lib/diameter') diff --git a/lib/diameter/doc/src/notes.xml b/lib/diameter/doc/src/notes.xml index eafddd7d1e..e2723f3e99 100644 --- a/lib/diameter/doc/src/notes.xml +++ b/lib/diameter/doc/src/notes.xml @@ -36,6 +36,135 @@ first.

+
Diameter 0.10 + +
Fixed Bugs and Malfunctions + + +

+ Handle #sctp_paddr_change and #sctp_pdapi_event from + gen_sctp.

+

+ The events are enabled by default but diameter_sctp + neither disabled nor dealt with them. Reception of such + an event caused a transport process to crash.

+

+ Own Id: OTP-9538

+
+ +

+ Fix header folding bug.

+

+ A prepare_request callback from diameter can return a + diameter_header record in order to set values in the + header of an outgoing request. A fault in + diameter_lib:fold_tuple/3 caused the subsequent encode of + the outgoing request to fail.

+

+ Own Id: OTP-9577

+
+ +

+ Fix bugs in sending of answer-message replies.

+

+ 3001 (DIAMETER_COMMAND_UNSUPPORTED) was not sent since + the decode placed the AVP list in the wrong field of the + diameter_packet, causing the subsequent encode to fail. + Session-Id was also set improperly, causing encode to + fail even in this case.

+

+ Own Id: OTP-9578

+
+ +

+ Fix improper use of error_logger:info_report/2.

+

+ Function doesn't take a format string and arguments as it + was called. Instead use error_logger:info_report/1 and + use the same report format as used for warning and error + reports.

+

+ Own Id: OTP-9579

+
+ +

+ Fix and clarify semantics of peer filters.

+

+ An eval filter returning a non-true value caused the call + process to fail and the doc was vague on how an exception + was treated. Clarify that the non-tuple host/realm + filters assume messages of a certain form.

+

+ Own Id: OTP-9580

+
+ +

+ Fix and clarify relay behaviour.

+

+ Implicit filtering of the sending peer in relaying a + request could cause loop detection to be preempted in a + manner not specified by RFC3588. Reply with 3002 + (DIAMETER_UNABLE_TO_DELIVER) on anything but an answer to + a relayed request.

+

+ Own Id: OTP-9583

+
+
+
+ + +
Improvements and New Features + + +

+ @id required in dictionary files only when @messages is + specified.

+

+ @id defines an application identifier and this is used + only when sending or receiving messages. A dictionary can + define only AVP's however, to be included by other + dictionaries using @inherits, in which case it makes no + sense to require @id.

+

+ Note that message definitions are not inherited with + @inherits, only AVP's

+

+ Own Id: OTP-9467

+
+ +

+ Allow @enum when AVP is defined in an inherited + dictionary.

+

+ 3GPP standards (for one) extend the values allowed for + RFC 3588 AVP's of type Enumerated. Previously, extending + an AVP was only possible by completely redefining the + AVP.

+

+ Own Id: OTP-9469

+
+ +

+ Migrate testsuites to pure common test and add both + suites and testcases.

+

+ Own Id: OTP-9553

+
+ +

+ Requests of arbitrary form.

+

+ diameter:call/4 can be passed anything, as long as the + subsequent prepare_request callback returns a term that + can be encoded.

+

+ Own Id: OTP-9581

+
+
+
+ +
+
diameter 0.9 -- cgit v1.2.3