<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.loreto-sipping-3892bis" target="https://datatracker.ietf.org/doc/html/draft-loreto-sipping-3892bis-01">
   <front>
      <title>Updates to Referred-By in the Session Initiation Protocol (SIP).</title>
      <author initials="N." surname="Bishai" fullname="Nadia Bishai">
         <organization>Ericsson</organization>
      </author>
      <author initials="S." surname="Loreto" fullname="Salvatore Loreto">
         <organization>Ericsson</organization>
      </author>
      <author initials="A." surname="Haruna" fullname="Adamu Haruna">
         <organization>Nokia</organization>
      </author>
      <date month="March" day="1" year="2009" />
      <abstract>
	 <t>SIP has a mechanism for conveying the identity of the referrer of a
request by means of the Referred-By header field.  This header field
may be used when exploding a SIP MESSAGE request to a pre-defined
group URI and when exploding a SIP INVITE request to an ad-hoc group
or to a pre-defined group URI.  The Referred-By header is only
included if the P-Asserted-Identity header field or From header field
in the exploded SIP requests needs to carry another value, e.g. the
URI of a pre-defined group, or a conference focus URI.  In those
cases, the Referred-By header field in the resulting exploded
requests is set to the P-Asserted-Identity header field or to the
From header field of the original SIP request received before
exploding to convey to the receiver the identity of the original
inviting sender.

RFC 3892 restricts the value of the header to only one SIP URI.
However the P-Asserted-Identity header field currently allows two URI
values and may be expanded in the future to carry more than two
values as described in draft-ietf-sipping-update-pai-09.  This
document extends the Referred-By definition to support more than one
value as well.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-loreto-sipping-3892bis-01" />
   
</reference>
