<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
Inaki, I pinged you since you may be more familiar with procedures
about all this IETF output, but maybe others here can provide useful
information as well.<br>
<br>
At this moment the parser in Kamailio for Diversion header considers
it as with similar format as To header.<br>
<br>
Diversion (defined in an *Historic* rfc5806) is obsoleted by
History-Info(*Standard track* rfc4244). Its definition in rfc5806
is:<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre class="newpage">Diversion = "Diversion" ":" 1# (name-addr *( ";" diversion_params ))</pre>
<br>
and it is like To header. However, a newer *Informational* rfc6044,
redefines Diversion as:<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre class="newpage">Diversion = "Diversion" HCOLON diversion-params
*(COMMA diversion-params)
diversion-params = name-addr *(SEMI (diversion-reason /
diversion-counter / diversion-limit /
diversion-privacy / diversion-screen /
diversion-extension))</pre>
<br>
So in rfc6044, the sintax allow comma separated bodies for one
Diversion header, which was not in rfc5806. Obviously, the current
diversion parser throws error, so I guess it has to be updated to
accept a format similar to Route headers.<br>
<br>
My question is, apart of rfc number and the policy more recent
(bigger values) obsoletes older (lower value) specification, does
the Informational or Historic category to set some extra rules?<br>
<br>
Btw, are people here still using (or ever used -- I didn't so far)
Diversion?<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://linkedin.com/in/miconda">http://linkedin.com/in/miconda</a> -- <a class="moz-txt-link-freetext" href="http://twitter.com/miconda">http://twitter.com/miconda</a></pre>
</body>
</html>