File: rfc7463.html

package info (click to toggle)
doc-rfc 20201128-1
links: PTS, VCS
area: non-free
in suites: bullseye
size: 1,307,124 kB
file content (4029 lines) | stat: -rw-r--r-- 204,353 bytes
parent folder | download | duplicates (2)
<pre>Internet Engineering Task Force (IETF)                  A. Johnston, Ed.
Request for Comments: 7463                                         Avaya
Updates: <a href="./rfc3261">3261</a>, <a href="./rfc4235">4235</a>                                 M. Soroushnejad, Ed.
Category: Standards Track                              V. Venkataramanan
ISSN: 2070-1721                                   Sylantro Systems Corp.
                                                              March 2015


       <span class="h1">Shared Appearances of a Session Initiation Protocol (SIP)</span>
                        <span class="h1">Address of Record (AOR)</span>

Abstract

   This document describes the requirements and implementation of a
   group telephony feature commonly known as Bridged Line Appearance
   (BLA) or Multiple Line Appearance (MLA), or Shared Call/Line
   Appearance (SCA).  When implemented using the Session Initiation
   Protocol (SIP), it is referred to as shared appearances of an Address
   of Record (AOR) since SIP does not have the concept of lines.  This
   feature is commonly offered in IP Centrex services and IP Private
   Branch Exchange (IPBX) offerings and is likely to be implemented on
   SIP IP telephones and SIP feature servers used in a business
   environment.  This feature allows several user agents (UAs) to share
   a common AOR, learn about calls placed and received by other UAs in
   the group, and pick up or join calls within the group.  This document
   discusses use cases, lists requirements, and defines extensions to
   implement this feature.  This specification updates RFCs 3261 and
   4235.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc7463">http://www.rfc-editor.org/info/rfc7463</a>.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.




<span class="grey">Johnston, et al.             Standards Track                    [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-2">2</a>.  Conventions Used in This Document . . . . . . . . . . . . . .   <a href="#page-5">5</a>
   <a href="#section-3">3</a>.  Usage Scenarios . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-5">5</a>
     <a href="#section-3.1">3.1</a>.  Executive/Assistant Arrangement . . . . . . . . . . . . .   <a href="#page-5">5</a>
     <a href="#section-3.2">3.2</a>.  Call Group  . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-5">5</a>
     <a href="#section-3.3">3.3</a>.  Single Line Extension . . . . . . . . . . . . . . . . . .   <a href="#page-6">6</a>
     <a href="#section-3.4">3.4</a>.  Changing UAs  . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-6">6</a>
   <a href="#section-4">4</a>.  Requirements and Implementation . . . . . . . . . . . . . . .   <a href="#page-6">6</a>
     <a href="#section-4.1">4.1</a>.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-6">6</a>
     <a href="#section-4.2">4.2</a>.  Implementation  . . . . . . . . . . . . . . . . . . . . .   <a href="#page-8">8</a>
   <a href="#section-5">5</a>.  Normative Description . . . . . . . . . . . . . . . . . . . .  <a href="#page-10">10</a>
     <a href="#section-5.1">5.1</a>.  Elements  . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-11">11</a>
     <a href="#section-5.2">5.2</a>.  Shared Appearance Dialog Package Extensions . . . . . . .  <a href="#page-11">11</a>
       <a href="#section-5.2.1">5.2.1</a>.  The &lt;appearance&gt; Element  . . . . . . . . . . . . . .  <a href="#page-11">11</a>
       <a href="#section-5.2.2">5.2.2</a>.  The &lt;exclusive&gt; Element . . . . . . . . . . . . . . .  <a href="#page-12">12</a>
       <a href="#section-5.2.3">5.2.3</a>.  The &lt;joined-dialog&gt; Element . . . . . . . . . . . . .  <a href="#page-12">12</a>
       <a href="#section-5.2.4">5.2.4</a>.  The &lt;replaced-dialog&gt; Element . . . . . . . . . . . .  <a href="#page-13">13</a>
     <a href="#section-5.3">5.3</a>.  Shared Appearance User Agents . . . . . . . . . . . . . .  <a href="#page-13">13</a>
       <a href="#section-5.3.1">5.3.1</a>.  Appearance Numbers and Call Context . . . . . . . . .  <a href="#page-16">16</a>
       <a href="#section-5.3.2">5.3.2</a>.  Appearance Numbers and Call Control . . . . . . . . .  <a href="#page-17">17</a>
       <a href="#section-5.3.3">5.3.3</a>.  Appearance Numbers and Transfer . . . . . . . . . . .  <a href="#page-18">18</a>
     <a href="#section-5.4">5.4</a>.  Appearance Agent  . . . . . . . . . . . . . . . . . . . .  <a href="#page-18">18</a>
   <a href="#section-6">6</a>.  XML Schema Definition . . . . . . . . . . . . . . . . . . . .  <a href="#page-21">21</a>
   <a href="#section-7">7</a>.  Alert-Info Appearance Parameter Definition  . . . . . . . . .  <a href="#page-23">23</a>



<span class="grey">Johnston, et al.             Standards Track                    [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   <a href="#section-8">8</a>.  User Interface Considerations . . . . . . . . . . . . . . . .  <a href="#page-24">24</a>
     <a href="#section-8.1">8.1</a>.  Appearance Number Rendering . . . . . . . . . . . . . . .  <a href="#page-24">24</a>
       <a href="#section-8.1.1">8.1.1</a>.  Single Appearance UAs . . . . . . . . . . . . . . . .  <a href="#page-24">24</a>
       <a href="#section-8.1.2">8.1.2</a>.  Dual Appearance UAs . . . . . . . . . . . . . . . . .  <a href="#page-24">24</a>
       8.1.3.  Shared Appearance UAs with Fixed Appearance Number  .  25
       8.1.4.  Shared Appearance UAs with Variable Appearance
               Numbers . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-25">25</a>
       <a href="#section-8.1.5">8.1.5</a>.  Example User Interface Issues . . . . . . . . . . . .  <a href="#page-25">25</a>
     <a href="#section-8.2">8.2</a>.  Call State Rendering  . . . . . . . . . . . . . . . . . .  <a href="#page-26">26</a>
   <a href="#section-9">9</a>.  Interoperability with Non-shared Appearance UAs . . . . . . .  <a href="#page-26">26</a>
     <a href="#section-9.1">9.1</a>.  Appearance Assignment . . . . . . . . . . . . . . . . . .  <a href="#page-26">26</a>
     <a href="#section-9.2">9.2</a>.  Appearance Release  . . . . . . . . . . . . . . . . . . .  <a href="#page-27">27</a>
     9.3.  UAs Supporting Dialog Events but Not Shared Appearance  .  27
   <a href="#section-10">10</a>. Provisioning Considerations . . . . . . . . . . . . . . . . .  <a href="#page-27">27</a>
   <a href="#section-11">11</a>. Example Message Flows . . . . . . . . . . . . . . . . . . . .  <a href="#page-28">28</a>
     <a href="#section-11.1">11.1</a>.  Registration and Subscription  . . . . . . . . . . . . .  <a href="#page-28">28</a>
     <a href="#section-11.2">11.2</a>.  Appearance Selection for Incoming Call . . . . . . . . .  <a href="#page-32">32</a>
     <a href="#section-11.3">11.3</a>.  Outgoing Call without Appearance Seizure . . . . . . . .  <a href="#page-35">35</a>
     <a href="#section-11.4">11.4</a>.  Outgoing Call with Appearance Seizure  . . . . . . . . .  <a href="#page-38">38</a>
     <a href="#section-11.5">11.5</a>.  Outgoing Call without Using an Appearance Number . . . .  <a href="#page-42">42</a>
     <a href="#section-11.6">11.6</a>.  Appearance Release . . . . . . . . . . . . . . . . . . .  <a href="#page-44">44</a>
     <a href="#section-11.7">11.7</a>.  Appearance Pickup  . . . . . . . . . . . . . . . . . . .  <a href="#page-45">45</a>
     <a href="#section-11.8">11.8</a>.  Call between UAs within the Group  . . . . . . . . . . .  <a href="#page-50">50</a>
     <a href="#section-11.9">11.9</a>.  Consultation Hold with Appearances . . . . . . . . . . .  <a href="#page-52">52</a>
     <a href="#section-11.10">11.10</a>. Joining or Bridging an Appearance  . . . . . . . . . . .  <a href="#page-55">55</a>
     <a href="#section-11.11">11.11</a>. Loss of Appearance during Allocation . . . . . . . . . .  <a href="#page-58">58</a>
     <a href="#section-11.12">11.12</a>. Appearance Seizure Contention Race Condition . . . . . .  <a href="#page-59">59</a>
     <a href="#section-11.13">11.13</a>. Appearance Agent Subscription to UAs . . . . . . . . . .  <a href="#page-60">60</a>
     <a href="#section-11.14">11.14</a>. Appearance Pickup Race Condition Failure . . . . . . . .  <a href="#page-62">62</a>
     11.15. Appearance Seizure Incoming/Outgoing Contention Race
            Condition  . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-65">65</a>
   <a href="#section-12">12</a>. Security Considerations . . . . . . . . . . . . . . . . . . .  <a href="#page-66">66</a>
   <a href="#section-13">13</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  <a href="#page-67">67</a>
     <a href="#section-13.1">13.1</a>.  SIP Event Header Field Parameter: shared . . . . . . . .  <a href="#page-67">67</a>
     <a href="#section-13.2">13.2</a>.  SIP Alert-Info Header Field Parameter: appearance  . . .  <a href="#page-68">68</a>
     <a href="#section-13.3">13.3</a>.  URN Sub-Namespace Registration: sa-dialog-info . . . . .  <a href="#page-68">68</a>
     <a href="#section-13.4">13.4</a>.  XML Schema Registration  . . . . . . . . . . . . . . . .  <a href="#page-68">68</a>
   <a href="#section-14">14</a>. References  . . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-69">69</a>
     <a href="#section-14.1">14.1</a>.  Normative References . . . . . . . . . . . . . . . . . .  <a href="#page-69">69</a>
     <a href="#section-14.2">14.2</a>.  Informative References . . . . . . . . . . . . . . . . .  <a href="#page-70">70</a>
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-71">71</a>
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-71">71</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The feature and functionality requirements for SIP user agents (UAs)
   supporting business telephony applications differ greatly from basic
   SIP UAs, both in terms of services and end-user experience.  In



<span class="grey">Johnston, et al.             Standards Track                    [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   addition to basic SIP support [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>], many of the services in a
   business environment require the support for SIP extensions such as
   REFER [<a href="./rfc3515" title="&quot;The Session Initiation Protocol (SIP) Refer Method&quot;">RFC3515</a>], SUBSCRIBE/NOTIFY [<a href="./rfc6665" title="&quot;SIP-Specific Event Notification&quot;">RFC6665</a>], PUBLISH [<a href="./rfc3903" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">RFC3903</a>], the
   SIP Replaces [<a href="./rfc3891" title="&quot;The Session Initiation Protocol (SIP) &quot;">RFC3891</a>], and Join [<a href="./rfc3911" title="&quot;The Session Initiation Protocol (SIP) &quot;">RFC3911</a>] header fields, etc.  Many
   of the popular business services have been documented in the SIP
   Service Examples [<a href="./rfc5359" title="&quot;Session Initiation Protocol Service Examples&quot;">RFC5359</a>].

   This specification details a method for implementing a group
   telephony feature known variously in telephony as Bridged Line
   Appearance (BLA) or Multiple Line Appearances (MLA), one of the more
   popular advanced features expected of SIP IP telephony devices in a
   business environment.  Other names for this feature include Shared
   Call/Line Appearance (SCA), Shared Call Status and Multiple Call
   Appearance (MCA).  A variant of this feature is known as Single Line
   Extension.

   This document looks at how this feature can be implemented using
   standard SIP [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>] in conjunction with SIP events [<a href="./rfc6665" title="&quot;SIP-Specific Event Notification&quot;">RFC6665</a>] and
   publication [<a href="./rfc3903" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">RFC3903</a>] (carrying the SIP dialog state event package
   [<a href="./rfc4235" title="&quot;An INVITE- Initiated Dialog Event Package for the Session Initiation Protocol (SIP)&quot;">RFC4235</a>]) for exchanging status among UAs.

   In traditional telephony, the line is physical.  A common scenario in
   telephony is for a number of business telephones to share a single or
   a small number of lines.  The sharing or appearance of these lines
   between a number of phones is what gives this feature its name.  A
   common scenario in SIP is for a number of business telephones to
   share a single or a small number of Address of Record (AOR) URIs.

   In addition, an AOR can have multiple appearances on a single UA in
   terms of the user interface.  The appearance number relates to the
   user interface for the telephone; typically, each appearance of an
   AOR has a visual display (lamp that can change color or blink or a
   screen icon) and a button (used to select the appearance) where each
   appearance number is associated with a different dialog to/from the
   AOR.  The telephony concept of line appearance is still relevant to
   SIP due to the user interface considerations.  It is important to
   keep the appearance number construct because:

   1.  Human users are used to the concept and will expect it in
       replacement systems (e.g., an overhead page announcement says
       "Joe pickup line 3").

   2.  It is a useful structure for user interface representation.

   The purpose of the appearance number is to identify active calls to
   facilitate sharing between users (e.g., passing a call from one user
   to another).  If a telephone has enough buttons/lamps, the appearance
   number could be the positional sequence number of the button.  If



<span class="grey">Johnston, et al.             Standards Track                    [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   not, it may still be desirable to present the call state, but the
   appearance number should be displayed so that users know which call,
   for example, is on hold on which key.

   In this document, except for the usage scenarios in the next section,
   we will use the term "appearance" rather than "line appearance" since
   SIP does not have the concept of lines.  Note that this does not mean
   that a conventional telephony user interface (lamps and buttons) must
   be used: implementations may use another metaphor as long as the
   appearance number is readily apparent to the user.  Each AOR has a
   separate appearance numbering space.  As a result, a given UA user
   interface may have multiple occurrences of the same appearance
   number, but they will be for different AORs.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Conventions Used in This Document</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>]
   and indicate requirement levels for compliant mechanisms.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Usage Scenarios</span>

   The following examples are common applications of the shared
   appearances feature and are mentioned here as informative use cases.
   All these example usages can be supported by the shared appearances
   feature described in this document.  The main differences relate to
   the user interface considerations of the device.

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  Executive/Assistant Arrangement</span>

   The appearances on the executive's UA also appear on the assistant's
   UA.  The assistant may answer incoming calls to the executive and
   then place the call on hold for the executive to pick up.  The
   assistant can always see the state of all calls on the executive's
   UA.

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  Call Group</span>

   Users with similar business needs or tasks can be assigned to
   specific groups and share an AOR.  For example, an IT department
   staff of five might answer a help line that has three appearances on
   each phone in the IT work area.  A call answered on one phone can be
   put on hold and picked up on another phone.  A shout or an IM to
   another staff member can result in them taking over a call on a
   particular appearance.  Another phone can request to be added/joined/
   bridged to an existing appearance resulting in a conference call.




<span class="grey">Johnston, et al.             Standards Track                    [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  Single Line Extension</span>

   In this scenario, incoming calls are offered to a group of UAs.  When
   one answers, the other UAs are informed.  If another UA in the group
   seizes the line (i.e., goes off-hook), it is immediately bridged or
   joined in with the call.  This mimics the way residential telephone
   extensions usually operate.

<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>.  Changing UAs</span>

   A user is on a call on one UA and wishes to change devices and
   continue the call on another UA.  They place the call on hold, note
   the appearance number of the call, then walk to another UA.  They are
   able to identify the same appearance number on the other UA, pick up
   the call, and continue the conversation.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Requirements and Implementation</span>

   The next section details the requirements and discusses the
   implementation of the shared appearances feature.

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Requirements</span>

   The basic requirements of the shared appearances feature can be
   summarized as follows:

   REQ-1:   Incoming calls to the AOR must be offered to a group of UAs
            and can be answered by any of them.

   REQ-2:   Each UA in the group must be able to learn the call status
            of the others in the group for the purpose of rendering this
            information to the user.

   REQ-3:   A UA must be able to join (also called bridge or conference
            together) or pick up (take) an active call of another UA in
            the group in a secure way.

   REQ-4:   The mechanism should require the minimal amount of
            configuration.  UAs registering against the group AOR should
            be able to participate in the shared appearance group
            without manual configuration of group members.

   REQ-5:   The mechanism must scale for large numbers of appearances
            and large numbers of UAs without introducing excessive
            messaging traffic.

   REQ-6:   Each call or session (incoming or outgoing) should be
            assigned a common "appearance" number from a managed pool



<span class="grey">Johnston, et al.             Standards Track                    [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


            administered for the AOR group.  Once the session has
            terminated, the appearance number is released back into the
            pool and can be reused by another incoming or outgoing
            session.

   REQ-7:   Each UA in the group must be able to learn the status of all
            appearances of the group.

   REQ-8:   There must be mechanisms to resolve appearance contention
            among the UAs in the group.  Contention in this context
            means an appearance number being associated with multiple
            dialogs that are not mixed or otherwise associated.

   REQ-9:   The mechanism must allow all UAs receiving an incoming
            session request to utilize the same appearance number at the
            time of alerting.

   REQ-10:  The mechanism must have a way of reconstructing appearance
            state after an outage that does not result in excessive
            traffic and processing.

   REQ-11:  The mechanism must have backwards compatibility such that a
            UA that is unaware of the feature can still register against
            the group AOR and make and receive calls.

   REQ-12:  The mechanism must not allow UAs outside the group to
            select, seize, or manipulate appearance numbers.

   REQ-13:  For privacy reasons, there must be a mechanism so that
            appearance information is not leaked outside the group of
            UAs (e.g., "So who do you have on line 1?").

   REQ-14:  The mechanism must support a way for UAs to request
            exclusivity on a line appearance.  Exclusivity means that
            the UA requesting it desires a private conversation with the
            external party and other UAs must not be allowed to join or
            take the call.  Exclusivity may be requested at the start of
            an incoming or outgoing session or during the session.  An
            exclusivity request may be accepted or rejected by the
            entity providing the shared appearance service.  Therefore,
            the mechanism must provide a way of communicating the result
            back to the requester UA.

   REQ-15:  The mechanism should support a way for a UA to seize a
            particular appearance number for outgoing requests prior to
            sending the actual request.  This is often called seizure.





<span class="grey">Johnston, et al.             Standards Track                    [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   REQ-16:  The mechanism should support a way for a UA to seize a
            particular appearance number and also send the request at
            the same time.  This is needed when an automatic ringdown
            feature (a telephone configured to immediately dial a phone
            number when it goes off-hook) is combined with shared
            appearances.  In this case, seizing the line is integrated
            with dialing.

<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Implementation</span>

   This section non-normatively discusses the implementation of the
   shared appearances feature.  The normative description is in
   <a href="#section-5">Section 5</a>.  Many of the requirements for this service can be met
   using standard SIP mechanisms such as:

   o  A SIP Forking Proxy and Registrar/Location Service meets REQ-1.

   o  The SIP Dialog Package meets REQ-2.

   o  The combination of the SIP Replaces and Join header fields meets
      REQ-3.

   o  The use of a State Agent for the Dialog Package meets REQ-4 and
      REQ-5.

   REQ-6 suggests the need for an entity that manages the appearance
   resource.  Just as conferencing systems commonly have a single point
   of control, known as a focus, a shared appearance group has a single
   point of control of the appearance shared resource.  This is defined
   as an Appearance Agent for a group.  While an Appearance Agent can be
   part of a centralized server, it could also be co-resident in a
   member UA that has taken on this functionality for a group.  The
   Appearance Agent knows or is able to determine the dialog state of
   all members of the group.

   While the appearance resource could be managed cooperatively by a
   group of UAs without any central control, this is outside the scope
   of this document.  It is also possible that the Appearance Agent
   logic could be distributed in all UAs in the group.  For example,
   rules that govern assigning appearance numbers for incoming requests
   (e.g., lowest available appearance number) and rules for contention
   handling (e.g., when two UAs request the use of the same appearance
   number, hash dialog identifiers and compare with the lowest hash
   winning) would need to be defined and implemented.

   To best meet REQ-9, the appearance number for an incoming INVITE
   needs to be contained in the INVITE, in addition to being delivered
   in the dialog package NOTIFY.  Otherwise, if the NOTIFY is delayed or



<span class="grey">Johnston, et al.             Standards Track                    [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   lost, a UA in the group might receive an incoming INVITE but might
   not know which appearance number to render during alerting.

   This specification defines an extension parameter, which is
   normatively defined in <a href="#section-7">Section 7</a>, for the Alert-Info header field in
   <a href="./rfc3261">RFC 3261</a> to carry the appearance number:

   Alert-Info: &lt;urn:alert:service:normal&gt;;appearance=1

   The following list describes the operation of the shared appearances
   feature.

   1.  A UA is configured with the AOR of a shared appearance group.  It
       registers against the AOR, then attempts a dialog state
       subscription to the AOR.  If the subscription fails, loops back
       to itself, or returns an error, it knows there is no State Agent
       and, hence, no Appearance Agent and this feature is not
       implemented.

   2.  If the subscription receives a 200 OK, the UA knows there is a
       State Agent and that the feature is implemented.  The UA then
       follows the steps in this list.

   3.  Information learned about the dialog state of other UAs in the
       group is rendered to the user.

   4.  Incoming calls are forked to all UAs in the group, and any may
       answer.  UAs receive the appearance number to use in rendering
       the incoming call in a NOTIFY from the Appearance Agent and in
       the INVITE itself.  The UA will also receive a notification if
       the call is answered by another UA in the group so this
       information can be rendered to the user.

   5.  For outgoing calls, the operation depends on the implementation.
       If the user seizes a particular appearance number for the call,
       the UA publishes the trying state dialog information with the
       desired appearance number and waits for a 2xx response before
       sending the INVITE.

   6.  For outgoing calls, if the user does not seize a particular
       appearance or does not care, the INVITE can be sent immediately,
       and the appearance number learned as the call progresses from a
       notification from the Appearance Agent.

   7.  For outgoing calls, if the user does not want an appearance
       number assigned (such as during a consultation call or if a UA is
       fetching 'service media' such as music on hold [<a href="./rfc7088" title="&quot;Session Initiation Protocol Service Example -- Music on Hold&quot;">RFC7088</a>]), the UA




<span class="grey">Johnston, et al.             Standards Track                    [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


       also publishes prior to sending the INVITE but does not include
       an appearance number in the publication.

   8.  Established calls within the group may be joined (bridged) or
       taken (picked) by another UA.  Information in the dialog package
       notifications can be used to construct Join or Replaces header
       fields.  Since the same appearance number is used for these types
       of operations, this information is published prior to sending the
       INVITE Join or INVITE Replaces.

   9.  The Appearance Agent may not have direct access to the complete
       dialog state of some or all of the UAs in the group.  If this is
       the case, the Appearance Agent will subscribe to the dialog state
       of individual UAs in the group to obtain this information.  In
       any case, the Appearance Agent will send normal notifications
       (via the subscriptions established by the UAs in step 1) every
       time the aggregate dialog state of the AOR changes, including
       when calls are placed, answered, placed on and off hold, and hung
       up.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Normative Description</span>

   This section normatively describes the shared appearances feature
   extensions.  The following definitions are used throughout this
   document:

   Appearance number:  An appearance number is a positive integer
      associated with one or more dialogs of an AOR.  Appearance numbers
      are managed by an Appearance Agent and displayed and rendered to
      the user by UAs that support this specification.  When an
      appearance number is assigned or requested, generally the assigned
      number is the smallest positive integer that is not currently
      assigned as an appearance number to a dialog for this AOR.  This
      specification does not define an upper limit on appearance
      numbers; however, using appearance numbers that are not easily
      represented using common integer representations is likely to
      cause failures.

   Seizing:  An appearance can be reserved prior to a call being placed
      by seizing the appearance.  An appearance can be seized by
      communicating an artificial state of "trying" prior to actually
      initiating a dialog (i.e., sending the INVITE), in order to appear
      as if it were already initiating a dialog.

   Selecting (or Not-Seizing):  An appearance is merely selected (i.e.,
      not seized) if there is no such communication of artificial state
      of "trying" prior to initiating a dialog: i.e., the state is




<span class="grey">Johnston, et al.             Standards Track                   [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


      communicated when the dialog is actually initiated.  The
      appearance number is learned after the INVITE is sent.

<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  Elements</span>

   A complete system to implement this feature consists of:

   1.  UAs that support publications, subscriptions, and notifications
       for the SIP dialog event package and the shared appearance dialog
       package extensions and behavior.

   2.  An Appearance Agent consisting of a State Agent for the dialog
       event package that implements an Event State Compositor (ESC) and
       the shared appearance dialog package extensions and behavior.
       The Appearance Agent also has logic for assigning and releasing
       appearance numbers and resolving appearance number contention.

   3.  A forking proxy server that can communicate with the State Agent.

   4.  A registrar that supports the registration event package.

   The behavior of these elements is described normatively in the
   following sections after the definitions of the dialog package
   extensions.

<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>.  Shared Appearance Dialog Package Extensions</span>

   This specification defines four new elements as extensions to the SIP
   Dialog Event package [<a href="./rfc4235" title="&quot;An INVITE- Initiated Dialog Event Package for the Session Initiation Protocol (SIP)&quot;">RFC4235</a>].  The schema is defined in <a href="#section-6">Section 6</a>.
   The elements are &lt;appearance&gt;, &lt;exclusive&gt;, &lt;joined-dialog&gt;, and
   &lt;replaced-dialog&gt;, which are sub-elements of the &lt;dialog&gt; element.

<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>.  The &lt;appearance&gt; Element</span>

   The &lt;appearance&gt; element, a child of the &lt;dialog&gt; element, is used to
   convey the appearance number of the dialog described by the parent
   &lt;dialog&gt; element.  When sent by a UA in a PUBLISH with parent
   &lt;dialog&gt; with state attribute "trying" to the Appearance Agent, the
   UA is requesting assignment of the given appearance number to the
   current or future dialog with the given dialog identifiers.  When an
   &lt;appearance&gt; element is sent by the Appearance Agent in a NOTIFY, it
   indicates that the appearance number has been assigned to the
   specified dialog.

   Note that a &lt;dialog-info&gt; element describes the contained dialogs
   from the point of view of the UA (named by the "entity" attribute),
   regardless of whether the containing request is sent by the UA or the
   Appearance Agent.  In particular, if the UA sent a request within the



<span class="grey">Johnston, et al.             Standards Track                   [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   described dialog, the To header field URI would match the &lt;remote&gt;
   &lt;identity&gt; value and the to-tag parameter would match the remote-tag
   attribute.  Similarly, the From header field URI would match the
   &lt;local&gt; &lt;identity&gt; value and the from-tag parameter would match the
   local-tag attribute.

<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>.  The &lt;exclusive&gt; Element</span>

   The &lt;exclusive&gt; element, a child of the &lt;dialog&gt; element, is a
   boolean, which, when true, indicates that the UA is not willing to
   accept an INVITE with a Join or Replaces header field targeted to the
   dialog described by the &lt;dialog&gt; element that is the parent of the
   &lt;exclusive&gt; element.  For example, some shared appearance systems
   only allow call pickup when the call is on hold.  In this case, the
   &lt;exclusive&gt; element should be set to "false" when the call is held
   and "true" when the call is not held, rather than having the
   "exclusive" value implied by the hold state.

   It is important to note that this element is a hint.  In order to
   prevent another UA from taking or joining a call, a UA can, in
   addition to setting the &lt;exclusive&gt; tag, not report full dialog
   information to the Appearance Agent.  Not having the full dialog
   information (Call-ID, remote-tag, and local-tag) prevents another UA
   from constructing a Join or Replaces header field.  Although a UA may
   set &lt;exclusive&gt; to "true", the UA must still be ready to reject an
   INVITE Join relating to this dialog.  If these dialog identifiers
   have already been shared with the Appearance Agent, the UA could send
   an INVITE Replaces to change them and then not report the new ones to
   the Appearance Agent.

   If the proxy knows which dialogs are marked exclusive, the proxy MAY
   enforce this exclusivity by rejecting INVITE Join and INVITE Replaces
   requests containing those dialog identifiers with a 403 (Forbidden)
   response.

      Note that exclusivity has nothing to do with appearance number
      selection or seizing -- instead, it is about call control
      operations that can be performed on a dialog.

   If the &lt;exclusive&gt; element is not present, it is assumed to be false.

<span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>.  The &lt;joined-dialog&gt; Element</span>

   The &lt;joined-dialog&gt; element, a child of the &lt;dialog&gt; element, is used
   to convey dialog identifiers of any other dialogs that are joined
   (mixed or bridged) with the dialog.  Only the UA that is the common
   endpoint of the mixed dialogs (and thus controlling the mixing
   operation) should include this element in publications to the



<span class="grey">Johnston, et al.             Standards Track                   [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Appearance Agent.  Note that this element should still be used even
   when the Join header field was not used to join the dialogs.  For
   example, two separate dialogs on a UA could be joined without any SIP
   call control operations.  Joined dialogs will share the same
   appearance number.

   If the &lt;joined-dialog&gt; element is not present, it is assumed that the
   dialog is not joined or to be joined to any other dialog.

<span class="h4"><a class="selflink" id="section-5.2.4" href="#section-5.2.4">5.2.4</a>.  The &lt;replaced-dialog&gt; Element</span>

   The &lt;replaced-dialog&gt; element, a child of the &lt;dialog&gt; element, is
   used to convey dialog identifiers of any other dialogs that will be
   or have been replaced with this dialog.  For example, a UA in the
   group picking up a call on another UA by sending an INVITE with
   Replaces would include this element for the replacing dialog.
   Replaced dialogs will share the same appearance number.

   If the &lt;replaced-dialog&gt; element is not present, it is assumed that
   the dialog has not replaced or is not to replace to any other dialog.

<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>.  Shared Appearance User Agents</span>

   UAs that support the shared appearances feature use the dialog state
   package [<a href="./rfc4235" title="&quot;An INVITE- Initiated Dialog Event Package for the Session Initiation Protocol (SIP)&quot;">RFC4235</a>] with the shared appearance extensions and the
   'shared' Event header field parameter defined in <a href="#section-13">Section 13</a>.

   UAs use the dialog package extensions in <a href="#section-5.2">Section 5.2</a> along with
   SUBSCRIBE [<a href="./rfc6665" title="&quot;SIP-Specific Event Notification&quot;">RFC6665</a>], NOTIFY [<a href="./rfc6665" title="&quot;SIP-Specific Event Notification&quot;">RFC6665</a>], and PUBLISH [<a href="./rfc3903" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">RFC3903</a>].
   SUBSCRIBE, NOTIFY, and PUBLISH requests for the dialog event package
   include the 'shared' Event header field parameter as required by this
   specification.

      The presence of the 'shared' Event header field parameter tells
      the Appearance Agent that the UA supports this specification.

   Upon initialization, the UA MUST subscribe to the dialog event
   package of the AOR and refresh the subscription per the SIP Events
   Framework [<a href="./rfc6665" title="&quot;SIP-Specific Event Notification&quot;">RFC6665</a>].  If the SUBSCRIBE request fails, then no
   Appearance Agent may be present and this feature is not active for
   this AOR.  The UA MAY periodically retry the subscription to see if
   conditions have changed at intervals no shorter than four hours.

      Four hours was chosen to limit the subscription test to six per
      day per UA.  Increasing this interval would reduce this failure
      traffic but take longer for a newly activated Appearance Agent to
      be discovered.




<span class="grey">Johnston, et al.             Standards Track                   [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   UAs can also use the presence of the 'shared' Event header field
   parameter in NOTIFYs to discover the presence of an Appearance Agent
   for the AOR.

   UAs that implement the shared appearances feature, call pickup,
   joining, and bridging MUST support sending an INVITE with Replaces
   [<a href="./rfc3891" title="&quot;The Session Initiation Protocol (SIP) &quot;">RFC3891</a>]  or Join [<a href="./rfc3911" title="&quot;The Session Initiation Protocol (SIP) &quot;">RFC3911</a>].  The User Agent Client (UAC) needs to
   include the to-tag and from-tag information in the Replaces or Join
   header so that the correct dialog will be matched by the User Agent
   Server (UAS) per the rules in RFCs 3891 and 3911.

   All UAs that implement the shared appearances feature and support
   INVITE MUST support receiving an INVITE with a Replaces [<a href="./rfc3891" title="&quot;The Session Initiation Protocol (SIP) &quot;">RFC3891</a>] or
   a Join [<a href="./rfc3911" title="&quot;The Session Initiation Protocol (SIP) &quot;">RFC3911</a>] header field.

   When publishing or notifying dialog package information, a UA
   includes the largest set of dialog identification available at the
   time of publication, with the exception that a UA may omit
   information if it wishes to prevent other UAs from joining or picking
   up a call.  Dialog identification includes local and remote target
   URIs, call-id, to-tag, and from-tag.  While this dialog
   identification information is optional in [<a href="./rfc4235" title="&quot;An INVITE- Initiated Dialog Event Package for the Session Initiation Protocol (SIP)&quot;">RFC4235</a>], it is essential
   in the shared appearances feature, allowing call control operations.
   When placing calls on hold, use the "+sip.rendering=no" feature tag
   to indicate this in dialog package notifications.  Using the full SDP
   session description instead forces the endpoint to do a lot of extra
   parsing, unnecessarily complicating the code and inviting errors.

      The accurate rendering of the idle/active/alerting/hold state of
      other UAs in the group is an important part of the shared
      appearances feature.

   A UA that does not need to seize a particular appearance number (or
   doesn't care) would just send an INVITE as normal to place an
   outbound call.

   If the call is an emergency call, a UA MUST never wait for a
   confirmed seizure before sending an INVITE.  Instead, the emergency
   call MUST proceed without waiting for the PUBLISH transaction.

   If a UA requires a particular appearance number, the a UA MUST send a
   dialog package PUBLISH request and wait for a 2xx response before
   sending the INVITE.  This is required in the following situations:

   1.  When the user seizes a particular appearance number for an
       outgoing call (e.g., seizing the appearance and going "off-hook",
       if the UA's user interface uses this metaphor).




<span class="grey">Johnston, et al.             Standards Track                   [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   2.  When the user has requested that an appearance number not be used
       for an outgoing call (i.e., during a consultation call, a
       'service media' call such as for music on hold [<a href="./rfc7088" title="&quot;Session Initiation Protocol Service Example -- Music on Hold&quot;">RFC7088</a>], or for
       a call not considered part of the shared appearance group).

   3.  When the user has selected to join (or bridge) an existing call.

   4.  When the user has selected to replace (or take) an existing call.

   Note that when a UA seizes an appearance prior to establishment of a
   dialog (numbers 1 and 2 in the above list), not all dialog
   information will be available.  In particular, when a UA publishes an
   attempt to seize an appearance prior to knowing the destination URI,
   minimal or no dialog information may be available.  For example, in
   some cases, only the local target URI for the call will be known: not
   any dialog information.  If the From tag and Call-ID were not present
   in the initial PUBLISH, a new PUBLISH MUST be sent as soon as this
   information is available.

      The first publication will cause the Appearance Agent to reserve
      the appearance number for this UA.  If the publication does not
      have any dialog identifiers (e.g., Call-ID or local-tag), the
      Appearance Agent cannot assign the appearance number to a
      particular dialog of the UA until the second publication, which
      will contain some dialog identifiers.

   This publication state is refreshed as described in [<a href="./rfc3903" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">RFC3903</a>] during
   the early dialog state or the Appearance Agent may reassign the
   appearance number.  Once the dialog has transitioned to the confirmed
   state, no publication refreshes are necessary.

      This specification assumes that the Appearance Agent has other
      means besides UA publication to learn about the state of UA
      dialogs.  In this specification, PUBLISH is used to indicate
      desired and intended appearance number operations.  Once a dialog
      transitions from early to confirmed, this role is over; hence, no
      publication refreshes are needed.

   Appearance numbers are a shorthand label for active and pending
   dialogs related to an AOR.  Many of the features and services built
   using this extension rely on the correct rendering of this
   information to the human user.  In addition, the group nature of the
   feature means that the rendering must be similar between different
   vendors and different models.  Failure to do so will greatly reduce
   the value and usefulness of these protocol extensions.  In a
   correctly designed user interface for this feature, the appearances
   number for each active and pending dialog is explicitly (i.e., by
   appearance number) or implicitly (using a user interface metaphor



<span class="grey">Johnston, et al.             Standards Track                   [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   that makes the numbering and ordering clear to the user) rendered to
   the user.  The far-end identity of each dialog (e.g., the remote
   party identity) is not a useful replacement for the appearance
   number.  The state of each appearance is also to be rendered (idle,
   active, busy, joined, etc.).  UAs can tell that a set of dialogs are
   joined (bridged or mixed) together by the presence of one or more
   &lt;joined-dialog&gt; elements containing other SIP dialog identifiers.
   Appearance numbers of dialogs can be learned by dialog package
   notifications containing the &lt;appearance&gt; element from the Appearance
   Agent or from the 'appearance' Alert-Info parameter in an incoming
   INVITE.  Should they conflict, the dialog package notification takes
   precedence.

   A user may select an appearance number but then abandon placing a
   call (go back on-hook).  In this case, the UA frees up the appearance
   number by removing the event state with a PUBLISH as described in
   [<a href="./rfc3903" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">RFC3903</a>].  A failure to do this will require unnecessary operations
   by the Appearance Agent and tie up appearance numbers that could
   otherwise be used by other UAs in the shared appearance group.

   A UA SHOULD register against the AOR only if it is likely the UA will
   be answering incoming calls.  If the UA is mainly going to be
   monitoring the status of the shared appearance group calls and
   picking or joining calls, the UA SHOULD only subscribe to the AOR and
   not register against the AOR.  If a monitoring UA registers rather
   than just subscribing, it generates large amounts of unnecessary
   network traffic.

      All subscribed UAs will receive dialog package NOTIFYs of trying
      state for incoming INVITEs.

   A UA MUST NOT insert an 'appearance' parameter into an Alert-Info
   header field in an INVITE or other request.

      The Appearance Agent is solely responsible for doing this.

<span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a>.  Appearance Numbers and Call Context</span>

   There are cases where two separate dialogs at a UA are not mixed but
   share the same 'context'.  That is, they relate to each other and
   should not be treated the same as any other two dialogs within the
   group.  One example of this is a 'consultation call' where a user
   puts an existing dialog on hold, then calls another user, before
   switching back to the original dialog.  Another case, described
   below, occurs during transfer operations, where for a transient
   period, a UA is involved in dialogs with two other UAs, but the
   dialogs are related, and should not be treated as independent
   dialogs.  These cases are best handled by not assigning an appearance



<span class="grey">Johnston, et al.             Standards Track                   [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   number to a newly created dialog when it shares a context with an
   existing dialog.  But if the preexisting dialog is terminated, its
   appearance number should be reassigned to the newly created dialog.

   A UA that wants to place a call but does not have an appearance
   number assigned sends a PUBLISH before sending the INVITE.  The
   PUBLISH does not have an 'appearance' element present, but it does
   have the 'shared' Event header field parameter present.  If the
   Appearance Agent policy does not allow calls without an assigned
   appearance number, a 400 (Bad Request) response is sent by the
   Appearance Agent and the UA will republish either selecting/seizing
   an appearance number or send the INVITE without publishing, in which
   case the Appearance Agent will assign one.

      Note that if an Appearance Agent rejects calls without an
      appearance number, certain operations such as consultation calls,
      transfer, and music on hold may be negatively impacted.

<span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a>.  Appearance Numbers and Call Control</span>

   When an INVITE is generated to attempt to bridge or take a call
   (i.e., contains Join or Replaces with a dialog identifier of another
   dialog in the shared appearance group), the UA MUST first send a
   PUBLISH to the Appearance Agent.  This PUBLISH will contain:

   1.  The appearance number of the joined or replaced call in the
       &lt;appearance&gt; element

   2.  The dialog information from the Join header field in the &lt;joined-
       dialog&gt; element, if the dialog is being joined

   3.  The dialog information from the Replaces header field in the
       &lt;replaced-dialog&gt; element, if the dialog is being replaced

      Note that this information is provided to the Appearance Agent so
      that it can provide proper appearance assignment behavior.  If the
      INVITE Join or Replaces was sent without publishing first, the
      Appearance Agent might assign a new appearance number to this
      INVITE, which would be a mistake.  With Join, the publication has
      the &lt;joined-dialog&gt; element to prevent the Appearance Agent from
      generating a 400 (Bad Request) response due to the reuse of an
      appearance number.  For Replaces, the purpose of the &lt;replaced-
      dialog&gt; is to prevent a race condition where the BYE could cause
      the appearance number to be released when it should stay with the
      replacing dialog.






<span class="grey">Johnston, et al.             Standards Track                   [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h4"><a class="selflink" id="section-5.3.3" href="#section-5.3.3">5.3.3</a>.  Appearance Numbers and Transfer</span>

   During a transfer operation, it is important that the appearance
   number not change during the operation.  Consider the example of
   Alice, a member of a shared appearance group, who is talking to
   Carol, who is outside the shared appearance group.  Carol transfers
   Alice to David, who is also outside the shared appearance group.  For
   example, if Alice is using appearance 3 for the session with Carol,
   the resulting session with David should also use appearance number 3.
   Otherwise, an appearance number change can cause a "jump" on the UI
   and confusion to the user.  There are two possible scenarios using
   the terminology of <a href="./rfc5589">RFC 5589</a>: Alice is the transferee in any type of
   transfer (receives the REFER) or the transfer target in an attended
   transfer (receives the INVITE with Replaces).

   If Alice is the transferee, the triggered INVITE from the REFER is
   treated as a consultation call.  Alice SHOULD publish requesting that
   the Appearance Agent not assign an appearance number for this INVITE.
   When the transfer completes, Alice SHOULD publish again to move the
   appearance number from the dialog with Carol to the dialog with
   David.  If a PUBLISH is sent to move the appearance number, the
   publication MUST be sent prior to sending the BYE to Carol to avoid a
   race condition where the Appearance Agent reassigns the appearance
   number after seeing the BYE.

   If Alice is the target, the incoming INVITE will contain a Replaces
   header field.  As a result, the Appearance Agent will have reused the
   appearance number of the dialog with Carol, and this appearance
   number will continue to be used after the dialog with Carol has been
   terminated.

<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>.  Appearance Agent</span>

   An Appearance Agent defined in this specification MUST implement a
   dialog package state agent for the UAs registered against the AOR.
   The Appearance Agent MUST support the appearance dialog package
   extensions defined in <a href="#section-5.2">Section 5.2</a> and use the 'shared' Event header
   field parameter.  The Appearance Agent MUST support publications and
   subscriptions for this event package.

   The Appearance Agent MUST have a way of discovering the state of all
   dialogs associated with the AOR.  If this information is not
   available from a call stateful proxy or Back-to-Back User Agent
   (B2BUA), the Appearance Agent can use the registration event package
   [<a href="./rfc3680" title="&quot;A Session Initiation Protocol (SIP) Event Package for Registrations&quot;">RFC3680</a>] to learn of UAs associated with the AOR and subscribe to
   their dialog event state.  An Appearance Agent can also subscribe to
   a UA's dialog event state in order to reconstruct state.  As a
   result, the registrar MUST support the registration event package.



<span class="grey">Johnston, et al.             Standards Track                   [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Dialog package notifications are recommended by <a href="./rfc4235">RFC 4235</a> to "only
   contain information on the dialogs whose state or participation
   information has changed."  This specification extends <a href="./rfc4235">RFC 4235</a> as
   follows.  The Appearance Agent SHOULD send dialog event state
   notifications whenever the following events happen to UAs in the AOR
   group:

   1.  A call is received, placed, answered, or terminated.

   2.  A call is placed on or off hold.

   3.  A call is joined or replaced.

   4.  An appearance number is reserved or released.

   The Appearance Agent MUST allocate an appearance number for all
   incoming calls and send immediate notifications to the UAs subscribed
   to the shared group AOR.  A new appearance number is allocated except
   for an incoming INVITE with a Join or Replaces header field.  For
   this case, the appearance number should match the appearance number
   of the dialog being joined or replaced.  If the INVITE Replaces or
   Join comes from outside the shared appearance group, the Appearance
   Agent will include a &lt;joined-dialog&gt; or &lt;replaced-dialog&gt; element in
   the NOTIFY containing the dialog information from the Replaces or
   Joined header field.

   The Appearance Agent MUST be able to communicate with the forking
   proxy to learn about incoming calls and also to pass the appearance
   number to the proxy or ensure the Alert-Info header field is included
   in the INVITE with the appropriate appearance number.

      Note that UAs need to be able to handle incoming INVITEs without
      an appearance number assigned.  This could be caused by a failure
      of the Appearance Agent or other error condition.  Although the
      proper rendering of the INVITE may not be possible, this is better
      than ignoring or failing the INVITE.

   An Appearance Agent SHOULD assign an appearance number to an outgoing
   dialog if a PUBLISH has not been received selecting/seizing a
   particular appearance number.

      Note that if the shared appearance group has appearance-unaware
      UAs making calls, the Appearance Agent will still allocate
      appearance numbers for INVITEs sent by those UAs.

   An Appearance Agent receiving a PUBLISH with an appearance number
   checks to make sure the publication is valid.  An appearance number
   can be assigned to only one dialog unless there is a &lt;joined-dialog&gt;



<span class="grey">Johnston, et al.             Standards Track                   [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   or &lt;replaced-dialog&gt; element indicating that the dialog will be/has
   been replaced or joined.  A 400 (Bad Request) response is returned if
   the chosen appearance number is invalid, and an immediate NOTIFY
   SHOULD be sent to the UA containing full dialog event state.

   An Appearance Agent receiving a PUBLISH without an appearance number
   but with the 'shared' Event header field parameter present interprets
   this as a request by the UA to not assign an appearance number.  If
   the Appearance Agent policy does not allow this, a 400 (Bad Request)
   response is returned.  If policy does allow this, a 200 (OK) response
   is returned and no appearance number is allocated.  An Appearance
   Agent does not have to share this dialog information (i.e., send a
   NOTIFY) with other UAs in the group as the information will not be
   rendered by the other UAs.

   The Appearance Agent allocates an appearance number to a dialog from
   the time the appearance is requested via a PUBLISH or from the
   receipt of an INVITE to the time when the last dialog associated with
   the appearance is terminated, including all dialogs that are joined
   or replaced.  During the early dialog state, the Appearance Agent
   controls the rate of dialog state publication using the Expires
   header field in 200 (OK) responses to PUBLISH requests.  An interval
   of 3 minutes is RECOMMENDED.  After the dialog associated with the
   publication has been confirmed, the expiration of the publication
   state has no effect on the appearance allocation.  If the publication
   contains no dialog state information, the Appearance Agent MUST
   reserve the appearance number for the UA but cannot assign the
   appearance to any particular dialog of the UA.  When the publication
   state is updated with any dialog information, the appearance number
   can then be assigned to the particular dialog.  A UA that has been
   allocated an appearance number using a PUBLISH MAY free up the
   appearance number by removing the event state with a PUBLISH as
   described in [<a href="./rfc3903" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">RFC3903</a>].

   If an INVITE is sent by a member of the group to the shared AOR
   (i.e., they call their own AOR), the Appearance Agent MUST assign two
   appearance numbers.  The first appearance number will be the one
   selected or assigned to the outgoing INVITE.  The second appearance
   number will be another one assigned by the Appearance Agent for the
   INVITE as it is forked back to the members of the group.

      The is to preserve a common behavior in legacy systems.

   If an INVITE is sent by a member of the group using the shared AOR or
   sent to the shared AOR and no appearance number is available, the
   proxy MAY reject the INVITE with a 403 (Forbidden) response code.





<span class="grey">Johnston, et al.             Standards Track                   [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Appearance numbers are only used for dialogs in which one or more UAs
   associated with the group AOR are participants.  If an incoming
   INVITE to the group AOR is forwarded to another AOR, the appearance
   number is immediately freed up and can be assigned to another dialog.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  XML Schema Definition</span>

   The 'appearance', 'joined-dialog', 'replaced-dialog', and 'exclusive'
   elements are defined within a new XML namespace URI.  This namespace
   is "urn:ietf:params:xml:ns:sa-dialog-info".  The schema for these
   elements is:








































<span class="grey">Johnston, et al.             Standards Track                   [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
     &lt;xs:schema
       targetNamespace="urn:ietf:params:xml:ns:sa-dialog-info"
       xmlns="urn:ietf:params:xml:ns:sa-dialog-info"
       xmlns:xs="http://www.w3.org/2001/XMLSchema"
       elementFormDefault="qualified"&gt;


      &lt;xs:element name="joined-dialog" minOccurs="0"
                                            maxOccurs="unbounded"&gt;
           &lt;xs:complexType&gt;
               &lt;xs:attribute name="call-id" type="xs:string"
                 use="mandatory"/&gt;
               &lt;xs:attribute name="local-tag" type="xs:string"
                 use="mandatory"/&gt;
               &lt;xs:attribute name="remote-tag" type="xs:string"
                 use="mandatory"/&gt;
           &lt;/xs:complexType&gt;
      &lt;/xs:element&gt;

      &lt;xs:element name="replaced-dialog" minOccurs="0"
                                             maxOccurs="unbounded"&gt;
           &lt;xs:complexType&gt;
               &lt;xs:attribute name="call-id" type="xs:string"
                 use="mandatory"/&gt;
               &lt;xs:attribute name="local-tag" type="xs:string"
                 use="mandatory"/&gt;
               &lt;xs:attribute name="remote-tag" type="xs:string"
                 use="mandatory"/&gt;
           &lt;/xs:complexType&gt;
       &lt;/xs:element&gt;

       &lt;xs:element name="appearance" minOccurs="0" maxOccurs="1"&gt;
           &lt;xs:simpleType type="xs:integer"&gt;
           &lt;/xs:simpleType&gt;
       &lt;/xs:element&gt;

       &lt;xs:element name="exclusive" minOccurs="0" maxOccurs="1"&gt;
           &lt;xs:simpleType type="xs:boolean"&gt;
           &lt;/xs:simpleType&gt;
       &lt;/xs:element&gt;
   &lt;/xs:schema&gt;









<span class="grey">Johnston, et al.             Standards Track                   [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Alert-Info Appearance Parameter Definition</span>

   This specification extends [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>] to add an 'appearance' parameter
   to the Alert-Info header field and also to allow proxies to modify or
   delete the Alert-Info header field.

   The changes to the ABNF [<a href="./rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>] in <a href="./rfc3261">RFC 3261</a> are:

        alert-param      =  LAQUOT absoluteURI RAQUOT *( SEMI
                              (generic-param / appearance-param) )
        appearance-param = "appearance" EQUAL 1*DIGIT

   A proxy inserting an 'appearance' Alert-Info parameter follows normal
   Alert-Info policies.  To indicate the appearance number for this
   dialog, the proxy adds the Alert-Info header field with the
   'appearance' parameter to the INVITE.  If an Alert-Info is already
   present, the proxy adds the 'appearance' parameter to the Alert-Info
   header field.  If an appearance number parameter is already present
   (associated with another AOR or by mistake), the value is rewritten
   adding the new appearance number.  There MUST NOT be more than one
   appearance parameter in an Alert-Info header field.

   If no special ringtone is desired, a normal ringtone SHOULD be
   indicated using the urn:alert:service:normal in the Alert-Info, as
   per [<a href="./rfc7462" title="&quot;URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)&quot;">RFC7462</a>].  The appearance number present in an Alert-Info header
   field SHOULD be rendered by the UA to the user, following the
   guidelines in <a href="#section-5.3">Section 5.3</a>.  If the INVITE is forwarded to another
   AOR, the appearance parameter in the Alert-Info SHOULD be removed
   before forwarding outside the group.

   The determination as to what value to use in the appearance parameter
   can be done at the proxy that forks the incoming request to all the
   registered UAs.

      There is a variety of ways the proxy can determine what value it
      should use to populate this parameter.  For example, the proxy
      could fetch this information by initiating a SUBSCRIBE request
      with Expires: 0 to the Appearance Agent for the AOR to fetch the
      list of lines that are in use.  Alternatively, it could act like a
      UA that is a part of the shared appearance group and SUBSCRIBE to
      the State-Agent like any other UA.  This would ensure that the
      active dialog information is available without having to poll on a
      need basis.  It could keep track of the list of active calls for
      the appearance AOR based on how many unique INVITE requests it has
      forked to or received from the appearance AOR.  Another approach
      would be for the Proxy to first send the incoming INVITE to the
      Appearance Agent, which would redirect to the shared appearance




<span class="grey">Johnston, et al.             Standards Track                   [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


      group URI and escape the proper Alert-Info header field for the
      Proxy to recurse and distribute to the other UAs in the group.

      The Appearance Agent needs to know about all incoming requests to
      the AOR in order to seize the appearance number.  One way in which
      this could be done is for the Appearance Agent to register against
      the AOR with a higher q value.  This will result in the INVITE
      being sent to the Appearance Agent first, then being offered to
      the UAs in the group.

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  User Interface Considerations</span>

   The appearance number allocated to a call is an important concept
   that enables calls to be handled by multiple devices with
   heterogeneous user interfaces in a manner that still allows users to
   see a consistent model.  Careful treatment of the appearance number
   is essential to meet the expectations of the users.  Also, rendering
   the correct call/appearance state to users is also important.

<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>.  Appearance Number Rendering</span>

   Since different UAs have different user interface capabilities, it is
   usual to find that some UAs have restrictions that others do not.
   Perfect interoperability across all UAs is clearly not possible, but
   by careful design, interoperability up to the limits of each UA can
   be achieved.

   The following guidelines suggest how the appearance number should be
   handled in three typical user interface implementations.

<span class="h4"><a class="selflink" id="section-8.1.1" href="#section-8.1.1">8.1.1</a>.  Single Appearance UAs</span>

   These devices are constrained by only having the capability of
   displaying status indications for a single appearance.  The UA SHOULD
   still send messages annotated with appearance number "1".  Any call
   indications for appearances other than for number "1" SHOULD be
   rejected with a 480 (Temporarily Unavailable) or 486 (Busy Here)
   response.  Note that this means that a single appearance UA cannot
   answer its own call to the shared AOR, since this call would use a
   second appearance number.

<span class="h4"><a class="selflink" id="section-8.1.2" href="#section-8.1.2">8.1.2</a>.  Dual Appearance UAs</span>

   These devices are essentially single appearance phones that implement
   call waiting.  They have a very simple user interface that allows
   them to switch between two appearances (toggle or flash hook) and
   perhaps audible tones to indicate the status of the other appearance.
   Only appearance numbers "1" and "2" will be used by these UAs.



<span class="grey">Johnston, et al.             Standards Track                   [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h4"><a class="selflink" id="section-8.1.3" href="#section-8.1.3">8.1.3</a>.  Shared Appearance UAs with Fixed Appearance Number</span>

   This UA is the typical 'business-class' hard-phone.  A number of
   appearances are typically configured statically and labeled on
   buttons, and calls may be managed using these configured appearances.
   Any calls outside this range should be rejected, and not mapped to a
   free button.  Users of these devices often seize specific appearance
   numbers for outgoing calls, and the UA will need to seize the
   appearance number and wait for confirmation from the Appearance Agent
   before proceeding with calls.

<span class="h4"><a class="selflink" id="section-8.1.4" href="#section-8.1.4">8.1.4</a>.  Shared Appearance UAs with Variable Appearance Numbers</span>

   This UA is typically a soft-phone or graphically rich user interface
   hard-phone.  In these cases, even the idea of an appearance index may
   seem unnecessary.  However, for these phones to be able to interwork
   successfully with other phone types, it is important that they still
   use the appearance index to govern the order of appearance of calls
   in progress.  No specific guidance on presentation is given except
   that the order should be consistent.  These devices can typically
   make calls without waiting for confirmation from the Appearance Agent
   on the appearance number.

<span class="h4"><a class="selflink" id="section-8.1.5" href="#section-8.1.5">8.1.5</a>.  Example User Interface Issues</span>

   The problems faced by each style of user interface are readily seen
   in this example:

   1.  A call arrives at the shared appearance group and is assigned an
       appearance number of "1".  All UAs should be able to render to
       the user the arrival of this call.

   2.  Another call arrives at the shared appearance group and is
       assigned an appearance number of "2".  The single appearance UA
       should not present this call to the user.  Other UAs should have
       no problems presenting this call distinctly from the first call.

   3.  The first call clears, releasing appearance number "1".  The
       single appearance UA should now be indicating no calls since it
       is unable to manage calls other than on the first appearance.
       Both shared appearance UAs should clearly show that appearance
       number "1" is now free, but that there is still a call on
       appearance number "2".

   4.  A third call arrives and is assigned the appearance number of
       "1".  All UAs should be able to render the arrival of this new
       call to the user.  Multiple appearance UAs should continue to
       indicate the presence of the second call, and they should also



<span class="grey">Johnston, et al.             Standards Track                   [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


       ensure that the presentation order is related to the appearance
       number and not the order of call arrival.

<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>.  Call State Rendering</span>

   UAs that implement the shared appearances feature typically have a
   user interface that provides the state of other appearances in the
   group.  As dialog state NOTIFYs from the Appearance Agent are
   processed, this information can be rendered.  Even the simplest user
   interface typically has three states: idle, active, and hold.  The
   idle state, usually indicated by lamp off, is indicated for an
   appearance when the appearance number is not associated with any
   dialogs, as reported by the Appearance Agent.  The active state,
   usually indicated by a lamp on, means that an appearance number is
   associated with at least one dialog, as reported by the Appearance
   Agent.  The hold state, often indicated by a blinking lamp, means the
   call state from the perspective of the UA in the shared appearance
   group is hold.  This can be determined by the presence of the
   "+sip.rendering=no" feature tag [<a href="./rfc3840" title="&quot;Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)&quot;">RFC3840</a>] with the local target URI.
   Note that the hold state of the remote target URI is not relevant to
   this display.  For joined dialogs, the state is rendered as hold only
   if all local target URIs are indicated with the "+sip.rendering=no"
   feature tag.

<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  Interoperability with Non-shared Appearance UAs</span>

   It is desirable to allow a basic UA that does not directly support
   shared appearance to be part of a shared appearance group.  To
   support this, the Proxy must collaborate with the Appearance Agent.
   This is not required in the basic shared appearance architecture;
   consequently, shared appearance interoperability with non-shared
   appearance UAs will not be available in all shared appearance
   deployments.

   First, a UA that does not support dialog events or the shared
   appearances feature will be discussed.  Then, a UA that does support
   dialog events but not the shared appearances feature will be
   discussed.

<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>.  Appearance Assignment</span>

   A UA that has no knowledge of appearances will only have appearance
   numbers for outgoing calls if assigned by the Appearance Agent.  If
   the non-shared appearance UA does not support Join or Replaces, all
   dialogs SHOULD be marked "exclusive" to indicate that these options
   are not available.  Marking these dialogs "exclusive" provides a
   better user experience and avoids extra SIP messaging failures.




<span class="grey">Johnston, et al.             Standards Track                   [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>.  Appearance Release</span>

   In all cases, the Appearance Agent must be aware of the dialog
   lifetime to release appearances back into the group.

   It is also desirable that any dialog state changes (such as hold,
   etc.) be made available to other UAs in the group through the Dialog
   Event Package.  If the Appearance Agent includes a proxy that Record-
   Routes for dialogs from the non-shared-appearance-aware UA, the
   Appearance Agent will know about the state of dialogs including hold,
   etc.  This information could be determined from inspection of non-
   end-to-end-encrypted INVITE and re-INVITE messages and added to the
   dialog information conveyed to other UAs.

<span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>.  UAs Supporting Dialog Events but Not Shared Appearance</span>

   Interoperability with UAs that support dialog events but not the
   shared appearances feature is more straightforward.  As before, all
   appearance number assignments must be done by the Appearance Agent.
   The Appearance Agent SHOULD still include appearance information in
   NOTIFYs -- this UA will simply ignore this extra information.  This
   type of UA will also ignore appearance number limitations and may
   attempt to join or replace dialogs marked exclusive.  As a result,
   the Proxy or UAs need to reject such requests or the dialogs will be
   joined or taken.

<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  Provisioning Considerations</span>

   UAs can automatically discover if this feature is active for an AOR
   by looking for the 'shared' Event header field parameter in a
   response to a dialog package SUBSCRIBE to the AOR, so no provisioning
   for this is needed.

   The registrar will need to be provisioned to accept either first or
   third party registrations for the shared AOR.  First party
   registration means the To and From URIs in the REGISTER request are
   the shared AOR URI.  Third-party registration means the To URI is the
   shared AOR URI and the From URI is a different AOR, perhaps that of
   the individual user.  Either the credentials of the shared AOR or the
   user MUST be accepted by the registrar and the Appearance Agent,
   depending on the authorization policy in place for the domain.

   If the Appearance Agent needs to subscribe to the dialog state of the
   UAs, then the Appearance Agent and the UAs need to be provisioned
   with credentials so the UAs can authenticate the Appearance Agent.

   In some cases, UAs in the shared appearance group might have a UI
   limitation on the number of appearances that can be rendered.



<span class="grey">Johnston, et al.             Standards Track                   [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Typically, this will be hard-phones with buttons/lamps instead of
   more flexible UIs.  In this case, it can be useful for the Appearance
   Agent to know this maximum number.  This can allow the Appearance
   Agent to apply policy when this limit is reached, e.g., deny a call.
   However, this mechanism does not provide any way to discover this by
   protocol means.

<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>.  Example Message Flows</span>

   The next section shows call flow and message examples.  The flows and
   descriptions are non-normative.  Note that, in these examples, all
   INVITEs sent by a UA in the group will be From the shared AOR
   (sip:HelpDesk@example.com in this case), and all INVITES sent to the
   group will have a Request-URI of the shared AOR.  Any other requests
   would not apply to this feature and would be handled using normal SIP
   mechanisms.

   Note that the first 12 examples assume the Appearance Agent is aware
   of dialog state events.  The example in <a href="#section-11.13">Section 11.13</a> shows the case
   where this is not the case, and, as a result, the Appearance Agent
   initiates a subscription to users of the shared AOR.  Any of the
   other call flow examples could have shown this mode of operation as
   it is equally valid.

<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>.  Registration and Subscription</span>

   Bob and Alice are in a shared appearance group identified by the
   shared appearance AOR sip:HelpDesk@example.com.  Bob REGISTERs using
   contact sip:bob@ua2.example.com.  Alice REGISTERs with contact
   sip:alice@ua1.example.com.

   UAs for Alice and Bob subscribe to the dialog package for the
   appearance AOR and publish dialog state to the Appearance Agent.
   Message exchanges between the Registrar, Appearance Agent, Alice, and
   Bob are shown below.  The call flow examples below do not show the
   authentication of subscriptions, publications, and notifications.  It
   should be noted that for security purposes, all publications and
   subscriptions must be authorized before they are accepted.

   Also note that registrations and subscriptions must all be refreshed
   by Alice at intervals determined by the expiration intervals returned
   by the Registrar or Appearance Agent.

   Registrar     Appearance Agent          Alice             Bob
   |                    |                    |                |
   |                    |                    |                |
   |&lt;--------------------------- REGISTER F1&lt;|                |
   |                    |                    |                |



<span class="grey">Johnston, et al.             Standards Track                   [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |&gt;F2 200 OK -----------------------------&gt;|                |
   |                    |                    |                |
   |                    |&lt;----- SUBSCRIBE F3&lt;|                |
   |                    |                    |                |
   |                    |&gt;F4 200 OK --------&gt;|                |
   |                    |                    |                |
   |                    |&gt;F5 NOTIFY --------&gt;|                |
   |                    |                    |                |
   |                    |&lt;-------- 200 OK F6&lt;|                |
   |                    |                    |                |
   |&lt;-------------------------------------------- REGISTER F7&lt;|
   |                    |                    |                |
   |&gt;F8 200 OK ----------------------------------------------&gt;|
   |                    |                    |                |
   |                    |&lt;---------------------- SUBSCRIBE F9&lt;|
   |                    |                    |                |
   |                    |&gt;F10 200 OK ------------------------&gt;|
   |                    |                    |                |
   |                    |&gt;F11 NOTIFY ------------------------&gt;|
   |                    |                    |                |
   |                    |&lt;------------------------ 200 OK F12&lt;|
   |                    |                    |                |

   Figure 1. Registration and Subscription Example

   F1-F2: Alice registers AOR with
          contact: &lt;sip:alice@ua1.example.com&gt;

   F1 Alice ----&gt; Registrar

   REGISTER sip:registrar.example.com SIP/2.0
   Via: SIP/2.0/UDP ua1.example.com;branch=z9hG4bK527b54da8ACC7B09
   From: &lt;sip:alice@example.com&gt;;tag=CDF9A668-909E2BDD
   To: &lt;sip:HelpDesk@example.com&gt;
   CSeq: 2 REGISTER
   Call-ID: d3281184-518783de-cc23d6bb
   Contact: &lt;sip:alice@ua1.example.com&gt;
   Max-Forwards: 70
   Expires: 3600
   Content-Length: 0


   F2 Registrar ----&gt; Alice

   SIP/2.0 200 OK
   Via: SIP/2.0/UDP ua1.example.com;branch=z9hG4bK527b54da8ACC7B09
   CSeq: 2 REGISTER
   Call-ID: d3281184-518783de-cc23d6bb



<span class="grey">Johnston, et al.             Standards Track                   [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   From: &lt;sip:alice@example.com&gt;;tag=CDF9A668-909E2BDD
   To: &lt;sip:HelpDesk@example.com&gt;;tag=1664573879820199
   Contact:  &lt;sip:alice@ua1.example.com&gt;;expires=3600
   Content-Length: 0


   F3 to F6: Alice also subscribes to the events associated with the
   Appearance AOR.  Appearance Agent notifies Alice of the status.

   F3 Alice ----&gt; Appearance Agent

   SUBSCRIBE sip:HelpDesk@example.com SIP/2.0
   Via: SIP/2.0/UDP ua1.example.com;branch=z9hG4bKf10fac97E7A76D6A
   From: &lt;sip:alice@example.com&gt;;tag=925A3CAD-CEBB276E
   To: &lt;sip:HelpDesk@example.com&gt;
   CSeq: 91 SUBSCRIBE
   Call-ID: ef4704d9-bb68aa0b-474c9d94
   Contact: &lt;sip:alice@ua1.example.com&gt;
   Event: dialog;shared
   Accept: application/dialog-info+xml
   Max-Forwards: 70
   Expires: 3700
   Content-Length: 0


   F4 Appearance Agent ----&gt; Alice

   SIP/2.0 200 OK
   Via: SIP/2.0/UDP ua1.example.com;branch=z9hG4bKf10fac97E7A76D6A
   CSeq: 91 SUBSCRIBE
   Call-ID: ef4704d9-bb68aa0b-474c9d94
   From: &lt;sip:alice@example.com&gt;;tag=925A3CAD-CEBB276E
   To: &lt;sip:HelpDesk@example.com&gt;;tag=1636248422222257
   Allow-Events: dialog
   Expires: 3700
   Contact: &lt;sip:appearanceagent.example.com&gt;
   Content-Length: 0


   F5 Appearance Agent ----&gt; Alice

   NOTIFY sip:alice@ua1.example.com SIP/2.0
   From: &lt;sip:HelpDesk@example.com&gt;;tag=1636248422222257
   To: &lt;sip:alice@example.com&gt;;tag=925A3CAD-CEBB276E
   Call-ID: ef4704d9-bb68aa0b-474c9d94
   CSeq: 232 NOTIFY
   Via: SIP/2.0/UDP appearanceagent.example.com;branch=z9hG4bK1846
   Max-Forwards: 70



<span class="grey">Johnston, et al.             Standards Track                   [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Content-Type: application/dialog-info+xml
   Event: dialog;shared
   Subscription-State: active;expires=3000
   Contact: &lt;sip:appearanceagent.example.com&gt;
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                version="40"
                state="full"
                entity="sip:HelpDesk@example.com"&gt;
   &lt;/dialog-info&gt;


   F6 Alice ----&gt; Appearance Agent

   SIP/2.0 200 OK
   Via: SIP/2.0/UDP appearanceagent.example.com;branch=z9hG4bK1846
   From: &lt;sip:HelpDesk@example.com&gt;;tag=1636248422222257
   To: &lt;sip:alice@example.com&gt;;tag=925A3CAD-CEBB276E
   CSeq: 232 NOTIFY
   Call-ID: ef4704d9-bb68aa0b-474c9d94
   Contact: &lt;sip:alice@ua1.example.com&gt;
   Content-Length: 0


   F7 Bob ----&gt; Registrar

   REGISTER sip:registrar.example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4b53b54d87B
   From: &lt;sip:bob@example.com&gt;;tag=34831131
   To: &lt;sip:HelpDesk@example.com&gt;
   CSeq: 72 REGISTER
   Call-ID: 139490230230249348
   Contact: &lt;sip:bob@ua2.example.com&gt;
   Max-Forwards: 70
   Expires: 3600
   Content-Length: 0


   F8 Registrar ----&gt; Bob

   SIP/2.0 200 OK
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4b53b54d87B
   From: &lt;sip:bob@example.com&gt;;tag=34831131
   To: &lt;sip:HelpDesk@example.com&gt;;tag=fkwlwqi1
   CSeq: 72 REGISTER
   Call-ID: 139490230230249348



<span class="grey">Johnston, et al.             Standards Track                   [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Contact: &lt;sip:alice@ua1.example.com&gt;;expires=3200
   Contact: &lt;sip:bob@ua2.example.com&gt;;expires=3600
   Content-Length: 0




<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>.  Appearance Selection for Incoming Call</span>

   In the call flow below, Bob and Alice are in a shared appearance
   group.  Carol places a call to the shared appearance group AOR.  The
   Appearance Agent sends NOTIFYs to Alice and Bob telling them what
   appearance the call is using.  Both Alice and Bob's devices are
   alerted of the incoming call.  Bob answers the call.

   Note that it is possible that both Alice and Bob answer the call and
   send 200 (OK) responses to Carol.  It is up to Carol to resolve this
   situation.  Typically, Carol will send ACKs to both 200 OKs but send
   a BYE to terminate one of the dialogs.  As a result, either Alice or
   Bob will receive the BYE and publish that their dialog is over.
   However, if Carol answers both Alice and Bob and keeps both dialogs
   active, then the Appearance Agent will need to resolve the situation
   by moving either Alice or Bob's dialog to a different appearance.

   All NOTIFY messages in the call flow below carry dialog events and
   only dialog states are mentioned for simplicity.  For brevity, the
   details of some messages are not shown below.  Note that the order of
   F2 - F5 and F7 - F8 could be reversed.

              Forking     Appearance
   Carol      Proxy         Agent         Alice      Bob
   |            |             |             |         |
   |&gt;F1 INVITE &gt;|             |             |         |
   |            |&lt; - - - - - &gt;|             |         |
   |            |             |&gt;F2 NOTIFY -----------&gt;|
   |            |             |             |         |
   |            |             |&lt;F3 200 OK -----------&lt;|
   |            |             |             |         |
   |            |             |&gt;F4 NOTIFY -&gt;|         |
   |            |             |             |         |
   |            |             |&lt;-200 OK F5-&lt;|         |
   |&lt;- 100 F6 -&lt;|             |             |         |
   |            |&gt;F7 INVITE (appearance=1) ----------&gt;|
   |            |             |             |         |
   |            |&gt;F8 INVITE (appearance=1) &gt;|         |
   |            |             |             |         |
   |            |&lt;-------------------- Ringing 180 F9&lt;|
   |&lt; 180 F10 -&lt;|             |             |         |



<span class="grey">Johnston, et al.             Standards Track                   [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |            |&lt;--------- 180 Ringing F11&lt;|         |
   |&lt; 180 F12 -&lt;|             |             |         |
   |            |             |             |         |
   |            |&lt;------------------------ 200 OK F13&lt;|
   |&lt; 200 F14 -&lt;|             |             |         |
   |            |             |             |         |
   |            |&gt;F15 CANCEL --------------&gt;|         |
   |            |             |             |         |
   |            |&lt;-------------- 200 OK F16&lt;|         |
   |            |             |             |         |
   |            |&lt;Request Cancelled 487 F17&lt;|         |
   |            |             |             |         |
   |            |&gt;F18 ACK -----------------&gt;|         |
   |&gt;F19 ACK --&gt;|             |             |         |
   |            |&gt;F20 ACK ---------------------------&gt;|
   |            |             |             |         |
   |&lt;=============Both way RTP established===========&gt;|
   |            |             |             |         |
   |            |&lt; - - - - - &gt;|             |         |
   |            |             |             |         |
   |            |             |&gt;F21 NOTIFY &gt;|         |
   |            |             |             |         |
   |            |             |&lt;- 200 F22 -&lt;|         |
   |            |             |             |         |
   |            |             |&gt;F23 NOTIFY ----------&gt;|
   |            |             |             |         |
   |            |             |&lt;F24 200 OK ----------&lt;|
   |            |             |                       |

   Figure 2. Appearance Selection for Incoming Call Example


   F4 Appearance Agent ----&gt; Alice

   NOTIFY sip:alice@ua1.example.com SIP/2.0
   From: &lt;sip:HelpDesk@example.com&gt;;tag=151702541050937
   To: &lt;sip:alice@example.com&gt;;tag=18433323-C3D237CE
   Call-ID: 1e361d2f-a9f51109-bafe31d4
   CSeq: 12 NOTIFY
   Via: SIP/2.0/UDP appearanceagent.example.com;branch=z9hG4bK1403
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Event: dialog;shared
   Subscription-State: active;expires=2800
   Contact: &lt;sip:appearanceagent.example.com&gt;
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;



<span class="grey">Johnston, et al.             Standards Track                   [Page 33]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="13"
                state="partial"
                entity="sip:HelpDesk@example.com"&gt;
      &lt;dialog id="2a7294823093f5274e3fd2ec54a2d76c"
           call-id="14-1541707345"
           remote-tag="44BAD75D-E3128D42"
           direction="recipient"&gt;
         &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
         &lt;state&gt;trying&lt;/state&gt;
         &lt;remote&gt;
           &lt;identity&gt;sip:carol@ua.example.com&lt;/identity&gt;
         &lt;/remote&gt;
      &lt;/dialog&gt;
   &lt;/dialog-info&gt;


   F7 Proxy ----&gt; Bob

   INVITE sip:bob@ua2.example.com SIP/2.0
   Via: SIP/2.0/UDP ua3.example.com;branch=z9hG4bK4324ea
   Via: SIP/2.0/UDP proxy.example.com;branch=z9hG4bK38432ji
   From: &lt;sip:carol@example.com&gt;;tag=44BAD75D-E3128D42
   To: &lt;sip:HelpDesk@example.com&gt;
   CSeq: 106 INVITE
   Call-ID: 14-1541707345
   Contact: &lt;sip:carol@ua3.example.com&gt;
   Max-Forwards: 69
   Alert-Info: &lt;urn:alert:service:normal&gt;;appearance=1
   Content-Type: application/sdp
   Content-Length: ...

   v=0
   o=- 1102980499 1102980499 IN IP4 ua3.example.com
   s=
   c=IN IP4 ua3.example.com
   t=0 0
   m=audio 2238 RTP/AVP 0 8 101
   a=rtpmap:0 PCMU/8000
   a=rtpmap:8 PCMA/8000
   a=rtpmap:101 telephone-event/8000


   F21 Appearance Agent ----&gt; Alice

   NOTIFY sip:alice@ua1.example.com SIP/2.0
   From: &lt;sip:HelpDesk@example.com&gt;;tag=151702541050937



<span class="grey">Johnston, et al.             Standards Track                   [Page 34]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   To: &lt;sip:alice@example.com&gt;;tag=18433323-C3D237CE
   Call-ID: 1e361d2f-a9f51109-bafe31d4
   CSeq: 13 NOTIFY
   Via: SIP/2.0/UDP appearanceagent.example.com;branch=z9hG4bK4164F03j
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Event: dialog;shared
   Subscription-State: active;expires=2500
   Contact: &lt;sip:appearanceagent.example.com&gt;
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="17"
                state="partial"
                entity="sip:HelpDesk@example.com"&gt;
      &lt;dialog id="2a7294823093f5274e3fd2ec54a2d76c"
           call-id="14-1541707345"
           remote-tag="44BAD75D-E3128D42"
           local-tag="7349dsfjkFD03s"
           direction="recipient"&gt;
         &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
         &lt;state&gt;confirmed&lt;/state&gt;
         &lt;local&gt;
           &lt;target&gt;sip:bob@ua2.example.com&lt;/target&gt;
         &lt;/local&gt;
         &lt;remote&gt;
           &lt;identity&gt;sip:carol@ua.example.com&lt;/identity&gt;
         &lt;/remote&gt;
      &lt;/dialog&gt;
   &lt;/dialog-info&gt;


<span class="h3"><a class="selflink" id="section-11.3" href="#section-11.3">11.3</a>.  Outgoing Call without Appearance Seizure</span>

   In this scenario, Bob's UA places a call without first selecting/
   seizing an appearance number.  After Bob sends the INVITE, the
   appearance assigns an appearance number for it and notifies both
   Alice and Bob.


   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |              |               |              |                  |
   |              |&lt;------------------------------------- INVITE F1&lt;|
   |              |               |              |                  |
   |              |&gt;F2 100 Trying ---------------------------------&gt;|



<span class="grey">Johnston, et al.             Standards Track                   [Page 35]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |&lt;-- INVITE F3&lt;|               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;-- NOTIFY F4&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F5 200 OK --&gt;|                  |
   |              |               |              |------- NOTIFY F6&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F7 200 OK ------&lt;|
   |&gt;F8 180  ----&gt;|               |              |                  |
   |              |&gt;F9 180 Ringing --------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F10&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F11 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F12&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F13 200 OK -----&lt;|
   |&gt;F14 200 OK -&gt;|               |              |                  |
   |              |&gt;F15 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F16&lt;|
   |&lt;---- ACK F17&lt;|               |              |                  |
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F18&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F19 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F20&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F21 200 OK -----&lt;|
   |              |               |              |                  |

   Figure 3. Outgoing Call without Appearance Seizure Example


   F1 Bob ----&gt; Proxy

   INVITE sip:carol@example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bK98c87c52123A08BF
   From: &lt;sip:HelpDesk@example.com&gt;;tag=15A3DE7C-9283203B
   To: &lt;sip:carol@example.com&gt;
   CSeq: 1 INVITE



<span class="grey">Johnston, et al.             Standards Track                   [Page 36]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Call-ID: f3b3cbd0-a2c5775e-5df9f8d5
   Contact: &lt;sip:bob@ua2.example.com&gt;
   Max-Forwards: 70
   Content-Type: application/sdp
   Content-Length: 223

   v=0
   o=- 1102980499 1102980499 IN IP4 ua2.example.com
   s=IP SIP UA
   c=IN IP4 ua2.example.com
   t=0 0
   a=sendrecv
   m=audio 2236 RTP/AVP 0 8 101
   a=rtpmap:0 PCMU/8000
   a=rtpmap:8 PCMA/8000
   a=rtpmap:101 telephone-event/8000


   F4 Appearance Agent ----&gt; Alice

   NOTIFY sip:alice@ua1.example.com SIP/2.0
   Via: SIP/2.0/UDP appearanceagent.example.com;branch=z9hG4bK81d84f62
   From: &lt;sip:HelpDesk@example.com&gt;;tag=1636248422222257
   To: &lt;sip:alice@example.com&gt;;tag=925A3CAD-CEBB276E
   Call-ID: ef4704d9-bb68aa0b-474c9d94
   CSeq: 233 NOTIFY
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Event: dialog;shared
   Subscription-State: active;expires=2200
   Contact: &lt;sip:appearanceagent.example.com&gt;
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="27"
                state="partial"
                entity="sip:HelpDesk@example.com"&gt;
       &lt;dialog id="fa02538339df3ce597f9e3e3699e28fc"
            call-id="f3b3cbd0-a2c5775e-5df9f8d5"
            local-tag="15A3DE7C-9283203B"    direction="initiator"&gt;
               &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
               &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
                  &lt;state&gt;trying&lt;/state&gt;
                   &lt;local&gt;
                       &lt;target uri="sip:bob@ua2.example.com"&gt;
                       &lt;/target&gt;



<span class="grey">Johnston, et al.             Standards Track                   [Page 37]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


                      &lt;/local&gt;
           &lt;/dialog&gt;
   &lt;/dialog-info&gt;


   F6 Appearance Agent ----&gt; Bob

   NOTIFY sip:bob@ua1.example.com SIP/2.0
   From: &lt;sip:HelpDesk@example.com&gt;;tag=497585728578386
   To: &lt;sip:bob@example.com&gt;;tag=633618CF-B9C2EDA4
   Call-ID: a7d559db-d6d7dcad-311c9e3a
   CSeq: 7 NOTIFY
   Via: SIP/2.0/UDP appearanceagent.example.com
    ;branch=z9hG4bK1711759878512309
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Event: dialog;shared
   Subscription-State: active;expires=2000
   Contact: &lt;sip:appearanceagent.example.com&gt;
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="78"
                state="partial"
                entity="sip:HelpDesk@example.com"&gt;
       &lt;dialog id="02538339hfgdf3ce597f9e3egkl3699e28fc"
            call-id="f3b3cbd0-a2c5775e-5df9f8d5"
            local-tag="15A3DE7C-9283203B"    direction="initiator"&gt;
               &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
               &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
                  &lt;state&gt;trying&lt;/state&gt;
                   &lt;local&gt;
                       &lt;target uri="sip:bob@ua2.example.com"&gt;
                       &lt;/target&gt;
                      &lt;/local&gt;
           &lt;/dialog&gt;
   &lt;/dialog-info&gt;

<span class="h3"><a class="selflink" id="section-11.4" href="#section-11.4">11.4</a>.  Outgoing Call with Appearance Seizure</span>

   In this scenario, Bob's UA sends out a dialog event PUBLISH with
   state (trying) selecting/seizing an appearance number before sending
   the INVITE.  After receiving the 200 (OK) from the Appearance Agent
   confirming the appearance number, Bob's UA sends the INVITE to Carol
   and establishes a session.  For brevity, details of some of the
   messages are not included in the message flows.  Bob's UA puts as



<span class="grey">Johnston, et al.             Standards Track                   [Page 38]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   much of the dialog information from F7 as can be determined in
   advance.  In this case, the minimum of the Contact URI is included,
   which allows the Appearance Agent to correlate the INVITE with the
   PUBLISH.

   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |              |               |              |&lt;----- PUBLISH F1&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F2 200 OK ------&gt;|
   |              |               |              |                  |
   |              |               |&lt;-- NOTIFY F3&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F4 200 OK --&gt;|                  |
   |              |               |              |------- NOTIFY F5&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F6 200 OK ------&lt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------- INVITE F7&lt;|
   |              |               |              |                  |
   |              |&gt;F8 100 Trying ---------------------------------&gt;|
   |&lt;-- INVITE F9&lt;|               |              |                  |
   |              |               |              |&lt;---- PUBLISH F10&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F11 200 OK -----&gt;|
   |              |               |              |                  |
   |&gt;F12 180  ---&gt;|               |              |                  |
   |              |&gt;F13 180 Ringing -------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F14&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F15 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F16&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F17 200 OK -----&lt;|
   |&gt;F18 200 OK -&gt;|               |              |                  |
   |              |&gt;F19 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F20&lt;|
   |&lt;---- ACK F21&lt;|               |              |                  |
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F22&lt;|                  |



<span class="grey">Johnston, et al.             Standards Track                   [Page 39]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |              |               |              |                  |
   |              |               |&gt;F23 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F24&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F25 200 OK -----&lt;|
   |              |               |              |                  |

   Figure 4. Outgoing Call with Appearance Seizure Example

   F1 to F4: Bob uses the shared appearance of the Help Desk on his UA
   to place an outgoing call (e.g., he goes off-hook).  Before sending
   the outgoing INVITE request, Bob publishes to the Appearance Agent
   reserving appearance number 1.  The Appearance Agent notifies Alice
   (and all other UAs, including Bob) of the event by sending NOTIFYs.


   F1 Bob ----&gt; Appearance Agent

   PUBLISH sip:HelpDesk@example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bK61314d6446383E79
   From: &lt;sip:bob@example.com&gt;;tag=44150CC6-A7B7919D
   To: &lt;sip:HelpDesk@example.com&gt;
   CSeq: 7 PUBLISH
   Call-ID: 44fwF144-F12893K38424
   Contact: &lt;sip:bob@ua2.example.com&gt;
   Event: dialog;shared
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="6"
                state="full"
                entity="sip:HelpDesk@example.com"&gt;
       &lt;dialog id="id3d4f9c83" direction="initiator"&gt;
           &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
           &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
           &lt;state&gt;trying&lt;/state&gt;
           &lt;local&gt;
               &lt;target uri="sip:bob@ua2.example.com"&gt;
               &lt;/target&gt;
           &lt;/local&gt;
       &lt;/dialog&gt;
   &lt;/dialog-info&gt;





<span class="grey">Johnston, et al.             Standards Track                   [Page 40]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   F2 Appearance Agent  ----&gt; Bob

   SIP/2.0 200 OK
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bK61314d6446383E79
   From: &lt;sip:bob@example.com&gt;;tag=44150CC6-A7B7919D
   To: &lt;sip:HelpDesk@example.com&gt;
   CSeq: 7 PUBLISH
   Call-ID: 44fwF144-F12893K38424
   Contact: &lt;sip:bob@ua2.example.com&gt;
   Event: dialog;shared
   SIP-Etag: 482943245
   Allow-Events: dialog
   Expires: 60
   Content-Length: 0


   F7 Bob ---&gt; Proxy

   INVITE sip:carol@example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bK342122
   Max-Forwards: 70
   From: &lt;sip:HelpDesk@example.com&gt;;tag=15A3DE7C-9283203B
   To: &lt;sip:carol@example.com&gt;
   Call-ID: f3b3cbd0-a2c5775e-5df9f8d5
   CSeq: 31 INVITE
   Contact: &lt;sip:bob@ua2.example.com&gt;
   Content-Type: application/sdp
   Content-Length: ...

   (SDP Not Shown)


   F10 Bob ----&gt; Appearance Agent

   PUBLISH sip:HelpDesk@example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bK6d644638E7
   From: &lt;sip:bob@example.com&gt;;tag=0CCf6-A7FdsB79D
   To: &lt;sip:HelpDesk@example.com&gt;
   CSeq: 437 PUBLISH
   Call-ID: fwF14d4-F1FFF2F2893K38424
   Contact: &lt;sip:bob@ua2.example.com&gt;
   Event: dialog;shared
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"



<span class="grey">Johnston, et al.             Standards Track                   [Page 41]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="6"
                state="full"
                entity="sip:HelpDesk@example.com"&gt;
       &lt;dialog id="id3d4f9c83"
            call-id="f3b3cbd0-a2c5775e-5df9f8d5"
            local-tag="15A3DE7C-9283203B"
                                            direction="initiator"&gt;
           &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
           &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
           &lt;state&gt;trying&lt;/state&gt;
           &lt;local&gt;
               &lt;target uri="sip:bob@ua2.example.com"&gt;
               &lt;/target&gt;
           &lt;/local&gt;
           &lt;remote&gt;
               &lt;identity uri="sip:carol@example.com"&gt;
               &lt;/identity&gt;
           &lt;/remote&gt;
       &lt;/dialog&gt;
   &lt;/dialog-info&gt;

<span class="h3"><a class="selflink" id="section-11.5" href="#section-11.5">11.5</a>.  Outgoing Call without Using an Appearance Number</span>

   In this scenario, Bob's UA sends out a dialog event PUBLISH with
   state (trying) indicating that he does not want to utilize an
   appearance number for this dialog.  The PUBLISH does not have an
   appearance element but does have the 'shared' Event header field
   parameter.  As a result, the Appearance Agent knows the UA does not
   wish to use an appearance number for this call.  If the Appearance
   Agent does not wish to allow this, it would reject the PUBLISH with a
   400 (Bad Request) response and the UA would know to re-PUBLISH
   selecting/seizing an appearance number.

   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |              |               |              |&lt;----- PUBLISH F1&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F2 200 OK ------&gt;|
   |              |               |              |                  |
   |              |               |&lt;-- NOTIFY F3&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F4 200 OK --&gt;|                  |
   |              |               |              |------- NOTIFY F5&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F6 200 OK ------&lt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------- INVITE F7&lt;|



<span class="grey">Johnston, et al.             Standards Track                   [Page 42]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |              |               |              |                  |
   |              |&gt;F8 100 Trying ---------------------------------&gt;|
   |&lt;-- INVITE F9&lt;|               |              |                  |
   |              |               |              |&lt;---- PUBLISH F10&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F11 200 OK -----&gt;|
   |              |               |              |                  |
   |&gt;F12 180  ---&gt;|               |              |                  |
   |              |&gt;F13 180 Ringing -------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F14&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F15 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F16&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F17 200 OK -----&lt;|
   |&gt;F18 200 OK -&gt;|               |              |                  |
   |              |&gt;F19 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F20&lt;|
   |&lt;---- ACK F21&lt;|               |              |                  |
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F22&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F23 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F24&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F25 200 OK -----&lt;|
   |              |               |              |                  |

   Figure 5. Outgoing Call without using an Appearance Number Example


   F1 Bob ----&gt; Appearance Agent

   PUBLISH sip:appearanceagent.example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bK61314d6446383E79
   From: &lt;sip:bob@example.com&gt;;tag=4415df82k39sf
   To: &lt;sip:HelpDesk@example.com&gt;
   CSeq: 7 PUBLISH
   Call-ID: 44fwF144-F12893K38424
   Contact: &lt;sip:bob@ua2.example.com&gt;



<span class="grey">Johnston, et al.             Standards Track                   [Page 43]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Event: dialog;shared
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="6"
                state="full"
                entity="sip:HelpDesk@example.com"&gt;
       &lt;dialog id="id3d4f9c83" direction="initiator"&gt;
           &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
           &lt;state&gt;trying&lt;/state&gt;
           &lt;local&gt;
               &lt;target uri="sip:bob@ua2.example.com"&gt;
               &lt;/target&gt;
           &lt;/local&gt;
       &lt;/dialog&gt;
   &lt;/dialog-info&gt;

   Note that F7 would be the same as the previous example.

<span class="h3"><a class="selflink" id="section-11.6" href="#section-11.6">11.6</a>.  Appearance Release</span>

   Bob and Carol are in a dialog, created, for example as in
   <a href="#section-11.3">Section 11.3</a>.  Carol sends a BYE to Bob to terminate the dialog and
   the Appearance Agent de-allocates the appearance number used, sending
   notifications out to the UAs in the shared group.

   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |
   |&gt;F22 BYE ----&gt;|               |              |                  |
   |              |&gt;F23 BYE ---------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------ 200 OK F24&lt;|
   |&lt;--200 OK F25&lt;|               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F26&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F27 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F28&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F29 200 OK -----&lt;|



<span class="grey">Johnston, et al.             Standards Track                   [Page 44]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Figure 6. Appearance Release Example

   F28 Appearance Agent ----&gt; Bob

   NOTIFY sip:bob@ua1.example.com SIP/2.0
   From: &lt;sip:HelpDesk@example.com&gt;;tag=497585728578386
   To: &lt;sip:bob@example.com&gt;
   Call-ID: a7d559db-d6d7dcad-311c9e3a
   CSeq: 7 NOTIFY
   Via: SIP/2.0/UDP appearanceagent.example.com
    ;branch=z9hG4bK759878512309
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Event: dialog;shared
   Subscription-State: active;expires=1800
   Contact: &lt;sip:appearanceagent.example.com&gt;
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="27"
                state="partial"
                entity="sip:HelpDesk@example.com"&gt;
       &lt;dialog id="fa02538339df3ce597f9e3e3699e28fc"
            call-id="f3b3cbd0-a2c5775e-5df9f8d5"
            local-tag="15A3DE7C-9283203B"
            remote-tag="65a98f7c-1dd2-11b2-88c6-b0316298f7c"
                                            direction="initiator"&gt;
               &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
               &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
                  &lt;state&gt;terminated&lt;/state&gt;
                   &lt;local&gt;
                       &lt;target uri="sip:bob@ua2.example.com"&gt;
                       &lt;/target&gt;
                      &lt;/local&gt;
           &lt;/dialog&gt;
   &lt;/dialog-info&gt;


<span class="h3"><a class="selflink" id="section-11.7" href="#section-11.7">11.7</a>.  Appearance Pickup</span>

   In this scenario, Bob has an established dialog with Carol created
   using the call flows of Figures 1 or 2.  Bob then places Carol on
   hold.  Alice receives a notification of this and renders this on
   Alice's UI.  Alice subsequently picks up the held call and has a
   established session with Carol.  Finally, Carol hangs up.  Alice must
   PUBLISH F32 to indicate that the INVITE F38 will be an attempt to



<span class="grey">Johnston, et al.             Standards Track                   [Page 45]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   pickup the dialog between Carol and Bob and, hence, may use the same
   appearance number.  This example also shows Secure SIP (sips) being
   used.

   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |
   |              |&lt;------------------------------(hold) INVITE F22&lt;|
   |&lt;- INVITE F23&lt;|               |              |                  |
   |              |               |              |                  |
   |&gt;F24 200 OK -&gt;|               |              |                  |
   |              |&gt;F25 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F26&lt;|
   |&lt;---- ACK F27&lt;|               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F28&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F29 200 OK -&gt;|                  |
   |              |               |              |&gt;F30 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F31&lt;|
   |              |               |              |                  |
   |              |  Alice decides to pick up the call              |
   |              |               |              |                  |
   |              |               |&gt;F32 PUBLISH-&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- 200 OK F33&lt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F34&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F35 200 OK -&gt;|                  |
   |              |               |              |&gt;F36 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F37&lt;|
   |              |&lt;-- INVITE F38&lt;|              |                  |
   |&lt;- INVITE F39&lt;|(w/ Replaces)  |              |                  |
   |( w/ Replaces)|               |              |                  |
   |&gt;F40 200 OK -&gt;|               |              |                  |
   |              |&gt;F41 200 OK --&gt;|              |                  |
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |              |&gt;F42 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F43&lt;|



<span class="grey">Johnston, et al.             Standards Track                   [Page 46]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |              |               |&lt;- NOTIFY F44&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F45 200 OK -&gt;|                  |
   |              |               |              |                  |
   |              |&lt;----- ACK F46&lt;|              |                  |
   |&lt;---- ACK F47&lt;|               |              |                  |
   |              |               |              |                  |
   |&lt;= Both way RTP established =&gt;|              |                  |
   |              |               |              |                  |
   |&gt;F48 BYE ----&gt;|               |              |                  |
   |              |&gt;F49 BYE ---------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------ OK 200 F50&lt;|
   |&lt;- 200 OK F51&lt;|               |              |                  |
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F52&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F53 200 OK -&gt;|                  |
   |              |               |              |                  |
   |              |               |              |&gt;F54 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F55&lt;|

   Figure 7. Appearance Pickup Example


   F28 Appearance ----&gt; Alice

   NOTIFY sips:alice@ua1.example.com SIP/2.0
   From: &lt;sips:HelpDesk@example.com&gt;;tag=151702541050937
   To: &lt;sips:alice@example.com&gt;;tag=18433323-C3D237CE
   Call-ID: 1e361d2f-a9f51109-bafe31d4
   CSeq: 12 NOTIFY
   Via: SIP/2.0/TLS appearanceagent.example.com
    ;branch=z9hG4bK1403
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Event: dialog;shared
   Subscription-State: active;expires=1800
   Contact: &lt;sips:appearanceagent.example.com&gt;
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="10"



<span class="grey">Johnston, et al.             Standards Track                   [Page 47]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


                state="partial"
                entity="sips:HelpDesk@example.com"&gt;
      &lt;dialog id="id3d4f9c83"
            call-id="f3b3cbd0-a2c5775e-5df9f8d5"
            local-tag="15A3DE7C-9283203B"
            remote-tag="65a98f7c-1dd2-11b2-88c6-b0316298f7c"
            direction="initiator"&gt;
            &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
            &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
            &lt;state&gt;active&lt;/state&gt;
            &lt;local&gt;
              &lt;target uri="sips:bob@ua2.example.com"&gt;
                &lt;param pname="+sip.rendering" pval="no"/&gt;
              &lt;/target&gt;
            &lt;/local&gt;
            &lt;remote&gt;
              &lt;identity&gt;sips:carol@example.com&lt;/identity&gt;
              &lt;target uri="sips:carol@ua3.example.com" /&gt;
            &lt;/remote&gt;
       &lt;/dialog&gt;
   &lt;/dialog-info&gt;


   F32 Alice ----&gt; Appearance Agent

   PUBLISH sips:HelpDesk@example.com SIP/2.0
   Via: SIP/2.0/TLS ua2.example.com;branch=z9hG4bKa5d6cf61F5FBC05A
   From: &lt;sips:HelpDesk@example.com&gt;;tag=44150CC6-A7B7919D
   To: &lt;sips:alice@example.com&gt;;tag=428765950880801
   CSeq: 11 PUBLISH
   Call-ID: 87837Fkw87asfds
   Contact: &lt;sips:alice@ua2.example.com&gt;
   Event: dialog;shared
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="10"
                state="full"
                entity="sips:HelpDesk@example.com"&gt;
      &lt;dialog id="id3d4f9c83"
          call-id="3d57cd17-47deb849-dca8b6c6"
                         local-tag="8C4183CB-BCEAB710" &gt;
            &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
            &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;



<span class="grey">Johnston, et al.             Standards Track                   [Page 48]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


            &lt;sa:replaced-dialog
              call-id="f3b3cbd0-a2c5775e-5df9f8d5"
              from-tag="15A3DE7C-9283203B"
              to-tag="65a98f7c-1dd2-11b2-88c6-b03162323164+65a98f7c" /&gt;
            &lt;state&gt;trying&lt;/state&gt;
            &lt;local&gt;
              &lt;target uri="sips:alice@ua1.example.com"&gt;
                &lt;param pname="+sip.rendering" pval="yes"/&gt;
              &lt;/target&gt;
            &lt;/local&gt;
            &lt;remote&gt;
                &lt;target uri="sips:carol@ua3.example.com" /&gt;
            &lt;/remote&gt;
       &lt;/dialog&gt;
   &lt;/dialog-info&gt;


   F38 Alice ----&gt; Proxy

   INVITE sips:carol@example.com SIP/2.0
   Via: SIP/2.0/TLS ua1.example.com;branch=z9hG4bK4ea695b5B376A60C
   From: &lt;sips:HelpDesk@example.com&gt;;tag=8C4183CB-BCEAB710
   To: &lt;sips:carol@example.com:5075&gt;
   CSeq: 1 INVITE
   Call-ID: 3d57cd17-47deb849-dca8b6c6
   Contact: &lt;sips:alice@ua1.example.com&gt;
   &lt;all-one-line&gt;
   Replaces: f3b3cbd0-a2c5775e-5df9f8d5;to-tag=65a98f7c
   -1dd2-11b2-88c6-b03162323164+65a98f7c;from-tag=15A3DE7C-9283203B
   &lt;/all-one-line&gt;
   Max-Forwards: 70
   Content-Type: application/sdp
   Content-Length: 223

   v=0
   o=- 1102980497 1102980497 IN IP4 ua1.example.com
   s=IP SIP UA
   c=IN IP4 ua1.example.com
   t=0 0
   a=sendrecv
   m=audio 2238 RTP/AVP 0 8 101
   a=rtpmap:0 PCMU/8000
   a=rtpmap:8 PCMA/8000
   a=rtpmap:101 telephone-event/8000







<span class="grey">Johnston, et al.             Standards Track                   [Page 49]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h3"><a class="selflink" id="section-11.8" href="#section-11.8">11.8</a>.  Call between UAs within the Group</span>

   In this scenario, Bob calls Alice who is also in the shared
   appearance group.  Only one appearance number is used for this
   dialog.  This example also shows the use of the 'exclusive' tag to
   indicate that other UAs in the group can not join or take this
   dialog.

   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |              |&lt;--------------------  INVITE (to Alice's UA) F1&lt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |              |                  |
   |              |               |&lt;-- NOTIFY F2&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F3 200 OK --&gt;|                  |
   |              |               |              |&gt;F4 NOTIFY ------&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;------ 200 OK F5&lt;|
   |              |&gt;F6 INVITE ---&gt;|              |                  |
   |              | (appearance=1)|              |                  |
   |              |               |              |                  |
   |              |&lt;------ 180 F7&lt;|              |                  |
   |              |               |              |                  |
   |              |&gt;F8 180  ---------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;-- NOTIFY F9&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F10 200 OK -&gt;|                  |
   |              |               |              |&gt;F11 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F12&lt;|
   |              |&lt;-- 200 OK F13&lt;|              |                  |
   |              |               |              |                  |
   |              |&gt;F14 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F15&lt;|
   |              |               |              |                  |
   |              |&gt;F16 ACK -----&gt;|              |                  |
   |              |               |              |                  |
   |              |               |&lt;======= RTP established =======&gt;|
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |



<span class="grey">Johnston, et al.             Standards Track                   [Page 50]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |              |               |&lt;- NOTIFY F17&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F18 200 OK -&gt;|                  |
   |              |               |              |&gt;F19 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F24&lt;|
   |              |               |              |                  |

   Figure 8. Call between UAs within the Group Example


   F19 Appearance Agent ----&gt; Bob

   NOTIFY sip:bob@ua1.example.com SIP/2.0
   From: &lt;sip:HelpDesk@example.com&gt;;tag=497585728578386
   To: &lt;sip:bob@example.com&gt;;tag=633618CF-B9C2EDA4
   Call-ID: a7d559db-d6d7dcad-311c9e3a
   CSeq: 7 NOTIFY
   Via: SIP/2.0/UDP appearanceagent.example.com
    ;branch=z9hG4bK1711759878512309
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Event: dialog;shared
   Subscription-State: active;expires=1500
   Contact: &lt;sip:appearanceagent.example.com&gt;
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="10"
                state="partial"
                entity="sip:HelpDesk@example.com"&gt;
      &lt;dialog id="3xdsd4f9c83"
              call-id="b3cbd0-ad2c5775e-5df9f8d5"
                 local-tag="34322kdfr234f"
              remote-tag="3153DE7C-928203B"
              direction="initiator"&gt;
            &lt;sa:exclusive&gt;true&lt;/sa:exclusive&gt;
            &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
            &lt;state&gt;confirmed&lt;/state&gt;
            &lt;local&gt;
              &lt;target uri="sip:bob@ua2.example.com"&gt;
              &lt;/target&gt;
            &lt;/local&gt;
            &lt;remote&gt;
              &lt;identity&gt;sip:HelpDesk@example.com&lt;/identity&gt;
              &lt;target uri="sip:alice@ua1.example.com" /&gt;



<span class="grey">Johnston, et al.             Standards Track                   [Page 51]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


            &lt;/remote&gt;
       &lt;/dialog&gt;

       &lt;dialog id="4839589"
              call-id="b3cbd0-ad2c5775e-5df9f8d5"
              local-tag="3153DE7C-928203B"
                 remote-tag="34322kdfr234f"
              direction="responder"&gt;
            &lt;sa:exclusive&gt;true&lt;/sa:exclusive&gt;
            &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
            &lt;state&gt;confirmed&lt;/state&gt;
            &lt;local&gt;
               &lt;target uri="sip:alice@ua1.example.com" /&gt;
            &lt;/local&gt;
            &lt;remote&gt;
              &lt;identity&gt;sip:HelpDesk@example.com&lt;/identity&gt;
              &lt;target uri="sip:bob@ua2.example.com" /&gt;
            &lt;/remote&gt;
       &lt;/dialog&gt;

   &lt;/dialog-info&gt;

<span class="h3"><a class="selflink" id="section-11.9" href="#section-11.9">11.9</a>.  Consultation Hold with Appearances</span>

   In this scenario, Bob has a call with Carol.  Bob makes a
   consultation call to Alice by putting Carol on hold and calling
   Alice.  Bob's UA chooses not to have an appearance number for the
   call to Alice since it is treating it as part of the call to Carol.
   He indicates this in the PUBLISH F32, which contains the 'shared'
   Event header field parameter but no &lt;appearance&gt; element.  The
   PUBLISH is sent before the INVITE to Alice to ensure no appearance
   number is assigned by the Appearance Agent.  Finally, Bob hangs up
   with Alice and resumes the call with Carol.  Dialog notifications of
   the consultation call are not shown, as they are not used.

   Note that if Carol hangs up while Bob is consulting with Alice, Bob
   can decide if he wants to reuse the appearance number used with Carol
   for the call with Alice.  If not, Bob publishes the termination of
   the dialog with Carol and the Appearance Agent will re-allocate the
   appearance.  If he wants to keep the appearance, Bob will publish the
   termination of the dialog with Carol and also publish the appearance
   with the dialog with Alice.  This will result in Bob keeping the
   appearance number until he reports the dialog with Alice terminated.

   Note that the call flow would be similar if Bob called a music on
   hold server instead of Alice to implement a music on hold service as
   described in [<a href="./rfc7088" title="&quot;Session Initiation Protocol Service Example -- Music on Hold&quot;">RFC7088</a>].




<span class="grey">Johnston, et al.             Standards Track                   [Page 52]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |
   |              |&lt;------------------------------(hold) INVITE F22&lt;|
   |&lt;- INVITE F23&lt;|               |              |                  |
   |              |               |              |                  |
   |&gt;F24 200 OK -&gt;|               |              |                  |
   |              |&gt;F25 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F26&lt;|
   |&lt;---- ACK F27&lt;|               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F28&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F29 200 OK -&gt;|                  |
   |              |               |              |&gt;F30 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F31&lt;|
   |              |               |              |                  |
   |              |  Bob makes a consultation call to Alice         |
   |              |               |              |                  |
   |              |               |              |&lt;---- PUBLISH F32&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F33 200 OK -----&gt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------ INVITE F34&lt;|
   |              |               |              |                  |
   |              |&gt;F35 INVITE --&gt;|              |                  |
   |              |               |              |                  |
   |              |&lt;-- 200 OK F36&lt;|              |                  |
   |              |               |              |                  |
   |              |&gt;F37 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F38&lt;|
   |              |               |              |                  |
   |              |&gt;F39 ACK -----&gt;|              |                  |
   |              |               |              |                  |
   |              |               |&lt;======= RTP established =======&gt;|
   |              |               |              |                  |
   |              |            Bob hangs up with Alice              |
   |              |               |              |                  |
   |              |&lt;--------------------------------------- BYE F40&lt;|
   |              |               |              |                  |
   |              |&gt;F41 BYE -----&gt;|              |                  |
   |              |               |              |                  |
   |              |&lt;-- 200 OK F42&lt;|              |                  |



<span class="grey">Johnston, et al.             Standards Track                   [Page 53]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |              |               |              |                  |
   |              |&gt;F43 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;----------------------------(unhold) INVITE F44&lt;|
   |&lt;- INVITE F45&lt;|               |              |                  |
   |              |               |              |                  |
   |&gt;F46 200 OK -&gt;|               |              |                  |
   |              |&gt;F47 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F48&lt;|
   |&lt;---- ACK F49&lt;|               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F50&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F51 200 OK -&gt;|                  |
   |              |               |              |&gt;F52 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F53&lt;|
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |

   Figure 9. Consultation Hold with Appearances Example

   F32 Bob ----&gt; Appearance Agent

   PUBLISH sip:HelpDesk@example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bKa5d6cf61F5FBC05A
   From: &lt;sip:bob@example.com&gt;;tag=44150CC6-A7B7919D
   To: &lt;sip:HelpDesk@example.com&gt;;tag=428765950880801
   CSeq: 11 PUBLISH
   Call-ID: 44fwF144-F12893K38424
   Contact: &lt;sip:bob@ua2.example.com&gt;
   Event: dialog;shared
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="10"
                state="full"
                entity="sip:HelpDesk@example.com"&gt;
      &lt;dialog id="id3d4f9c83"
              call-id="b3cbd0-ad2c5775e-5df9f8d5"
              local-tag="3153DE7C-928203B"



<span class="grey">Johnston, et al.             Standards Track                   [Page 54]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


              direction="initiator"&gt;
            &lt;sa:exclusive&gt;true&lt;/sa:exclusive&gt;
            &lt;state&gt;trying&lt;/state&gt;
            &lt;local&gt;
              &lt;target uri="sip:bob@ua2.example.com"&gt;
              &lt;/target&gt;
            &lt;/local&gt;
            &lt;remote&gt;
              &lt;identity&gt;sip:HelpDesk@example.com&lt;/identity&gt;
              &lt;target uri="sip:alice@ua1.example.com" /&gt;
            &lt;/remote&gt;
       &lt;/dialog&gt;
   &lt;/dialog-info&gt;

<span class="h3"><a class="selflink" id="section-11.10" href="#section-11.10">11.10</a>.  Joining or Bridging an Appearance</span>

   In this call flow, a call answered by Bob is joined by Alice or
   "bridged".  The Join header field is used by Alice to request this
   bridging.  If Bob did not support media mixing, Bob could obtain
   conferencing resources as described in [<a href="./rfc4579" title="&quot;Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents&quot;">RFC4579</a>].

   Carol    Forking Proxy Appearance Agent  Alice      Bob
     |            |             |             |         |
     |&lt;=============Both way RTP established===========&gt;|
     |            |             |             |         |
     |            |             |&lt; PUBLISH F22|         |
     |            |             |             |         |
     |            |             |&gt;F23 200 OK &gt;|         |
     |            |             |             |         |
     |            |&lt;---- INVITE (w/ Join) F24&lt;|         |
     |            |             |             |         |
     |            |&gt;F25 INVITE (w/Join)----------------&gt;|
     |            |             |             |         |
     |            |&lt;---- OK 200 Contact:Bob;isfocus F26&lt;|
     |            |             |             |         |
     |            |&lt; - - - - - &gt;|             |         |
     |            |             |             |         |
     |            |             |&gt;F27 NOTIFY &gt;|         |
     |            |             |             |         |
     |            |             |&lt; 200 OK F28&lt;|         |
     |            |             |             |         |
     |            |             |&gt;F29 NOTIFY ----------&gt;|
     |            |             |             |         |
     |            |             |&lt;F30 200 OK ----------&lt;|
     |            |             |             |         |
     |            |&gt;F31 200 OK Contact:B-----&gt;|         |
     |            |             |             |         |
     |            |&lt;----------------- ACK F32&lt;|         |



<span class="grey">Johnston, et al.             Standards Track                   [Page 55]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


     |            |             |             |         |
     |            |&gt;ACK F33----------------------------&gt;|
     |            |             |             |         |
     |            |&lt;-----INVITE Contact:Bob;isfocus F34&lt;|
     |&lt;-INVITE F35|             |             |         |
     |            |             |             |         |
     |&gt;F26 200 --&gt;|             |             |         |
     |            |&gt;F37 200 OK ------------------------&gt;|
     |            |             |             |         |
     |            |&lt;--------------------------- ACK F38&lt;|
     |&lt;--- ACK F39|             |             |         |
     |            |             |             |&lt;==RTP==&gt;|
     |&lt;=============Both way RTP established===========&gt;|
     |            |             |             |         |
     |            |&lt; - - - - - &gt;|             |         |
     |            |             |             |         |
     |            |             |&gt;F40 NOTIFY &gt;|         |
     |            |             |             |         |
     |            |             |&lt; 200 OK F41&lt;|         |
     |            |             |             |         |
     |            |             |&gt;F42 NOTIFY ----------&gt;|
     |            |             |             |         |
     |            |             |&lt;F43 200 OK ----------&lt;|
     |            |             |             |         |

   Figure 10. Joining or Bridging an Appearance Example

   F22 Alice ----&gt; Appearance Agent

   PUBLISH sip:HelpDesk@example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bKa5d6cf61F5FBC05A
   From: &lt;sip:alice@example.com&gt;;tag=44150CC6-A7B7919D
   To: &lt;sip:HelpDesk@example.com&gt;;tag=428765950880801
   CSeq: 11 PUBLISH
   Call-ID: 87837Fkw87asfds
   Contact: &lt;sip:alice@ua2.example.com&gt;
   Event: dialog;shared
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="10"
                state="full"
                entity="sip:HelpDesk@example.com:5060"&gt;
      &lt;dialog id="id3d4f9c83"



<span class="grey">Johnston, et al.             Standards Track                   [Page 56]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


          call-id="dc95da63-60db1abd-d5a74b48"
          local-tag="605AD957-1F6305C2" &gt;
            &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
            &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
            &lt;sa:joined-dialog
              call-id="14-1541707345"
              from-tag="44BAD75D-E3128D42"
              to-tag="d3b06488-1dd1-11b2-88c5-b03162323164+d3e48f4c" /&gt;
            &lt;state&gt;trying&lt;/state&gt;
            &lt;local&gt;
              &lt;target uri="sip:alice@ua1.example.com"&gt;
              &lt;/target&gt;
            &lt;/local&gt;
            &lt;remote&gt;
                &lt;target uri="sip:bob@example.com" /&gt;
            &lt;/remote&gt;
       &lt;/dialog&gt;
   &lt;/dialog-info&gt;


   F24 Alice ----&gt; Proxy

   INVITE sip:bob@ua.example.com SIP/2.0
   Via: SIP/2.0/UDP ua1.example.com;branch=z9hG4bKcc9d727c2C29BE31
   From: &lt;sip:HelpDesk@example.com&gt;;tag=605AD957-1F6305C2
   To: &lt;sip:bob@ua.example.com&gt;
   CSeq: 2 INVITE
   Call-ID: dc95da63-60db1abd-d5a74b48
   Contact: &lt;sip:alice@ua1.example.com&gt;
   &lt;all-one-line&gt;
   Join: 14-1541707345;to-tag=d3b06488-1dd1-11b2-88c5
   -b03162323164+d3e48f4c;from-tag=44BAD75D-E3128D42
   &lt;/all-one-line&gt;
   Max-Forwards: 70
   Content-Type: application/sdp
   Content-Length: 223

   v=0
   o=- 1103061265 1103061265 IN IP4 ua1.example.com
   s=IP SIP UA
   c=IN IP4 ua1.example.com
   t=0 0
   a=sendrecv
   m=audio 2236 RTP/AVP 0 8 101
   a=rtpmap:0 PCMU/8000
   a=rtpmap:8 PCMA/8000
   a=rtpmap:101 telephone-event/8000




<span class="grey">Johnston, et al.             Standards Track                   [Page 57]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h3"><a class="selflink" id="section-11.11" href="#section-11.11">11.11</a>.  Loss of Appearance during Allocation</span>

   Bob reserves an appearance with a PUBLISH, sends an INVITE to Carol,
   then becomes unreachable.  When he fails to refresh his publication
   to the appearance agent, the Appearance Agent declares the dialog
   terminated and frees up the appearance using NOTIFYs F14 and F16.
   After retransmitting the NOTIFY to Bob (in not shown messages F17,
   F18, etc.), the subscription is terminated.

   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |              |               |              |&lt;----- PUBLISH F1&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F2 200 OK ------&gt;|
   |              |               |              |                  |
   |              |               |&lt;-- NOTIFY F3&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F4 200 OK --&gt;|                  |
   |              |               |              |------- NOTIFY F5&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F6 200 OK ------&lt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------- INVITE F7&lt;|
   |              |               |              |                  |
   |              |&gt;F8 100 Trying ---------------------------------&gt;|
   |&lt;-- INVITE F9&lt;|               |              |                  |
   |              |               |              |&lt;---- PUBLISH F10&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F11 200 OK -----&gt;|
   |              |               |              |                  |
   |&gt;F12 180  ---&gt;|               |              |                  |
   |              |&gt;F13 180 Ringing -------------------------------&gt;|
   |              |               |              |                  |
   |              |               |              | Bob goes offline |
   |              |               |              |                  |
   |              |               | Appearance selection times out  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F14&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F15 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F16&gt;|
   |              |               |              |                  |
   |              |               |   NOTIFY is retransmitted       |

   Figure 11. Loss of Appearance during Allocation Example






<span class="grey">Johnston, et al.             Standards Track                   [Page 58]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h3"><a class="selflink" id="section-11.12" href="#section-11.12">11.12</a>.  Appearance Seizure Contention Race Condition</span>

   Bob and Alice both try to reserve appearance 2 by publishing at the
   same time.  The Appearance Agent allocates the appearance to Bob by
   sending a 200 OK and denies it to Alice by sending a 400 (Bad
   Request) response.  After the NOTIFY F5, Alice learns that Bob is
   using appearance 2.  Alice then attempts to reserve appearance 3 by
   publishing, which is then accepted.











































<span class="grey">Johnston, et al.             Standards Track                   [Page 59]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |              |               |              |&lt;----- PUBLISH F1&lt;|
   |              |               |              |        (appearance=2)
   |              |               |&gt;F2 PUBLISH -&gt;|                  |
   |              |               |     (appearance=2)              |
   |              |               |              |                  |
   |              |               |              |&gt;F3 200 OK ------&gt;|
   |              |               |&lt;---- F4 400 &lt;|                  |
   |              |               |              |                  |
   |              |               |&lt;-- NOTIFY F5&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F6 200 OK --&gt;|                  |
   |              |               |              |------- NOTIFY F7&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F8 200 OK ------&lt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------- INVITE F9&lt;|
   |              |               |              |                  |
   |              |&gt;F10 100 Trying --------------------------------&gt;|
   |&lt;- INVITE F11&lt;|               |              |                  |
   |              |               |              |&lt;---- PUBLISH F12&lt;|
   |              |               |              |        (appearance=2)
   |              |               |              |&gt;F13 200 OK -----&gt;|
   |              |               |&gt;F14 PUBLISH-&gt;|                  |
   |              |               |     (appearance=3)              |
   |              |               |              |                  |
   |              |               |&lt;--- F15 200 &lt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F16&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F17 200 OK -&gt;|                  |
   Dave           |               |              |------ NOTIFY F18&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F19 200 OK -----&lt;|
   |              |&lt;-- INVITE F20&lt;|              |                  |
   |              |               |              |                  |
   |              |&gt;F21 100 -----&gt;|              |                  |
   |&lt;- INVITE F22&lt;|               |              |                  |

   Figure 12. Appearance Seizure Contention Race Condition Example


<span class="h3"><a class="selflink" id="section-11.13" href="#section-11.13">11.13</a>.  Appearance Agent Subscription to UAs</span>

   In this scenario, the Appearance Agent does not have any way of
   knowing Bob's dialog state information, except through Bob.  This
   could be because the Appearance Agent is not part of a B2BUA, or



<span class="grey">Johnston, et al.             Standards Track                   [Page 60]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   perhaps Bob is remotely registering.  When Bob registers, the
   Appearance Agent receives a registration event package notification
   from the registrar.  The Appearance Agent then SUBSCRIBEs to Bob's
   dialog event state using Event:dialog in the SUBSCRIBE.  Whenever
   Bob's dialog state changes, Bob's UA sends a NOTIFY to the Appearance
   Agent which then notifies the other UAs in the group.

   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |              |&lt;----------------------------------- REGISTER F1&lt;|
   |              |               |              |                  |
   |              |&gt;F2 200 OK -------------------------------------&gt;|
   |              |               |              |                  |
   |              |&gt;F3 NOTIFY ------------------&gt;|                  |
   |              |               |              |                  |
   |              |&lt;------------------ 200 OK F4&lt;|                  |
   |              |               |              |---- SUBSCRIBE F5&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F6 200 OK ------&lt;|
   |              |               |              |                  |
   |              |               |              |&lt;------ NOTIFY F7&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F8 200 OK ------&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;--- SUBSCRIBE F9&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F10 200 OK -----&gt;|
   |              |               |              |                  |
   |              |               |              |------ NOTIFY F11&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F12 200 OK -----&lt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------ INVITE F13&lt;|
   |              |               |              |                  |
   |              |&gt;F14 100 Trying --------------------------------&gt;|
   |&lt;- INVITE F15&lt;|               |              |                  |
   |              |               |              |&lt;----- NOTIFY F16&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F17 200 OK -----&gt;|
   |              |               |&lt;- NOTIFY F18&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F19 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F20&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F21 200 OK -----&lt;|
   |&gt;F22 180  ---&gt;|               |              |                  |
   |              |&gt;F23 180 Ringing -------------------------------&gt;|
   |              |               |              |                  |



<span class="grey">Johnston, et al.             Standards Track                   [Page 61]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |              |               |              |&lt;----- NOTIFY F24&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F25 200 OK -----&gt;|
   |              |               |&lt;- NOTIFY F26&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F27 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F28&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F29 200 OK -----&lt;|
   |&gt;F30 200 OK -&gt;|               |              |                  |
   |              |&gt;F31 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- NOTIFY F32&lt;|
   |              |               |              |                  |
   |              |               |              |&gt;F33 200 OK -----&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F34&lt;|
   |&lt;---- ACK F35&lt;|               |              |                  |
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F36&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F37 200 OK -&gt;|                  |
   |              |               |              |------ NOTIFY F38&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F39 200 OK -----&lt;|
   |              |               |              |                  |

   Figure 13. Appearance Agent Subscription to UAs Example


<span class="h3"><a class="selflink" id="section-11.14" href="#section-11.14">11.14</a>.  Appearance Pickup Race Condition Failure</span>

   In this scenario, Bob has an established dialog with Carol created
   using the call flows of Figure 1 or Figure 2.  Bob then places Carol
   on hold.  Alice receives a notification of this and renders this on
   Alice's UI.  Alice attempts to pick up the call but Carol hangs up
   before the pickup can complete.  Alice cancels the pickup attempt
   with the PUBLISH F48.  Note that the call flow for a failed Join
   would be almost identical.

   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |&lt;================= Both way RTP established ===================&gt;|
   |              |               |              |                  |
   |              |&lt;------------------------------(hold) INVITE F22&lt;|
   |&lt;- INVITE F23&lt;|               |              |                  |



<span class="grey">Johnston, et al.             Standards Track                   [Page 62]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |              |               |              |                  |
   |&gt;F24 200 OK -&gt;|               |              |                  |
   |              |&gt;F25 200 OK ------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;--------------------------------------- ACK F26&lt;|
   |&lt;---- ACK F27&lt;|               |              |                  |
   |              |               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F28&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F29 200 OK -&gt;|                  |
   |              |               |              |&gt;F30 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F31&lt;|
   |              |               |              |                  |
   |              |  Alice decides to pick up the call              |
   |              |               |              |                  |
   |              |               |&gt;F32 PUBLISH-&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- 200 OK F33&lt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F34&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F35 200 OK -&gt;|                  |
   |              |               |              |&gt;F36 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F37&lt;|
   |&gt;F38 BYE ----&gt;|               |              |                  |
   |              |&gt;F39 BYE ---------------------------------------&gt;|
   |              |               |              |                  |
   |              |&lt;------------------------------------ OK 200 F40&lt;|
   |&lt;- 200 OK F41&lt;|               |              |                  |
   |              |&lt;-- INVITE F42&lt;|              |                  |
   |&lt;- INVITE F43&lt;|(w/ Replaces)  |              |                  |
   |( w/ Replaces)|               |              |                  |
   |              |               |              |                  |
   |&gt;F44 481 ----&gt;|               |              |                  |
   |              |&gt;F45 481 -----&gt;|              |                  |
   |&lt;---- ACK F46&lt;|               |              |                  |
   |              |&lt;----- ACK F47&lt;|              |                  |
   |              |               |&gt;F48 PUBLISH-&gt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- 200 OK F49&lt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F50&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F51 200 OK -&gt;|                  |



<span class="grey">Johnston, et al.             Standards Track                   [Page 63]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   |              |               |              |&gt;F52 NOTIFY -----&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;----- 200 OK F53&lt;|

   Figure 14. Appearance Pickup Race Condition Failure Example

   F48 Alice ----&gt; Appearance Agent

   PUBLISH sip:HelpDesk@example.com SIP/2.0
   Via: SIP/2.0/UDP ua2.example.com;branch=z9hG4bKa5d6cf61F5FBC05A
   From: &lt;sip:alice@example.com&gt;;tag=44150CC6-A7B7919D
   To: &lt;sip:HelpDesk@example.com&gt;;tag=428765950880801
   CSeq: 11 PUBLISH
   Call-ID: 87837Fkw87asfds
   Contact: &lt;sip:alice@ua2.example.com&gt;
   Event: dialog;shared
   Max-Forwards: 70
   Content-Type: application/dialog-info+xml
   Content-Length: ...

   &lt;?xml version="1.0"?&gt;
   &lt;dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
                xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
                version="10"
                state="full"
                entity="sip:HelpDesk@example.com"&gt;
      &lt;dialog id="id3d4f9c83"
          call-id="dc95da63-60db1abd-d5a74b48"
          local-tag="605AD957-1F6305C2" &gt;
            &lt;sa:appearance&gt;1&lt;/sa:appearance&gt;
            &lt;sa:exclusive&gt;false&lt;/sa:exclusive&gt;
            &lt;sa:replaced-dialog
              call-id="14-1541707345"
              from-tag="44BAD75D-E3128D42"
              to-tag="d3b06488-1dd1-11b2-88c5-b03162323164+d3e48f4c" /&gt;
            &lt;state&gt;terminated&lt;/state&gt;
            &lt;local&gt;
              &lt;target uri="sip:alice@ua1.example.com"&gt;
              &lt;/target&gt;
            &lt;/local&gt;
            &lt;remote&gt;
                &lt;target uri="sip:carol@ua3.example.com" /&gt;
            &lt;/remote&gt;
       &lt;/dialog&gt;
   &lt;/dialog-info&gt;






<span class="grey">Johnston, et al.             Standards Track                   [Page 64]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h3"><a class="selflink" id="section-11.15" href="#section-11.15">11.15</a>.  Appearance Seizure Incoming/Outgoing Contention Race Condition</span>

   Alice tries to seize appearance 2 at the same time appearance 2 is
   allocated to an incoming call.  The Appearance Agent resolves the
   conflict by sending a 400 (Bad Request) to Alice.  After the NOTIFY
   F6, Alice learns that the incoming call is using appearance 2.  Alice
   republishes for appearance 3, which is accepted.  Note that this
   example shows the INVITE being received before the NOTIFY from the
   Appearance Agent.










































<span class="grey">Johnston, et al.             Standards Track                   [Page 65]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Carol        Proxy           Alice     Appearance Agent         Bob
   |              |               |              |                  |
   |&gt;-- INVITE F1&gt;|               |              |                  |
   |              |&lt; - - - - - - - - - - - - - -&gt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F2 PUBLISH -&gt;|                  |
   |              |               |     (appearance=2)              |
   |              |               |              |                  |
   |              |&gt;F3 INVITE (appearance=2) ----------------------&gt;|
   |              |               |              |                  |
   |              |&gt;F4 INVITE     |              |                  |
   |              |(appearance=2)&gt;|              |                  |
   |              |               |&lt;---- F5 400 &lt;|                  |
   |              |               |              |                  |
   |              |               |&lt;-- NOTIFY F6&lt;|                  |
   |              |               |              |                  |
   |              |               |&gt;F7 200 OK --&gt;|                  |
   |              |               |              |------- NOTIFY F8&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F9 200 OK ------&lt;|
   |              |               |              |                  |
   |              |               |&gt;F10 PUBLISH-&gt;|                  |
   |              |               |     (appearance=3)              |
   |              |               |              |                  |
   |              |               |&lt; F11 200 OK &lt;|                  |
   |              |               |              |                  |
   |              |               |&lt;- NOTIFY F12&lt;|                  |
   |              |               |              |                  |
                  |               |&gt;F13 200 OK -&gt;|                  |
   Dave           |               |              |------ NOTIFY F14&gt;|
   |              |               |              |                  |
   |              |               |              |&lt;F15 200 OK -----&lt;|
   |              |&lt;-- INVITE F16&lt;|              |                  |
   |              |               |              |                  |
   |              |&gt;F17 100 -----&gt;|              |                  |
   |&lt;- INVITE F18&lt;|               |              |                  |

   Figure 15. Appearance Seizure Incoming/Outgoing Contention
              Race Condition Example


<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>.  Security Considerations</span>

   Since multiple line appearance features are implemented using
   semantics provided by SIP [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>], the SIP Event Package for Dialog
   State [<a href="./rfc4235" title="&quot;An INVITE- Initiated Dialog Event Package for the Session Initiation Protocol (SIP)&quot;">RFC4235</a>], and the SIP Event Framework [<a href="./rfc6665" title="&quot;SIP-Specific Event Notification&quot;">RFC6665</a>] and [<a href="./rfc3903" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">RFC3903</a>],
   security considerations in these documents apply to this document as
   well.



<span class="grey">Johnston, et al.             Standards Track                   [Page 66]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   To provide confidentiality, NOTIFY or PUBLISH message bodies that
   provide the dialog state information and the dialog identifiers MAY
   be encrypted end-to-end using the standard mechanisms such as S/MIME
   described in [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>].  Alternatively, sending the NOTIFY and
   PUBLISH requests over TLS also provides confidentiality, although on
   a hop-by-hop basis.  All SUBSCRIBEs and PUBLISHes between the UAs and
   the Appearance Agent MUST be authenticated.  Without proper
   authentication and confidentiality, a third party could learn
   information about dialogs associated with a AOR and could try to use
   this information to hijack or manipulate those dialogs using SIP call
   control primitives.

   This feature relies on standard SIP call control primitives such as
   Replaces and Join.  Proper access controls on their use MUST be used
   so that only members of the shared appearance group can use these
   mechanisms.  All INVITEs with Replaces or Join header fields MUST
   only be accepted if the peer requesting dialog replacement or joining
   has been properly authenticated using a standard SIP mechanism (such
   as Digest or S/MIME), and authorized to request a replacement.
   Otherwise, a third party could disrupt or hijack existing dialogs in
   the shared appearance group.

   For an emergency call, a UA MUST NOT wait for a confirmed seizure of
   an appearance before sending an INVITE.  Waiting for confirmation
   could inadvertently delay or block the emergency call, which by its
   nature needs to be placed as expeditiously as possible.  Instead, a
   emergency call MUST proceed regardless of the status of the PUBLISH
   transaction.

<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>.  IANA Considerations</span>

   This section registers the SIP Event header field parameter 'shared',
   the SIP Alert-Info header field parameter 'appearance', and the XML
   namespace extensions to the SIP Dialog Package.

<span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>.  SIP Event Header Field Parameter: shared</span>

   This document defines the 'shared' header field parameter in the
   Event header field in the "Header Field Parameters and Parameter
   Values" registry defined by [<a href="./rfc3968" title="&quot;The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)&quot;">RFC3968</a>].

                                                    Predefined
  Header Field                  Parameter Name      Values     Reference
  ----------------------------  ------------------  ---------- ---------
  Event                         shared               No        <a href="./rfc7463">RFC 7463</a>






<span class="grey">Johnston, et al.             Standards Track                   [Page 67]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


<span class="h3"><a class="selflink" id="section-13.2" href="#section-13.2">13.2</a>.  SIP Alert-Info Header Field Parameter: appearance</span>

   This document defines the 'appearance' parameter in the Alert-Info
   header in the "Header Field Parameters and Parameter Values" registry
   defined by [<a href="./rfc3968" title="&quot;The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)&quot;">RFC3968</a>].

                                                    Predefined
   Header Field                  Parameter Name     Values     Reference
   ----------------------        ---------------    ---------  ---------
   Alert-Info                    appearance         No         <a href="./rfc7463">RFC 7463</a>

<span class="h3"><a class="selflink" id="section-13.3" href="#section-13.3">13.3</a>.  URN Sub-Namespace Registration: sa-dialog-info</span>

   This section registers a new XML namespace per the procedures in
   [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].

      URI: urn:ietf:params:xml:ns:sa-dialog-info.

      Registrant Contact: IETF BLISS working group, &lt;bliss@ietf.org&gt;,
      Alan Johnston &lt;alan.b.johnston@gmail.com&gt;

      XML:

      BEGIN
       &lt;?xml version="1.0"?&gt;
       &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
                 "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
       &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
       &lt;head&gt;
         &lt;meta http-equiv="content-type"
            content="text/html;charset=iso-8859-1"/&gt;
         &lt;title&gt;Shared Appearance Dialog Information Namespace&lt;/title&gt;
       &lt;/head&gt;
       &lt;body&gt;
        &lt;h1&gt;Namespace for Shared Appearance Dialog Information&lt;/h1&gt;
        &lt;h2&gt;urn:ietf:params:xml:ns:sa-dialog-info&lt;/h2&gt;
        &lt;p&gt;See &lt;a href="http://www.rfc-editor.org/rfc/rfc7463.txt"&gt;
           <a href="./rfc7463">RFC 7463</a>&lt;/a&gt;.&lt;/p&gt;
       &lt;/body&gt;
       &lt;/html&gt;
      END

<span class="h3"><a class="selflink" id="section-13.4" href="#section-13.4">13.4</a>.  XML Schema Registration</span>

   This section registers an XML schema per the procedures in [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].






<span class="grey">Johnston, et al.             Standards Track                   [Page 68]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


      URI: urn:ietf:params:xml:schesa:sa-dialog-info.

      Registrant Contact: IETF BLISS working group, &lt;bliss@ietf.org&gt;,
       Alan Johnston &lt;alan.b.johnston@gmail.com&gt;

      The XML for this schema can be found in <a href="#section-6">Section 6</a>.


<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>.  References</span>

<span class="h3"><a class="selflink" id="section-14.1" href="#section-14.1">14.1</a>.  Normative References</span>

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997,
              &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.

   [<a id="ref-RFC3261">RFC3261</a>]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
              A., Peterson, J., Sparks, R., Handley, M., and E.
              Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>,
              June 2002, &lt;<a href="http://www.rfc-editor.org/info/rfc3261">http://www.rfc-editor.org/info/rfc3261</a>&gt;.

   [<a id="ref-RFC3515">RFC3515</a>]  Sparks, R., "The Session Initiation Protocol (SIP) Refer
              Method", <a href="./rfc3515">RFC 3515</a>, April 2003,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3515">http://www.rfc-editor.org/info/rfc3515</a>&gt;.

   [<a id="ref-RFC3688">RFC3688</a>]  Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
              January 2004, &lt;<a href="http://www.rfc-editor.org/info/rfc3688">http://www.rfc-editor.org/info/rfc3688</a>&gt;.

   [<a id="ref-RFC3840">RFC3840</a>]  Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
              "Indicating User Agent Capabilities in the Session
              Initiation Protocol (SIP)", <a href="./rfc3840">RFC 3840</a>, August 2004,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3840">http://www.rfc-editor.org/info/rfc3840</a>&gt;.

   [<a id="ref-RFC3891">RFC3891</a>]  Mahy, R., Biggs, B., and R. Dean, "The Session Initiation
              Protocol (SIP) "Replaces" Header", <a href="./rfc3891">RFC 3891</a>, September
              2004, &lt;<a href="http://www.rfc-editor.org/info/rfc3891">http://www.rfc-editor.org/info/rfc3891</a>&gt;.

   [<a id="ref-RFC3903">RFC3903</a>]  Niemi, A., "Session Initiation Protocol (SIP) Extension
              for Event State Publication", <a href="./rfc3903">RFC 3903</a>, October 2004,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3903">http://www.rfc-editor.org/info/rfc3903</a>&gt;.

   [<a id="ref-RFC3911">RFC3911</a>]  Mahy, R. and D. Petrie, "The Session Initiation Protocol
              (SIP) "Join" Header", <a href="./rfc3911">RFC 3911</a>, October 2004,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3911">http://www.rfc-editor.org/info/rfc3911</a>&gt;.







<span class="grey">Johnston, et al.             Standards Track                   [Page 69]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   [<a id="ref-RFC3968">RFC3968</a>]  Camarillo, G., "The Internet Assigned Number Authority
              (IANA) Header Field Parameter Registry for the Session
              Initiation Protocol (SIP)", <a href="https://www.rfc-editor.org/bcp/bcp98">BCP 98</a>, <a href="./rfc3968">RFC 3968</a>, December
              2004, &lt;<a href="http://www.rfc-editor.org/info/rfc3968">http://www.rfc-editor.org/info/rfc3968</a>&gt;.

   [<a id="ref-RFC4235">RFC4235</a>]  Rosenberg, J., Schulzrinne, H., and R. Mahy, "An INVITE-
              Initiated Dialog Event Package for the Session Initiation
              Protocol (SIP)", <a href="./rfc4235">RFC 4235</a>, November 2005,
              &lt;<a href="http://www.rfc-editor.org/info/rfc4235">http://www.rfc-editor.org/info/rfc4235</a>&gt;.

   [<a id="ref-RFC5234">RFC5234</a>]  Crocker, D. and P. Overell, "Augmented BNF for Syntax
              Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5234">http://www.rfc-editor.org/info/rfc5234</a>&gt;.

   [<a id="ref-RFC6665">RFC6665</a>]  Roach, A., "SIP-Specific Event Notification", <a href="./rfc6665">RFC 6665</a>,
              July 2012, &lt;<a href="http://www.rfc-editor.org/info/rfc6665">http://www.rfc-editor.org/info/rfc6665</a>&gt;.

   [<a id="ref-RFC7462">RFC7462</a>]  Liess, L., Ed., Jesske, R., Johnston, A., Worley, D., and
              P. Kyzivat, "URNs for the Alert-Info Header Field of the
              Session Initiation Protocol (SIP)", <a href="./rfc7462">RFC 7462</a>, March 2015,
              &lt;<a href="http://www.rfc-editor.org/info/rfc7462">http://www.rfc-editor.org/info/rfc7462</a>&gt;.

<span class="h3"><a class="selflink" id="section-14.2" href="#section-14.2">14.2</a>.  Informative References</span>

   [<a id="ref-RFC3680">RFC3680</a>]  Rosenberg, J., "A Session Initiation Protocol (SIP) Event
              Package for Registrations", <a href="./rfc3680">RFC 3680</a>, March 2004,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3680">http://www.rfc-editor.org/info/rfc3680</a>&gt;.

   [<a id="ref-RFC4579">RFC4579</a>]  Johnston, A. and O. Levin, "Session Initiation Protocol
              (SIP) Call Control - Conferencing for User Agents", <a href="https://www.rfc-editor.org/bcp/bcp119">BCP</a>
              <a href="https://www.rfc-editor.org/bcp/bcp119">119</a>, <a href="./rfc4579">RFC 4579</a>, August 2006,
              &lt;<a href="http://www.rfc-editor.org/info/rfc4579">http://www.rfc-editor.org/info/rfc4579</a>&gt;.

   [<a id="ref-RFC5359">RFC5359</a>]  Johnston, A., Sparks, R., Cunningham, C., Donovan, S., and
              K. Summers, "Session Initiation Protocol Service
              Examples", <a href="https://www.rfc-editor.org/bcp/bcp144">BCP 144</a>, <a href="./rfc5359">RFC 5359</a>, October 2008,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5359">http://www.rfc-editor.org/info/rfc5359</a>&gt;.

   [<a id="ref-RFC7088">RFC7088</a>]  Worley, D., "Session Initiation Protocol Service Example
              -- Music on Hold", <a href="./rfc7088">RFC 7088</a>, February 2014,
              &lt;<a href="http://www.rfc-editor.org/info/rfc7088">http://www.rfc-editor.org/info/rfc7088</a>&gt;.










<span class="grey">Johnston, et al.             Standards Track                   [Page 70]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


Acknowledgements

   The following individuals were part of the shared appearance design
   team and have provided input and text to the document (in
   alphabetical order):

   Martin Dolly, Andrew Hutton, Raj Jain, Fernando Lombardo, Derek
   MacDonald, Bill Mitchell, Michael Procter, and Theo Zourzouvillys.

   Thanks to Chris Boulton for helping with the XML schema.

   Much of the material has been drawn from previous work by Mohsen
   Soroushnejad, Venkatesh Venkataramanan, Paul Pepper, and Anil Kumar,
   who in turn received assistance from:

      Kent Fritz, John Weald, and Sunil Veluvali of Sylantro Systems;
      Steve Towlson and Michael Procter of Citel Technologies; Rob
      Harder and Hong Chen of Polycom, Inc.; John Elwell and JD Smith of
      Siemens Communications; Dale R. Worley of Pingtel; and Graeme
      Dollar of Yahoo, Inc.

   Also thanks to Geoff Devine, Paul Kyzivat, Jerry Yin, John Elwell,
   Dan York, Spenser Dawkins, Martin Dolly, and Brett Tate for their
   comments.

   Thanks to Carolyn Beeton, Francois Audet, Andy Hutton, Tim Ross, Raji
   Chinnappa, and Harsh Mendiratta for their detailed review of the
   document.

Authors' Addresses

   Alan Johnston (editor)
   Avaya
   St. Louis, MO
   United States

   EMail: alan.b.johnston@gmail.com


   Mohsen Soroushnejad (editor)
   Sylantro Systems Corp.

   EMail: msoroush@gmail.com








<span class="grey">Johnston, et al.             Standards Track                   [Page 71]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
<span class="grey"><a href="./rfc7463">RFC 7463</a>                 SIP Shared Appearances               March 2015</span>


   Venkatesh Venkataramanan
   Sylantro Systems Corp.

   EMail: vvenkatar@gmail.com















































Johnston, et al.             Standards Track                   [Page 72]
</pre>