<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<?rfc docmapping="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-avtcore-rtp-avatar-04" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="RTP-Payload-avatar">RTP Payload Format for Avatar Representation Format (ARF) Animation Stream</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-avtcore-rtp-avatar-04"/>
    <author initials="" surname="HS Yang" fullname="Hyunsik Yang">
      <organization>InterDigital</organization>
      <address>
        <postal>
          <country>USA</country>
        </postal>
        <email>hyunsik.yang@interdigital.com</email>
      </address>
    </author>
    <author initials="X." surname="de Foy" fullname="Xavier de Foy">
      <organization>InterDigital</organization>
      <address>
        <postal>
          <country>Canada</country>
        </postal>
        <email>xavier.defoy@interdigital.com</email>
      </address>
    </author>
    <author initials="A." surname="Hamza" fullname="Ahmed Hamza">
      <organization>InterDigital</organization>
      <address>
        <postal>
          <country>Canada</country>
        </postal>
        <email>ahmed.hamza@interdigital.com</email>
      </address>
    </author>
    <author initials="I." surname="Bouazizi" fullname="Imed Bouazizi">
      <organization>Qualcomm</organization>
      <address>
        <postal>
          <country>Canada</country>
        </postal>
        <email>BOUAZIZI@qti.qualcomm.com</email>
      </address>
    </author>
    <date/>
    <area>Transport</area>
    <workgroup>avtcore</workgroup>
    <abstract>
      <?line 70?>

<t>This memo outlines RTP payload formats for the animation stream format as defined in the ISO/IEC 23090-39 standard (MPEG-I Avatar Representation Format), in the following referred to as ARF. ARF is composed of Avatar Animation Units (AAU) including an AAU header and zero or more AAU packets. The RTP payload header format allows for packetization of an AAU unit in an RTP packet payload as well as fragmentation of an AAU into multiple RTP packets.</t>
    </abstract>
  </front>
  <middle>
    <?line 74?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Avatars are digital representations of users in the metaverse, a set of virtual worlds where people can interact with each other in real-time. Users can customize different aspects of their avatars, such as clothing, accessories, and even physical attributes. Avatars allow users to express themselves and create a unique digital identity within the metaverse. The integration, animation, and representation of avatars in real-time communication services is essential to enable immersive experiences.</t>
      <t><xref target="ISO.IEC.23090-39"/> specifies the Avatar Representation Format (ARF) to offer an interoperable exchange format for the storage, carriage and animation of avatars. It defines the "Avatar Animation Unit"(AAU) as a unit of packetization suitable for Avatar animation streams, and similar in essence to the NAL unit defined in some video specifications. This document describes how AAUs can be transmitted using the RTP protocol. This document follows recommendations in <xref target="RFC8088"/> and <xref target="RFC2736"/> for RTP payload format writers.</t>
    </section>
    <section anchor="conventions">
      <name>Conventions</name>
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
    </section>
    <section anchor="definitions-and-abbreviations">
      <name>Definitions and Abbreviations</name>
      <section anchor="general">
        <name>General</name>
        <t>This document uses the definitions of the Avatar Representation Format <xref target="ISO.IEC.23090-39"/>. Some of these terms are provided here for convenience.</t>
      </section>
      <section anchor="definitions">
        <name>Definitions</name>
        <t>Animation Streams: timed data used to animate the base avatar.</t>
      </section>
      <section anchor="abbreviation">
        <name>Abbreviation</name>
        <t>ARF Avatar Representation Format</t>
        <t>AAU Avatar Animation Unit</t>
        <t>LoD Level of Detail</t>
      </section>
    </section>
    <section anchor="avatar-format">
      <name>Avatar Representation Format (informative)</name>
      <section anchor="overview-of-avatar-representation-format">
        <name>Overview of Avatar Representation Format</name>
        <t>The Avatar Representation Format (ARF) defines two key components of an avatar animation system: the Base Avatar Format, which describes static assets, and the Animation Stream Format, which describes the dynamic part of the avatar animation, and is the core subject of this document.</t>
        <t>The Base Avatar Format defines a structure for avatar models, among other things allowing them to be stored in digital asset repositories. This ensures that core avatar assets can be accessed and animated by receiving systems. On the other hand, the Animation Stream Format specifies how animation data is organized and transmitted between sender and receiver. It defines the encoding of facial and body animation, enabling data captured from input devices such as head-mounted displays (HMDs) and sensors to be consistently interpreted across different systems for animating associated avatars. <xref target="_figure-avatar-architecture"/> describes an Avatar reference architecture.</t>
        <figure anchor="_figure-avatar-architecture">
          <name>Avatar reference architecture</name>
          <artwork><![CDATA[
+---------+
|Reference|
|  Model  |
+----+----+
     |                +-------------+                       
     +--------------->|Digital Asset|Base Avatar Format(BAF)
     |                |    Repo     +--------------------+
     |                +-------------+                    |
     |                                                   |
+----+---+                                               |     
|Tracking|    +------+   Animation Stream Format    +----v---+
| System |--->|Sender|----------------------------->|receiver|
+--------+    +------+                              +--------+  
]]></artwork>
        </figure>
      </section>
      <section anchor="avatar-stream">
        <name>Avatar Animation Streams</name>
        <t>Animation streams are timed data used to animate an avatar. In <xref target="ISO.IEC.23090-39"/>, this data includes skeletal, blend shape set, and other animation-related information. Animation stream format defines how animation data is structured and carried between senders and receivers. This format defines how facial and body animation information is encoded, allowing data captured from input devices like Head-Mounted Displays (HMDs) and sensors to be consistently interpreted across different systems for the animation of associated avatars.</t>
        <t>The animation streams may be read from a file, or generated on-the-fly as cameras and/or sensors capture a person's motion and generate corresponding commands to mimic this movement for an avatar that represents the user. Avatar animation samples are structured into a bitstream comprising a sequence of Avatar Animation Units (AAUs), defined in <xref target="ISO.IEC.23090-39"/>, and whose general structure is provided in <xref target="figure1"/>.</t>
        <t>An avatar animation is associated with a Base Avatar, using an avatar ID. Each AAU is associated with an Avatar ID that indicates the target avatar to which the animation data applies. In addition, it is also associated with a Level of Detail (LoD), which indicates the level of detail of the asset to which the animation data is associated. The animation data within an AAU can for example be generated by a tracking and animation framework (e.g., OpenXR or ARKit). <xref target="ISO.IEC.23090-39"/> defines this identified using a URN.</t>
        <t>The receiver is aware of the avatar IDs and/or levels of detail that are transmitted in a stream, and needs the appropriate assets to render the avatar animation. The method for accessing the assets is not described in this document. The receiver can for example use the avatar ID and level of detail associated with an AAU to transmit the AAU to an animation player instance that has the proper assets.</t>
        <figure anchor="figure1">
          <name>The structure of AAU Header(a) and Payload(b)</name>
          <artwork><![CDATA[
   +---------+-----------+  +----------+-----------------+
   |unit_type|unit_length|  |timestamp |data of unit_type|
   +---------+-----------+  +----------+-----------------+
   (a) AAU Header           (b) AAU Payload
]]></artwork>
        </figure>
      </section>
    </section>
    <section anchor="section5">
      <name>Payload format for ARF Animation Streams</name>
      <section anchor="general-1">
        <name>General</name>
        <t>This section specifies details related to the RTP payload format definitions for the ARF Animation Streams defined in <xref target="ISO.IEC.23090-39"/>. Aspects related to RTP header, RTP payload header and general payload structure are defined.</t>
      </section>
      <section anchor="rtp-header-usage">
        <name>RTP Header Usage</name>
        <t>The RTP header is defined in <xref target="RFC3550"/> and represented in <xref target="_figure-rtpheader"/>. Some of the header field values are interpreted as follows.</t>
        <figure anchor="_figure-rtpheader">
          <name>RTP header for Avatar Animation Unit</name>
          <artwork><![CDATA[
   0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X|  CC   |M|     PT      |       sequence number         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           timestamp                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                             ....                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   
]]></artwork>
        </figure>
        <t>Marker bit (M): 1 bit.</t>
        <t>The marker bit SHOULD be set to one in the first RTP packet after an idle period. This is aligned with the use of the marker bit in audio codecs. This can for example be used for jitter buffer adaptation. The marker bit in all other packets MUST be set to zero.</t>
        <t>Payload type (PT): 7 bits</t>
        <t>The assignment of a payload type MUST be performed either through the profile used or in a dynamic way.</t>
        <t>Sequence Number (SN): 16 bits</t>
        <t>Set and used in accordance with <xref target="RFC3550"/></t>
        <t>Timestamp: 32 bits</t>
        <t>A timestamp representing the sampling time of the earliest AAU (Avatar Animation Unit) in the payload. The AAU defines aau_timestamp in its payload <xref target="ISO.IEC.23090-39"/>. The timestamp in seconds can be calculated as: timestamp / timescale.</t>
        <t>Synchronization source (SSRC): 32 bits</t>
        <t>Used to identify the source of the RTP packets. By definition a single SSRC is used for all parts of a single bitstream. The remaining RTP header fields are used as specified in <xref target="RFC3550"/>.</t>
      </section>
      <section anchor="payload-header">
        <name>RTP Payload Header for Avatar Animation Unit</name>
        <t>The RTP Payload Header follows the RTP header. <xref target="_figure-rtpheader-aau"/> describes RTP Payload Header.</t>
        <figure anchor="_figure-rtpheader-aau">
          <name>RTP Payload header for Avatar Animation</name>
          <artwork><![CDATA[
 0 1 2 3 4 5 6 7      0 1 2 3 4 5 6 7 
+-+-+------------+   +-+-+------------+
|A|R|     UT     |   |A|R|     UT     |
+-+-+------------+   +----------------+
                     |    Avatar ID   |
                     +----------------+
   
 (a) A = 0            (b) A = 1  
]]></artwork>
        </figure>
        <t>A (Avatar bit, 1 bit): This field indicates the presence of the Avatar ID field in the RTP payload header. A value of 1 indicates that an 8-bit Avatar ID field is present immediately following the first octet of the RTP payload header, while a value of 0 indicates that the Avatar ID field is not present.</t>
        <t>R (Reserved, 1 bit): This bit is reserved for future use. It MUST be set to 0 by the sender and MUST be ignored by the receiver.</t>
        <t>UT (Unit Type, 6 bits): this field indicates the type of the payload, which can be the type of the AAU <xref target="ISO.IEC.23090-39"/> for single unit payload, or the type of the payload otherwise, as shown in <xref target="_figure-transmission-type"/>.</t>
        <t>Avatar ID (8 bits): This field identifies the avatar to which the animation data carried in the RTP packet belongs. The field is present only when the Avatar bit (A) is set to 1. When SDP is used, the value of this field SHOULD match an avatar ID key signaled in the avatar-ids SDP parameter. When the Avatar bit (A) is set to 0, the RTP stream SHOULD be associated with a single avatar, whose identity is determined through session signaling, such as the avatar-ids SDP parameter. When SDP is used, the value of this field SHOULD match an avatar ID key signaled in the avatar-ids SDP parameter. The receiver MAY ignore the RTP payload otherwise.</t>
      </section>
      <section anchor="payload-structures">
        <name>Payload structures</name>
        <section anchor="general-2">
          <name>General</name>
          <t>Three different types of RTP packet payload structures are specified. A single unit packet contains a single AAU in the payload. A fragmentation unit contains a subset of an AAU. An aggregation packet contains multiple Avatar Animation Units in the payload. The unit type (UT) field of the RTP payload header, as shown in <xref target="_figure-transmission-type"/>, identifies both the payload structure and, in the case of a single-unit structure, also identifies the type of AAU present in the payload. The Unit Types 1 through 5 in <xref target="_figure-transmission-type"/> are defined in <xref target="ISO.IEC.23090-39"/>.</t>
          <t>The RTP payload header described in Figures 7, 8, 10, and 11 illustrate the case where the Avatar bit (A) is set to 1.  When A is set to 0, the Avatar ID field is omitted, and the RTP payload header consists of a single octet.</t>
          <figure anchor="_figure-transmission-type">
            <name>Payload structure type for Avatar</name>
            <artwork><![CDATA[
Unit     Payload   Name
Type     Structure
----------------------------------------
0        Single    Configuration AAU
1        Single    Blendshape AAU
2        Single    Joint AAU
3        Single    Landmark AAU
4        Single    Texture AAU   
5        Single    Silent AAU  
61       Aggr      Aggregation Packet (STAP)
62       Aggr      Aggregation Packet (MTAP)
63       Frag      Fragmentation Unit
]]></artwork>
          </figure>
          <t>The payload structures are represented in <xref target="_figure-transmission-style"/>. The single unit payload structure is specified in <xref target="single"/>. The fragmented unit payload structure is specified in <xref target="fragmented"/>. The aggregation unit payload structure is specified in <xref target="aggregated"/>.</t>
          <figure anchor="_figure-transmission-style">
            <name>RTP Transmission mode</name>
            <artwork><![CDATA[
                                            +-------------------+
                                            |     RTP Header    |
                                            +-------------------+
                                            | RTP Payload Header|
                      +-------------------+ |   (Aggregation)   |
                      |    RTP Header     | +-------------------+
+-------------------+ +-------------------+ |     AAU 1 Size    |
|     RTP Header    | | RTP Payload Header| +-------------------+
+-------------------+ |  (Fragmentation)  | |       AAU 1       |
| RTP Payload Header| +-------------------+ +-------------------+
+-------------------+ |     FU Header     | |     AAU 2 Size    |
|    RTP Payload    | +-------------------+ +-------------------+
|   (Single AAU)|   | |   RTP Payload     | |      ...          |
+-------------------+ +-------------------+ +-------------------+
(a) single unit      (b)fragmentation unit (c) aggregation packet

]]></artwork>
          </figure>
        </section>
        <section anchor="single">
          <name>Single Unit Payload Structure</name>
          <t>In a single unit payload structure, as described in <xref target="_figure-transmission-single"/>, the RTP packet contains the RTP header, followed by the Payload Header and one single AAU. The Payload Header follows the structure described in <xref target="payload-header"/>. The  payload contains an AAU as defined in <xref target="ISO.IEC.23090-39"/>.</t>
          <figure anchor="_figure-transmission-single">
            <name>Single AAU payload structure</name>
            <artwork><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                          RTP Header                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Payload Header |   (Avatar ID) |                               |
+---------------+---------------+                               |
|                           AAU  Data                           |
|                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                               :...OPTIONAL RTP padding        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
          </figure>
        </section>
        <section anchor="fragmented">
          <name>Fragmented Unit Payload Structure</name>
          <t>In a fragmented unit payload structure, as described in <xref target="_figure-fragment-structure"/>, the RTP packet contains the RTP header, followed by the Payload Header, a Fragmented Unit (FU) header, and an AAU fragment. The Payload Header follows the structure described in <xref target="payload-header"/>. The value of the UT field of the Payload Header is 63. The FU header follows the structure described in <xref target="_figure-fragment-header"/>.</t>
          <figure anchor="_figure-fragment-structure">
            <name>Fragmentation unit header</name>
            <artwork><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                          RTP Header                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Payload Header |   (Avatar ID) | FU Header     |               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               |
|                          AAU Fragment                         |
|                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                               :...OPTIONAL RTP padding        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
          </figure>
          <t>FU headers are used to enable fragmenting a single AAU into multiple RTP packets. Fragments of the same AAU MUST be sent in consecutive order with ascending RTP sequence numbers (with no other RTP packets within the same RTP stream being sent between the first and last fragment). FUs MUST NOT be nested, i.e., an FU MUST NOT contain a subset of another FU.</t>
          <t><xref target="_figure-fragment-header"/> describes a FU header, including the following fields:</t>
          <figure anchor="_figure-fragment-header">
            <name>Fragmentation unit header</name>
            <artwork><![CDATA[
+-------------------------------+
| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
+---+---+---+---+---+---+---+---+
|FUS|FUE|          UT           |
+---+---+-----------------------+
]]></artwork>
          </figure>
          <t>FUS (Fragmented Unit Start, 1 bit): this field MUST be set to 1 for the first fragment, and 0 for the other fragments.</t>
          <t>FUE (Fragmented Unit End, 1 bit): this field MUST be set to 1 for the last fragment, and 0 for the other fragments.</t>
          <t>UT (Unit Type, 6 bits): this field indicates the type of the AAU this fragment belongs to, using values defined in <xref target="_figure-transmission-type"/>.</t>
        </section>
        <section anchor="aggregated">
          <name>Aggregation Packet Payload Structure</name>
          <t>In an aggregation packet, as described in <xref target="_figure-aggre-structure"/>, the RTP packet contains an RTP header, followed by a Payload Header, and, for each aggregated AAU, an AAU size followed by the AAU. The Payload Header follows the structure described in <xref target="payload-header"/>.</t>
          <figure anchor="_figure-aggre-structure">
            <name>Single-Time Aggregation Packet</name>
            <artwork><![CDATA[
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                          RTP Header                           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |Payload Header |  (Avatar ID)  |           AAU 1 Size          |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                              AAU 1                            |
    |                                                               |
    :                                                               :
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |            AAU 2 Size       |                                 |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                                 |
    |                              AAU 2                            |
    |                                                               |
    |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                               :...OPTIONAL RTP padding        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
          </figure>
          <t><xref target="_figure-aggre-structure"/> shows a Single-Time Aggregation Packet (STAP), which can be used to transmit multiple Avatar Animation Units that correspond to the same timestamp. For example, if two different AAUs are used for different animations for different parts of the avatar, they can be transmitted together in a single STAP. The default size of the avatar animation unit length field is 16 bits. The value of the UT field of the Payload Header is 61.</t>
          <t>All AAUs contained in an aggregation packet MUST belong to the same avatar. When the Avatar bit (A) is set to 1, the Avatar ID field identifies the avatar to which all AAUs in the aggregation packet belong.</t>
          <figure anchor="_figure-aggremtap-structure">
            <name>Multiple-time aggregation packet</name>
            <artwork><![CDATA[
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                          RTP Header                           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |Payload Header |  (Avatar ID)  |          AAU 1 Size           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                           TS offset           |               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               |
    |                               AAU 1                           |
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |             AAU 2 Size        |            TS offset          |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |   TS offset   |                                               |
    |-+-+-+-+-+-+-+-+                                               |
    |                              AAU 2                            |
    |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                               :...OPTIONAL RTP padding        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   
]]></artwork>
          </figure>
          <t><xref target="_figure-aggremtap-structure"/> shows a multi-time aggregation packet. It is used to transmit multiple Avatar Animation Units with different timestamps, in one RTP packet. Multi-time aggregation can help reduce the number of packets, in environments where some delay is acceptable. The default size of both the TS offset field and the AAU length field is 16 bits. The value of the UT field of the Payload Header is 62. In case of MTAP, the timestamp offset field MUST be set to the value of (AAU-time of the animation unit - RTP timestamp of the packet). The timestamp offset of the earliest aggregation unit MUST always be zero. Therefore, the RTP timestamp of the MTAP is identical to the earliest AAU-time.</t>
        </section>
      </section>
    </section>
    <section anchor="transmission-consdier">
      <name>AAU Transmission Considerations</name>
      <t>The following considerations apply for the streaming of Avatar Animation Units over RTP:</t>
      <t>In some multimedia conference scenarios using an RTP video mixer (e.g., when adding or selecting a new source), it is recommended to use Full Intra Request (FIR) feedback <xref target="RFC5104"/> messages with avatar animation. The purpose of the FIR message is to cause an encoder to send a decoder refresh point at the earliest opportunity. In the context of avatar animation, an appropriate decoder refresh point is a configuration AAU. The configuration AAU point enables a decoder to be reset to a known state and be able to decode all AAUs following it.</t>
    </section>
    <section anchor="payload-format-parameters">
      <name>Payload Format Parameters</name>
      <t>This section describes payload format optional parameters. A mapping of the parameters into the Session Description Protocol (SDP) <xref target="RFC8866"/> is also provided for applications that use SDP. Equivalent parameters could be defined elsewhere for use with control protocols that do not use SDP.</t>
      <section anchor="format-param">
        <name>Media Type Registration Update</name>
        <t>The receiver MUST ignore any parameter unspecified in this memo.</t>
        <t>Type name: application</t>
        <t>Subtype name: ampg</t>
        <t>Required parameters: N/A</t>
        <t>Optional parameters: Optional parameters are defined in the following section.</t>
        <t>Encoding considerations: This type is only defined for transfer via RTP <xref target="RFC3550"/>.</t>
        <t>Security considerations: Please see section 11.</t>
        <t>Interoperability considerations: N/A</t>
        <t>Published specification: Please refer to <xref target="ISO.IEC.23090-39"/></t>
        <t>Applications that use this media type: Any application that relies on Avatar media services over RTP</t>
        <t>Fragment identifier considerations: N/A</t>
        <t>Additional information: N/A</t>
        <t>Person &amp; email address to contact for further information:</t>
        <t>Intended usage: COMMON</t>
        <t>Restrictions on usage: N/A</t>
        <t>Author: See Authors' Address section of this memo.</t>
        <t>Change controller: IETF avtcore@ietf.org (mailto:avtcore@ietf.org)</t>
        <t>Provisional registration? (standards tree only): No</t>
      </section>
      <section anchor="optional-param">
        <name>Optional Parameters Definition</name>
        <t>version:
It provides the year of the edition and amendment of the specifications followed by this RTP payload type. This parameter is defined in Table 3 of <xref target="ISO.IEC.23090-39"/>.</t>
        <t>frameworks:
It provides a comma-separated list of the tracking framework names (URNs) used to generate the encoded stream. The URNs in this parameter correspond to the URNs in Table 5, 6 of <xref target="ISO.IEC.23090-39"/>.</t>
        <t>avatar-ids: 
It provides an association between avatar IDs for which animation data is carried in the animation stream, and their corresponding ARF containers. This parameter is provided as a comma-separated list of "key/value" pairs, where the key is the avatar id (an integer between 0 and 255 inclusive) and the value is a base64 encoded string. The semantic of the value is application dependent and can for example be a URL to the ARF container. The parameter avatar_id is defined in section 7 of <xref target="ISO.IEC.23090-39"/>.</t>
        <t>avatar-lods:
It indicates which levels of detail are used in the avatar animation stream. This parameter is a comma-separated list of integers. Each item in this list corresponds to a level of detail as defined in section 7 of <xref target="ISO.IEC.23090-39"/></t>
      </section>
    </section>
    <section anchor="congestion-control-consideration">
      <name>Congestion Control Consideration</name>
      <t>General congestion control considerations for RTP transmission, as described in <xref target="RFC3550"/>, also apply to avatar streaming over RTP. By adjusting the SDP 'avatar-lods' parameter, it is possible to reduce processing load and optimize bandwidth usage, thereby partially mitigating congestion issues. The ability to adapt to the level of detail dynamically allows senders or receivers to manage computational complexity and network resource consumption based on system constraints or user context. Moreover, in use cases such as video conferencing, different levels of detail may be applied to different parts of the avatar and transmitted via separate streams.</t>
    </section>
    <section anchor="sdp-considerations">
      <name>SDP Considerations</name>
      <t>The mapping of above-defined payload format media type to the corresponding fields in the Session Description Protocol (SDP) is done according to <xref target="RFC8866"/>.</t>
      <t>The media name in the "m=" line of SDP MUST be application.</t>
      <t>The encoding name in the "a=rtpmap" line of SDP MUST be ampg</t>
      <t>The clock rate in the "a=rtpmap" line may be any sampling rate and SHOULD match the acu_timescale value of the AAU CONFIG unit <xref target="ISO.IEC.23090-39"/>.</t>
      <t>The OPTIONAL parameters (defined in <xref target="optional-param"/>), when present, MUST be included in the "a=fmtp" line of SDP. This is expressed as a media type string, in the form of a semicolon-separated list of parameter=value pairs.</t>
      <t>An example of media representation corresponding to the avatar animation RTP payload in SDP is as follows:</t>
      <artwork><![CDATA[
m=application 43291 UDP/TLS/RTP/SAVPF 120 a=rtpmap:120 ampg/8000
a=fmtp:120 
frameworks=urn:mpeg:avatar:v1:openxr:face,urn:mpeg:avatar:v1:
openxr:body;version=2025;avatar-ids=1/ 
aHR0cDovL2V4YW1wbGUuY29tL2F2YXRhcjEuYXJm,
2/aHR0cDovL2V4YW1wbGUuY29tL2F2YXRhcjIuYXJm;avatar-lods=0,1,2
]]></artwork>
      <section anchor="sdp-offeranswer-considerations">
        <name>SDP Offer/Answer Considerations</name>
        <t>When using the offer/answer procedure described in <xref target="RFC3264"/> to negotiate the use of avatar animations, the following considerations apply:</t>
        <t>The SDP parameter version identifies the version of the avatar animation specification. It MUST be used symmetrically in SDP offer and answer, and it MUST NOT be changed in subsequent offers or answers within the same session. If it is not specified, the initial version of the specification SHOULD be assumed. Any receiver compliant with <xref target="ISO.IEC.23090-39"/> must accept any stream with a compatible version.</t>
        <t>The properties expressed using SDP parameters other than 'version' are provided as recommendations for efficient data transmission and are not binding, meaning that a sender is encouraged but not required to conform to the parameters specified by the receiver. These properties may be set to different values in offers and answers. These properties may be updated in subsequent offers or answers. These properties can be sent by a sender to reflect the characteristics of bitstreams and can be set by a receiver to reflect the capabilities and configurations of the local player device, or a preferred set of bitstream properties.</t>
        <t>The parameter frameworks indicates that the AAUs of the stream carry animation data that conforms to the one or more framework names (URNs) signalled with this parameter. The sender uses this parameter to indicate the formats of data transported within the AAUs of the stream. The receiver, to be able to render the animations, needs to support the formats associated with signalled frameworks. The receiver uses this parameter to indicate the desired framework names.</t>
        <t>The parameter avatar-ids indicates that a stream corresponds to the one or more avatar IDs signalled with this parameter. The sender uses this parameter to indicate that the AAUs of the stream carry data corresponding to the signalled avatar IDs. The receiver uses this parameter to indicate the avatar IDs it wishes to receive data for.</t>
        <t>The parameter avatar-lods indicates that the AAUs of the stream correspond to one or more levels of detail signalled with this parameter. The sender uses this parameter to indicate available LoDs, and the receiver uses it to select the desired LoD. To render the animations, the receiver MUST have loaded the corresponding assets associated with the selected level(s) of detail.</t>
        <t>A receiver may ignore any part of a received stream, e.g., that it does not have support for rendering.</t>
      </section>
      <section anchor="declarative-sdp-considerations">
        <name>Declarative SDP Considerations</name>
        <t>When avatar animation over RTP is offered with SDP in a declarative style, the parameters capable of indicating both bitstream properties as well as receiver capabilities are used to indicate only bitstream properties. For example, in this case, the parameters frameworks, avatar-ids, and avatar-lods declare the values used by the bitstream, not the capabilities and configurations for receiving bitstreams. A receiver of the SDP is required to support all parameters and values of the parameters provided; otherwise, the receiver MUST reject or not participate in the session. It falls on the creator of the session to use values that are expected to be supported by the receiving application.</t>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="avatar-animation-media-registration">
        <name>Avatar Animation Media Registration</name>
        <t>New media types will be registered with IANA; see <xref target="format-param"/>.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>RTP packets using the payload format defined in this specification are subject to the security considerations discussed in the RTP specification <xref target="RFC3550"/>, and in any applicable RTP profile such as RTP/AVP <xref target="RFC3551"/>, RTP/AVPF <xref target="RFC4585"/>, RTP/SAVP <xref target="RFC3711"/>, or RTP/SAVPF <xref target="RFC5124"/>.</t>
      <t>For example, an avatar may contain sensitive information derived from a user's personal data, and thus requires protection against leakage or tampering during transmission. When avatar data is delivered over a network or downloaded from a server, it is critical to ensure its integrity and confidentiality to prevent unauthorized access, modification, or unauthorized disclosure.</t>
      <t>However, as "Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution" <xref target="RFC7202"/> discusses, it is not an RTP payload format's responsibility to discuss or mandate what solutions are used to meet the basic security goals like confidentiality, integrity, and source authenticity for RTP in general. This responsibility lies with anyone using RTP in an application. They can find guidance on available security mechanisms and important considerations in "Options for Securing RTP Sessions" <xref target="RFC7201"/>. Applications SHOULD use one or more appropriate strong security mechanisms. The rest of this Security Considerations section discusses the security impacting properties of the payload format itself.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="ISO.IEC.23090-39" target="https://www.mpeg.org/standards/MPEG-I/39/">
          <front>
            <title>Information technology - Coded representation of immersive media - Part 39: Avatar Representation Format</title>
            <author>
              <organization>ISO/IEC</organization>
            </author>
            <date year="2025"/>
          </front>
          <seriesInfo name="ISO/IEC" value="23090-39"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC2736">
          <front>
            <title>Guidelines for Writers of RTP Payload Format Specifications</title>
            <author fullname="M. Handley" initials="M." surname="Handley"/>
            <author fullname="C. Perkins" initials="C." surname="Perkins"/>
            <date month="December" year="1999"/>
            <abstract>
              <t>This document provides general guidelines aimed at assisting the authors of RTP Payload Format specifications in deciding on good formats. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="36"/>
          <seriesInfo name="RFC" value="2736"/>
          <seriesInfo name="DOI" value="10.17487/RFC2736"/>
        </reference>
        <reference anchor="RFC8088">
          <front>
            <title>How to Write an RTP Payload Format</title>
            <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>This document contains information on how best to write an RTP payload format specification. It provides reading tips, design practices, and practical tips on how to produce an RTP payload format specification quickly and with good results. A template is also included with instructions.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8088"/>
          <seriesInfo name="DOI" value="10.17487/RFC8088"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC3550">
          <front>
            <title>RTP: A Transport Protocol for Real-Time Applications</title>
            <author fullname="H. Schulzrinne" initials="H." surname="Schulzrinne"/>
            <author fullname="S. Casner" initials="S." surname="Casner"/>
            <author fullname="R. Frederick" initials="R." surname="Frederick"/>
            <author fullname="V. Jacobson" initials="V." surname="Jacobson"/>
            <date month="July" year="2003"/>
            <abstract>
              <t>This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of- service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. The protocol supports the use of RTP-level translators and mixers. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes. There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="64"/>
          <seriesInfo name="RFC" value="3550"/>
          <seriesInfo name="DOI" value="10.17487/RFC3550"/>
        </reference>
        <reference anchor="RFC8866">
          <front>
            <title>SDP: Session Description Protocol</title>
            <author fullname="A. Begen" initials="A." surname="Begen"/>
            <author fullname="P. Kyzivat" initials="P." surname="Kyzivat"/>
            <author fullname="C. Perkins" initials="C." surname="Perkins"/>
            <author fullname="M. Handley" initials="M." surname="Handley"/>
            <date month="January" year="2021"/>
            <abstract>
              <t>This memo defines the Session Description Protocol (SDP). SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. This document obsoletes RFC 4566.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8866"/>
          <seriesInfo name="DOI" value="10.17487/RFC8866"/>
        </reference>
        <reference anchor="RFC3551">
          <front>
            <title>RTP Profile for Audio and Video Conferences with Minimal Control</title>
            <author fullname="H. Schulzrinne" initials="H." surname="Schulzrinne"/>
            <author fullname="S. Casner" initials="S." surname="Casner"/>
            <date month="July" year="2003"/>
            <abstract>
              <t>This document describes a profile called "RTP/AVP" for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. It provides interpretations of generic fields within the RTP specification suitable for audio and video conferences. In particular, this document defines a set of default mappings from payload type numbers to encodings. This document also describes how audio and video data may be carried within RTP. It defines a set of standard encodings and their names when used within RTP. The descriptions provide pointers to reference implementations and the detailed standards. This document is meant as an aid for implementors of audio, video and other real-time multimedia applications. This memorandum obsoletes RFC 1890. It is mostly backwards-compatible except for functions removed because two interoperable implementations were not found. The additions to RFC 1890 codify existing practice in the use of payload formats under this profile and include new payload formats defined since RFC 1890 was published. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="65"/>
          <seriesInfo name="RFC" value="3551"/>
          <seriesInfo name="DOI" value="10.17487/RFC3551"/>
        </reference>
        <reference anchor="RFC4585">
          <front>
            <title>Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)</title>
            <author fullname="J. Ott" initials="J." surname="Ott"/>
            <author fullname="S. Wenger" initials="S." surname="Wenger"/>
            <author fullname="N. Sato" initials="N." surname="Sato"/>
            <author fullname="C. Burmeister" initials="C." surname="Burmeister"/>
            <author fullname="J. Rey" initials="J." surname="Rey"/>
            <date month="July" year="2006"/>
            <abstract>
              <t>Real-time media streams that use RTP are, to some degree, resilient against packet losses. Receivers may use the base mechanisms of the Real-time Transport Control Protocol (RTCP) to report packet reception statistics and thus allow a sender to adapt its transmission behavior in the mid-term. This is the sole means for feedback and feedback-based error repair (besides a few codec-specific mechanisms). This document defines an extension to the Audio-visual Profile (AVP) that enables receivers to provide, statistically, more immediate feedback to the senders and thus allows for short-term adaptation and efficient feedback-based repair mechanisms to be implemented. This early feedback profile (AVPF) maintains the AVP bandwidth constraints for RTCP and preserves scalability to large groups. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4585"/>
          <seriesInfo name="DOI" value="10.17487/RFC4585"/>
        </reference>
        <reference anchor="RFC3711">
          <front>
            <title>The Secure Real-time Transport Protocol (SRTP)</title>
            <author fullname="M. Baugher" initials="M." surname="Baugher"/>
            <author fullname="D. McGrew" initials="D." surname="McGrew"/>
            <author fullname="M. Naslund" initials="M." surname="Naslund"/>
            <author fullname="E. Carrara" initials="E." surname="Carrara"/>
            <author fullname="K. Norrman" initials="K." surname="Norrman"/>
            <date month="March" year="2004"/>
            <abstract>
              <t>This document describes the Secure Real-time Transport Protocol (SRTP), a profile of the Real-time Transport Protocol (RTP), which can provide confidentiality, message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP). [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3711"/>
          <seriesInfo name="DOI" value="10.17487/RFC3711"/>
        </reference>
        <reference anchor="RFC5124">
          <front>
            <title>Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)</title>
            <author fullname="J. Ott" initials="J." surname="Ott"/>
            <author fullname="E. Carrara" initials="E." surname="Carrara"/>
            <date month="February" year="2008"/>
            <abstract>
              <t>An RTP profile (SAVP) for secure real-time communications and another profile (AVPF) to provide timely feedback from the receivers to a sender are defined in RFC 3711 and RFC 4585, respectively. This memo specifies the combination of both profiles to enable secure RTP communications with feedback. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5124"/>
          <seriesInfo name="DOI" value="10.17487/RFC5124"/>
        </reference>
        <reference anchor="RFC7201">
          <front>
            <title>Options for Securing RTP Sessions</title>
            <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
            <author fullname="C. Perkins" initials="C." surname="Perkins"/>
            <date month="April" year="2014"/>
            <abstract>
              <t>The Real-time Transport Protocol (RTP) is used in a large number of different application domains and environments. This heterogeneity implies that different security mechanisms are needed to provide services such as confidentiality, integrity, and source authentication of RTP and RTP Control Protocol (RTCP) packets suitable for the various environments. The range of solutions makes it difficult for RTP-based application developers to pick the most suitable mechanism. This document provides an overview of a number of security solutions for RTP and gives guidance for developers on how to choose the appropriate security mechanism.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7201"/>
          <seriesInfo name="DOI" value="10.17487/RFC7201"/>
        </reference>
        <reference anchor="RFC7202">
          <front>
            <title>Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution</title>
            <author fullname="C. Perkins" initials="C." surname="Perkins"/>
            <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
            <date month="April" year="2014"/>
            <abstract>
              <t>This memo discusses the problem of securing real-time multimedia sessions. It also explains why the Real-time Transport Protocol (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a single media security mechanism. This is relevant for designers and reviewers of future RTP extensions to ensure that appropriate security mechanisms are mandated and that any such mechanisms are specified in a manner that conforms with the RTP architecture.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7202"/>
          <seriesInfo name="DOI" value="10.17487/RFC7202"/>
        </reference>
        <reference anchor="RFC5104">
          <front>
            <title>Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)</title>
            <author fullname="S. Wenger" initials="S." surname="Wenger"/>
            <author fullname="U. Chandra" initials="U." surname="Chandra"/>
            <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
            <author fullname="B. Burman" initials="B." surname="Burman"/>
            <date month="February" year="2008"/>
            <abstract>
              <t>This document specifies a few extensions to the messages defined in the Audio-Visual Profile with Feedback (AVPF). They are helpful primarily in conversational multimedia scenarios where centralized multipoint functionalities are in use. However, some are also usable in smaller multicast environments and point-to-point calls.</t>
              <t>The extensions discussed are messages related to the ITU-T Rec. H.271 Video Back Channel, Full Intra Request, Temporary Maximum Media Stream Bit Rate, and Temporal-Spatial Trade-off. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5104"/>
          <seriesInfo name="DOI" value="10.17487/RFC5104"/>
        </reference>
        <reference anchor="RFC3264">
          <front>
            <title>An Offer/Answer Model with Session Description Protocol (SDP)</title>
            <author fullname="J. Rosenberg" initials="J." surname="Rosenberg"/>
            <author fullname="H. Schulzrinne" initials="H." surname="Schulzrinne"/>
            <date month="July" year="2002"/>
            <abstract>
              <t>This document defines a mechanism by which two entities can make use of the Session Description Protocol (SDP) to arrive at a common view of a multimedia session between them. In the model, one participant offers the other a description of the desired session from their perspective, and the other participant answers with the desired session from their perspective. This offer/answer model is most useful in unicast sessions where information from both participants is needed for the complete view of the session. The offer/answer model is used by protocols like the Session Initiation Protocol (SIP). [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3264"/>
          <seriesInfo name="DOI" value="10.17487/RFC3264"/>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+09a28bR5LfBeg/NGTgLCIkJcrPMPDdMpYVa8+ytaKUTXax
CJpkk5p4OMPMDCXTlu+3X736MQ9ScqwEh8MykEPO9HRXV9e7q2s6nc72VhEV
semrnbPzU3WqV3GqJ+oozea6UNM0U4MrXehMnZlFZnKTFLqI0sQ22B2cHbXU
IInmfHlYZEbPd7a39GiUmau+gk470mlHU0/bW5N0nOg5DDnJ9LToRKaYwr1i
nGamkxULadfZfwxNdQHtPh0Ozl993t7Kqfe+On51frS9NYZ7szRb9VVeTLa3
okXWV0W2zIuD/f1v9w8ABmjdV+eZTvJFmhXbW9dp9n6WpctFX8l421vYq04m
v+g4TWColcm3txZRX/2zSMdtlcNzmZnm8G015y8A/VwvFlEy+xc+rZfFZZr1
t7eU6uA/SkVJ3levh131s05mfImn+3q1TPLofXA9zWYwm6Qw2WE0iwod82Uz
11HcV5fcvruC9n+JsNWEW3XH6ZxbjtNlUiAKLoaDKgg/ddXEwEKtQhh+0leR
yUo3NgPxgR7oTsw0Xd0GxEud6ImuwjHoqtd6/lGHYAwu52bCl9VdoNDYvnuJ
7e8GBF6qAnLcVd+nS/0x+hiFsBwjKPZGCM3fljqG/uclSL5/dzH4x/E/jv/y
WxF1f5MWG3CB/yXELNGV6fNvpY6H77rHr152Dx4BqXYefdvnpy0rHidTfgRY
qjDjyySN09lKddTLdALAZmVeTKcqms9NlsMICiYTaWh5qrNCQccb+XeHhw1o
2E1+B0DcAxClCTPiwf7BE/6dmywyeQRwusfkAWglk5I56WxmCqDmoljk/b29
6+vr7nxhZl0YZo94T2eTfO/k9NUPneO9R9/uIYYiiwDCmVJnRy8Per1v3fdn
j57a78/3nz9333vPHtvvj5482XfXnz99Glzv2e+Pnzx/4q4/67nrT3oHrp9n
B/u94PuBb7Pvxzp4St+3tzqdjtIjEFR6XOBEzi+jHNZknqp0WcRRYnIUiWoh
cpZnmZOgLS6N0k6SsqyTBkrnwLJTeHwCpEwtBdsO2cqiUu0yKjcufKtt+5mm
cZxegzQDqpqaLIMRihTHA8nexX8UTADIe5HmcAtITbr1Mv8iiWAGu4PBRQs6
HcfLCfamEwVX1KXRE5A3AJr6aDLAQqbmIHfp3kKP35si76pzgCPEijxk544A
Mor4ieijo3sZZQkg4ITgJ/eDzVx3MJlrE8f4/2mmZ/OQcaQDkCmpmi/jIlrE
Jugj7+Ii4qLOo8kkJn3xAMVUlk6WY+xke4sRkitQN0rEUoVDcxxpCSyTW6zP
TaGv4LdpKw28VGCDqygrQJ4o0FLxBEC+NNDhwqQI0RjgJLkHZKWuo+JSGT2+
VCn0lWGfQCtxp4jmpqsuaBx8YAy6MJ1HHxGsKawtgAM4WJhxQQDBsxGsDEMP
Cm4JHQKKxjH0CisIkI3HJgcNCIzephU0VyZRi8tVHo0BTl0UWTRaFgZW0OEA
10qmChg1HxANOQ41z018BdSP/YwB3AKIHdftt6XHWjQBEKNiRTOsYorJBJEw
ywirbc8tDF5dLMrkShhCYp7DwGPhM5NdRTBPJHMAFQEASBD2RI8A816ywmRQ
6CXQmKji06eqFP/8WSF6oylgjIC/g+0EI6W4OMqucAqj0Mjmw/gSNL+xfGBl
BCwqUDFQzlhnWQTfaPJecvh5d9VxIXKD4dlpZN4d5l1Ye82cBD2UOS1fwvog
TIFBWBVVQiN5NI9iTURJ6BwbnCIO/nbwhrsPJFmewoJcwbqnFnO8LCQUYEXA
2Foiv8Iz+RioDeZxCQQG8DKJj6B3tO/mUVFAj8scRU9hxUmWghGXxtW+WOTl
QBJICgakJjMpwPPpk2gUWEqcDf1GbQO/ce512a2uswhWDQBm2fAyTa6QiKBD
lv9GvTcrZGrg6Z2Ti+H5Tpv/r96+o+9nr/52cXz26hC/D18P3rxxX2yL4et3
F28O/Tf/5Mt3Jyev3h7yw3BVVS6dDH7e4XXZeXd6fvwO1mCHZVCIEJRcsEgj
Zq8MiBWRSTqHsU5r9f3LU9V7LCgBZQwoYXSB0oXvIK+ED9MkXslPWIqVAmvZ
MEWAeIBlWyCzI7nkKofVTBRKui6bRg/UIVJHxCuCvQ3Ik4i0Q+mDB+oHkwCT
xE7BupmA5GFKnwS9sKzbzIxNzNxVQyRPfjwHFJlszmIeKAuJdkKQE2GMadlJ
OnQFyGAieKXqJIFBiuJogqaVRsBZ8VIrQwCPNAzKrGz7DJHBCEMNvWlm1AY0
XCPn48036aF6A5I9xokegrSNYiHlzdIrMNFaSn16IF4bX/ws8L67QvFqrgPD
YS2U53cTmE6eXafEWWSbJNA2F32ua/JplRcG3EbE6feIUxmFu20DqUag+ryE
yXHYMZAnKGaRakQ/lQVc+zzR3wqcC+hkgWa4EGAVMO464gfQGwU5O/oV1DM/
ENB11+KnDr7Dh0Y5DDbJUihSRpuDx0DMNk9BNLLBQPpdlLUIzLkIAFQuzO5W
KRMaULemeVSQMSDy1CQ5jIXQAxQEvp0gIc7KZ7YiUJ44LQU/RisUvya6wvF5
gaDfd6zzGUpQfpP2JswHyhaVgl9w4iiAEDwMuPhRxg4VxcgU18ag9k+secrg
gKtbVZrA0ymZtLAqUz1G8wDbj9LJKlxLshewGY0OUg5XArREls4BnYsldsqW
hrW00MztzNFhRCkQ5YtYr8CQfn1ymLdYlwKKU7akRkghSR4BopICxGtJUI+z
FIwsb+QJPpkMGEK0yMGWA+jpCWsffPo0jWYAp4256Gx8CeqMqAhkuqdptJN5
dclNIL0eNhbx/T/us731Tcd+vtneujmzj93AD6VOkCyVupFm30gzciRvVOXj
e6Jm1dvykafLjTud/7yRgIIaIF3e1Flo9/vBUWvd2HQB5FHa2Lmd3u+G+2bd
s3f4hMhbh5S1z9K/sBTn4FK8B/K4CQDGztbxnG11JeuqhkRs6oZQPSR+umnC
UrAgltVuAiL5pjL+hk/4TJnkPvXVg/UEzeGVFzsbCXnnsxgiD+oqUxR3oO3Y
9P1c1u9iD7NZtV7FO1UFEidpNEDaogVInJFnjdLjvYlBS8dtBQY5ColLvTDo
Q4rxRbLTyaVOZmJi+ciHlLqqCqu1Za3YaxanTr+wPCX3oyZL85Iwtbqiof+1
ojQElbwylL8GVIHTV7dK2Dh6b9RrFK8nIl4P/yDxWg7aoAHSIGWt9q65TGqu
Vzg2/JB5aDWNYvDtoOsZGbnYESwjjNOZAmDooGvwSDXheQ+a2VkIPqAHcCDz
NHkIvac0GM7VdoaKGpQ2WEyk0tABgtuEg3mEBgtR3Dy9MuIqZYFJRZreedms
HdHX7zb4hHq+iA3zQEA3FGfRahQVQnhovWURuW0YCPltSQy5OcyUt9qhD9nM
OTjp68sUZD1PPQ7MI5ihs+CpA5YZPTD5mZPrNiQ8EqwsRWB0aI21xff0yDo+
7KpXGKSh+FLD406jHh8yZiNYE9zUYMRy3NShPhUzs0xwxAngX8VkloEY0ZNJ
xPYIRsTQxsvTBsirBv8ueAEta8mW4Yht0wk3tcYsmYWbwCrNmaM3lRYS5pEY
HNqLSG/mA9EO8oVnAbAXNVpwpKsqAY9pBhyBeztq13Rn3bZ6tzDJT2fIQ4Oz
/46KVreRRgIjD0Dl2NM0clEErS7O3nretRKNpnWNZF226o8PHUcSxvIAZbS6
pA0CExQnLnKAqTUxZsIohwXNUmAL0hJsTAOiM7ZVmzwJxu7cFJfphHmWjG4b
DJE+APIkLcpOfdnNUKWZVhdkmZvyjAnsKn000TmsLgaBZPZs0/M15Be3kCih
KZ6JsWwMHCHeLjUjZUGRMZlLg7kZGgad0PL6pmSI1S04Nt9uMDT1S7FaGP4G
unVWXIJVdIMqHACaL9QNUS3Gcl3brx53V7cIF6855u0/uyO+Ibun6wydnrVq
zi8DSUsS1PWKY+BSSVfQs7Vy0M0/LcezKMSHQYWa2fPpQW4o5v3EuvfVOIzc
DxwzJgqMtbEZIrHAhjhaGLGxmrUZjltkP2gjCXIHg+KAvK3Qbtpq8Coydrc8
Mimyz4PaQAz2IUt2keuZsWLCj4PsVoJU9qQksujUaFkH4QY4P1+JP7lNkcjE
E3Wl46Vo10rIToKbDQxC5LbfYE/3Gq4dNFx7xL7KPjxwoB6px+qJeqqeqefq
2y+5Jhzzlf8xz/744uDm9OYn4NKXL/H3Cbs1p+ehk6O8XZEs56OAyW7uE5YN
DouXIOs/fxQs+SoZX2Zp4kL56TIDTOwOh2cvW17rZQ2wvPjK/+p4ARub94wo
6iOQvKxAkjfgZbN73IXPxgb3it21LqdjXSuSA2EQbJxUNl8+C2ee6Ow9NATT
WO2etPrAPPC1q2RI+IdUvG8kWwEj8v1oGykxblM3yvIi3ArV00K2mCYxbipm
UToR14yMxGiWWH0tRr0VO8GIaLEsJ1Gq0B8bW9euwWwjTxev/YqmDjy85B2u
Cbgoob1S7jqOxXmVrVdFmyR+frh/3PXosGoL1bDaPT0HlD0jx6KMMbAXYHLk
zKB35qQ7PWZHAISgFgKoTSQR0ixdzi6t4YE+Gc8q5X0MF9+91quuLODQSpm3
LGV2h29xGZ8KUNKmIOlPfWFHY/DHJmTsEPIDLRFMw4qPvnp0EPY2CCSL0yfW
6CMPjH5EXokYnaGrUJBxsNtIkC1LRIIpXits7yLNevmLHxhao2Nm8dqskbGL
0iNgKaTod0qQeKzj8ZKVtZaNEW66x9/hvgnWfrhJqDksKUHThQReRMSsGD38
iOAl3PFX368CYwSNdMAirD92jtziqBspFuP7vPFgmznf1lrTcw1dwTqE0gCV
OKtv6g13wsRkqhoLocFhSf71LTIFLDVZjo7YEqF5UuuFd0OLkvXSbbBIOrDw
paBwvbdug9FRtQPoU72IkcBvykbyN05il43mm8HNGeuDC9bz+KN+cW2PjWZ4
g8rAf7yH7kO11c+aHuEfsu3Vi7LRRXY9XOzdRZMgykNtclrLkKlRACuUgeNu
oMc2KxPgDA7GkQlZ9vJZeHiG8BO3rWt2uyWUAVuj+GSv1Cs6vYl63kEBX+sv
lyELyrCYoMMYr4JsJK/G0nFhijKjhgBQ1CLGuJcDY78KRuOM2BsWKIhwz9Tu
mcGEEIw2llA24mhKJncJ8dMlOQdLTE05Lqraah9DFiRo/BaTbQIKiXbZpIXb
eUIYgHx3iYfPQUG1FWuPVp8d9aaVI0Um2BHM2ECOzZCotEJZ3hgQwVmJFKNE
DdeduGMNQ7HKvo4ok8nu54f+jDj9oIUxigkd2CCbW47d53aOIXVaczAPQw6b
wk02HF2iVDJ+RiZOk5nkmdXIz2UrhFRCVtigRVFvXs9eV/0dGw0PT60S4M1J
R3XBColtBuCNL0shQdqxRoME9JkDVfYSItAI2DuoFD0Hdy6TETeCtd92s5WI
qrcL62E/WVwtIUuOj7qsK3JYMcmBfFZrAuWG1k6gpsQwu4F5B+D/VHSVolcn
g5+F0WqCw9GsVa6nVZdfEk1KEQ4yKDMTZtMhPZP2b8g69H1xENzqdxSYZSaj
x9A1AkMh96vEeYllU2xQyWCkHsJHlyPJJuSwG271KD2bZWYmIbbKaC7ncU28
vckWpEHZ7L44b8kabpDPd5UL7ZDrR6n4Ig3hGMwLEMDGml0Vi7UOAefatjkA
XpEmVo5REqrVQg0TdXI4B21g+eHJbdMIw0VrY1RlJ6UhIlWK0h7RYLl61lbP
QTPtc8C4B+o2jpeYbCwZQ4QNThy9TZgxew7qoqRBT6YcsvapMA3wyvZZ2RYm
1d1gExJiVeDEKfUWmBhsVFwZ/AztClL27Z0+21vOzhry8PB5mSa0UkzTsODb
W716q+9xJ5U3UqnJQb3JX9MoKfjuo/rdN4AZdGe5weN6g3PzgWgXSQ4X/km9
yRCsGB4CGzy1YA6Ae/03y8enzMe7w/PBaQtaH9yp9Ym0tjM4AmHiv3mxwrlh
a4zTGslbA7UmRZnRvJG64/yQNUJyXVC0NGRerGJjncoGc6W80Vfxq7i9fdoK
U9z0uWsP/hnbSyhf79yNfYi7adjMuPOnKSdlnVOz5sOeUxDTVuvdnT8SirpD
uRaKxvFoIrsB5bc2TYRTe0qThmtrJtI83nooFDFyD7j6I3E3pz3VBrxpnvWX
QQEd75YYuMUdqwAOmTJCcefxvhgK+BxdlNHpcXFQw0UIyHrcr4OC1nrobKXW
jRuv0q/HRSlOfPNli7oGCvTxQyFEH/DxG+y03XGrwRarsv46SUtiT4XBgPPg
NuV57ny2ZqughfSsxYRTqbiRx2IQmx8HIa5m6dWupYKvEcwiW9tVB8xZm+UY
U1vcfe8JV0JTnExuAoOYBe6GCJYXuRWAKwExEd1ust6G5u1qffs2Y01mf+3e
2ldvrN3D/saGjZaKpGz+3NwPFJUVZrFuDdPWrdmSDaxd+317F5tGISvtEOMO
v7sL/HzditCnD0LNnu0QpptQbpeH4h5W5E4SSkxZEVFeNNdFis+yfOBMT2C1
tfIqMLqczLrVeNsgt+yzHdf4/sQWHumrzmn36KLl/WHKXiLEWDjuW64FURaD
EfGSj14ZBmzTp4/4saMLH1m+w9hVZDoY/i0aGz5/lmisWmBfD0W9iw24QLK2
5L8JF//fRWNdxFjBeFQ3DZlzWCo6Jgw2CP15VNutZMyGocJ1R5jdcrijcLme
80N+04JDYBjFMeMlHupSaYY0xJHjfGw4YZgCzeV0mlztUqMklf37YOzwJC8N
GgSqR4ayQHBkm0LuN30os1DDFzvfFkzjQnIC8KAjAJ2YnKJSUdd0Uaoi5bv7
IrwrMVEG8OhCDvCuE2DhwRcvFNvB8XaC1G1W8X5uf/0JmOYPkfA+sGgP/g7g
7xH8PYa/J/D3FP6eWUtm4x/0cnQxhL9XAUPINmhA6P6JNbDcRsjl5JZbqXjo
nVKrBocgpYLdyGALoLJ71nMpgEwOFgZWnvvuLq+nvctZb4CH+sivksmXjVsi
vrsM+1Ubd5QNSw2t5JRNKwDKppZLzl/JLbllkw3Nq4Y4YJOFFcSjrIXVtHOw
waaixnczqKROQ5M9pevWFC4dZRhhNr2HE5HWtoZUjqGFql12zw5jY5DuHhIq
7yWj8p6S2za5Vne1cu4Tmrq1Exo7JWjL8bY/BJoN81blQNsm3Pyes34N3fS/
spv+H4ebcrivenfTpG4Z667d3GGlmhjyC7u5J2juYurepZs7mLt3Gu12aNZY
ChUNUA4EdDCNsUEbsbmwXovQ3jHaYZu7ka2wSuqLNZ7d0ZPb9rvtYXY5I2fP
K5Dt6rISu3gY1ia8glU4pWIEPi2AypM42x1VV1CAxw6YV264TEKf4yD1MxoK
nRTpzBRS+8cnKAICWN+BjaBhoqwV11QfYJONj7n4rV5JV/19UYQe68hBHEuF
Ftb3kuramIgg9hfaOiVc25Oxt2fA9NZsW29OINIWRptUUgeNoWo+afR/4ByF
+rfax0+T1v8T1f75EMs3ISkGo98Tbpq7uU0L3GaF3K9q+0NQXDMfyvcbcH7/
0ISDfCmuLIpvWdC7drO51X3ZMvfADPj5s4wQtan2AwrzeaEXdVvkRPQ/l4Kr
S/0ma6TcU2CRkDGxridKCrbHBb7EBKFgWpBjaK2OnJLecD/Uu9RdddIMA9oM
lybGcyGT5ZjTweT0m6vuxh2a5CrK0oTjg5w7RlXZJibWlBOKZ4kXVP6t2bhw
mXqeZVgFu8JJQKH3amcc0FF3m/qHSU1sA/hjIyU4KjGeUhYq1hPohCdkKvZR
h5AddixpgojAVvVgiwxbPWxTSxAiiHR8jQUpADA62YRdZQZsQuPjJrVxca7K
nVYfc6XC6sEeLgQpNbwA96U8gZeYpzcxmdignx6UYkcY/51EJvvszr37IOe4
/CRWHVgFRQkxpitVktYQdnrFweG+BJiIzIgbuGgtDGArsmC8WWdRmvuyCogP
rhQ4jz7g8So+60+Z2yJiqBpGjGeQKTiemGs55tOy5RBcyT/mSTzndrQEUxAr
emp1hoHtHHfrjs9aamrMZATrzKdxsNwrsD6sBx73FS5tPoe/WGZYLdWuGXRm
H6NiXylQLg6sEyltQmYpHhPAc2WGrwAlgAtyqRaUdihHGNwipwssaI2ktCJW
oNxPMLbNh8KXfywXGisVFWgeBXmdFqGUMMlzql2WZ3hXIg8g52oqmMZH3KbV
+wRzf7GoGleqxMx03MmAm/yMN8Y9sUWFKwhYqUl+avO9c6VqB8993L5yujxd
4H063W0fx2xqqeTt2dr1TdspeG0o+e+H1PWCXU6pLAlO5+FpS8ogPn+KVSJt
zQ1XYIROimGFDqlsyS4mEgA821WvfltGII3EA7Sjj9NlTJiy0V4T5+baVRvE
p4kA6UAtwGFLXUrvk5TOtthBJMv9hLiMUmzPzCyivGHizgVWd8ZddsJVh+Cw
5w/LOfUotySpXicrDzGItVJ+Y2HLHnPlOhySi20HmMA7w+WoCG7OFzM6hwN8
GOEBGY+Rvnq7N8B77+oL2VcNF6tZ2OUNG6EXgu6Vre9WFnByHIXAwxxoPCZi
+yOph3ITj7VeAVJROP1Tzuz9i3odmvEyw1MV1V5PY4OKKzfGUW2v12WR6Mq/
RnHTo4KC0+UojvJLgKNUM9V1TYWtkL2a0pbIQW8kR1kzpBGcdB/k9ypcLyXl
f1AEqdRVr+EnXBldK+RpJ8ZuZgTHzNfMaSB1a7AKsC//5KdMJY3Uf3AVdpT3
XFc45RjDuJATWZkERXwPFrEk8pcohPsKS6S+e8uUBlwQjaVOaGIbWKC4LjqI
ADBi6Hv+UA1kbLt49iiLo/aXXLVXWDM2Gb+wwL5y4C/4vgMsfq52cS5F2q/e
aNGMUX7kjJEs4Nb/UruuaDrQIECGlNkCmFNhc8cMgaT0tUixeJkVho7Tt7ew
Vhej67iwsosjJyus3WotmknkKkppVKP2XDWZAKUCvpXNmKhc9xwJTM6PexlS
LphxTkriEfa+Nv3OVf7JK4BrrmzVyQ12jxEz4BgHqasj5CsHoQDK1e7F2du8
5Ux2VzSL5s5lyFR4uBebO3HnJ1KPH9qGPKknuD24aV7+iFNfVSaWuGNduBB2
4zwoQoSMIDGuWj2myhm5aj0yd8Ajyip1wrAQi43muaJupZVz+k5vwv7Oe7Pa
I+N7Bx6PsO64P66Ch72iUrgumqhdqYs9w0oBMtt9gvPgyRPekM+pBK31Nti0
J1sGC+g+fRyuHMxFzg2AIEEL2pKEfyoQeBOzQLmRFFLvrlboAGtEvbFrXMKR
WIIOQzyhX6JJhcqtFHm2lh5UQBBxOhFK91vJvNa1mlMu/Fw6NVdb8qalXL98
shC5VDaLsPCjJX9q46kmZ+OvXh3qi2bPlYjBZwGTuxD3hQyekhuDjeSgHq6A
bWuNo4rjYut4h45P07a2O4Ivh8jY4cFZMSoDl0d0HpUO0JNfl7mrwoAnFB8G
q/fQo9r6JOAr5JEYxOKtAzPZ+l38BgNMhAahTcX8R/DrOpqA9UfairzFzIzI
GsPi9QDkHMT0jKu+BviAqS6NuNzWxMDpYFkOS8TV9ZI6F9SrvIjB1nlMM1/m
keoH6kST3psvlpwVQsuBvPIBh+IaZwWJWyASrr+Aa7Ocs1WN7IoJ31Jgke7B
IkWUuERGb2a9nK46AY2JeKcYBpovGA7wtXXZU3QeJR1b9TGVGrdIHUaupEdS
e+PGTK2e8BWZQMwutrhjl14I8gApoOx0W9c6cD70CObSsZxR8V28TWZXqSyc
pZqEMPod/BUq+ZYYqT4S8dZL4MS4ctM8MupG2/vO/MWOwveYINQ4NRtcCeSm
e9xVTi71oF9kxQLmvqYf8QHI6YxTcL8Jp2setusGlqqrd5JZR7N0rJgWbyyF
S7CcSDnqhB7ty3dvj45/4AjNWtWMcLn4ZuBu7JbycioW1ueWBCrkeFvblwLg
sq6TYILTeVHGjS/UI+/TsFo2IAzWbcFbXbK5nMQ0wL5pjOnZNXHuwH/BuCCN
bEtgWjUH7Xicyus1yjQohFnTMqHRF7nj4L5OWb+WVTN/Eargx48Ovu2pi8PT
vfM3wz3obW84+PH0SPUOwAgQWujTD6Cbvef7+/ugLAmFdDU0EV8ss6SPbx7q
M5T9q14fvK3kQ9af6rFpN9ze3pIGWKH2O7GRX+BbkL7zJtqL3h6Mo1+f7Y8P
06s3Bz8+/vnvvevRDxfLnw++Ld4cHB38/NPZ5fjXV8uff/rrvL29dbB3e+Nj
avxdoDle7Ld77YPqSVqy+BGr71Bc7Q2S/BqkZCXIh81oI9W/H4PeObKnuTmp
m0ktB+qf8majf+HqJmaWFpE1hqVAVHW583bFz26KGfYtG5VO7yvBbnXj1l5e
t4td8jpKhTjI+slXc+g+Ew0mFGhfuIKKFREghfiLUnYpv3yFzRTMIMWc14If
JXXEj9YzXKVeAoAyFQWPoRgXHWEMkTMG6rEyu9JkypUclnMqHZCsgvqcqFsj
MGNt7agG+2m+xPgzRfBZSnLurdSDwB5gLDQ+BBIn47jcZoHL4KUO009p3XL3
TgEwjx9KLw/Lb8nQ9XetkCE9halG9HYX9E9Ce4wXB/pA3I0ikjFtkEM6YQLG
0jK2soqUiF7iS3HA21wW9FBmY0gcIyCBKEIqgN0Hraq1WNBKyktoEF0jcU1v
H0heJu7NMHF4wsrXd7OkoNut5NXQgaSDcOL0yuOBzMcphr/ZRrjU+LYok4Gw
j8ZkwLjSVLlzaGRC1I8jrGpPesHmYmTf3xQGg51pBMoaI3Bcw5UrcVPlGI1a
T14tJrsjvv6zn5cvtetlghfejRV9MGRsOUfKSYODu6o6vpLTQzSQWyJA+8e+
jGxNGIALj8S+MF7oKFk3klAvr50pOVJYcExgdipZsyHpyR3D+NK/yJD6pMp1
TdoSYNfOY/BVgQMxLMWEUyAu2isogVAtDOMn6hFeqaZylxmC8oiysBNGZ7e+
rkEJl2rBKLeSZU+yumRBwOM+l+k2yuJKQ02Wj4fCg/Y7cBjMK0K5nl8aKf5M
nTAAsI7rkYq2wl25pRSnCtFbc5DuD8kAZhQT9b5JD4PX65TRFBW8KeaEkCUu
eAiGW0v3pZ5InV/qK0NetJk0+E5SGrvKEYQkGtxIhetdEAgOHWwj+4FQppe3
RaTapLSYuAAbb1pyuXfcpzFsHhCQllWn5Fnj9CKXf0bvkxrHaMAjGTQ7lWTj
1SwkG52gXQxSWjJJMsYT3rpzPdMx83ZVT5IKYGdAFhKRRzv/TbI8fOViUE48
VCPBySZHGrTH0qwbygmXEnJCl78Gqhdh7UDOyKnLgEV40sZH/yRVQwwBB0ab
FuguenDqIiKEHKdscaPRYUE4UByh0Eqxyy9lJd0+VuLKPdd3Ka2J9V1Yh63O
A5nh10plXPIO40TjaBH41d5oBfIDAGgzhOaMr2pMHdi2GJjsnQtcrr49viJx
LBW3R46gq9YV8V0lXPBAHQ/eDhpouuk9LLyRGe5hYsu35jrwiNEwB0TSVjS2
82SPA31H+2+fPpV2POXMjHJbd3VowqNt3plqqmQe7IOWrXodvOfL6o7mvUJ8
J9R4mQdBXDo9V+qtHKZMJNPW7duNYvcqRKpha8Nj6EiDH+0e7+HjcvGIr+K7
ce3VoW/7rEdtOYYqzrgkSBw8FhSWmNXXc0MpaY/l4VtLIhI44dteUORReUV+
FQpG/B7m8j4TsC1R+VmFsXTMQ1xQSCRZz/CAEUb49HuMRuJGLQBColSBi0tL
FjgakmEsENp9komJkXkwGok8pF3cEjO20+tE1ImASTUhXTgX/GeXmcOvSFNc
SA1fXGrjoCQ5JvyyUQnDgpF8Ra8wTPh1zPzeMnqPQxure7g1J+SXWiGdxGlu
X8P1Or02V1J4bYeJOXgrposFHllB2QccrOjeIeqjtyAiTnCHkV7RKqf4meUc
ZwzTeEnFRnnt8b3IeGpS6DVvB56vLgeBeLEfUi3NBZK7D0TL42SEyPjXKFly
GaysNebGsFge6Twaex6apTqWNwBVsNz2iyDvKuUYNGKS0qnwcbs7ADQqLwSQ
8FsFXtoFlxdcrNB0YnEgj3K+jZNwaB9xHj9IhomaLSOu+ZwmgTnkZjA3GHuI
cnHTojkKUXTzK+IBxtnhzV7WPW6pEQgJA+d+hXr0aoRw618CDBTMCW3rIFMI
BGzK+RJV2Kxxm/vXFa4RnD47x9JHWerBBDXnbAUWRKXMqIhW4CQTT7tb/wuD
NbwouYAAAA==

-->

</rfc>
