From a2f9fa00d184d89619bfd61313387a943f9dd19e Mon Sep 17 00:00:00 2001 From: Anders Svensson Date: Fri, 26 Aug 2016 08:15:26 +0200 Subject: Fix xmllint errors in documentation --- lib/diameter/doc/src/diameter.xml | 138 +++++++++++++++++++------------------- 1 file changed, 69 insertions(+), 69 deletions(-) (limited to 'lib/diameter/doc/src/diameter.xml') diff --git a/lib/diameter/doc/src/diameter.xml b/lib/diameter/doc/src/diameter.xml index f9f3839094..72181a42b0 100644 --- a/lib/diameter/doc/src/diameter.xml +++ b/lib/diameter/doc/src/diameter.xml @@ -94,12 +94,12 @@ in this module.

-Address() -DiameterIdentity() -Grouped() -OctetString() -Time() -Unsigned32() +Address() +DiameterIdentity() +Grouped() +OctetString() +Time() +Unsigned32() UTF8String()

@@ -338,8 +338,8 @@ Has one of the following types.

-{'Origin-Host', &dict_DiameterIdentity;} -{'Origin-Realm', &dict_DiameterIdentity;} +{'Origin-Host', &dict_DiameterIdentity;} +{'Origin-Realm', &dict_DiameterIdentity;} {'Host-IP-Address', [&dict_Address;]}

@@ -351,8 +351,8 @@ question communicates an address list as described in &man_transport;

 -{'Vendor-Id', &dict_Unsigned32;} -{'Product-Name', &dict_UTF8String;} +{'Vendor-Id', &dict_Unsigned32;} +{'Product-Name', &dict_UTF8String;} {'Origin-State-Id', &dict_Unsigned32;}

@@ -365,8 +365,8 @@ can be used as to retrieve a value that is computed when the diameter application is started.

 -{'Supported-Vendor-Id', [&dict_Unsigned32;]} -{'Auth-Application-Id', [&dict_Unsigned32;]} +{'Supported-Vendor-Id', [&dict_Unsigned32;]} +{'Auth-Application-Id', [&dict_Unsigned32;]} {'Inband-Security-Id', [&dict_Unsigned32;]}

@@ -376,9 +376,9 @@ If 1 (TLS) is specified then TLS is selected if the CER/CEA received from the peer offers it.

 -{'Acct-Application-Id', [&dict_Unsigned32;]} -{'Vendor-Specific-Application-Id', [&dict_Grouped;]} -{'Firmware-Revision', &dict_Unsigned32;} +{'Acct-Application-Id', [&dict_Unsigned32;]} +{'Vendor-Specific-Application-Id', [&dict_Grouped;]} +{'Firmware-Revision', &dict_Unsigned32;} @@ -566,9 +566,8 @@ Can have one of the following types.

-start +start stop -

The service is being started or stopped. @@ -577,8 +576,8 @@ No event follows a stop event, and this event implies the termination of all transport processes.

 -{up, Ref, Peer, Config, Pkt} -{up, Ref, Peer, Config} +{up, Ref, Peer, Config, Pkt} +{up, Ref, Peer, Config} {down, Ref, Peer, Config} 
@@ -787,8 +786,8 @@ be matched by corresponding &capability; configuration, of
 
 
 
-
-{incoming_maxlen, 0..16777215}
+
+{incoming_maxlen, 0..16777215}
 
 

 Bound on the expected size of incoming Diameter messages.
@@ -916,8 +915,8 @@ Options monitor and link are ignored.

 Defaults to the empty list.

 
 
-
-{strict_mbit, boolean()}
+
+{strict_mbit, boolean()}
 
 

 Whether or not to regard an AVP setting the M-bit as erroneous when
@@ -934,7 +933,7 @@ Defaults to true.

 

 RFC 6733 is unclear about the semantics of the M-bit.
 One the one hand, the CCF specification in section 3.2 documents AVP
-in a command grammar as meaning any arbitrary AVP; on the
+in a command grammar as meaning any arbitrary AVP; on the
 other hand, 1.3.4 states that AVPs setting the M-bit cannot be added
 to an existing command: the modified command must instead be
 placed in a new Diameter application.

@@ -944,7 +943,7 @@ allowing arbitrary AVPs setting the M-bit in a command makes its
 interpretation implementation-dependent, since there's no
 guarantee that all implementations will understand the same set of
 arbitrary AVPs in the context of a given command.
-However, interpreting AVP in a command grammar as any
+However, interpreting AVP in a command grammar as any
 AVP, regardless of M-bit, renders 1.3.4 meaningless, since the receiver
 can simply ignore any AVP it thinks isn't relevant, regardless of the
 sender's intent.

@@ -959,8 +958,8 @@ occur in the message in question.

 
 
 
-
-{string_decode, boolean()}
+
+{string_decode, boolean()}
 
 

 Whether or not to decode AVPs of type &dict_OctetString; and its
@@ -1030,8 +1029,9 @@ Option passed to &add_transport;.
 Has one of the following types.

 
 
-
-{applications, [&application_alias;]}
+
+
+{applications, [&application_alias;]}
 
 

 Diameter applications to which the transport should be restricted.
@@ -1049,8 +1049,8 @@ implies having to set matching *-Application-Id AVPs in a
 
 
 
-
-{capabilities, [&capability;]}
+
+{capabilities, [&capability;]}
 
 

 AVPs used to construct outgoing CER/CEA messages.
@@ -1063,8 +1063,8 @@ may be particularly appropriate for Inband-Security-Id, in case
 TLS is desired over TCP as implemented by &man_tcp;.

 
 
-
-{capabilities_cb, &evaluable;}
+
+{capabilities_cb, &evaluable;}
 
 

 Callback invoked upon reception of CER/CEA during capabilities
@@ -1111,8 +1111,8 @@ case the corresponding callbacks are applied until either all return
 ok or one does not.

 
 
-
-{capx_timeout, &dict_Unsigned32;}
+
+{capx_timeout, &dict_Unsigned32;}
 
 

 Number of milliseconds after which a transport process having an
@@ -1126,8 +1126,8 @@ For a listening transport, the peer determines the timing.

 Defaults to 10000.

 
 
-
-{connect_timer, Tc}
+
+{connect_timer, Tc}
 
 
 Tc = &dict_Unsigned32;
@@ -1157,9 +1157,8 @@ Defaults to 30000 for a connecting transport and 60000 for a listening
 transport.

 
 
-
-{disconnect_cb, &evaluable;}
-
+
+{disconnect_cb, &evaluable;}
 
 

 Callback invoked prior to terminating the transport process of a
@@ -1235,8 +1234,8 @@ configured them.

 Defaults to a single callback returning dpr.

 
 
-
-{dpa_timeout, &dict_Unsigned32;}
+
+{dpa_timeout, &dict_Unsigned32;}
 
 

 Number of milliseconds after which a transport connection is
@@ -1246,8 +1245,8 @@ terminated following an outgoing DPR if DPA is not received.

 Defaults to 1000.

 
 
-
-{dpr_timeout, &dict_Unsigned32;}
+
+{dpr_timeout, &dict_Unsigned32;}
 
 

 Number of milliseconds after which a transport connection is
@@ -1258,8 +1257,8 @@ connection.

 Defaults to 5000.

 
 
-
-{length_errors, exit|handle|discard}
+
+{length_errors, exit|handle|discard}
 
 

 How to deal with errors in the Message Length field of the
@@ -1307,8 +1306,8 @@ the same peer.

 
 
 
-
-{spawn_opt, [term()]}
+
+{spawn_opt, [term()]}
 
 

 Options passed to &spawn_opt; when spawning a process for an
@@ -1319,8 +1318,8 @@ Options monitor and link are ignored.

 Defaults to the list configured on the service if not specified.

 
 
-
-{transport_config, term()}
+
+{transport_config, term()}
 {transport_config, term(), &dict_Unsigned32; | infinity}
 
 

@@ -1348,8 +1347,8 @@ request a connection with one peer over SCTP or another
 To listen on both SCTP and TCP, define one transport for each.

 
 
-
-{transport_module, atom()}
+
+{transport_module, atom()}
 
 

 Module implementing a transport process as defined in &man_transport;.
@@ -1368,8 +1367,9 @@ modules in order until one establishes a connection within the
 corresponding timeout (see below) or all fail.

 
 
-
-{watchdog_config, [{okay|suspect, non_neg_integer()}]}
+
+{watchdog_config,
+                       [{okay|suspect, non_neg_integer()}]}
 
 

 Configuration that alters the behaviour of the watchdog
@@ -1392,8 +1392,8 @@ misbehaving nodes during test.

 
 
 
-
-{watchdog_timer, TwInit}
+
+{watchdog_timer, TwInit}
 
 
 TwInit = &dict_Unsigned32;
@@ -1421,10 +1421,10 @@ Unrecognized options are silently ignored but are returned unmodified
 by &service_info; and can be referred to
 in predicate functions passed to &remove_transport;.

 
-
 
 
-transport_ref() = reference()
+
+transport_ref() = reference()
 
 

 Reference returned by &add_transport; that
@@ -1681,17 +1681,17 @@ returned.

 
 
 
-'Origin-Host'
-'Origin-Realm'
-'Vendor-Id'
-'Product-Name'
-'Origin-State-Id'
-'Host-IP-Address'
-'Supported-Vendor'
-'Auth-Application-Id'
-'Inband-Security-Id'
-'Acct-Application-Id'
-'Vendor-Specific-Application-Id'
+'Origin-Host'
+'Origin-Realm'
+'Vendor-Id'
+'Product-Name'
+'Origin-State-Id'
+'Host-IP-Address'
+'Supported-Vendor'
+'Auth-Application-Id'
+'Inband-Security-Id'
+'Acct-Application-Id'
+'Vendor-Specific-Application-Id'
 'Firmware-Revision'
 
 

-- 
cgit v1.2.3