On 2/9/16 4:52 AM, Roger Wiklund wrote:
Hi
If a request contains multiple Diversion headers, can one assume that
the topmost is used, or is this up to the application?
I'm looking for a MUST in one of the RFCs.
You won't find one.
Note that the Diversion header was an unsuccessful effort. It was first
submitted as a draft 16 years ago, and was never approved as a draft
standard. Eventually (much later) a different approach (History-Info
(RFC7044) was approved to address the same problem, among others.
In the meantime various implementations started using Diversion based on
the unapproved draft.
Finally there was agreement to publish the unapproved Diversion draft
(as RFC5806). It was published "as-is", without resolving open issues
about it, and as a "historic" RFC. That means it is intended simply to
provide a stable reference for something that is *not* currently
approved as a standard of any kind.
So it is what it is. There will be no formal clarifications.
If you are asking this question, I presume that it is because you are
trying to interoperate with something that uses it, and perhaps have a
dispute about how it works. In that case your only recourse is to be
consistent with what you are trying to interoperate with.
If you are designing something new, without need for compatibility with
existing implementations using it, *do not* use Diversion.
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
