<?xml version="1.0" encoding="ascii"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.40 (Ruby 2.6.10) --> version='1.0' encoding='UTF-8'?>

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-avtcore-rtp-evc-07" number="9584" category="std" consensus="true" submissionType="IETF" obsoletes="" updates="" tocInclude="true" sortRefs="true" symRefs="true"> symRefs="true" version="3" xml:lang="en">

  <front>
    <title abbrev="RTP payload format Payload Format for EVC">RTP Payload Format for Essential Video Coding (EVC)</title>
    <seriesInfo name="RFC" value="9584"/>
    <author initials="S." surname="Zhao" fullname="Shuai Zhao">
      <organization>Intel</organization>
      <address>
        <postal>
          <street>2200 Mission College Blvd</street>
          <city>Santa Clara</city> Clara</city><region>California</region>
          <code>95054</code>
          <country>USA</country>
          <country>United States of America</country>
        </postal>
        <email>shuai.zhao@ieee.org</email>
      </address>
    </author>
    <author initials="S." surname="Wenger" fullname="Stephan Wenger">
      <organization>Tencent</organization>
      <address>
        <postal>
          <street>2747 Park Blvd</street>
          <city>Palo Alto</city> Alto</city><region>California</region>
          <code>94588</code>
          <country>USA</country>
          <country>United States of America</country>
        </postal>
        <email>stewe@stewe.org</email>
      </address>
    </author>
    <author initials="Y." surname="Lim" fullname="Youngkwon Lim">
      <organization>Samsung Electronics</organization>
      <address>
        <postal>
          <street>6625 Excellence Way</street>
          <city>Plano</city>
          <city>Plano</city><region>Texas</region>
          <code>75013</code>
          <country>USA</country>
          <country>United States of America</country>
        </postal>
        <email>yklwhite@gmail.com</email>
      </address>
    </author>

    <date year="2023" month="December" day="19"/>

    <area>ART</area> year="2024" month="June"/>

    <area>WIT</area>
    <workgroup>avtcore</workgroup>
    <keyword>Internet-Draft</keyword>

    <keyword>EVC</keyword>
    <keyword>ISO/IEC 23094-1</keyword>
    <keyword>Essential Video Coding</keyword>

    <abstract>

<?line 113?>
      <t>This document describes an RTP payload format for the Essential Video
      Coding (EVC) standard, published as ISO/IEC International Standard
      23094-1. EVC was developed by the Moving Picture Experts Group (MPEG). MPEG. The RTP payload format allows
      for the packetization of one or more Network Abstraction Layer (NAL)
      units in each RTP packet payload and the fragmentation of a NAL unit
      into multiple RTP packets. The payload format has broad applicability in
      videoconferencing, Internet video streaming, and high-bitrate
      entertainment-quality video, among other applications.</t>
    </abstract>
  </front>
  <middle>

<?line 117?>

<section anchor="introduction"><name>Introduction</name> anchor="introduction">
      <name>Introduction</name>
      <t>The Essential Video Coding <xref target="EVC"/> standard,  which is formally designated as ISO/IEC International Standard 23094-1 <xref target="ISO23094-1"/> has been target="EVC"/>, was published in 2020.  One goal of MPEG MPEG's goals is to keep <xref target="EVC"/>&#39;s EVC's Baseline profile essentially royalty-free by using technologies published more than 20 years ago or otherwise known to be available for use without a requirement for paying royalties, whereas more advanced profiles follow a reasonable and non-discriminatory licensing terms policy. Both the Baseline profile and higher profiles of EVC <xref target="EVC"/> are reported to provide coding efficiency gains over High Efficiency Video Coding <xref target="HEVC"/> and Advanced Video Coding <xref target="AVC"/> under certain configurations.</t>
      <t>This document describes an RTP payload format for EVC. It shares its basic design with the NAL unit-based RTP payload formats of H.264 Video Coding <xref target="RFC6184"/>, Scalable Video Coding (SVC) <xref target="RFC6190"/>, High Efficiency Video Coding (HEVC) <xref target="RFC7798"/>, and Versatile Video Coding (VVC)<xref (VVC) <xref target="RFC9328"/>.  With respect to design philosophy, security, congestion control, and overall implementation complexity, it has similar properties to those earlier payload format specifications.  This is a conscious choice, as at least the RTP Payload Format for H.264 video as described in <xref target="RFC6184"/> is widely deployed and generally known in the relevant implementer communities.  Certain mechanisms known from described in <xref target="RFC6190"/> were incorporated incorporated, as EVC supports temporal scalability. EVC currently does not offer higher forms of scalability.</t>
      <section anchor="overview-of-the-evc-codec"><name>Overview anchor="overview-of-the-evc-codec">
        <name>Overview of the EVC Codec</name>

<t><xref
        <t>The codings described in <xref target="EVC"/>, <xref target="AVC"/>, <xref target="HEVC"/> target="HEVC"/>, and <xref target="VVC"/> share a similar hybrid video codec design.  In this document, we provide a very brief overview of those features of EVC that are, in some form, addressed by the payload format specified herein.  Implementers have to read, understand, and apply the ISO/IEC standard pertaining to EVC <xref target="EVC"/> to arrive at interoperable, well-performing implementations. The EVC standard has a Baseline profile and a Main profile, the latter being a superset of the Baseline profile but including more advanced features.  EVC also includes still image variants of both Baseline and Main profiles, in each of which the bitstream is restricted to a single IDR picture. EVC facilitates certain walled-garden walled garden implementations under commercial constraints imposed by intellectual property rights by including syntax elements that allow encoders to mark a bitstream as to what of the many independent coding tools are exercised in the bitstream, in a spirit similar to the general_constraint_flags general_constraint_info of <xref target="VVC"/>.</t>
        <t>Conceptually, all EVC, AVC, HEVC HEVC, and VVC include a Video Coding Layer (VCL); (VCL), a term that is often used to refer to the coding-tool features, and a Network Abstraction Layer (NAL), which usually refers to the systems and transport interface aspects of the codecs.</t>
        <section anchor="coding-tool-features-informative"><name>Coding-Tool anchor="coding-tool-features-informative">
          <name>Coding-Tool Features (informative)</name>

<t>Coding (Informative)</name>

       <dl newline="true">
          <dt>Coding blocks and transform structure</t>

<t>EVC structure</dt>
          <dd><t>EVC uses a traditional block-based coding structure, which
          divides the encoded image into blocks of up to 64x64 luma samples
          for the Baseline profile and 128x128 luma samples for the Main
          profile that can be recursively divided into smaller blocks.  The baseline
          Baseline profiles utilize an HEVC-like quad-tree blocks quad-tree-blocks partitioning
          that allows to divide a block to be divided horizontally and vertically onto into
          four smaller square blocks. The Main profile adds two advanced
          coding structure tools: 1) Binary Ternary Tree (BTT) partitioning
          that allows non-square coding units; units and 2) Split Unit Coding Order
          segmentation that changes the processing order of the blocks from
          traditional left-to-right and top-to-bottom scanning order
          processing to an alternative right-to-left and bottom-to-top
          scanning order. In the Main profile, the picture can be divided into
          slices and tiles, which can be independently encoded and/or decoded
          in parallel.</t>
          <t>EVC also uses a traditional video codecs prediction model assuming two general types of predictions: Intra (spatial) and Inter (temporal) predictions. A residue block is calculated by subtracting predicted data from the original (encoded) one. The Baseline profile allows only discrete cosine transform (DCT-2) and scalar quantization to transform and quantize residue data, wherein the Main profile additionally has options to use discrete sine transform (DST-7) and another type of discrete cosine transform (DCT-8). In addition, for the Main profile, Improved Quantization and Transform (IQT) uses a different mapping/clipping mapping or clipping function for quantization. An inverse zig-zag scanning order is used for coefficient coding. Advanced Coefficient Coding (ADCC) in the Main profile can code coefficient values more efficiently, for example, indicated by the last non-zero coefficient. The Baseline profile uses a straightforward run-length encoding (RLE) based RLE-based approach to encode the quantized coefficients.</t>

<t>Entropy coding</t>

<t>EVC coefficients.</t></dd>
          <dt>Entropy coding</dt>
          <dd><t>EVC uses a similar binary arithmetic coding mechanism as HEVC CABAC (context adaptive binary arithmetic coding) and VVC. The mechanism includes a binarization step and a probability update defined by a lookup table. In the Main profile, the derivation process of syntax elements based on adjacent blocks makes the context modeling and initialization process more efficient.</t>

<t>In-loop filtering</t>

<t>The
</dd>

          <dt>In-loop filtering</dt>
          <dd><t>The Baseline profile of EVC uses the deblocking filter defined in H.263 Annex J. J <xref target="VIDEO-CODING" format="default"/>. In the Main profile, an Advanced Deblocking Filter (ADDB) can be used as an alternative, which can further reduce undesirable compression artifacts. The Main profile also defines two additional in-loop filters that can be used to improve the quality of decoded pictures before output and/or for inter-prediction. Inter prediction. A Hadamard Transform Domain Filter (HTDF) is applied to the luma samples before deblocking, and a lookup  table is used to determine four adjacent samples for filtering. An adaptive Loop Filter (ALF) allows to send signals of up to 25 different filters to be sent for the luma components, and components; the best filter can be selected through the classification process for each 4x4 block. Similarly to VVC, the filter parameters of ALF are signaled in the Adaptation Parameter Set (APS).</t>

<t>Inter-prediction</t>

<t>The (APS).</t></dd>

          <dt>Inter prediction</dt>
          <dd><t>The basis of EVC&#39;s inter-prediction EVC's Inter prediction is motion compensation using interpolation filters with a quarter sample resolution. In the Baseline profile, a motion vector is transmitted using one of three spatially neighboring motion vectors and a temporally collocated motion vector as a predictor. A motion vector difference may be signaled relative to the selected predictor, but there is a case where no motion vector difference is signaled, and there is no remaining data in the block. This mode is called a skip "skip" mode. The Main profile includes six additional tools to provide improved inter-prediction. Inter prediction. With Advanced Motion Vectors Prediction (ADMVP), adjacent blocks can be conceptually merged to indicate that they use the same motion, but more advanced schemes can also be used to create predictions from the basic model list of candidate predictors. The Merge with Motion Vector Difference (MMVD) tool uses a process similar to the concept of merging neighboring blocks but also allows the use of expressions that include a starting point, motion amplitude, and direction of motion to send a motion vector signal. Using Advanced Motion Vector Prediction (AMVP), candidate motion vector predictions for the block can be derived from its neighboring blocks in the same picture and collocated blocks in the reference picture. The Adaptive Motion Vector Resolution (AMVR) tool provides a way to reduce the accuracy of a motion vector from a quarter sample to half sample, full sample, double sample, or quad sample, which provides an efficiency advantage, such as when sending large motion vector differences. The Main profile also includes the Decoder-side Motion Vector Refinement (DMVR), which uses a bilateral template matching process to refine the motion vectors without additional signaling.</t>

<t>Intra signaling.</t></dd>

          <dt>Intra prediction and intra-coding</t>

<t>Intra intra coding</dt>
          <dd><t>Intra prediction in EVC is performed on adjacent samples of coding units in a partitioned structure. For the Baseline profile, when all coding units are square, there are five different prediction modes: DC (mean value of the neighborhood), horizontal, vertical, and two different diagonal directions. In the Main profile, intra prediction can be applied to any rectangular coding unit, and 28 additional direction modes are available in the so-called Enhanced Intra Prediction Directions (EIPD). (EIPDs). In the Main profile, an encoder can also use Intra Block Copy (IBC), where previously decoded sample blocks of the same picture are used as a predictor. A displacement vector in integer sample precision is signaled to indicate where the prediction block in the current picture is used for this mode.</t>

<t>Reference mode.</t></dd>

          <dt>Reference frames management</t>

<t>In management</dt>
          <dd><t>In EVC, decoded pictures can be stored in a decoded picture buffer (DPB) for predicting pictures that follow them in the decoding order. In the Baseline profile, the management of the DPB (i.e., the process of adding and deleting reference pictures) is controlled by a straightforward AVC-like sliding window approach with very few parameters from the SPS. sequence parameter set (SPS). For the Main profile, DPB management can be handled much more flexibly using explicitly signaled reference Reference Picture Lists (RPL) (RPLs) in the SPS or slice level.</t> level.</t></dd>
	</dl>
        </section>
        <section anchor="systems-and-transport-interfaces"><name>Systems anchor="systems-and-transport-interfaces">
          <name>Systems and Transport Interfaces</name>
          <t>EVC inherits the basic systems and transport interface designs from AVC and HEVC. These include the NAL-unit-based syntax, hierarchical syntax and data unit structure, and Supplemental Enhancement Information (SEI) message mechanism. The hierarchical syntax and data unit structure consists of a sequence-level parameter set (SPS), (i.e., SPS), two picture-level parameter sets (PPS (i.e., PPS and APS, each of which can apply to one or more pictures), slice-level header parameters, and lower-level parameters.</t>
          <t>A number of key components that influenced the Network Abstraction Layer NAL design of EVC as well as this document, document are described below:</t>

<t>Sequence

          <dl newline="true">
	    <dt>Sequence parameter set</t>

<ul empty="true"><li>
  <t>The set</dt>
              <dd><t>The Sequence Parameter Set (SPS) contains syntax elements pertaining to a Coded Video Sequence (CVS), which is a group of pictures, starting with a random access point picture and followed by zero or more pictures that may depend on each other and the random access point picture. In MPEG-2, the equivalent of a CVS is a Group of Pictures (GOP), which generally started starts with an I frame and is followed by P and B frames. While more complex in its options of random access points, EVC retains this basic concept. In many TV-like applications, a CVS contains a few hundred milliseconds to a few seconds of video. In video conferencing (without switching MCUs Multipoint Control Units (MCUs) involved), a CVS can be as long in duration as the whole session.</t>
</li></ul>

<t>Picture session.</t></dd>
              <dt>Picture and adaptation parameter set</t>

<ul empty="true"><li>
  <t>The set</dt>
              <dd><t>The Picture Parameter Set (PPS) and the Adaptation Parameter Set (PPS and APS, respectively) (APS) carry information pertaining to a single picture. The PPS contains information that is likely to stay constant from picture to picture, at least for pictures of a certain type type; whereas the APS contains information, such as adaptive loop filter coefficients, that are likely to change from picture to picture.</t>
</li></ul>

<t>Profile, picture.</t></dd>
	      <dt>Profile, level, and toolsets</t>

<ul empty="true"><li>
  <t>Profiles toolsets</dt>
              <dd><t>Profiles and levels follow the same design considerations known from AVC, HEVC, and video codecs as old as MPEG-1 Video. The profile defines a set of tools (not to confuse be confused with the &quot;toolset&quot; "toolset" discussed below) that a decoder compliant with this profile has to support. In EVC, profiles are defined in Annex A. A of <xref target="EVC"/>.  Formally, they are defined as a set of constraints that a bitstream needs to conform to. In EVC, the Baseline profile is much more severely constraint constrained than the Main profile, reducing implementation complexity. Levels relate to bitstream complexity in dimensions such as maximum sample decoding rate, maximum picture size, and similar parameters directly related to computational complexity and/or memory demands.</t>
</li></ul>
<t>Profiles and levels are signaled in the highest parameter set available, the SPS.</t>

<ul empty="true"><li>
  <t>EVC contains another mechanism related to the use of coding tools, known as the toolset syntax element. This elements. These syntax element, elements, toolset_idc_h and toolset_idc_l located (located in the SPS, is a bitmask SPS), are bitmasks that allows allow encoders to indicate which coding tools they are using within the menu of profiles offered by the profile that is also signaled. No decoder conformance point is associated with the toolset, but a bitstream that was using a coding tool that is indicated as not being used in the toolset syntax element would be non-compliant. While MPEG specifically rules out the use of the toolset syntax element as a conformance point, walled garden implementations could do so without incurring the interoperability problems MPEG fears and create bitstreams and decoders that do not support one or more given tools. That, in turn, may be useful to mitigate certain intellectual property-related risks.</t>
</li></ul>

<t>Bitstream </dd>

          <dt>Bitstream and elementary stream</t>

<ul empty="true"><li>
  <t>Above stream</dt>
          <dd><t>Above the Coded Video Sequence (CVS), EVC defines a video bitstream that can be used as an elementary stream in the MPEG systems context. For this document, the video bitstream syntax level is not relevant.</t>
</li></ul>

<t>Random relevant.</t></dd>
          <dt>Random access support</t>

<ul empty="true"><li>
  <t>EVC support</dt>
          <dd><t>EVC supports random access mechanisms based on IDR and CRA clean random access units.</t>
</li></ul>

<t>Temporal (CRA) access units.</t></dd>
          <dt>Temporal scalability support</t>

<ul empty="true"><li>
  <t>EVC support</dt>
          <dd><t>EVC supports temporal scalability through the generalized reference picture selection approach known since AVC/SVC. Up to six temporal layers are supported. The temporal layer is signaled in the NAL unit header (which co-serves as the payload header in this document), in the nuh_temporal_id field.</t>
</li></ul>

<t>Reference field.</t></dd>

          <dt>Reference picture management</t>

<ul empty="true"><li>
  <t>EVC&#39;s management</dt>
          <dd><t>EVC's reference picture management is POC-based (Picture Order Count), POC-based, similar to HEVC. In the Main profile, substantially all reference picture list manipulations available in HEVC are available, specified, including explicit transmissions/updates transmissions or updates of reference picture lists, although lists. Although for reference pictures management purposes, EVC uses a modern VVC-like RPL approach, which is conceptually simpler than the HEVC one. In the Baseline profile, reference picture management is more restricted, allowing for a comparatively simple group of picture structures only.</t>
</li></ul>

<t>SEI Message</t>

<ul empty="true"><li>
  <t>EVC only.</t></dd>
          <dt>SEI Message</dt>
          <dd><t>EVC inherits many of HEVC&#39;s HEVC's SEI Messages, messages, occasionally with syntax and/or semantics changes, making them applicable to EVC.
In addition, some of the codec-agnostic SEI Messages messages of the VSEI specification <xref target="VSEI"/> are also mapped.</t>
</li></ul> mapped.</t></dd>
            </dl>
        </section>
        <section anchor="parallel-processing-support-informative"><name>Parallel anchor="parallel-processing-support-informative">
          <name>Parallel Processing Support (informative)</name>

<ul empty="true"><li>
  <t>EVC&#39;s (Informative)</name>

          <t>EVC's Baseline profile includes no tools specifically addressing parallel processing
          parallel-processing support. The Main profile includes independently
          decodable slices for parallel processing.  The slices are defined as
          any rectangular region within a picture and picture. They can be encoded to have no
          coding dependencies with other slices in from the same previous picture but
          not with other slices from in the previous same picture. No specific support for
          parallel processing is specified in this RTP payload format.</t>
</li></ul>

        </section>
        <section anchor="NALUnitHeader"><name>NAL anchor="NALUnitHeader">
          <name>NAL Unit Header</name>
          <t>EVC maintains the NAL unit concept of <xref target="VVC"/> with different parameter options. EVC also uses a two-byte NAL unit header, as shown in <xref target="evc-nuh"/>.  The payload of a NAL unit refers to the NAL unit excluding the NAL unit header.</t>
          <figure anchor="evc-nuh"><artwork><![CDATA[ anchor="evc-nuh">
	    <name>The Structure of the EVC NAL Unit Header</name>
            <artwork><![CDATA[
                     0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                    |F|   Type    | TID | Reserve |E|
                    +-------------+-----------------+

                  The Structure of the EVC NAL Unit Header
]]></artwork></figure>
                    +-------------+-----------------+]]></artwork>
          </figure>
          <t>The semantics of the fields in the NAL unit header are as specified in EVC and described briefly below for convenience. In addition to the name and size of each field, the corresponding syntax element name in EVC is also provided.</t>

<t>F: 1

	  <dl>
            <dt>F:</dt>
	    <dd><t>1 bit</t>

<ul empty="true"><li>
  <t>forbidden_zero_bit.  Required
	    <dl>
            <dt>forbidden_zero_bit:</dt>
	    <dd>Required to be zero in EVC. Note that the
            inclusion of this bit in the NAL unit header was included to
            enable transport of EVC video over MPEG-2 transport systems
            (avoidance of start code emulations) <xref target="MPEG2S"/>. In
            this document, the value 1 may be used to indicate a syntax
            violation, e.g., for a NAL unit resulting from aggregating a
            number of fragmented units of a NAL unit but missing the last
            fragment, as described in <xref target="funits"/>.</t>
</li></ul>

<t>Type: 6 target="funits"/>.</dd></dl>
	    </dd>
            <dt>Type:</dt>
	    <dd>
	      <t>6 bits</t>

<ul empty="true"><li>
  <t>nal_unit_type_plus1. This
	      <dl>
	      <dt>nal_unit_type_plus1:</dt>
	      <dd><t>This field allows the NAL Unit Type to
	      be computed. The NAL Unit Type (NalUnitType) is equal to the
	      value found in this field, minus 1; in other words:</t>
</li></ul>

<ul empty="true"><li>
  <ul empty="true"><li>
	      <t>NalUnitType = nal_unit_type_plus1 - 1.</t>
  </li></ul>
</li></ul>

<ul empty="true"><li>
	      <t>The NAL unit type is detailed in Table 4 of <xref
	      target="EVC"/>. If the value of NalUnitType is less than or
	      equal to 23, the NAL unit is a VCL NAL unit.  Otherwise, the NAL
	      unit is a non-VCL NAL unit.  For a reference of all currently
	      defined NAL unit types and their semantics, please refer to
	      Section 7.4.2.2 in of <xref target="EVC"/>. Note that
	      nal_unit_type_plus1 MUST NOT <bcp14>MUST NOT</bcp14> be zero.</t>
</li></ul>

<t>TID: 3 zero.</t></dd></dl>
            </dd>
            <dt>TID:</dt>
	    <dd><t>3 bits</t>

<ul empty="true"><li>
  <t>nuh_temporal_id.  This
	    <dl>
            <dt>nuh_temporal_id:</dt>
	    <dd>This field specifies the temporal identifier
            of the NAL unit. The value of TemporalId is equal to
            TID. TemporalId shall be equal to 0 if it is an IDR NAL unit type
            (NAL unit type 1).</t>
</li></ul>

<t>Reserve: 5 1).</dd></dl>
            </dd>
            <dt>Reserve:</dt>
	    <dd><t>5 bits</t>

<ul empty="true"><li>
  <t>nuh_reserved_zero_5bits. This
	    <dl>
	    <dt>nuh_reserved_zero_5bits:</dt>
	    <dd>This field shall be equal to the version of the EVC
	    standard. Values of nuh_reserved_zero_5bits greater than 0 are
	    reserved for future use by ISO/IEC. Decoders conforming to a
	    profile specified in <xref target="EVC"/>&#39;s Annex A of <xref target="EVC"/> shall ignore
	    (i.e., remove from the bitstream and discard) all NAL units with
	    values of nuh_reserved_zero_5bits greater than 0.</t>
</li></ul>

<t>E: 1 0.</dd></dl>
            </dd>
            <dt>E:</dt>
	    <dd><t>1 bit</t>

<ul empty="true"><li>
  <t>nuh_extension_flag. This
	    <dl>
	    <dt>nuh_extension_flag:</dt>
	    <dd>This field shall be equal to the version of
	    the EVC standard. The value of nuh_extension_flag equal to 1 is
	    reserved for future use by ISO/IEC. Decoders conforming to a
	    profile specified in <xref target="EVC"/>&#39;s Annex A of <xref target="EVC"/> shall ignore
	    (i.e., remove from the bitstream and discard) all NAL units with
	    values of nuh_extension_flag equal to 1.</t>
</li></ul> 1.</dd></dl>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="overview-of-the-payload-format"><name>Overview anchor="overview-of-the-payload-format">
        <name>Overview of the Payload Format</name>
        <t>This payload format defines the following processes required for transport of EVC-coded data over RTP <xref target="RFC3550"/>:</t>

<t><list style="symbols">
  <t>usage
        <ul spacing="normal">
          <li>usage of RTP header with this payload format</t>
  <t>packetization format</li>
          <li>packetization of EVC-coded NAL units into RTP packets using
          three types of payload structures: a single NAL unit, aggregation,
          and fragment unit</t>
  <t>transmission unit</li>
          <li>transmission of EVC NAL units of the same bitstream within a
          single RTP stream.</t>
  <t>media stream</li>
          <li>usage of media type parameters to be used with the Session
          Description Protocol (SDP) <xref target="RFC8866"/></t>
  <t>usage target="RFC8866"/></li>
          <li>usage of RTCP feedback messages</t>
</list></t> messages</li>
        </ul>
      </section>
    </section>
    <section anchor="conventions"><name>Conventions</name>

<t>The anchor="conventions">
      <name>Conventions</name>
        <t>
    The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL
NOT&quot;, &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;NOT RECOMMENDED&quot;,
&quot;MAY&quot;, "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
    "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and &quot;OPTIONAL&quot; "<bcp14>OPTIONAL</bcp14>" in this document are to be
    interpreted as described in BCP 14 BCP&nbsp;14 <xref target="RFC2119"/> <xref
    target="RFC8174"/> when, and only when, they appear in all capitals, as
    shown above.</t> here.
        </t>

    </section>
    <section anchor="definitionsandabbr"><name>Definitions anchor="definitionsandabbr">
      <name>Definitions and Abbreviations</name>
      <section anchor="definitions"><name>Definitions</name> anchor="definitions">
        <name>Definitions</name>
        <t>This document uses the terms and definitions of EVC.  <xref target="definitionforevc"/>
lists relevant definitions from <xref target="EVC"/> for convenience.  <xref target="def"/>
provides definitions specific to this document.</t>
        <section anchor="definitionforevc"><name>Definitions anchor="definitionforevc">
          <name>Definitions from the EVC Standard</name>

<t>Access Unit: A
	  <dl spacing="normal" newline="true">
            <dt>Access Unit (AU):</dt>
	    <dd>A set of NAL units that are associated with each other
	    according to a specified classification rule, are consecutive in
	    decoding order, and contain exactly one coded picture.</t>

<t>Adaptation parameter set (APS): A picture.</dd>
            <dt>Adaptation Parameter Set (APS):</dt>
	    <dd>A syntax structure containing syntax elements that apply to
	    zero or more slices as determined by zero or more syntax elements
	    found in slice headers.</t>

<t>Bitstream: A headers.</dd>
            <dt>Bitstream:</dt>
	    <dd>A sequence of bits, in the form of a NAL unit stream or a byte
	    stream, that forms the representation of coded pictures and
	    associated data forming one or more coded video sequences (CVSs).</t>

<t>Coded Picture: A CVSs.</dd>
            <dt>Coded Picture:</dt>
	    <dd>A coded representation of a picture containing all CTUs of the picture.</t>

<t>Coded
	    picture.</dd>
            <dt>Coded Video Sequence (CVS): A (CVS):</dt>
	    <dd>A sequence of access units that consists, in decoding order,
	    of an IDR access unit, followed by zero or more access units that
	    are not IDR access units, including all subsequent access units up
	    to but not including any subsequent access unit that is an IDR
	    access unit.</t>

<t>Coding unit.</dd>
            <dt>Coding Tree Block (CTB): An (CTB):</dt>
	    <dd>An NxN block of samples for some value of N such that the
	    division of a component into CTBs is a partitioning.</t>

<t>Coding partitioning.</dd>
            <dt>Coding Tree Unit (CTU): A (CTU):</dt>

	    <dd>A CTB of luma samples, two corresponding CTBs of chroma
	    samples of a picture that has three sample arrays, or a CTB of
	    samples of a monochrome picture or a picture that is coded using
	    three separate colour color planes and syntax structures used to code
	    the samples.</t>

<t>Decoded Picture: A samples.</dd>
            <dt>Decoded Picture:</dt>
	    <dd>A decoded picture is derived by decoding a coded picture.</t>

<t>Decoded picture.</dd>
            <dt>Decoded Picture Buffer (DPB): A (DPB):</dt>
	    <dd>A buffer holding decoded pictures for reference, output
	    reordering, or output delay specified for the hypothetical
	    reference decoder in Annex C of the <xref target="EVC"/> standard.</t>

<t>Dynamic
	    standard.</dd>
            <dt>Dynamic Range Adjustment (DRA): A (DRA):</dt>
	    <dd>A mapping process that is applied to the decoded picture prior to
	    cropping and output as part of the decoding process and process; it is
	    controlled by parameters conveyed in an Adaptation Parameter Set (APS).</t>

<t>Hypothetical
	    (APS).</dd>
            <dt>Hypothetical Reference Decoder (HRD): A (HRD):</dt>
	    <dd>A hypothetical decoder model that specifies constraints on the
	    variability of conforming NAL unit streams or conforming byte
	    streams that an encoding process may produce.</t>

<t>IDR access unit: produce.</dd>
            <dt>IDR Access Unit:</dt>
	    <dd>An access unit in which the coded picture is an IDR picture.</t>

<t>IDR picture: picture.</dd>
            <dt>IDR Picture:</dt>
	    <dd>The coded picture for which each VCL NAL unit has NalUnitType equal to IDR_NUT.</t>

<t>Level: A IDR_NUT.</dd>
            <dt>Level:</dt>
	    <dd>A defined set of constraints on the values that may be taken
	    by the syntax elements and variables of this document, or the
	    value of a transform coefficient prior to scaling.</t>

<t>Network scaling.</dd>
            <dt>Network Abstraction Layer (NAL) unit: A Unit:</dt>
	    <dd>A syntax structure containing an indication of the type of
	    data to follow and bytes containing that data in the form of an
	    RBSP interspersed as necessary.</t>

<t>Network necessary.</dd>
            <dt>Network Abstraction Layer (NAL) Unit Stream: A Stream:</dt>
	    <dd>A sequence of NAL units.</t>

<t>Non-IDR Picture: A units.</dd>
            <dt>Non-IDR Picture:</dt>
	    <dd>A coded picture that is not an IDR picture.</t>

<t>Non-VCL picture.</dd>
            <dt>Non-VCL NAL Unit: A Unit:</dt>
	    <dd>A NAL unit that is not a VCL NAL unit.</t>

<t>Picture unit.</dd>
            <dt>Picture Parameter Set (PPS): A (PPS):</dt>
	    <dd>A syntax structure containing syntax elements that apply to
	    zero or more entire coded pictures as determined by a syntax
	    element found in each slice header.</t>

<t>Picture header.</dd>
            <dt>Picture Order Count (POC): A (POC):</dt>
	    <dd>A variable that is associated with each picture, uniquely
	    identifies the associated picture among all pictures in the CVS, and, when
	    and (when the associated picture is to be output from the decoded picture buffer, DPB) indicates the position of the associated picture
	    in output order relative to the output order positions of the
	    other pictures in the same CVS that are to be output from the decoded picture buffer.</t>

<t>Raw
	    DPB.</dd>
            <dt>Raw Byte Sequence Payload (RBSP): A (RBSP):</dt>
	    <dd>A syntax structure containing an integer number of bytes that
	    is encapsulated in a NAL unit and that is either empty or has the
	    form of a string of data bits containing syntax elements followed
	    by an RBSP stop bit and zero or more subsequent bits equal to 0.</t>

<t>Sequence
	    0.</dd>
            <dt>Sequence Parameter Set (SPS): A (SPS):</dt>
	    <dd>A syntax structure containing syntax elements that apply to
	    zero or more entire CVSs as determined by the content of a syntax
	    element found in the PPS referred to by a syntax element found in
	    each slice header.</t>

<t>Slice: header.</dd>
            <dt>Slice:</dt>
	    <dd>An integer number of tiles of a picture in the tile scan of
	    the picture and that are picture, exclusively contained in a single NAL unit.</t>

<t>Tile: unit.</dd>
            <dt>Tile:</dt>
	    <dd>A rectangular region of CTUs within a particular tile column and
	    a particular tile row in a picture.</t>

<t>Tile column: picture.</dd>
            <dt>Tile Column:</dt>
	    <dd>A rectangular region of CTUs having a height equal to the height
	    of the picture and width specified by syntax elements in the PPS.</t>

<t>Tile row: A
	    PPS.</dd>
            <dt>Tile Row:</dt>
	    <dd>A rectangular region of CTUs having a height specified by
	    syntax elements in the PPS and a width equal to the width of the picture.</t>

<t>Tile scan: A
	    picture.</dd>
            <dt>Tile Scan:</dt>
	    <dd>A specific sequential ordering of CTUs partitioning a picture
	    in which the CTUs are ordered consecutively in CTU raster scan in
	    a tile tile, whereas tiles in a picture are ordered consecutively in a
	    raster scan of the tiles of the picture.</t>

<t>Video coding layer picture.</dd>
            <dt>Video Coding Layer (VCL) NAL unit: A Unit:</dt>
	    <dd>A collective term for coded slice NAL units and the subset of
	    NAL units that have reserved values of NalUnitType that are
	    classified as VCL NAL units in this document.</t> document.</dd>
	  </dl>
        </section>
        <section anchor="def"><name>Definitions anchor="def">
          <name>Definitions Specific to This Document</name>

<t>Media-Aware
	  <dl newline="true" spacing="normal">
            <dt>Media-Aware Network Element (MANE): A (MANE):</dt><dd><t>A network
            element, such as a middlebox, selective forwarding unit, or
            application-layer gateway gateway, that is capable of parsing certain
            aspects of the RTP payload headers or the RTP payload and reacting
            to their contents.</t>

<ul empty="true"><li>
  <t>Informative
	    <aside><t>Informative note: The concept of a MANE goes beyond normal
	    routers or gateways in that a MANE has to be aware of the
	    signaling (e.g., to learn about the payload type mappings of the
	    media streams), and in that it has to be trusted when working with
	    Secure RTP (SRTP).  The advantage of using MANEs is that they
	    allow packets to be dropped according to the needs of the media
	    coding.  For example, if a MANE has to drop packets due to
	    congestion on a certain link, it can identify and remove those
	    packets whose elimination produces the least adverse effect on the
	    user experience.  After dropping packets, MANEs must rewrite RTCP
	    packets to match the changes to the RTP stream, as specified in Section 7 of
	    <xref target="RFC3550"/>.</t>
</li></ul>

<t>NAL target="RFC3550" section="7" sectionFormat="of"/>.</t></aside>
	  </dd>
	  <dt>NAL unit decoding order: A order:</dt><dd>A NAL unit order that conforms
	  to the constraints on NAL unit order given in Section 7.4.2.3 in of
	  <xref target="EVC"/>, follow target="EVC"/> and follows the order of NAL units in the bitstream.</t>

<t>NALU-time: The
	  bitstream.</dd>
          <dt>NALU-time:</dt><dd>The value that the RTP timestamp would have
          if the NAL unit would be transported in its own RTP packet.</t>

<t>NAL packet.</dd>
          <dt>NAL unit output order: A order:</dt><dd>A NAL unit order in which NAL
          units of different access units are in the output order of the
          decoded pictures corresponding to the access units, as specified in
          <xref target="EVC"/>, and in which NAL units within an access unit
          are in their decoding order.</t>

<t>RTP stream: See order.</dd>
          <dt>RTP stream:</dt><dd>See <xref target="RFC7656"/>.  Within the
          scope of this document, one RTP stream is utilized to transport a an
          EVC bitstream, which may contain one or more temporal sub-layers.</t>

<t>Transmission order: The
          sub-layers.</dd>
          <dt>Transmission order:</dt><dd>The order of packets in ascending
          RTP sequence number order (in modulo arithmetic).  Within an aggregation packet,
          Aggregation Packet (AP), the NAL unit transmission order is the same as
          the order of appearance of NAL units in the packet.</t> packet.</dd>
	  </dl>
        </section>
      </section>
      <section anchor="abbreviations"><name>Abbreviations</name>

<t>AU &#160;&#160;&#160;&#160;&#160;&#160;&#160; Access Unit</t>

<t>AP &#160;&#160;&#160;&#160;&#160;&#160;&#160; Aggregation Packet</t>

<t>APS &#160;&#160;&#160;&#160;&#160;&#160; Adaptation anchor="abbreviations">
        <name>Abbreviations</name>
	<dl newline="false" spacing="normal" indent="9">
          <dt>AU</dt>
          <dd>Access Unit</dd>
          <dt>AP</dt>
	  <dd>Aggregation Packet</dd>
          <dt>APS</dt>
	  <dd>Adaptation Parameter Set</t>

<t>ATS &#160;&#160;&#160;&#160;&#160;&#160; Adaptive Set</dd>
          <dt>ATS</dt>
	  <dd>Adaptive Transform Selection</t>

<t>B &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Bi-predictive</t>

<t>CBR &#160;&#160;&#160;&#160;&#160;&#160; Constant Selection</dd>
          <dt>B</dt>
	  <dd>Bi-predictive</dd>
          <dt>CBR</dt>
	  <dd>Constant Bit Rate</t>

<t>CPB  &#160;&#160;&#160;&#160;&#160;&#160; Coded Rate</dd>
          <dt>CPB</dt>
	  <dd>Coded Picture Buffer</t>

<t>CTB &#160;&#160;&#160;&#160;&#160;&#160; Coding Buffer</dd>
          <dt>CTB</dt>
	  <dd>Coding Tree Block</t>

<t>CTU &#160;&#160;&#160;&#160;&#160;&#160; Coding Block</dd>
          <dt>CTU</dt>
	  <dd>Coding Tree Unit</t>

<t>CVS &#160;&#160;&#160;&#160;&#160;&#160; Coded Unit</dd>
          <dt>CVS</dt>
	  <dd>Coded Video Sequence</t>

<t>DPB &#160;&#160;&#160;&#160;&#160;&#160; Decoded Sequence</dd>
          <dt>DPB</dt>
	  <dd>Decoded Picture Buffer</t>

<t>HRD &#160;&#160;&#160;&#160;&#160;&#160; Hypothetical Buffer</dd>
          <dt>HRD</dt>
	  <dd>Hypothetical Reference Decoder</t>

<t>HSS &#160;&#160;&#160;&#160;&#160;&#160; Hypothetical Decoder</dd>
          <dt>HSS</dt>
	  <dd>Hypothetical Stream Scheduler</t>

<t>I &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Intra</t>

<t>IDR &#160;&#160;&#160;&#160;&#160;&#160; Instantaneous Scheduler</dd>
          <dt>I</dt>
	  <dd>Intra</dd>
          <dt>IDR</dt>
	  <dd>Instantaneous Decoding Refresh</t>

<t>LSB &#160;&#160;&#160;&#160;&#160;&#160; Least Refresh</dd>
          <dt>LSB</dt>
	  <dd>Least Significant Bit</t>

<t>LTRP &#160;&#160;&#160;&#160;&#160; Long-Term Bit</dd>
          <dt>LTRP</dt>
	  <dd>Long-Term Reference Picture</t>

<t>MMVD &#160;&#160;&#160;&#160;&#160; Merge Picture</dd>
          <dt>MMVD</dt>
	  <dd>Merge with Motion Vector Difference</t>

<t>MSB &#160;&#160;&#160;&#160;&#160;&#160; Most Difference</dd>
          <dt>MSB</dt>
	  <dd>Most Significant Bit</t>

<t>NAL &#160;&#160;&#160;&#160;&#160;&#160; Network Bit</dd>
          <dt>NAL</dt>
	  <dd>Network Abstraction Layer</t>

<t>P &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Predictive</t>

<t>POC &#160;&#160;&#160;&#160;&#160;&#160; Picture Layer</dd>
          <dt>P</dt>
	  <dd>Predictive</dd>
          <dt>POC</dt>
	  <dd>Picture Order Count</t>

<t>PPS  &#160;&#160;&#160;&#160;&#160;&#160; Picture Count</dd>
          <dt>PPS</dt>
	  <dd>Picture Parameter Set</t>

<t>QP &#160;&#160;&#160;&#160;&#160;&#160;&#160; Quantization Parameter</t>

<t>RBSP &#160;&#160;&#160;&#160;&#160; Raw Set</dd>
          <dt>QP</dt>
	  <dd>Quantization Parameter</dd>
          <dt>RBSP</dt>
	  <dd>Raw Byte Sequence Payload</t>

<t>RGB &#160;&#160;&#160;&#160;&#160;&#160; Same as GBR</t>

<t>SAR &#160;&#160;&#160;&#160;&#160;&#160; Sample Payload</dd>
          <dt>RGB</dt>
	  <dd>Red, Green, and Blue</dd>
          <dt>SAR</dt>
	  <dd>Sample Aspect Ratio</t>

<t>SEI &#160;&#160;&#160;&#160;&#160;&#160; Supplemental Ratio</dd>
          <dt>SEI</dt>
	  <dd>Supplemental Enhancement Information</t>

<t>SODB &#160;&#160;&#160;&#160;&#160; String Information</dd>
          <dt>SODB</dt>
	  <dd>String Of Data Bits</t>

<t>SPS &#160;&#160;&#160;&#160;&#160;&#160; Sequence Bits</dd>
          <dt>SPS</dt>
	  <dd>Sequence Parameter Set</t>

<t>STRP &#160;&#160;&#160;&#160;&#160; Short-Term Set</dd>
          <dt>STRP</dt>
	  <dd>Short-Term Reference Picture</t>

<t>VBR &#160;&#160;&#160;&#160;&#160;&#160; Variable Picture</dd>
          <dt>VBR</dt>
	  <dd>Variable Bit Rate</t>

<t>VCL &#160;&#160;&#160;&#160;&#160;&#160; Video Rate</dd>
          <dt>VCL</dt>
	  <dd>Video Coding Layer</t> Layer</dd>
	  </dl>
      </section>
    </section>
    <section anchor="RTPPayloadFormat"><name>RTP anchor="RTPPayloadFormat">
      <name>RTP Payload Format</name>
      <section anchor="RTPHeaderUsage"><name>RTP anchor="RTPHeaderUsage">
        <name>RTP Header Usage</name>
        <t>The format of the RTP header is specified in <xref target="RFC3550"/> (reprinted (included as
<xref target="rtp-header"/> for convenience).  This payload format uses the fields of
the header in a manner consistent with that specification.</t>
        <t>The RTP payload (and the settings for some RTP header bits) for
aggregation packets
APs and fragmentation units Fragmentation Units (FUs) are specified in Sections
<xref target="aps"/> target="aps" format="counter"/> and <xref target="funits"/>, target="funits" format="counter"/>, respectively.</t>

        <figure anchor="rtp-header"><sourcecode type="~"><![CDATA[ anchor="rtp-header">
	  <name>RTP Header According to RFC 3550</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             |
   |                             ....                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                     RTP Header According to [RFC3550]
]]></sourcecode></figure>
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
        </figure>

        <t>The RTP header information to be set according to this RTP payload format is set as follows:</t>

<t>Marker
	<dl newline="false" spacing="normal">
          <dt>Marker bit (M): 1 (M):</dt>
	  <dd><t>1 bit</t>

<ul empty="true"><li>
	  <t>Set for the last packet of the access unit, unit and carried in the
	  current RTP stream.  This is in line with the normal use of the M
	  bit in video formats to allow an efficient playout buffer
	  handling.</t>
</li></ul>

<t>Payload
          </dd>
          <dt>Payload Type (PT): 7 (PT):</dt>
	  <dd><t>7 bits</t>

<ul empty="true"><li>
	  <t>The assignment of an RTP payload type for this new payload format
	  is outside the scope of this document and will not be specified
	  here.  The assignment of a payload type has to be performed either
	  through the profile used or in a dynamic way.</t>
</li></ul>

<t>Sequence
          </dd>
	  <dt>Sequence Number (SN): 16 (SN):</dt>
	  <dd><t>16 bits</t>

<ul empty="true"><li>
	  <t>Set and used in accordance with <xref target="RFC3550"/>.</t>
</li></ul>

<t>Timestamp: 32
	  </dd>
          <dt>Timestamp:</dt>
	  <dd><t>32 bits</t>

<ul empty="true"><li>
	  <t>The RTP timestamp is set to the sampling timestamp of the
	  content. A 90 kHz clock rate MUST <bcp14>MUST</bcp14> be used.  If the
	  NAL unit has no timing properties of its own (e.g., parameter sets
	  or certain SEI NAL units), the RTP timestamp MUST <bcp14>MUST</bcp14> be
	  set to the RTP timestamp of the coded picture of the access unit in
	  which the NAL unit is included.  For SEI messages, this information
	  is specified in Annex D of <xref target="EVC"/>. Receivers MUST
	  <bcp14>MUST</bcp14> use the RTP timestamp for the display process,
	  even when the bitstream contains picture timing SEI messages or
	  decoding unit information SEI messages as specified in <xref
	  target="EVC"/>.</t>
</li></ul>

<t>Synchronization
          </dd>
          <dt>Synchronization source (SSRC): 32 (SSRC):</dt>
	  <dd><t>32 bits</t>

<ul empty="true"><li>
	  <t>Used to identify the source of the RTP packets.  According to
	  this document, a single SSRC is used for all parts of a single
	  bitstream.</t>
</li></ul>
          </dd>
        </dl>

      </section>
      <section anchor="PayloadHeaderUsage"><name>Payload anchor="PayloadHeaderUsage">
        <name>Payload Header Usage</name>
        <t>The first two bytes of the payload of an RTP packet are referred to
        as the payload header.  The payload header consists of the same fields
        (F, TID, Reserve Reserve, and E) as the NAL unit header header, as shown in <xref
        target="NALUnitHeader"/>, irrespective of the type of the payload
        structure.</t>
        <t>The TID value indicates (among other things) the relative
        importance of an RTP packet, for example, because NAL units with
        larger TID value values are not used for the decoding of to decode the ones with
        smaller TID value. values. A lower value of TID indicates a higher
        importance. More-important More important NAL units MAY <bcp14>MAY</bcp14> be better
        protected against transmission losses than less-important less important NAL
        units.</t>
      </section>
      <section anchor="PayloadStructures"><name>Payload anchor="PayloadStructures">
        <name>Payload Structures</name>
        <t>Three different types of RTP packet payload structures are specified. A receiver can identify the type of an RTP packet payload through the Type field in the payload header.</t>
        <t>The three different payload structures are as follows:</t>

<t><list style="symbols">
  <t>Single
        <ul>
          <li>Single NAL unit packet: Contains a single NAL unit in
          the payload, and the NAL unit header of the NAL unit also serves as
          the payload header.  This payload structure is specified in <xref target="SingleNALUnit"/>.</t>
  <t>Aggregation
          target="SingleNALUnit"/>.</li>
          <li>Aggregation Packet (AP): Contains more than one NAL unit
          within one access unit.  This payload structure is specified in
          <xref target="aps"/>.</t>
  <t>Fragmentation target="aps"/>.</li>
          <li>Fragmentation Unit (FU): Contains a subset of a single
          NAL unit. This payload structure is specified in <xref target="funits"/>.</t>
</list></t>
          target="funits"/>.</li>
        </ul>
        <section anchor="SingleNALUnit"><name>Single anchor="SingleNALUnit">
          <name>Single NAL Unit Packets</name>
          <t>A single NAL unit packet contains exactly one NAL unit, unit and
          consists of a payload header as defined in Table 4 of <xref
          target="EVC"/> (denoted as PayloadHdr), followed by a conditional
          16-bit DONL field (in network byte order), and the NAL unit payload
          data (the NAL unit excluding its NAL unit header) of the contained
          NAL unit, as shown in <xref target="single-nhr"/>.</t>

          <figure anchor="single-nhr"><artwork><![CDATA[ anchor="single-nhr">
	    <name>The Structure of a Single NAL Unit 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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |           PayloadHdr          |      DONL (conditional)       |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                                                               |
  |                  NAL unit payload data                        |
  |                                                               |
  |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                               :...OPTIONAL RTP padding        |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

               The Structure of a Single NAL Unit Packet
]]></artwork></figure>
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
          </figure>

          <t>The DONL field, when present, specifies the value of the 16 least significant bits of the decoding order number of the contained NAL unit.  If sprop-max-don-diff (defined in <xref target="optionalParameters"/> target="optionalParameters"/>) is greater than 0, the DONL field MUST <bcp14>MUST</bcp14> be present, and the variable DON for the contained NAL unit is derived as equal to the value of the DONL field.  Otherwise (sprop-max-don-diff (where sprop-max-don-diff is equal to 0), the DONL field MUST NOT <bcp14>MUST NOT</bcp14> be present.</t>
        </section>
        <section anchor="aps"><name>Aggregation anchor="aps">
          <name>Aggregation Packets (APs)</name>
          <t>Aggregation Packets (APs) enable the reduction of packetization overhead for small NAL units, such as most of the non-VCL NAL units, which are often only a few octets in size.</t>
          <t>An AP aggregates NAL units of one access unit, and it MUST NOT <bcp14>MUST NOT</bcp14> contain NAL units from more than one AU. Each NAL unit to be carried in an AP is encapsulated in an aggregation unit. NAL units aggregated in one AP are included in NAL-unit-decoding order.</t>
          <t>An AP consists of a payload header, as defined in Table 4 of <xref target="EVC"/> (denoted here as PayloadHdr with Type=56) Type=56), followed by two or more aggregation units, as shown in <xref target="au-hdr"/>.</t>

          <figure anchor="au-hdr"><artwork><![CDATA[ anchor="au-hdr">
	    <name>The Structure of an 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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |    PayloadHdr (Type=56)       |                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
 |                                                               |
 |             two or more aggregation units                     |
 |                                                               |
 |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                               :...OPTIONAL RTP padding        |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                The Structure of an Aggregation Packet

]]></artwork></figure>
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
          </figure>

          <t>The fields in the payload header of an AP are set as follows. The F bit MUST <bcp14>MUST</bcp14> be equal to 0 if the F bit of each aggregated NAL unit is equal to zero; otherwise, it MUST <bcp14>MUST</bcp14> be equal to 1. The Type field MUST <bcp14>MUST</bcp14> be equal to 56.</t>
          <t>The value of TID MUST <bcp14>MUST</bcp14> be the smallest value of TID of all the aggregated NAL units. The value of Reserve and E MUST <bcp14>MUST</bcp14> be equal to 0 for this specification.</t>

<ul empty="true"><li>
  <t>Informative

          <aside><t>Informative note: All VCL NAL units in an AP have the
          same TID value since they belong to the same access unit. However,
          an AP may contain non-VCL NAL units for which the TID value in the
          NAL unit header may be different from the TID value of the VCL NAL
          units in the same AP.</t>
</li></ul> AP.</t></aside>

          <t>An AP MUST <bcp14>MUST</bcp14> carry at least two aggregation units
          and can carry as many aggregation units as necessary; however, the
          total amount of data in an AP obviously MUST <bcp14>MUST</bcp14> fit into
          an IP packet, and the size SHOULD <bcp14>SHOULD</bcp14> be chosen so that
          the resulting IP packet is smaller than the path MTU size so to
          avoid IP layer fragmentation. An AP MUST NOT <bcp14>MUST NOT</bcp14> contain
          FUs specified in <xref target="funits"/>. APs MUST NOT <bcp14>MUST
          NOT</bcp14> be nested; i.e., an AP can not cannot contain another AP.</t>

<ul empty="true"><li>
  <t>Informative

	  <aside><t>Informative note: If a receiver encounters nested Aggregation Packets,
	  APs, which is against the aforementioned
	  requirement, it has several options, listed in order of ease of
	  implementation: 1) Ignore ignore the nested AP; 2) Ignore ignore the nested AP and
	  report a &quot;packet loss&quot; "packet loss" to the decoder, if such functionality exists
	  in the API, API; and 3) Implement implement support for nested APs and extract the Network Abstraction Layer (NAL)
	  NAL units from these nested APs.</t>
</li></ul> APs.</t></aside>

          <t>The first aggregation unit in an AP consists of a conditional 16-bit DONL field (in network byte order) followed by a 16-bit unsigned size information (in network byte order) that indicates the size of the
NAL unit in bytes (excluding these two octets but including the NAL unit header), followed by the NAL unit itself, including its NAL unit header, as shown in <xref target="au-first-nhdr"/>.</t>

          <figure anchor="au-first-nhdr"><artwork><![CDATA[ anchor="au-first-nhdr">
	    <name>The Structure of the First Aggregation Unit in an AP</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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |               :       DONL (conditional)      |   NALU size   |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |   NALU size   |                                               |
 +-+-+-+-+-+-+-+-+         NAL unit                              |
 |                                                               |
 |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                               :
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

        The Structure of the First Aggregation Unit in an AP
]]></artwork></figure>

<ul empty="true"><li>
  <t>Informative
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
          </figure>

          <aside><t>Informative note: The first octet of <xref
          target="au-first-nhdr"/> (indicated by the first colon) belongs to a
          previous aggregation unit. It is depicted to emphasize that
          aggregation units are octet aligned only. Similarly, the NAL unit
          carried in the aggregation unit can terminate at the octet boundary.</t>
</li></ul>
          boundary.</t></aside>

          <t>The DONL field, when present, specifies the value of the 16 least significant bits of the decoding order number of the aggregated NAL unit.</t>
          <t>If sprop-max-don-diff is greater than 0, the DONL field MUST <bcp14>MUST</bcp14> be present in an aggregation unit that is the first aggregation unit in an AP. The variable DON for the aggregated NAL unit is derived as equal to the value of the DONL field, and the variable DON Decoding Order Number (DON) for an aggregation unit that is not the first aggregation unit in an AP-aggregated NAL unit is derived as equal to the DON of the preceding aggregated NAL unit in the same AP plus 1 modulo 65536. Otherwise (sprop-max-don-diff (where sprop-max-don-diff is equal to 0), the DONL field MUST NOT <bcp14>MUST NOT</bcp14> be present in an aggregation unit that is the first aggregation unit in an AP</t> AP.</t>
          <t>An aggregation unit that is not the first aggregation unit in an AP will be followed immediately by a 16-bit unsigned size information (in network byte order) that indicates the size of the NAL unit in bytes (excluding these two octets but including the NAL unit header), followed by the NAL unit itself, including its NAL unit header, as shown in <xref target="au-not-first-nhdr"/>.</t>

          <figure anchor="au-not-first-nhdr"><artwork><![CDATA[ anchor="au-not-first-nhdr">
	    <name> The Structure of an Aggregation Unit That Is Not the First Aggregation Unit in an AP</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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |               :       NALU size               |   NAL unit    |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               |
  |                                                               |
  |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                               :
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      The Structure of an Aggregation Unit That Is Not the First
                        Aggregation Unit in an AP
]]></artwork></figure>

<ul empty="true"><li>
  <t>Informative
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
          </figure>

          <aside><t>Informative note: The first octet of <xref
          target="au-not-first-nhdr"/> (indicated by the first colon) belongs
          to a previous aggregation unit. It is depicted to emphasize that
          aggregation units are octet aligned only. Similarly, the NAL unit
          carried in the aggregation unit can terminate at the octet boundary.</t>
</li></ul>
          boundary.</t></aside>

          <t><xref target="au-wout-donl"/> presents an example of an AP that
          contains two aggregation units, labeled as  NALU 1 "NALU 1" and  NALU 2 in the figure, "NALU 2",
          without the DONL field being present.</t>

          <figure anchor="au-wout-donl"><artwork><![CDATA[ anchor="au-wout-donl">
	    <name>An Example of an AP Packet Containing Two Aggregation Units without the DONL Field</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                           |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |   PayloadHdr (Type=56)        |         NALU 1 Size           |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |          NALU 1 HDR           |                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+         NALU 1 Data           |
 |                   . . .                                       |
 |                                                               |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  . . .        | NALU 2 Size                   | NALU 2 HDR    |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 | NALU 2 HDR    |                                               |
 +-+-+-+-+-+-+-+-+              NALU 2 Data                      |
 |                   . . .                                       |
 |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                               :...OPTIONAL RTP padding        |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

            An Example of an AP Packet Containing
          Two Aggregation Units without the DONL Field
]]></artwork></figure>
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
          </figure>

          <t><xref target="au-with-donl"/> presents an example of an AP that contains two aggregation
units, labeled as  NALU 1 "NALU 1" and  NALU 2 in the figure, "NALU 2", with the DONL field being present.</t>

          <figure anchor="au-with-donl"><artwork><![CDATA[ anchor="au-with-donl">
	    <name>An Example of an AP Containing Two Aggregation Units with the DONL Field</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                           |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |   PayloadHdr (Type=56)        |        NALU 1 DONL            |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |          NALU 1 Size          |            NALU 1 HDR         |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                                                               |
 |                 NALU 1 Data   . . .                           |
 |                                                               |
 +        . . .                  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                               :          NALU 2 Size          |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |          NALU 2 HDR           |                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+          NALU 2 Data          |
 |                                                               |
 |        . . .                  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                               :...OPTIONAL RTP padding        |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                An Example of an AP Containing
              Two Aggregation Units with the DONL Field
]]></artwork></figure>
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
          </figure>

        </section>
        <section anchor="funits"><name>Fragmentation Units</name>

<t>Fragmentation anchor="funits">
          <name>Fragmentation Units (FUs) (FUs)</name>
          <t>FUs are introduced to enable fragmenting a single NAL unit into multiple RTP packets, possibly without cooperation or knowledge of the EVC encoder.  A fragment of a NAL unit consists of an integer number of consecutive octets of that NAL unit.  Fragments of the same NAL unit MUST <bcp14>MUST</bcp14> 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).</t>
          <t>When a NAL unit is fragmented and conveyed within FUs, it is referred to as a fragmented NAL unit.  APs MUST NOT <bcp14>MUST NOT</bcp14> be fragmented.  FUs MUST NOT <bcp14>MUST NOT</bcp14> be nested; i.e., an FU must not contain a subset of another FU.</t>
          <t>The RTP timestamp of an RTP packet carrying an FU is set to the NALU-time of the fragmented NAL unit.</t>
          <t>An FU consists of a payload header as defined in Table 4 of <xref target="EVC"/> (denoted as PayloadHdr with type=57), Type=57), an FU header of one octet, a conditional 16-bit DONL field (in network byte order), and an FU payload, as shown in <xref target="fu-payload"/>.</t>

          <figure anchor="fu-payload"><artwork><![CDATA[ anchor="fu-payload">
	    <name>The Structure of an FU</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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |    PayloadHdr (Type=57)       |   FU header   | DONL (cond)   |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
 | DONL (cond)   |                                               |
 |-+-+-+-+-+-+-+-+                                               |
 |                         FU payload                            |
 |                                                               |
 |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                               :...OPTIONAL RTP padding        |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                       The Structure of an FU
]]></artwork></figure>
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
          </figure>

          <t>The fields in the payload header are set as follows.  The Type field MUST <bcp14>MUST</bcp14> be equal to 57.  The fields F, TID, Reserve Reserve, and E MUST <bcp14>MUST</bcp14> be equal to the fields F, TID, Reserve Reserve, and E, respectively, of the fragmented NAL unit.</t>
          <t>The FU header consists of an S bit, an E bit, and a 6-bit FuType field, as shown in <xref target="fu-header"/>.</t>

          <figure anchor="fu-header"><artwork><![CDATA[ anchor="fu-header">
	    <name>The Structure of FU Header</name>
            <artwork><![CDATA[
                           0 1 2 3 4 5 6 7
                          +-+-+-+-+-+-+-+-+
                          |S|E|  FuType   |
                          +---------------+

                      The Structure of FU Header
]]></artwork></figure>
                          +---------------+]]></artwork>
          </figure>

          <t>The semantics of the FU header fields are as follows:</t>

<t>S: 1
<dl>
          <dt>S:</dt>
<dd>
<t>1 bit</t>

<ul empty="true"><li>

<t>When set to 1, the S bit indicates the start of a fragmented NAL unit, i.e., the first byte of the FU payload is also the first byte of the payload of the fragmented NAL unit.  When the FU payload is not the start of the fragmented NAL unit payload, the S bit MUST <bcp14>MUST</bcp14> be set to 0.</t>
</li></ul>

<t>E: 1
            </dd>

          <dt>E:</dt>
<dd>
<t>1 bit</t>

<ul empty="true"><li>

<t>When set to 1, the E bit indicates the end of a fragmented NAL unit, i.e., the last byte of the payload is also the last byte of the fragmented NAL unit.  When the FU payload is not the last fragment of a fragmented NAL unit, the E bit MUST <bcp14>MUST</bcp14> be set to 0.</t>
</li></ul>

<t>FuType: 6
            </dd>

          <dt>FuType:</dt>
<dd>
<t>6 bits</t>

<ul empty="true"><li>

              <t>The field FuType MUST <bcp14>MUST</bcp14> be equal to the field Type of the fragmented NAL unit.</t>
</li></ul>
            </dd>
          </dl>

          <t>The DONL field, when present, specifies the value of the 16 least significant bits of the decoding order number of the fragmented NAL unit.</t>
          <t>If sprop-max-don-diff is greater than 0, 0 and the S bit is equal to 1, the DONL field MUST <bcp14>MUST</bcp14> be present in the FU, and the variable DON for the fragmented NAL unit is derived as equal to the value of the DONL field.  Otherwise (sprop-max-don-diff (where sprop-max-don-diff is equal to 0, or where the S bit is equal to 0), the DONL field MUST NOT <bcp14>MUST NOT</bcp14> be present in the FU.</t>
          <t>A non-fragmented NAL unit MUST NOT <bcp14>MUST NOT</bcp14> be transmitted in one FU; i.e., the Start bit S-bit and End bit MUST NOT E-bit <bcp14>MUST NOT</bcp14> both be set to 1 in the same FU header.</t>
          <t>The FU payload consists of fragments of the payload of the fragmented NAL unit so that if the FU payloads of consecutive FUs, starting with an FU with the S bit equal to 1 and ending with an FU with the E bit equal to 1, are sequentially concatenated, the payload of the fragmented NAL unit can be reconstructed.  The NAL unit header of the fragmented NAL unit is not included as such in the FU payload, but rather payload. Instead, the information of the NAL unit header of the fragmented NAL unit is conveyed in F, TID, Reserve Reserve, and E fields of the FU payload headers of the FUs and the FuType field of the FU header of the FUs. An FU payload MUST NOT <bcp14>MUST NOT</bcp14> be empty.</t>
          <t>If an FU is lost, the receiver SHOULD <bcp14>SHOULD</bcp14> discard all following fragmentation units in transmission order corresponding to the same fragmented NAL unit unless the decoder in the receiver is known to gracefully handle incomplete NAL units.</t>
          <t>A receiver in an endpoint or a MANE MAY <bcp14>MAY</bcp14> aggregate the first n-1 fragments of a NAL unit to an (incomplete) NAL unit, even if fragment n of that NAL unit is not received. In this case, the forbidden_zero_bit of the NAL unit MUST <bcp14>MUST</bcp14> be set to 1 to indicate a syntax violation.</t>
        </section>
      </section>
      <section anchor="DON"><name>Decoding anchor="DON">
        <name>Decoding Order Number</name>
        <t>For each NAL unit, the variable AbsDon is derived, representing derived; it represents the
decoding order number that is indicative of the NAL unit decoding
order.</t>
        <t>Let NAL unit n be the n-th NAL unit in transmission order within an
RTP stream.</t>
        <t>If sprop-max-don-diff is equal to 0, AbsDon[n], the then AbsDon[n] (the value of AbsDon for NAL unit n, n) is derived as equal to n.</t>
        <t>Otherwise (sprop-max-don-diff (where sprop-max-don-diff is greater than 0), AbsDon[n] is derived as follows, where DON[n] is the value
of the variable DON for NAL unit n:</t>

<t><list style="symbols">
  <t>If
        <ul spacing="normal">
          <li>If n is equal to 0 (i.e., NAL unit n is the very first NAL unit
          in transmission order), AbsDon[0] is set equal to DON[0].</t>
  <t>Otherwise (n DON[0].</li>
          <li><t>Otherwise (where n is greater than 0), the following applies
          for derivation of AbsDon[n]:</t>
</list></t>

<figure><artwork><![CDATA[

        <artwork><![CDATA[
If DON[n] == DON[n-1],
   AbsDon[n] = AbsDon[n-1]

If (DON[n] > DON[n-1] and DON[n] - DON[n-1] < 32768),
   AbsDon[n] = AbsDon[n-1] + DON[n] - DON[n-1]

If (DON[n] < DON[n-1] and DON[n-1] - DON[n] >= 32768),
   AbsDon[n] = AbsDon[n-1] + 65536 - DON[n-1] + DON[n]

If (DON[n] > DON[n-1] and DON[n] - DON[n-1] >= 32768),
   AbsDon[n] = AbsDon[n-1] - (DON[n-1] + 65536 - DON[n])

If (DON[n] < DON[n-1] and DON[n-1] - DON[n] < 32768),
   AbsDon[n] = AbsDon[n-1] - (DON[n-1] - DON[n])
]]></artwork></figure>
]]></artwork></li>
	</ul>
        <t>For any two NAL units m (m and n, n), the following applies:</t>

<t><list style="symbols">
  <t>AbsDon[n]
        <ul spacing="normal">
          <li>When AbsDon[n] is greater than AbsDon[m] indicates that AbsDon[m], the NAL unit n
          follows NAL unit m in NAL unit decoding order.</t>
  <t>When order.</li>
          <li>When AbsDon[n] is equal to AbsDon[m], the NAL unit decoding
          order of the two NAL units can be in either order.</t>
  <t>AbsDon[n] order.</li>
          <li>When AbsDon[n] is less than AbsDon[m] indicates that AbsDon[m], the NAL unit n precedes
          NAL unit m in decoding order.  <vspace blankLines='1'/>
    <ul empty="true"><li>
      <ul empty="true"><li>
        <t>Informative order.</li>
	</ul>

	<aside><t>Informative note: When two consecutive NAL units in
	the NAL unit decoding order has different values of AbsDon, the
the
	absolute difference between the two AbsDon values may be greater than
	or equal to 1.</t>
      </li></ul>
    </li></ul>
  <vspace blankLines='1'/>
    <ul empty="true"><li>
      <ul empty="true"><li>
        <t>Informative 1.</t></aside>

        <aside><t>Informative note: There are multiple reasons to allow for
        the absolute difference of the values of AbsDon for two
        consecutive NAL units in the NAL unit decoding order to be greater
        than one. An increment by one is not required, required as at the time of
        associating values of AbsDon to NAL units, it may not be known whether
        all NAL units are to be delivered to the receiver. For example, a
        gateway might not forward VCL NAL units of higher sub-layers or some
        SEI NAL units when there is congestion in the network. In another
        example, the first intra-coded picture of a pre-encoded clip is
        transmitted in advance to ensure that it is readily available in the
        receiver. When transmitting the first intra-coded picture, the
        originator still determines how many NAL units will be encoded before
        the first intra-coded picture of the pre-encoded clip follows in
        decoding order. Thus, the values of AbsDon for the NAL units of the
        first intra-coded picture of the pre-encoded clip have to be estimated
        when they are transmitted, transmitted and gaps in the values of AbsDon may occur.</t>
      </li></ul>
    </li></ul>
  </t>
</list></t>
        occur.</t></aside>

      </section>
    </section>
    <section anchor="PacketizationRules"><name>Packetization anchor="PacketizationRules">
      <name>Packetization Rules</name>
      <t>The following packetization rules apply:</t>

<t><list style="symbols">
  <t>If
      <ul spacing="normal">
        <li>If sprop-max-don-diff is greater than 0, the transmission order of
        NAL units carried in the RTP stream MAY <bcp14>MAY</bcp14> be different
        from the NAL unit decoding order. Otherwise (sprop-max-don-diff (where sprop-max-don-diff
        equals 0), the transmission order of NAL units carried in the RTP
        stream MUST <bcp14>MUST</bcp14> be the same as the NAL unit decoding order.</t>
  <t>A
        order.</li>
        <li>A NAL unit of small size SHOULD <bcp14>SHOULD</bcp14> be encapsulated in
        an aggregation packet AP together with one or more other NAL units to avoid the
        unnecessary packetization overhead for small NAL units. For example,
        non-VCL NAL units, such as access unit delimiters, parameter sets, or
        SEI NAL units, are typically small and can often be aggregated with
        VCL NAL units without violating MTU size constraints.</t>
  <t>Each constraints.</li>
        <li>Each non-VCL NAL unit SHOULD, <bcp14>SHOULD</bcp14>, when possible from an
        MTU size match viewpoint, be encapsulated in an aggregation packet AP with its associated
        VCL NAL unit, as unit as, typically, a non-VCL NAL unit would be meaningless
        without the associated VCL NAL unit being available.</t>
  <t>For available.</li>
        <li>A single NAL unit packet <bcp14>MUST</bcp14> be used for carrying
        precisely one NAL unit in an RTP packet, a single NAL unit packet MUST be used.</t>
</list></t> packet.</li>
      </ul>
    </section>
    <section anchor="DepacketizationProcess"><name>De-packetization anchor="DepacketizationProcess">
      <name>De-packetization Process</name>
      <t>The general concept behind de-packetization is to get the NAL units out of the RTP packets in an RTP stream and pass them to the decoder in the NAL unit decoding order.</t>
      <t>The de-packetization process is implementation dependent. Therefore, the following description should be seen as an example of a suitable implementation. Other schemes may also be used as long as the output for the same input is the same as the process described below. The output is the same when the set of output NAL units and their order are both identical. Optimizations relative to the described algorithms are possible.</t>
      <t>All normal RTP mechanisms related to buffer management apply. In particular, duplicated or outdated RTP packets (as indicated by the RTP sequence number and the RTP timestamp) are removed. To determine the exact time for decoding, factors such as a possible intentional delay to allow for proper inter-stream synchronization, MUST synchronization must be factored in.</t> considered.</t>
      <t>NAL units with NAL unit type values in the range of 0 to 55, inclusive, may be passed to the decoder. NAL-unit-like structures with NAL unit type values in the range of 56 to 62, inclusive, MUST NOT <bcp14>MUST NOT</bcp14> be passed to the decoder.</t>
      <t>The receiver includes a receiver buffer, which is used to compensate for transmission delay jitter within individual RTP streams and to reorder NAL units from transmission order to the NAL unit decoding order. In this section, the receiver operation is described under the assumption that there is no transmission delay jitter within an RTP stream. To clarify the distinction from a practical receiver buffer, which is also used to compensate for transmission delay jitter, the buffer in this section will henceforth be referred to as the de-packetization "de-packetization" buffer. Receivers should also prepare for transmission delay jitter; that is, either reserve separate buffers for transmission delay jitter buffering and de-packetization buffering buffering, or use a receiver buffer for both transmission delay jitter and de-packetization. Moreover, receivers should take transmission delay jitter into account in the buffering operation, e.g., by additional initial buffering before starting of decoding and playback.</t>
      <t>The de-packetization process extracts the NAL units from the RTP packets in an RTP stream as follows. When an RTP packet carries a single NAL unit packet, the payload of the RTP packet is extracted as a single NAL unit, excluding the DONL field, i.e., third and fourth bytes, when sprop-max-don-diff is greater than 0. When an RTP packet carries an aggregation packet, AP, several NAL units are extracted from the payload of the RTP packet. In this case, each NAL unit corresponds to the part of the payload of each aggregation unit that follows the NALU size field, as described in <xref target="aps"/>. When an RTP packet carries a Fragmentation Unit (FU), all RTP packets from the first FU (with the S field equal to 1) of the fragmented NAL unit up to the last FU (with the E field equal to 1) of the fragmented NAL unit are collected. The NAL unit is extracted from these RTP packets by concatenating all FU payloads in the same order as the corresponding RTP packets and appending the NAL unit header with the fields F and TID set to equal the values of the fields F and TID in the payload header of the FUs, respectively, and with the NAL unit type set equal to the value of the field FuType in the FU header of the FUs, as described in <xref target="funits"/>.</t>
      <t>When sprop-max-don-diff is equal to 0, the de-packetization buffer size is zero bytes, and the NAL units carried in the single RTP stream are directly passed to the decoder in their transmission order, which is identical to their decoding order.</t>
      <t>When sprop-max-don-diff is greater than 0, the process described in the remainder of this section applies.</t>
      <t>The receiver has two buffering states: initial buffering and buffering while playing. Initial buffering starts when the reception is initialized. After initial buffering, decoding and playback are started, and the buffering-while-playing mode is used.</t>
      <t>Regardless of the buffering state, the receiver stores incoming NAL units in reception order into the de-packetization buffer. NAL units carried in RTP packets are stored in the de-packetization buffer individually, and the value of AbsDon is calculated and stored for each NAL unit.</t>
      <t>Initial buffering lasts until the difference between the greatest and smallest AbsDon values of the NAL units in the de-packetization buffer is greater than or equal to the value of sprop-max-don-diff.</t>
      <t>After initial buffering, whenever the difference between the greatest and smallest AbsDon values of the NAL units in the de-packetization buffer is greater than or equal to the value of sprop-max-don-diff, the following operation is repeatedly applied until this difference is smaller than sprop-max-don-diff:</t>

<t><list style="symbols">
  <t>The
<t indent="3">The NAL unit in the de-packetization buffer with the smallest value of AbsDon is removed from the de-packetization buffer and passed to the decoder.</t>
</list></t>
      <t>When no more NAL units are flowing into the de-packetization buffer, all NAL units remaining in the de-packetization buffer are removed from the buffer and passed to the decoder in the order of increasing AbsDon values.</t>

<!-- Section 7 -->
</section>
    <section anchor="PayloadFormatParameters"><name>Payload anchor="PayloadFormatParameters">
      <name>Payload Format Parameters</name>
      <t>This section specifies the optional parameters. A mapping of the parameters with the Session Description Protocol (SDP) <xref target="RFC8866"/> is also provided for applications that use SDP.</t>
      <t>Parameters starting with the string &quot;sprop&quot; "sprop" for stream properties can be used by a sender to provide a receiver with the properties of the stream that is or will be sent. The media sender (and not the receiver) selects whether, and with what values, &quot;sprop&quot; "sprop" parameters are being sent. This uncommon characteristic of the &quot;sprop&quot; "sprop" parameters may not be intuitive in the context of some signaling protocol concepts, especially with offer/answer. Offer/Answer.  Please see <xref target="sdpoa"/> for guidance specific to the use of sprop parameters in the Offer/Answer case.</t>

<!-- Section 7.1 -->

<section anchor="oparams"><name>Media anchor="oparams">
        <name>Media Type Registration</name>
        <t>The receiver MUST <bcp14>MUST</bcp14> ignore any parameter unspecified
        in this document.</t>

<t>Type name:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;video</t>

<t>Subtype name:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;evc</t>

<t>Required parameters: N/A</t>

<t>Optional parameters: profile-id,
	<dl spacing="normal" newline="false">
          <dt>Type name:</dt><dd>video</dd>
          <dt>Subtype name:</dt><dd>evc</dd>
          <dt>Required parameters:</dt><dd>N/A</dd>
          <dt>Optional parameters:</dt><dd>profile-id, level-id, toolset-id,
          max-recv-level-id, sprop-sps, sprop-pps, sprop-sei,
          sprop-max-don-diff, sprop-depack-buf-bytes, depack-buf-cap (refer to
          <xref target="optionalParameters"/> for definitions)</t>

<t>Encoding considerations:</t>

<ul empty="true"><li>
  <t>This definitions)</dd>
          <dt>Encoding considerations:</dt> <dd>This type is only defined for
          transfer via RTP (RFC 3550).</t>
</li></ul>

<t>Security considerations:</t>

<ul empty="true"><li>
  <t>See <xref target="RFC3550" format="default"/>.</dd>
          <dt>Security considerations:</dt> <dd>See <xref target="Security"/>
          of RFC XXXX.</t>
</li></ul>

<t>Interoperability considerations: N/A</t>

<t>Published specification:</t>

<ul empty="true"><li>
  <t>Please 9584.</dd>
          <dt>Interoperability considerations:</dt><dd>N/A</dd>
          <dt>Published specification:</dt> <dd>Please refer to RFC XXXX 9584 and
          EVC standard <xref target="EVC"/>.</t>
</li></ul>

<t>Applications target="EVC"/>.</dd>
          <dt>Applications that use this media type:</t>

<ul empty="true"><li>
  <t>Any type:</dt> <dd>Any application
          that relies on EVC-based video services over RTP</t>
</li></ul>

<t>Fragment RTP</dd>
          <dt>Fragment identifier considerations: N/A</t>

<t>Additional information: N/A</t>

<t>Person considerations:</dt><dd>N/A</dd>
          <dt>Additional information:</dt><dd>N/A</dd>
	  <dt>Person &amp; email address to contact for further information:</t>

<ul empty="true"><li>
  <t>Stephan
	  information:</dt> <dd><br/>Stephan Wenger (stewe@stewe.org)</t>
</li></ul>

<t>Intended usage: COMMON</t>

<t>Restrictions (stewe@stewe.org)</dd>
          <dt>Intended usage:</dt><dd>COMMON</dd>
          <dt>Restrictions on usage: N/A</t>

<t>Author: See Authors&#39; usage:</dt><dd>N/A</dd>
          <dt>Author:</dt><dd>See Authors' Addresses section of RFC XXXX.</t>

<t>Change controller:</t>

<ul empty="true"><li>
  <t>IETF &lt;avtcore@ietf.org&gt;</t>
</li></ul>

<!-- Section 7.2 --> 9584.</dd>
          <dt>Change controller:</dt> <dd>IETF &lt;avtcore@ietf.org&gt;</dd>
	</dl>
      </section>
      <section anchor="optionalParameters"><name>Optional anchor="optionalParameters">
        <name>Optional Parameters Definition</name>

<t>profile-id,
	<dl newline="true">
        <dt>profile-id, level-id, toolset-id:</t>

<ul empty="true"><li>
  <t>These toolset-id:</dt>
          <dd><t>These parameters indicate the profile, the level, and
          constraints of the bitstream carried by the RTP stream, stream or a
          specific set of the profile, the level, and constraints the receiver
          supports.</t>
</li></ul>

<ul empty="true"><li>
          <t>More specifications of these parameters, including how they
          relate to syntax elements specified in <xref target="EVC"/> are
          provided below.</t>
</li></ul>

<t>profile-id:</t>

<ul empty="true"><li>
  <t>When
          </dd>

        <dt>profile-id:</dt>
           <dd><t>When profile-id is not present, a value of 0 (i.e., the
           Baseline profile) MUST <bcp14>MUST</bcp14> be inferred.</t>
</li></ul>

<ul empty="true"><li>
           <t>When used to indicate properties of a bitstream, profile-id MUST
           <bcp14>MUST</bcp14> be derived from the profile_idc in the SPS.</t>
</li></ul>

<ul empty="true"><li>
           <t>EVC bitstreams transported over RTP using the technologies of
           this document SHOULD <bcp14>SHOULD</bcp14> refer only to SPSs that have
           the same value in profile_idc, unless the sender has a priori
           knowledge that a receiver can correctly decode the EVC bitstream
           with different profile_idc values (for example example, in walled garden
           scenarios).  As exceptions to this rule, if the receiver is known
           to support a Baseline profile, a bitstream could safely end with CVS
           referring to an SPS wherein profile_idc indicates the Baseline
           Still Picture picture profile.  A similar exception can be made for Main
           profile and Main Still picture profile.</t>
</li></ul>

<t>level-id:</t>

<ul empty="true"><li>
  <t>When
          </dd>

        <dt>level-id:</dt>
           <dd><t>When level-id is not present, a value of 90 (corresponding
           to level 3, which allows for approximately SD TV standard-definition
           television (SD TV) resolution and frame rates; for details please see Annex A of EVC) MUST <xref
           target="EVC"/>) <bcp14>MUST</bcp14> be inferred.</t>
</li></ul>

<ul empty="true"><li>
           <t>When used to indicate properties of a bitstream, level-id MUST
           <bcp14>MUST</bcp14> be derived from the level_idc in the SPS.</t>
</li></ul>

<ul empty="true"><li>
           <t>If the level-id parameter is used for capability exchange, the
           following applies. If max-recv-level-id is not present, the default
           level defined by level-id indicates the highest level the codec
           wishes to support. Otherwise, max-recv-level-id indicates the
           highest level the codec supports for receiving. For either
           receiving or sending, all levels that are lower than the highest
           level supported MUST <bcp14>MUST</bcp14> also be supported.</t>
</li></ul>

<t>toolset-id:</t>

<ul empty="true"><li>
  <t>This
          </dd>

        <dt>toolset-id:</dt>
	<dd>This parameter is a base64 encoding (Section 4 of <xref target="RFC4648"></xref>) base64-encoding representation (<xref
	target="RFC4648" section="4" sectionFormat="of"/>) of a 64 bit 64-bit
	unsigned integer bit mask derived from the concatenation, in network
	byte order, of the syntax elements toolset_idc_h and toolset_idc_l.
	When used to indicate properties of a bitstream, its value MUST
	<bcp14>MUST</bcp14> be derived from toolset_idh_h and toolset_idc_l in
	the sequence parameter set.</t>
</li></ul>

<t>max-recv-level-id:</t>

<ul empty="true"><li>
  <t>This set.</dd>

        <dt>max-recv-level-id:</dt>
        <dd><t>This parameter MAY <bcp14>MAY</bcp14> be used to indicate the
        highest level a receiver supports.</t>
</li></ul>
        <t>The value of max-recv-level-id MUST <bcp14>MUST</bcp14> be in the range
        of 0 to 255, inclusive.P.</t> inclusive.</t>
        <t>When max-recv-level-id is not present, the value is inferred to be
        equal to level-id.</t>
        <t>max-recv-level-id MUST NOT <bcp14>MUST NOT</bcp14> be present when the
        highest level the receiver supports is not higher than the default level.</t>

<t>sprop-sps:</t>

<ul empty="true"><li>
  <t>This
        level.</t></dd>

        <dt>sprop-sps:</dt>
	<dd><t>This parameter MAY <bcp14>MAY</bcp14> be used to convey sequence
	parameter set NAL units of the bitstream for out-of-band transmission
	of sequence parameter sets.  The value of the parameter is a
	comma-separated (&#39;,&#39;) (',') list of base64 encoding (Section 4 of <xref target="RFC4648"/>) base64-encoding representations (<xref
	target="RFC4648" section="4" sectionFormat="of"/>) of the sequence
	parameter set NAL units as specified in Section 7.3.2.1 of <xref
	target="EVC"/>.</t>
</li></ul>

<t>sprop-pps:</t>

<ul empty="true"><li>
  <t>This
	</dd>

        <dt>sprop-pps:</dt>
	<dd><t>This parameter MAY <bcp14>MAY</bcp14> be used to convey picture
	parameter set NAL units of the bitstream for out-of-band transmission
	of picture parameter sets.  The value of the parameter is a
	comma-separated (&#39;,&#39;) (',') list of base64 encoding (Section 4 of <xref target="RFC4648"/>) base64-encoding representations (<xref
	target="RFC4648" section="4" sectionFormat="of"/>) of the picture
	parameter set NAL units as specified in Section 7.3.2.2 of <xref target="EVC"/>.</t>
</li></ul>

<t>sprop-sei:</t>

<ul empty="true"><li>
  <t>This
	target="EVC"/>.</t></dd>

        <dt>sprop-sei:</dt>
	<dd><t>This parameter MAY <bcp14>MAY</bcp14> be used to convey one or more
	SEI messages that describe bitstream characteristics.  When present, a
	decoder can rely on the bitstream characteristics that are described
	in the SEI messages for the entire duration of the session,
	independently from the persistence scopes of the SEI messages as
	specified in <xref target="VSEI"/>.</t>
</li></ul>

<ul empty="true"><li>
	<t>The value of the parameter is a comma-separated (&#39;,&#39;) (',') list of base64 encoding (Section 4 of <xref target="RFC4648"/>)
	base64-encoding representations (<xref target="RFC4648" section="4"
	sectionFormat="of"/>) of SEI NAL units as specified in
	<xref target="VSEI"/>.</t>
</li></ul>

<ul empty="true"><li>
  <ul empty="true"><li>
    <t>Informative
              <aside><t>Informative note: Intentionally, no list of
              applicable or inapplicable SEI messages is specified here.
              Conveying certain SEI messages in sprop-sei may be sensible in
              some application scenarios and meaningless in others.  However,
              a few couple of examples are described below:</t>
  </li></ul>
</li></ul>

<ul empty="true"><li>
  <ul empty="true"><li>
    <t>1) In below.</t>
              <ol type="1">
                <li>In an environment where the bitstream was created from
                film-based source material, and no splicing is going to occur
                during the lifetime of the session, the film grain
                characteristics SEI message is likely meaningful, meaningful; and sending
                it in sprop-sei rather than in the bitstream at each entry
                point may help with saving bits and allows allow one to configure
                the renderer only once, avoiding unwanted artifacts.</t>
  </li></ul>
</li></ul>

<ul empty="true"><li>
  <ul empty="true"><li>
    <t>2) Examples artifacts.</li>
                <li>Examples for SEI messages that would be meaningless to be
                conveyed in sprop-sei include the decoded picture hash SEI
                message (it is close to impossible that all decoded pictures
                have the same hashtag) or the filler payload SEI message (as
                there is no point in just having more bits in SDP).</t>
  </li></ul>
</li></ul>

<t>sprop-max-don-diff:</t>

<ul empty="true"><li>
  <t>If SDP).</li>
              </ol></aside>
            </dd>

        <dt>sprop-max-don-diff:</dt>

           <dd><t>If there is no NAL unit naluA that is followed in transmission order by any NAL unit preceding naluA in decoding order (i.e., the transmission order of the NAL units is the same as the decoding order), the value of this parameter MUST <bcp14>MUST</bcp14> be equal to 0.</t>
</li></ul>

<ul empty="true"><li>

            <t>Otherwise, this parameter specifies the maximum absolute difference between the decoding order number (i.e., AbsDon) values of any two NAL units naluA and naluB, where naluA follows naluB in decoding order and precedes naluB in transmission order.</t>
</li></ul>

<ul empty="true"><li>

            <t>The value of sprop-max-don-diff MUST <bcp14>MUST</bcp14> be an integer in the range of 0 to 32767, inclusive.</t>
</li></ul>

<ul empty="true"><li>

            <t>When not present, the value of sprop-max-don-diff is inferred to be equal to 0.</t>
</li></ul>

<t>sprop-depack-buf-bytes:</t>

<ul empty="true"><li>
	   </dd>

           <dt>sprop-depack-buf-bytes:</dt>
	   <dd>

            <t>This parameter signals the required size of the de-packetization buffer in units of bytes.  The value of the parameter MUST <bcp14>MUST</bcp14> be greater than or equal to the maximum buffer occupancy (in units of bytes) of the de-packetization buffer as specified in Section 6.</t>
</li></ul>

<ul empty="true"><li> <xref target="DepacketizationProcess" format="default"/>.</t>

            <t>The value of sprop-depack-buf-bytes MUST <bcp14>MUST</bcp14> be an integer in the range of 0 to 4294967295, inclusive.</t>
</li></ul>

<ul empty="true"><li>

            <t>When sprop-max-don-diff is present and greater than 0, this parameter MUST <bcp14>MUST</bcp14> be present and the value MUST <bcp14>MUST</bcp14> be greater than 0.  When not present, the value of sprop-depack-buf-bytes is inferred to be equal to 0.</t>
</li></ul>

<ul empty="true"><li>
  <ul empty="true"><li>
    <t>Informative

            <aside><t>Informative note: The value of
            sprop-depack-buf-bytes indicates the required size of the
            de-packetization buffer only.  When network jitter can occur, an
            appropriately sized jitter buffer has to be available as well.</t>
  </li></ul>
</li></ul>

<t>depack-buf-cap:</t>

<ul empty="true"><li>
            well.</t></aside>
	   </dd>

        <dt>depack-buf-cap:</dt>
	<dd>
          <t>This parameter signals the capabilities of a receiver
          implementation and indicates the amount of de-packetization buffer
          space in units of bytes that the receiver has available for
          reconstructing the NAL unit decoding order from NAL units carried in
          the RTP stream.  A receiver is able to handle any RTP stream for
          which the value of the sprop-depack-buf-bytes parameter is smaller
          than or equal to this parameter.</t>
</li></ul>

<ul empty="true"><li>
          <t>When not present, the value of depack-buf-cap is inferred to be
          equal to 4294967295.  The value of depack-buf-cap MUST
          <bcp14>MUST</bcp14> be an integer in the range of 1 to 4294967295,
          inclusive.</t>
</li></ul>

<ul empty="true"><li>
  <ul empty="true"><li>
    <t>Informative

          <aside><t>Informative note: The value of depack-buf-cap indicates
          the maximum possible size of the de-packetization buffer of the
          receiver only, without allowing for network jitter.</t>
  </li></ul>
</li></ul>

<!-- Section 7.3 --> jitter. When network
          jitter occurs, an appropriately sized jitter buffer has to be
          available as well. </t></aside>
	</dd>
        </dl>

      </section>

      <section anchor="sdp-parameters"><name>SDP anchor="sdp-parameters">
        <name>SDP Parameters</name>
        <t>The receiver MUST <bcp14>MUST</bcp14> ignore any parameter unspecified in this document.</t>

<!-- Section 7.3.1 -->

<section anchor="mapping-of-payload-type-parameters-to-sdp"><name>Mapping anchor="mapping-of-payload-type-parameters-to-sdp">
          <name>Mapping of Payload Type Parameters to SDP</name>
          <t>The media type video/evc string is mapped to fields in the Session Description Protocol (SDP) <xref target="RFC8866"/> as follows:</t>

<t><list style="symbols">
  <t>The
          <ul spacing="normal">
            <li>The media name in the &quot;m=&quot; "m=" line of SDP MUST <bcp14>MUST</bcp14>
            be video.</t>
  <t>The video.</li>
            <li>The encoding name in the &quot;a=rtpmap&quot; "a=rtpmap" line of SDP MUST
            <bcp14>MUST</bcp14> be evc (the media subtype).</t>
  <t>The subtype).</li>
            <li>The clock rate in the &quot;a=rtpmap&quot; "a=rtpmap" line MUST <bcp14>MUST</bcp14> be 90000.</t>
  <t>The OPTIONAL
            90000.</li>

            <li>The <bcp14>OPTIONAL</bcp14> parameters profile-id, level-id,
            toolset-id, max-recv-level-id, sprop-max-don-diff,
            sprop-depack-buf-bytes, and depack-buf-cap, when present, MUST
            <bcp14>MUST</bcp14> be included in the &quot;a=fmtp&quot; "a=fmtp" line of SDP. The fmtp
            "a=fmtp" line is expressed as a media type string, in the form of a
            semicolon-separated list of parameter=value pairs.</t>
  <t>The OPTIONAL pairs.</li>
            <li>The <bcp14>OPTIONAL</bcp14> parameters sprop-sps, sprop-pps,
            and sprop-sei, when present, MUST <bcp14>MUST</bcp14> be included in
            the &quot;a=fmtp&quot; "a=fmtp" line of SDP or conveyed using the &quot;fmtp&quot; "fmtp" source
            attribute as specified in Section 6.3 of <xref target="RFC5576"/>. target="RFC5576"
            sectionFormat="of" section="6.3"/>. For a particular media format
            (i.e., RTP payload type), sprop-sps, sprop-pps, or sprop-sei MUST NOT
            <bcp14>MUST NOT</bcp14> be both included in the &quot;a=fmtp&quot; "a=fmtp" line of
            SDP and conveyed using the &quot;fmtp&quot; "fmtp" source attribute. When included
            in the &quot;a=fmtp&quot; "a=fmtp" line of SDP, those parameters are expressed as a
            media type string, in the form of a semicolon-separated list
            of parameter=value pairs. When conveyed in the &quot;a=fmtp&quot; "a=fmtp" line of
            SDP for a particular payload type, the parameters sprop-sps,
            sprop-pps, and sprop-sei MUST <bcp14>MUST</bcp14> be applied to each
            SSRC with the payload type. When conveyed using the &quot;fmtp&quot; "fmtp" source
            attribute, these parameters are only associated with the given
            source and payload type as parts of the &quot;fmtp&quot; "fmtp" source attribute.</t>
</list></t>

<ul empty="true"><li>
  <t>Informative
            attribute.</li>
          </ul>
          <aside><t>Informative note: Conveyance of sprop-sps and sprop-pps
          using the &quot;fmtp&quot; "fmtp" source attribute allows for out-of-band transport
          of parameter sets in topologies like Topo-Video-switch-MCU, as
          specified in <xref target="RFC7667"/>.</t>
</li></ul> target="RFC7667"/>.</t></aside>

          <t>A general usage of media representation in SDP is as follows:</t>

<figure><artwork><![CDATA[

<artwork><![CDATA[
m=video 49170 RTP/AVP 98
a=rtpmap:98 evc/90000
a=fmtp:98 profile-id=1;
  sprop-sps=<sequence parameter set data>;
  sprop-pps=<picture parameter set data>;
]]></artwork></figure>
]]></artwork>

          <t>A SIP offer/answer Offer/Answer exchange wherein both parties are expected to
          both send and receive could look like the following. Only the media
          codec-specific parts of the SDP are shown.</t>

<figure><artwork><![CDATA[

<artwork><![CDATA[
Offerer->Answerer:
      m=video 49170 RTP/AVP 98
      a=rtpmap:98 evc/90000
      a=fmtp:98 profile-id=1; level_id=90;

]]></artwork></figure>

<ul empty="true"><li>
]]></artwork>

          <t>The above represents an offer for symmetric video communication
          using <xref target="EVC"/> and its payload specification at the main
          profile and level 3.0. 3.  Informally speaking, this offer tells the
          receiver of the offer that the sender is willing to receive up to
          xKpxx resolution at the maximum bitrates specified in <xref
          target="EVC"/>. At the same time, if this offer were accepted &quot;as is&quot;, "as
          is", the offer can expect that the answerer Answerer would be able to receive
          and properly decode EVC media up to and including level 3.0.</t>
</li></ul>

<figure><artwork><![CDATA[ 3.</t>

          <artwork><![CDATA[
Answerer->Offerer:
      m=video 49170 RTP/AVP 98
      a=rtpmap:98 evc/90000
      a=fmtp:98 profile-id=1; level_id=60
]]></artwork></figure>

<ul empty="true"><li>
  <ul empty="true"><li>
    <t>Informative
]]></artwork>

          <aside><t>Informative note: level_id shall be set equal to a
          value of 30 times the level number specified in Table A.1 of EVC.</t>
  </li></ul>
</li></ul>
          <xref target="EVC"/>.</t></aside>

          <t>With this answer to the offer above, the system receiving the
          offer advises the offerer Offerer that it is incapable of handing handling evc at
          level 3.0 3 but is capable of decoding level 2. As EVC video codecs
          must support decoding at all levels below the maximum level they
          implement, the resulting user experience would likely be that both
          systems send video at level 2. However, nothing prevents an encoder
          from further downgrading its sending to, for example, level 1 if it
          were short of cycles or bandwidth or for other reasons.</t>

<!-- Section 7.3.2 -->
	</section>
        <section anchor="sdpoa"><name>Usage anchor="sdpoa">
          <name>Usage with SDP Offer/Answer Model</name>
          <t>This section describes the negotiation of unicast messages using the offer/answer Offer/Answer model described in <xref target="RFC3264"/> and its updates.</t>
          <t>This section applies to all profiles defined in <xref target="EVC"/>, specifically to Baseline, Main, and the associated still image profiles.</t>
          <t>The following limitations and rules pertaining to the media configuration apply:</t>
          <t>The parameters identifying a media format configuration for EVC are profile-id and level-id. Profile_id MUST <bcp14>MUST</bcp14> be used symmetrically.</t>

          <t>The answerer MUST Answerer <bcp14>MUST</bcp14> structure its answer according to one of the following three two options:</t>
          <ul empty="true"><li>
  <t><list style="symbols">
    <t>maintain spacing="normal">
            <li>maintain all configuration parameters with the values
            remaining the same as in the offer for the media format (payload
            type), with the exception that the value of level-id is changeable
            as long as the highest level indicated by the answer is not higher
            than that indicated by the offer; or</t>
  </list></t>
</li></ul>

<ul empty="true"><li>
  <t><list style="symbols">
    <t>remove or</li>
            <li>remove the media format (payload type) completely (when one or
            more of the parameter values are not supported).</t>
  </list></t>
</li></ul>

<t>Informative supported).</li>
          </ul>

          <aside><t>Informative note: The above requirement for symmetric use does not apply for level-id and does not apply for the other bitstream or RTP stream properties and capability parameters, as described in <xref target="formatconfig"/> (Payload format config) below.</t> ("<xref target="formatconfig" format="title"/>").</t></aside>
          <t>To simplify handling and matching of these configurations, the same RTP payload type number used in the offer SHOULD <bcp14>SHOULD</bcp14> also be used in the answer, as specified in <xref target="RFC3264"></xref>.</t> target="RFC3264"/>.</t>
          <t>The answer MUST NOT <bcp14>MUST NOT</bcp14> contain a payload type number used in the offer for the media subtype unless the configuration is the same as in the offer or the configuration in the answer only differs from that in the offer with a different value of level-id.</t>

<!-- Section 7.3.2.x -->

<section anchor="formatconfig"><name>Payload anchor="formatconfig">
            <name>Payload Format Configuration</name>
            <t>The following limitations and rules pertain to the configuration of the payload format buffer management.</t>

<t>The
	    <ul spacing="normal">
              <li><t>The parameters sprop-max-don-diff and sprop-depack-buf-bytes describe the properties of an RTP stream that the offerer Offerer or the answerer Answerer is sending for the media format configuration. This differs from the normal usage of the offer/answer Offer/Answer parameters; normally, such parameters declare the properties of the bitstream or RTP stream that the offerer Offerer or the answerer Answerer is able to receive. When dealing with EVC, the offerer Offerer assumes that the answerer Answerer will be able to receive media encoded using the configuration being offered.</t>

<t>Informative offered.</t></li>
	    </ul>
            <aside><t>Informative note: The above parameters apply for any RTP stream, when present, sent by a declaring entity with the same configuration. In other words, the applicability of the above parameters to RTP streams depends on the source endpoint. Rather than being bound to the payload type, the values may have to be applied to another payload type when being sent, as they apply for the configuration.</t>

<t>When configuration.</t></aside>
	    <ul spacing="normal">
              <li><t>When an offerer Offerer offers an interleaved stream, indicated
              by the presence of sprop-max-don-diff with a value larger than
              zero, the offerer MUST Offerer <bcp14>MUST</bcp14> include the size of the
              de-packetization buffer sprop-depack-buf-bytes.</t>

<t>To sprop-depack-buf-bytes.</t></li>
              <li><t>To enable the offerer Offerer and answerer Answerer to inform each other
              about their capabilities for de-packetization buffering in
              receiving RTP streams, both parties are RECOMMENDED
              <bcp14>RECOMMENDED</bcp14> to include depack-buf-cap.</t>

<t>The depack-buf-cap.</t></li>
              <li><t>The parameters sprop-sps, sprop-sps or sprop-pps, when present
              (included in the &quot;a=fmtp&quot; "a=fmtp" line of SDP or conveyed using the &quot;fmtp&quot;
              "fmtp" source attribute, as specified in Section 6.3 of <xref target="RFC5576"></xref>), target="RFC5576"
              sectionFormat="of" section="6.3"/>), are used for out-of-band
              transport of the parameter sets (SPS or PPS, respectively).  The answerer MAY
              Answerer <bcp14>MAY</bcp14> use either out-of-band or in-band
              transport of parameter sets for the bitstream it is sending,
              regardless of whether out-of-band parameter sets transport has
              been used in the offerer-to-answerer Offerer-to-Answerer direction. Parameter sets
              included in an answer are independent of those parameter sets
              included in the offer, as they are used for decoding two
              different bitstreams; bitstreams: one from the answerer Answerer to the offerer Offerer, and
              the other in the opposite direction. In case some RTP packets
              are sent before the SDP offer/answer Offer/Answer settles down, in-band
              parameter sets MUST <bcp14>MUST</bcp14> be used for those RTP stream
              parts sent before the SDP offer/answer.</t>

<t>The Offer/Answer.</t></li>
              <li><t>The following rules apply to transport of parameter sets
              in the offerer-to-answerer Offerer-to-Answerer direction.</t>

<t>An
	      <ul spacing="normal">
		<li><t>An offer MAY <bcp14>MAY</bcp14> include sprop-sps, sprop-sps and/or
		sprop-pps. If none of these parameters are present in the
		offer, then only in-band transport of parameter sets is used.</t>

<t>If
		used.</t></li>
		<li><t>If the level to use in the offerer-to-answerer Offerer-to-Answerer
		direction is equal to the default level in the offer, the answerer MUST
		Answerer <bcp14>MUST</bcp14> be prepared to use the parameter
		sets included in sprop-sps, sprop-sps and sprop-pps (either included in
		the &quot;a=fmtp&quot; "a=fmtp" line of SDP or conveyed using the &quot;fmtp&quot; "fmtp" source
		attribute) for decoding the incoming bitstream, e.g., by
		passing these parameter set NAL units to the video decoder
		before passing any NAL units carried in the RTP
		streams. Otherwise, the answerer MUST Answerer <bcp14>MUST</bcp14> ignore
		sprop-vps, sprop-sps, and sprop-pps (either included in the &quot;a=fmtp&quot;
		"a=fmtp" line of SDP or conveyed using the &quot;fmtp&quot; "fmtp" source attribute)
		attribute), and the offerer MUST Offerer <bcp14>MUST</bcp14> transmit
		parameter sets in-band.</t>

<t>The in-band.</t></li>
	      </ul></li>
            <li><t>The following rules apply to transport of parameter sets in
            the answerer-to-offerer Answerer-to-Offerer direction.</t>

<t>An
	    <ul spacing="normal">
              <li><t>An answer MAY <bcp14>MAY</bcp14> include sprop-sps, sprop-sps and/or
              sprop-pps. If none of these parameters are present in the
              answer, then only in-band transport of parameter sets is used.</t>

<t>The offerer MUST
              used.</t></li>
              <li><t>The Offerer <bcp14>MUST</bcp14> be prepared to use the
              parameter sets included in sprop-sps and sprop-pps (either
              included in the &quot;a=fmtp&quot; "a=fmtp" line of SDP or conveyed using the &quot;fmtp&quot;
              "fmtp" source attribute) for decoding the incoming bitstream,
              e.g., by passing these parameter set NAL units to the video
              decoder before passing any NAL units carried in the RTP streams.</t>

<t>When
              streams.</t></li>
	    </ul></li>
            <li><t>When sprop-sps and/or sprop-pps are conveyed using the &quot;fmtp&quot;
            "fmtp" source attribute, as specified in Section 6.3 of <xref target="RFC5576"></xref>, target="RFC5576"
            sectionFormat="of" section="6.3"/>, the receiver of the parameters MUST
            <bcp14>MUST</bcp14> store the parameter sets included in sprop-sps
            and/or sprop-pps and associate them with the source given as part
            of the &quot;fmtp&quot; "fmtp" source attribute. Parameter sets associated with one
            source (given as part of the &quot;fmtp&quot; "fmtp" source attribute) MUST
            <bcp14>MUST</bcp14> only be used to decode NAL units conveyed in
            RTP packets from the same source (given as part of the &quot;fmtp&quot; "fmtp"
            source attribute). When this mechanism is in use, SSRC collision
            detection and resolution MUST <bcp14>MUST</bcp14> be performed as
            specified in <xref target="RFC5576"></xref>.</t> target="RFC5576"/>.</t></li>
	  </ul>
            <t><xref target="params-interpretation"/> lists the interpretation of all the parameters that MAY <bcp14>MAY</bcp14> be used for the various combinations of offer, answer, and direction attributes.</t>

            <figure anchor="params-interpretation"><artwork><![CDATA[ anchor="params-interpretation">
	      <name>Interpretation of Parameters for Various Combinations of
	      Offers, Answers, and Direction Attributes</name>
              <artwork><![CDATA[
                                 sendonly --+
                              recvonly --+  |
                           sendrecv --+  |  |
                                      |  |  |
   profile-id                         C  C  P
   level-id                           D  D  P
   toolset-id                         C  C  P
   max-recv-level-id                  R  R  -
   sprop-max-don-diff                 P  -  P
   sprop-depack-buf-bytes             P  -  P
   depack-buf-cap                     R  R  -
   sprop-sei                          P  -  P
   sprop-sps                          P  -  P
   sprop-pps                          P  -  P

Legend:

 C: configuration for sending and receiving bitstreams
 D: changeable configuration, configuration; same as C, except possible to
    answer with a different but consistent value (see the semantics
    of the level-id parameter on these parameters being
    consistent-basically,
    consistent -- basically, level down-grading is allowed)

 P: properties of the bitstream to be sent
 R: receiver capabilities
 -: not usable, usable; when present MUST be ignored

Interpretation of Parameters for Various Combinations of
Offers, Answers, and Direction Attributes.

]]></artwork></figure> ignored]]></artwork>
            </figure>

            <t>Parameters used for declaring receiver capabilities are, in general, downgradable, i.e., they express the upper limit for a sender&#39;s sender's possible behavior. Thus, a sender MAY <bcp14>MAY</bcp14> select to set its encoder using only lower/lesser or equal values of these parameters.</t>
            <t>When a sender&#39;s sender's capabilities are declared with the configuration parameters, these parameters express a configuration that is acceptable for the sender to receive bitstreams. In order to achieve high interoperability levels, it is often advisable to offer multiple alternative configurations. It is impossible to offer multiple configurations in a single payload type. Thus, when multiple configuration offers are made, each offer requires its own RTP payload type associated with the offer.</t>
            <t>An implementation SHOULD <bcp14>SHOULD</bcp14> be able to understand all media type parameters (including all optional media type parameters), even if it doesn&#39;t doesn't support the functionality related to the parameter. This, in conjunction with proper application logic in the implementation, allows the implementation, after having received an offer, to create an answer by potentially downgrading one or more of the optional parameters to the point where the implementation can cope, leading cope. This leads to higher chances of interoperability beyond the most basic interop points (for which, as described above, no optional parameters are necessary).</t>

<t>Informative
            <aside><t>Informative note: In implementations of various H.26x video coding payload Formats formats including those for <xref target="AVC"/> and <xref target="HEVC"/>, it was occasionally observed that implementations were incapable of parsing most (or all) of the optional parameters and hence rejected offers other than the most basic offers. As a result, the offer/answer Offer/Answer exchange resulted in a baseline performance (using the default values for the optional parameters) with the resulting suboptimal user experience. However, there are valid reasons to forego the implementation complexity of implementing the parsing of some or all of the optional parameters, for example, when there is predetermined knowledge, not negotiated by an SDP-based offer/answer Offer/Answer process, of the capabilities of the involved systems (walled gardens, baseline requirements defined in application standards higher up in the stack, and similar).</t> similar).</t></aside>
            <t>An answerer MAY Answerer <bcp14>MAY</bcp14> extend the offer with additional media format configurations. However, to enable their usage, in most cases, a second offer is required from the offerer Offerer to provide the bitstream property parameters that the media sender will use. This also has the effect that the offerer Offerer has to be able to receive this media format configuration, and not only to send it.</t>
          </section>
        </section>
        <section anchor="multicast"><name>Multicast</name> anchor="multicast">
          <name>Multicast</name>
          <t>For bitstreams being delivered over multicast, the following rules apply:</t>

<t>The
	  <ul spacing="normal">
            <li><t>The media format configuration is identified by profile-id
            and level-id. These media format configuration parameters,
            including level-id, MUST <bcp14>MUST</bcp14> be used symmetrically;
            that is, the answerer MUST Answerer <bcp14>MUST</bcp14> either maintain all
            configuration parameters or remove the media format (payload type)
            completely. Note that this implies that the level-id for offer/answer
            Offer/Answer in multicast is not changeable.</t>

<t>To changeable.</t></li>
            <li><t>To simplify the handling and matching of these
            configurations, the same RTP payload type number used in the offer SHOULD
            <bcp14>SHOULD</bcp14> also be used in the answer, as specified in
            <xref target="RFC3264"></xref>. target="RFC3264"/>. An answer MUST NOT <bcp14>MUST NOT</bcp14>
            contain a payload type number used in the offer unless the
            configuration is the same as in the offer.</t>

<t>Parameter offer.</t></li>
            <li><t>Parameter sets received MUST <bcp14>MUST</bcp14> be associated
            with the originating source and MUST <bcp14>MUST</bcp14> only be used
            in decoding the incoming bitstream from the same source.</t>

<t>The source.</t></li>
            <li><t>The rules for other parameters are the same as above for
            unicast as long as the three above rules are obeyed.</t> obeyed.</t></li>
	  </ul>
        </section>
        <section anchor="declativeSessiondesc"><name>Usage anchor="declativeSessiondesc">
          <name>Usage in Declarative Session Descriptions</name>
          <t>When EVC over RTP is offered with SDP in a declarative style, as in Real Time the Real-Time Streaming Protocol (RTSP) <xref target="RFC7826"></xref> target="RFC7826"/> or Session Announcement Protocol (SAP) <xref target="RFC2974"></xref>, target="RFC2974"/>, the following considerations apply.</t>

<t>All
	  <ul spacing="normal">
            <li><t>All parameters capable of indicating both bitstream properties and receiver capabilities are used to indicate only bitstream properties. For example, in this case, the parameters profile-id and level-id declare the values used by the bitstream, not the capabilities for receiving bitstreams. As a result, the following interpretation of the parameters MUST <bcp14>MUST</bcp14> be used:</t>

<ul><li>
          <t>Declaring actual configuration or bitstream properties:</t>

<t>profile-id
level-id
sprop-sps
sprop-pps
sprop-max-don-diff
sprop-depack-buf-bytes
sprop-sei</t>
<ul spacing="compact"><li><t>profile-id</t></li>
<li><t>level-id</t></li>
<li><t>sprop-sps</t></li>
<li><t>sprop-pps</t></li>
<li><t>sprop-max-don-diff</t></li>
<li><t>sprop-depack-buf-bytes</t></li>
<li><t>sprop-sei</t></li></ul></li>
<li>
         <t>Not usable (when present, they MUST <bcp14>MUST</bcp14> be ignored):</t>

<t>depack-buf-cap
recv-sublayer-id</t>
<ul spacing="compact"><li>
          <t>depack-buf-cap</t></li>
<li><t>recv-sublayer-id</t></li>
</ul>
</li>
<li>          <t>A receiver of the SDP is required to support all parameters and values of the parameters provided; otherwise, the receiver MUST <bcp14>MUST</bcp14> reject (RTSP) or not participate in (SAP) the session. It falls on the creator of the session to use values that are expected to be supported by the receiving application.</t> application.</t></li>
</ul>
	    </li>
	  </ul>
        </section>
        <section anchor="consider4pps"><name>Considerations anchor="consider4pps">
          <name>Considerations for Parameter Sets</name>
          <t>When out-of-band transport of parameter sets is used, parameter sets MAY <bcp14>MAY</bcp14> still be additionally transported in-band unless explicitly disallowed by an application, and some of these additional parameter sets may update some of the out-of-band transported parameter sets. An update of a parameter set refers to the sending of a parameter set of the same type using the same parameter set ID but with different values for at least one other parameter of the parameter set.</t>

<!-- Section 8 -->

</section>
      </section>
    </section>
    <section anchor="FeedbackMessage"><name>Use anchor="FeedbackMessage">
      <name>Use with Feedback Messages</name>

      <t>The following subsections define the use of the Picture Loss Indication (PLI) <xref target="RFC4585" format="default"/> and Full Intra Request (FIR) <xref target="RFC5104" format="default"/> feedback messages with <xref target="EVC"/>. The PLI is defined in <xref target="RFC4585"/>, and the FIR message is defined in <xref target="RFC5104"/>.</t> target="EVC"/>.</t>
      <t>In accordance with this document, a sender MUST NOT <bcp14>MUST NOT</bcp14> send Slice Loss Indication (SLI) or Reference Picture Selection Indication (RPSI), (RPSI); and a receiver MUST <bcp14>MUST</bcp14> ignore RPSI and MUST <bcp14>MUST</bcp14> treat a received SLI as a received PLI, ignoring the &quot;First&quot;, &quot;Number&quot;, "First", "Number", and &quot;PictureID&quot; "PictureID" fields of the PLI.</t>

<!-- Section 8.1 -->

      <section anchor="PLI"><name>Picture anchor="PLI">
        <name>Picture Loss Indication (PLI)</name>
        <t>As specified in Section 6.3.1 of <xref target="RFC4585"/>, target="RFC4585" sectionFormat="of" section="6.3.1"/>, the reception of a PLI by a media sender indicates &quot;the "the loss of an undefined amount of coded video data belonging to one or more pictures&quot;. pictures". Without having any specific knowledge of the setup of the bitstream (such as use and location of in-band parameter sets, IDR picture locations, picture structures, and so forth), a reaction to the reception of a PLI by a an EVC sender SHOULD <bcp14>SHOULD</bcp14> be to send an IDR picture and relevant parameter sets, potentially with sufficient redundancy so as to ensure correct reception. However, sometimes information about the bitstream structure is known. For example, such information can be parameter sets that have been conveyed out of band through mechanisms not defined in this document and that are known to stay static for the duration of the session. In that case, it is obviously unnecessary to send them in-band as a result of the reception of a PLI. Other examples could be devised based on a priori knowledge of different aspects of the bitstream structure. In all cases, the timing and congestion control congestion-control mechanisms of <xref target="RFC4585"/> MUST <bcp14>MUST</bcp14> be observed.</t>

<!-- Section 8.2 -->

</section>
      <section anchor="FIR"><name>Full anchor="FIR">
        <name>Full Intra Request (FIR)</name>
        <t>The purpose of the FIR message is to force an encoder to send an independent decoder refresh point as soon as possible while observing applicable congestion-control-related constraints, such as those set out in <xref target="RFC8082"/>.</t>
        <t>Upon reception of a FIR, a sender MUST <bcp14>MUST</bcp14> send an IDR picture. Parameter sets MUST <bcp14>MUST</bcp14> also be sent, except when there is a priori knowledge that the parameter sets have been correctly established. A typical example for that is an understanding between the sender and receiver, established by means outside this document, that parameter sets are exclusively sent out of band.</t>
      </section>
    </section>
    <section anchor="Security"><name>Security anchor="Security">
      <name>Security Considerations</name>
      <t>The scope of this section is limited to the payload format itself and to one feature of <xref target="EVC"/> that may pose a particularly serious security risk if implemented naively. The payload format, in isolation, does not form a complete system. Implementers are advised to read and understand relevant security-related documents, especially those pertaining to RTP (see the Security Considerations section in <xref target="RFC3550"/>) target="RFC3550" sectionFormat="of" section="14"/>) and the security of the call-control stack chosen (that may make use of the media type registration of this document). Implementers should also consider known security vulnerabilities of video coding and decoding implementations in general and avoid those.</t>
      <t>Within this RTP payload format, and with the exception of the user data SEI message as described below, no security threats other than those common to RTP payload formats are known. In other words, neither the various media-plane-based mechanisms nor the signaling part of this document seem to pose a security risk beyond those common to all RTP-based systems.</t>
      <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"/>, 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"/>.  However, as &quot;Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution&quot; "<xref target="RFC7202" format="title"/>" <xref target="RFC7202"/> target="RFC7202" format="default"/> discusses, it is not an RTP payload format&#39;s format's responsibility to discuss or mandate what solutions are used to meet the basic security goals like confidentiality, integrity integrity, and source authenticity for RTP in general.  This responsibility lays lies on anyone using RTP in an application.  They can find guidance on available security mechanisms and important considerations in &quot;Options for Securing RTP Sessions&quot; "<xref target="RFC7201" format="title"/>" <xref target="RFC7201"/>. target="RFC7201" format="default"/>. Applications SHOULD <bcp14>SHOULD</bcp14> use one or more appropriate strong security mechanisms.  The rest of this section discusses the security impacting properties of the payload format itself.</t>
      <t>Because the data compression used with this payload format is applied end-to-end, end to end, any encryption needs to be performed after compression. A potential denial-of-service threat exists for data encodings using compression techniques that have non-uniform receiver-end computational load.  The attacker can inject pathological datagrams into the bitstream that are complex to decode and that cause the receiver to be overloaded.</t>
      <t>EVC is particularly vulnerable to such attacks, as it is extremely simple to generate datagrams containing NAL units that affect the decoding process of many future NAL units. Therefore, the usage of data origin authentication and data integrity protection of at least the RTP packet is RECOMMENDED <bcp14>RECOMMENDED</bcp14> based on the thoughts of <xref target="RFC7202"/>.</t>
      <t>Like HEVC <xref target="RFC7798"/> and VVC <xref target="VVC"/>, EVC <xref target="EVC"/> includes a user data Supplemental Enhancement Information (SEI) message. This SEI message allows inclusion of an arbitrary bitstring into the video bitstream. Such a bitstring could include JavaScript, machine code, and other active content.</t>

<t><xref target="EVC"></xref>
      <t>EVC <xref target="EVC"/> leaves the handling of this SEI message to the receiving system. In order to avoid harmful side effects of the user data SEI message, decoder implementations cannot naively trust its content. For example, forwarding all received JavaScript code detected by a decoder implementation to a web-browser web browser unchecked would be a bad and insecure implementation practice. The safest way to deal with user data SEI messages is to simply discard them, but that can have negative side effects on the quality of experience by the user.</t>
      <t>End-to-end security with authentication, integrity, or confidentiality protection will prevent a MANE from performing media-aware operations other than discarding complete packets.  In the case of confidentiality protection, it will even be prevented from discarding packets in a media-aware way.  To be allowed to perform such operations, a MANE is required to be a trusted entity that is included in the security context establishment.</t>
    </section>
    <section anchor="CC"><name>Congestion anchor="CC">
      <name>Congestion Control</name>
      <t>Congestion control for RTP SHALL <bcp14>SHALL</bcp14> be used in accordance with RTP <xref target="RFC3550"/> and with any applicable RTP profile, e.g., AVP <xref target="RFC3551"/> or AVPF <xref target="RFC4585"/>. If best-effort service is being used, an additional requirement is that users of this payload format MUST <bcp14>MUST</bcp14> monitor packet loss to ensure that the packet loss rate is within an acceptable range. Packet loss is considered acceptable if a TCP flow across the same network path and experiencing the same network conditions would achieve an average throughput, measured on a reasonable timescale, that is not less than all RTP streams combined are achieved. combined. This condition can be satisfied by implementing congestion-control mechanisms to adapt the transmission rate, rate by implementing the number of layers subscribed for a layered multicast session, session or by arranging for a receiver to leave the session if the loss rate is unacceptably high.</t>
      <t>The bitrate adaptation necessary for obeying the congestion control principle is easily achievable when real-time encoding is used, for example, by adequately tuning the quantization parameter. However, when pre-encoded content is being transmitted, bandwidth adaptation requires the pre-coded bitstream to be tailored for such adaptivity.</t>
      <t>The key mechanism available in <xref target="EVC"></xref> target="EVC"/> is temporal scalability. A media sender can remove NAL units belonging to higher temporal sub-layers (i.e., those NAL units with a large value of TID) until the sending bitrate drops to an acceptable range.</t>
      <t>The mechanisms mentioned above generally work within a defined profile and level; therefore therefore, no renegotiation of the channel is required. Only when non-downgradable parameters (such as the profile) are required to be changed does it become necessary to terminate and restart the RTP stream(s). streams. This may be accomplished by using different RTP payload types.</t>
      <t>MANEs MAY <bcp14>MAY</bcp14> remove certain unusable packets from the RTP stream when that RTP stream was damaged due to previous packet losses. This can help reduce the network load in certain special cases. For example, MANEs can remove those FUs where the leading FUs belonging to the same NAL unit have been lost, because the trailing FUs are meaningless to most decoders. MANE can also remove higher temporal scalable layers if the outbound transmission (from the MANE&#39;s MANE's viewpoint) experiences congestion.</t>
    </section>
    <section anchor="iana-considerations"><name>IANA anchor="iana-considerations">
      <name>IANA Considerations</name>

<t>A new
      <t>The media type, as type specified in <xref target="oparams"/> of this document, has been registered with IANA.</t>
    </section>
<section anchor="acknowledgements"><name>Acknowledgements</name>

<t>Large parts of this specification share text with the RTP payload format for VVC <xref target="RFC9328"/>. Roman Chernyak is thanksed for his valueable review comments. We thank the authors of that specification for their excellent work.</t>

</section>

  </middle>
  <back>

    <references title='Normative References'>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>

        <reference anchor="ISO23094-1" anchor="EVC" target="https://www.iso.org/standard/57797.html">
          <front>
    <title>ISO/IEC DIS Information
            <title>Information technology --- -- General video coding --- -- Part 1 1: Essential video
coding</title>
    <author >
      <organization></organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>
<reference anchor="EVC" target="https://www.iso.org/standard/57797.html">
  <front>
    <title>ISO/IEC 23094-1 Essential Video Coding</title>
    <author >
      <organization></organization>
            <author>
              <organization/>
            </author>
            <date year="2020"/>
  </front>
</reference>

<reference anchor="RFC9328">
  <front>
    <title>RTP Payload Format for Versatile Video Coding (VVC)</title>
    <author fullname="S. Zhao" initials="S." surname="Zhao"/>
    <author fullname="S. Wenger" initials="S." surname="Wenger"/>
    <author fullname="Y. Sanchez" initials="Y." surname="Sanchez"/>
    <author fullname="Y.-K. Wang" initials="Y.-K." surname="Wang"/>
    <author fullname="M. M Hannuksela" initials="M. M" surname="Hannuksela"/>
    <date month="December" year="2022"/>
    <abstract>
      <t>This memo describes an RTP payload format for the Versatile Video Coding (VVC) specification, which was published as both ITU-T Recommendation H.266 and ISO/IEC International Standard 23090-3. VVC was developed by the Joint Video Experts Team (JVET). The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload, as well as fragmentation of a NAL unit into multiple RTP packets. The payload format has wide applicability in videoconferencing, Internet video streaming, and high-bitrate entertainment-quality video, among other applications.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9328"/>
  <seriesInfo name="DOI" value="10.17487/RFC9328"/>
</reference>

<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="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="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="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="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="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="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="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="June" 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>

<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="RFC4648">
  <front>
    <title>The Base16, Base32, and Base64 Data Encodings</title>
    <author fullname="S. Josefsson" initials="S." surname="Josefsson"/>
    <date month="October" year="2006"/>
    <abstract>
      <t>This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4648"/>
  <seriesInfo name="DOI" value="10.17487/RFC4648"/>
</reference>

<reference anchor="RFC5576">
  <front>
    <title>Source-Specific Media Attributes in the Session Description Protocol (SDP)</title>
    <author fullname="J. Lennox" initials="J." surname="Lennox"/>
    <author fullname="J. Ott" initials="J." surname="Ott"/>
    <author fullname="T. Schierl" initials="T." surname="Schierl"/>
    <date month="June" year="2009"/>
    <abstract>
      <t>The Session Description Protocol (SDP) provides mechanisms to describe attributes of multimedia sessions and of individual media streams (e.g., Real-time Transport Protocol (RTP) sessions) within a multimedia session, but does not provide any mechanism to describe individual media sources within a media stream. This document defines a mechanism to describe RTP media sources, which are identified by their synchronization source (SSRC) identifiers, in SDP, to associate attributes with these sources, and to express relationships among sources. It also defines several source-level attributes that can be used to describe properties of media sources. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5576"/>
  <seriesInfo name="DOI" value="10.17487/RFC5576"/>
</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="RFC8082">
  <front>
    <title>Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs</title>
    <author fullname="S. Wenger" initials="S." surname="Wenger"/>
    <author fullname="J. Lennox" initials="J." surname="Lennox"/>
    <author fullname="B. Burman" initials="B." surname="Burman"/>
    <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
    <date month="March" year="2017"/>
    <abstract>
      <t>This document updates RFC 5104 by fixing a shortcoming in the specification language of the Codec Control Message Full Intra Request (FIR) description when using it with layered codecs. In particular, a decoder refresh point needs to be sent by a media sender when a FIR is received on any layer of the layered bitstream, regardless of whether those layers are being sent in a single or in multiple RTP flows. The other payload-specific feedback messages defined in RFC 5104 and RFC 4585 (which was updated by RFC 5506) have also been analyzed, and no corresponding shortcomings have been found.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8082"/>
  <seriesInfo name="DOI" value="10.17487/RFC8082"/>
</reference>

<reference anchor="RFC7826">
  <front>
    <title>Real-Time Streaming Protocol Version 2.0</title>
    <author fullname="H. Schulzrinne" initials="H." surname="Schulzrinne"/>
    <author fullname="A. Rao" initials="A." surname="Rao"/>
    <author fullname="R. Lanphier" initials="R." surname="Lanphier"/>
    <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
    <author fullname="M. Stiemerling" initials="M." role="editor" surname="Stiemerling"/>
    <date month="December" year="2016"/>
    <abstract>
      <t>This memorandum defines the Real-Time Streaming Protocol (RTSP) version 2.0, which obsoletes RTSP version 1.0 defined in RFC 2326.</t>
      <t>RTSP is an application-layer protocol for the setup and control of the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. Sources of data can include both live data feeds and stored clips. This protocol is intended to control multiple data delivery sessions; provide a means for choosing delivery channels such as UDP, multicast UDP, and TCP; and provide a means for choosing delivery mechanisms based upon RTP (RFC 3550).</t>
    </abstract> year="2020"/>
          </front>
          <seriesInfo name="RFC" value="7826"/>
  <seriesInfo name="DOI" value="10.17487/RFC7826"/> name="ISO/IEC" value="23094-1:2020"/>
        </reference>

        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9328.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3551.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3711.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4585.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5124.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3264.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8866.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5576.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5104.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8082.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7826.xml"/>

        <reference anchor="VSEI" target="https://www.itu.int/rec/T-REC-H.274">
          <front>
            <title>Versatile supplemental enhancement information messages for coded video bitstreams</title>
    <author >
      <organization></organization>
            <author>
              <organization>ITU-T</organization>
            </author>
            <date year="2020"/> month="March" year="2024"/>
          </front>
	  <seriesInfo name="ITU-T Recommendation" value="H.274"/>
        </reference>

      </references>

    <references title='Informative References'>
      <references>
        <name>Informative References</name>

        <reference anchor="MPEG2S" > anchor="MPEG2S">
          <front>
            <title>Information technology - Generic coding ofmoving of moving pictures and associated audio information - Part 1:Systems, ISO International Standard 13818-1</title>
    <author initials="" surname="IS0/IEC" fullname="IS0/IEC">
      <organization></organization> 1: Systems</title>
            <author>
              <organization>IS0/IEC</organization>
            </author>
            <date month="June" year="2013"/>
          </front>
</reference>

<reference anchor="RFC6184">
  <front>
    <title>RTP Payload Format for H.264 Video</title>
    <author fullname="Y.-K. Wang" initials="Y.-K." surname="Wang"/>
    <author fullname="R. Even" initials="R." surname="Even"/>
    <author fullname="T. Kristensen" initials="T." surname="Kristensen"/>
    <author fullname="R. Jesup" initials="R." surname="Jesup"/>
    <date month="May" year="2011"/>
    <abstract>
      <t>This memo describes an RTP Payload format for the ITU-T Recommendation H.264 video codec and the technically identical ISO/IEC International Standard 14496-10 video codec, excluding the Scalable Video Coding (SVC) extension and the Multiview Video Coding extension, for which the RTP payload formats are defined elsewhere. The RTP payload format allows for packetization of one or more Network Abstraction Layer Units (NALUs), produced by an H.264 video encoder, in each RTP payload. The payload format has wide applicability, as it supports applications from simple low bitrate conversational usage, to Internet video streaming with interleaved transmission, to high bitrate video-on-demand.</t>
      <t>This memo obsoletes RFC 3984. Changes from RFC 3984 are summarized in Section 14. Issues on backward compatibility to RFC 3984 are discussed in Section 15. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6184"/>
         <seriesInfo name="DOI" value="10.17487/RFC6184"/> name="ISO/IEC" value="13818-1:2013"/>
        </reference>

        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6184.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6190.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7656.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7667.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7201.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7202.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7798.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2974.xml"/>

        <reference anchor="RFC6190"> anchor="HEVC" target="https://www.itu.int/rec/T-REC-H.265">
          <front>
    <title>RTP Payload Format for Scalable Video Coding</title>
    <author fullname="S. Wenger" initials="S." surname="Wenger"/>
    <author fullname="Y.-K. Wang" initials="Y.-K." surname="Wang"/>
    <author fullname="T. Schierl" initials="T." surname="Schierl"/>
    <author fullname="A. Eleftheriadis" initials="A." surname="Eleftheriadis"/>
    <date month="May" year="2011"/>
    <abstract>
      <t>This memo describes an RTP payload format for Scalable Video Coding (SVC) as defined in Annex G of ITU-T Recommendation H.264, which is technically identical to Amendment 3 of ISO/IEC International Standard 14496-10. The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload, as well as fragmentation of a NAL unit in multiple RTP packets. Furthermore, it supports transmission of an SVC stream over a single as well as multiple RTP sessions. The payload format defines a new media subtype name "H264-SVC", but is still backward compatible to RFC 6184 since the base layer, when encapsulated in its own RTP stream, must use the H.264 media subtype name ("H264") and the packetization method specified in RFC 6184. The payload format has wide applicability in videoconferencing, Internet
            <title>High efficiency video streaming, and high-bitrate entertainment-quality video, among others. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6190"/>
  <seriesInfo name="DOI" value="10.17487/RFC6190"/>
</reference>

<reference anchor="RFC7656">
  <front>
    <title>A Taxonomy of Semantics and Mechanisms for Real-Time Transport Protocol (RTP) Sources</title>
    <author fullname="J. Lennox" initials="J." surname="Lennox"/>
    <author fullname="K. Gross" initials="K." surname="Gross"/>
    <author fullname="S. Nandakumar" initials="S." surname="Nandakumar"/>
    <author fullname="G. Salgueiro" initials="G." surname="Salgueiro"/>
    <author fullname="B. Burman" initials="B." role="editor" surname="Burman"/>
    <date month="November" year="2015"/>
    <abstract>
      <t>The terminology about, and associations among, Real-time Transport Protocol (RTP) sources can be complex and somewhat opaque. This document describes a number of existing and proposed properties and relationships among RTP sources and defines common terminology for discussing protocol entities and their relationships.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7656"/>
  <seriesInfo name="DOI" value="10.17487/RFC7656"/>
</reference>

<reference anchor="RFC7667">
  <front>
    <title>RTP Topologies</title>
    <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
    <author fullname="S. Wenger" initials="S." surname="Wenger"/> coding</title>
            <author>
              <organization>ITU-T</organization>
            </author>
            <date month="November" year="2015"/>
    <abstract>
      <t>This document discusses point-to-point and multi-endpoint topologies used in environments based on the Real-time Transport Protocol (RTP). In particular, centralized topologies commonly employed in the video conferencing industry are mapped to the RTP terminology.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7667"/>
  <seriesInfo name="DOI" value="10.17487/RFC7667"/>
</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> year="2019"/>
          </front>
	  <seriesInfo name="RFC" value="7202"/>
  <seriesInfo name="DOI" value="10.17487/RFC7202"/> name="ITU-T Recommendation" value="H.265"/>
        </reference>

	<reference anchor="RFC7798"> anchor="VIDEO-CODING" target="https://www.itu.int/rec/T-REC-H.263">
	  <front>
    <title>RTP Payload Format for High Efficiency Video Coding (HEVC)</title>
    <author fullname="Y.-K. Wang" initials="Y.-K." surname="Wang"/>
    <author fullname="Y. Sanchez" initials="Y." surname="Sanchez"/>
    <author fullname="T. Schierl" initials="T." surname="Schierl"/>
    <author fullname="S. Wenger" initials="S." surname="Wenger"/>
    <author fullname="M. M. Hannuksela" initials="M. M." surname="Hannuksela"/>
    <date month="March" year="2016"/>
    <abstract>
      <t>This memo describes an RTP payload format for the video
	    <title>Video coding standard ITU-T Recommendation H.265 and ISO/IEC International Standard 23008-2, both also known as High Efficiency Video Coding (HEVC) and developed by the Joint Collaborative Team on Video Coding (JCT-VC). The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload as well as fragmentation of a NAL unit into multiple RTP packets. Furthermore, it supports transmission of an HEVC bitstream over a single stream as well as multiple RTP streams. When multiple RTP streams are used, a single transport or multiple transports may be utilized. The payload format has wide applicability in videoconferencing, Internet video streaming, and high-bitrate entertainment-quality video, among others.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7798"/>
  <seriesInfo name="DOI" value="10.17487/RFC7798"/>
</reference>

<reference anchor="RFC2974">
  <front>
    <title>Session Announcement Protocol</title>
    <author fullname="M. Handley" initials="M." surname="Handley"/>
    <author fullname="C. Perkins" initials="C." surname="Perkins"/>
    <author fullname="E. Whelan" initials="E." surname="Whelan"/>
    <date month="October" year="2000"/>
    <abstract>
      <t>This document describes version 2 of the multicast session directory announcement protocol, Session Announcement Protocol (SAP), and the related issues affecting security and scalability that should be taken into account by implementors. This memo defines an Experimental Protocol for the Internet community.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2974"/>
  <seriesInfo name="DOI" value="10.17487/RFC2974"/>
</reference>

<reference anchor="HEVC" target="https://www.itu.int/rec/T-REC-H.265">
  <front>
    <title>High efficiency video coding, ITU-T Recommendation H.265</title>
    <author >
      <organization></organization> low bit rate communication</title>
	    <author>
	      <organization>ITU-T</organization>
            </author>
	    <date year="2019"/> month="January" year="2005"/>
	  </front>
	  <seriesInfo name="ITU-T Recommendation" value="H.263"/>
	</reference>

        <reference anchor="AVC" target="https://www.iso.org/standard/66069.html">
          <front>
    <title>ITU-T Recommendation H.264 -
            <title>Part 10: Advanced video coding for generic audiovisual services</title>
    <author >
      <organization></organization> coding</title>
            <author>
              <organization>ITU-T</organization>
            </author>
            <date month="October" year="2014"/>
          </front>
	  <seriesInfo name="ITU-T Recommendation" value="H.264"/>
        </reference>

        <reference anchor="VVC" target="http://www.itu.int/rec/T-REC-H.266">
          <front>
            <title>Versatile Video Coding, ITU-T Recommendation H.266</title>
    <author >
      <organization></organization> video coding</title>
            <author>
              <organization>ITU-T</organization>
            </author>
            <date month="August" year="2020"/>
          </front>
	  <seriesInfo name="ITU-T Recommendation" value="H.266"/>
        </reference>

      </references>
    </references>

    <section anchor="acknowledgements" numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>Large parts of this specification share text with the RTP payload
      format for VVC <xref target="RFC9328"/>. <contact fullname="Roman
      Chernyak"/> is thanked for his valuable review comments. We thank the
      authors of that specification for their excellent work.</t>
    </section>

  </back>

<!-- ##markdown-source:
H4sIAOeOgmUAA+2963IbR7Yu+B9PUSNFnCamAVqkJEqi246mSKrFM7pwE5T6
9PR2OApAgawWUIVdVSBFy97RP+f3xPw85zXmAeZR+klmXTNXZhVIyJb7MnPY
bpsEqvK6cl2/tXI4HPaavJln+8nZ+Wlymt7My3SavCirRdoks7JKjus6K5o8
nSfv82lWJoflNC8ukq3j94f9XjoeV9kVv7uUd2fm3feHvWk5KdIFtD+t0lkz
zLNmNkyvmklZZcOqWQ6zq8nwwZPeNG3gmd0Huw+HO7vDnWe9Xt2kxfT7dF4W
8EVTrTL8qMrSxX5ycnz+Iun18mVF39TN7oMHzx7s9lL4ej85ODvvXV/sJ9JL
78M1vFE0WVVkzfAIR9GbpM1+UjfTXm9C04GH60me95b5fvLnppwMkrqsoLNZ
Db/dLPCX73q9dNVcltV+L6Gfofw3SfKi3k9G28n/fpmW7kOe9OhylebhF2V1
weOZu49wXhmMaBfmkbzO6zovC1jo+Ty7yJLn86upe3KSNzfQalo0aXI4T6vU
f1NOob9njx88fmQ+WxVNBS+8Gx24D7NFms9h9jiy7R9gZL/PsyzbhmGtndgf
s+Iiq+KpNdnyMi3iL2l651kxAappT/DJoydAZNWHrlmdwl4nB/OmjOf06PHT
p5vNqcmus9/Tv9fP50/byat8EU3mT9DqxYdrWHb7Hc1llC5q+DI5nmeTpiqL
fFK35rW3t/s4Of44yWDLYObJH9ObeHLztIgn9uTxg52HG03s5sP8+jJvst9f
4N/bk3LR6xV0zvKrDAnyZPR29+GDZ4+GO0yecqbh469Ojg+To5MRkByfTKSt
JptcFuW8vLhJ/vbX/yv5Q1ZkFZzwKzrhfCToC9iqJtkxPMA+QR3VWZVndQ5t
7yfcc1pd4JJcNs2y3v/qq+vr6+28LnE/vqIjnVbTrx4/efLsyfZls5j34CVg
E52jlhmtYUE/qzd8x7GaB9j52YvDZw93n+7zr7s7O8/k14ePHz/wv+7or092
9Fcgy8fy6+Od3Ufy65O9x3vy69OdJ/rpw909/fXp0z194NHeI+348eMne66F
vSeu3QfutQdPd/WBp7v4LPzxfnR8EizdvfdZVcMez7OkXi2X82wBKwcLlxVw
VCf0V5IbQlhkdZ1eZDWxa6TKqWzxOG+Y29b31i90s9rOi+arKpt8dT48Oz4c
vtyGE95aZNch0yr88/r0+A+7o3DTu8lzyMSZT5Qsy9mivMJflvmkWVUwdNhl
YN91OcmhT/h1Nc3LYJJDoeP90Q3whgXwdKAwEQn0BCzQSIgl2Xn4dOfpcIeG
FjJ84R8nowdInREDsZ/q3Olww37t7TzVXdzbeaZE9QQe8L+6vX3yzNHiMyQf
+P1lfEBe5heXSTab5ZMc2M1NcCphcufvhufJWQZcAvZ7ymsAO7P3+PN2Up53
s3mGYzmIz+q6zh7Bsh9Mr5DqpiFjQVK7kE2lzbrK6xVsAbCSq3yS1Zsf7L29
B3vP2gd75xFT2ftorOZwWEZyy4rttYn/1hXba9H+cDhM0jEcpXTS9Hrnl3md
gEa0ooM4zepJlY+JhNepUM1ldqsKluhiDJLlajzP60s8ArXjoWuoXFjrNvLe
5Bqen2ZX2bxcwsvjG+r0NZ+yUz5lINyWWdXUyR+qcrVMtvAA97eTc3iwY+Dp
fF5e1278y3TyIWvyH3hdy1kCKh3I1mQB2lnyJmuuS1AIDmSR8JFX6U1WJVtv
Dl71k1UBnAhOXpKlk0vpDJtzfeLxx15mVXpB3E57SRNogN6H15syWazmTQ4s
0TRS8xSi4V/CeowrahtYaD5Jx/kchDgOggh5UhazrIKTx8QjqqUQOXNN+gZH
dglHdQjMtAKaAC4MjzZpXuA4h/8BRI/N0nvw9KJE9gZTqbRfnEm9zUS0yKfT
OejA97HDqpyueKnuKxv6dD83n/+EtLaWcj59gm3/6SdDOwmoF7C8ec1rMJ/f
IHXmFwWz1E3pCVr2mgh0QCuZZYWhTVhEPBnbSfIWqOCihFZgr5CesHfYpg9Z
ttQR/qZOnqd1Ns/h0WVVzvDoZjonGGNV3qTz5mY4AzUMCXdV4/Sc+ADNxPRM
5Nagyrr7ILnJ0grO3UWJhEiLfp3XWfKhKK8LHMU4A/sBdK10DF0iIa/g2+sc
5MEK6Dupsv9Y5RXLU/wWKAh75vFAtwNYUCARmD71miojlEngMuMZoZbSGtYS
u0F6KcpiOM2RLwANpU1Z3SRACVkhE6sWMKMSPrnZTp7DsInyW0ukhAeU5DqE
RdZtBzMJul2ChQMjgrnCM0iDyp+NYLkAWoVXr6AhkjnH/quIoF5K09Cz4/rR
Iwf0xKqYQmsTPgcJHqX8YlU5Uv98DgkdbycnDRg0KWoDyC3GaQ2yhQmYNo2W
SbnBEL6G0bWbo0Vi2RUNXYT4Tz8NktEkZaIIefEIebE8+OwBPnjrgm29PHYv
oMjHF3DtuiVUsgWirE8Po676009wev6I04IJL8EqwU2U2S4v83lZl8vLG7Bc
s8mqAg4zwGUGJY8YBvwKbGLO3eHOwkFK8oWqivIM/v2RXs2ZH9ZAj2BvIq2g
IMCTBZ3CcYBjAUdpnmdVvDk4tHzm2FiS0N7CPykOAuztclUnk8sSyHuALAZe
mcNhaOx64+PXsBLEj5bz8iZjhn/BFgt8zCcWSAm3uMrmGRBf4yeEtAZSHfcd
xgyDOBTKWwCTSIu8hgPFTcyqcmF3MLmGAwwNT8oKjoryQZSXqFmXKAxBmcSv
QHUhoiApwSIVFh4ERIPDLmGpirIB2gKhoccSl4jIzb4JzP1+8vYK1aDsGr8k
4Q+tARVkk+T+/V5PjvBAj9MgPHqfPr1nxo5nAdZZd+3yZlzlRg3L9HTAgpzg
0plDB6wrcywhTWA4NyAN82xG1OKHhjs/y1LWweETHChw1wbZywA3pC4XxDoX
sLvTaYV822kX3aQC3yPXzGlYfgdroMCrDOkNmCUIK2IhJLuYilFacrMqpVSw
JUvebWKeJQ+xhAFWYIogveXYPBI0nmic+Hw+hL9wVPhKeCxEWSAK0PbxaKTd
DDhNXiOdyUcDGt88bZAixxm2niIhwUSyRve61c54hWOczFfEBUJRomu/TQY0
6Fx1Kc/CfsBZp2MNtl1ylVY5nAnapDHKDNcNDtMOsh44RQueZZUAx+WMQTyO
0GUDqrvIDqSx4gKGenJ0piYZH4FZOkGyhoNTO3Z/DUc2mw4vYOlAKYiWV0UD
KuHVBJUWZBOgOeU4eHi4FALCXZujNwatBmFIoAvAyULef2NWrL6Bxj8mGXdT
C32S5AWeXCIZ4SQW6JFKzTRT+vgan5atWaQFNgxMCAwEFE0iLJuynNckUbOP
OOqaVZxg1WhVYaGWOXBjdyaJfWbKyb73c/1+Nk8vRGDTcd5Gc+awhF1f4pTn
wJWRacMiD9AeG5CByOID/is0AB0GIkR06veHr/pfw3eoSvBy5NhVA9uxqnlL
qwwZlQyPpznEaTqKk1N3l+o+EApa1StW1rDdWhuu2RZn9b1KixpZKh9IoBwY
Pkm2WtefmFZNLPK+TGl4joN6oSxoy7gZ+sAsgVvK1MfzcvLB9ISPoZ6+Imrt
9XD1YPJ4kuH7aS7KLb0myoLstntJ5zbNkU3WNESmqKmcOjI5pGeYAxhN8Pfe
o4+gXMxXC6CGFKnfG0mdPGRn9+lH+H/3G/bk8lZOQEsaoxQE8VPDMqD4oQFO
eTg1avbIf2hYzM7GUb9wDIF35D/gAIiwhvP8Q5aAsTIdNqRm85yWKWgBuFJ0
Ci691Ye6SC7Cg55NLssq/6FEPxQMCKd1hRrEhP4scVyzclW5wdXQVZUFYwxm
CrIEOrkuPSeMN4cP5X6y00+egxIN8uscbRb8L05g6/n5eX/9+FEDlzFIw2SC
fk0j3+0nIzDNmuQdmpVCX28r5Ft1ZsxP3g5QMC6EOGD0E5CA5MGix4WuZTVJ
+bDEN89mDZy6IXE1Jt1yiR8AB2/gWdAbisK3ZppHpgzsZi52Ggg6agPfxUap
LW4EP4JWo7a2WSPIOsSX8Hels5C20EyRQ8aihE+IPGtYJ+y6HhV4+iugZjja
fHIK3BYkg/k2H0uSah1n02gyQIpVNs2Z/Szgkzl6A1ckwJFMhMEmzc2SFRX/
eE2BmCpNtupliiZln8ZPNm6ypdpd376xnRygBMynK9k75J9AypPVnFREED/1
aszsEJ2U/CZ8MU2bVLb5Er0f+UWOE9mSpeijU4Spvc0JmDDLgs4zWERZg7RZ
4zOeoW0dHZ4Pd3kGpFVWeGgL53dBvusexofk28zNB4cohmveJgE8eLL8MA5U
fMoly+2GtsgPrTWw0fnwCQ8sLdjBgZuBe3HHdJ72iRq150En7xugrgj6Kizy
v9kJY3/nvr2Tf4NTL6Q0zWfkwWlAri+XsFFfTeY5/ZLMVgWTEnZlFxB2Hu2M
K9TYkh/yi+EP6UV8DIEWSIqyN10NaVUWtr1pfGi+VBvv4OgQTMKulcczhFQS
tHmVzleZ+Bfcp6gbYOfZRxIWqHlM0QLzmvccLSzkcT+A5msbXEN8smKkmwAb
gcavUfGtVgWwk+IC1EmiYJrB2avjfsICE5a1KlGRBOJgEqfeleamtmc4VHDa
0Sxd3mhsyQpl1ZjGzMxBnW0uF1njYwLOlkPFjZShw4PnB04l4pn5h5yWnHKT
SjCgkCxFtYHBj9Xtt1qiQxeY1AzWhdYxTeZl+QFFOtoNtzBMoIn8ihsXDk02
X6SV8oohxU7/kmLcVKXCIv0g4gOt9uxjw/yNjIcC2WWOTEuHrz2EFAGM9AS2
qgQ+D+MCxkar27nVYsTRqvPoaRx0KuhVtwY5u8cfwpEoso/Jf12zBEC2juKP
fGMvuDEg+KPnfRUQdG7SOpJdVorMVhXxDmCpK1AQ0Vqoc7LcyGGBBiYde5Dr
oEE2nboDihOehOoQTqTkwSrVgUalqnHOjEZJmcgDuZjILxeSGmcz3IRy1SxX
jUo5PJek3w69PEFx8jKdpgs8U55ZHZULHLYu1Mvzoxd98pygX5iHQmfZqoXS
p980VdOFVplYHYsilxFaAUgBpIA56rOKpqMZYn8w0iWpFK9wpdw+voLRee2v
zlACoe94blTf3ceG6+oaKzunieAmghCEEzFwTv0xGJtKfLIXQLQZW5+XVbm6
YAt1Amytds4mdxSIFSIXevTxER+q7WTE3AQ9BiVyBz6p0geqH4uMxgYjh4mR
aceT8ZbdAS4D93SqLyQjsOO3Dk5HfTpx4TbzgUO3pLpKflO3aAG3ZlE6B1xW
1NwFO7Xp6WU55890Acm5mSItVjgG3jkU6OV8xfQlBzM+7LDE2tkVLGdJsouk
7yJvcHW5V4rUoKaKirMoSbByRQayYFxW7JUwrUg01nnG5sjQgTJYBIUdkutE
pl9WeBLC75VcJmh939DW6z5U2ZxVWzUmlSZccwPynSC/yMTlmKIDn/4uyvU9
5bXrxVEhN1GgZbwQZxJpc2rnM12RdxP5s2iEOE44nR/yJX3awY28tyb/aDkR
+xSMYz5X/abNPsgN7Jjsa57We9mLU09bwGxfvz/tD1oyRk7VxLgXQFRWF8Lw
RH1gbgizvSFVj9Yc6F7WkRc7dE/Vk0sQb9w+sV3DRkHlwzaNWu01Y/bdsx4/
z2tywEAb03xqXoHJyXriSPkUBHNPjvyWbr1+/f6oT6uqGoXyh8gXI4uAXeIS
4EZbSpcVw7nSjJTlXdLM8K3so4ohkR/eGVM3KJjQJChzdLIKBeKBzRt4hKlt
moPxrgFMeURZanxgmU63k3d0UrtpICQBpgC/mmF7wXYIY2YTR+091GZQu8W9
wjhLx+LImSDiUHMRJ2a4QPgkeYVon5z38FxZLJ7wcDpnjrPRdM5kW+Wg4NZe
pzfsxCIlAXtIJ5MV2GM3HBMO50xTafFPeP8ync/kT9CoV/O5+2NarlCO6p9s
JUzd36yv+AEVNp5Gp6NJL+C5egWPAQsEllTQ/uIizhFosJY5rdVoHCPB6R6R
MlINa+Qc8eqh5kORta0jXD3vohNtGI1YMpaBf8+JRNJmcsmWLB8ZdhCSrXaZ
xczfBUg9M2MqRQWCxGKVWnOdtVj4cKhqf+sRmCsqpcBTxTEfqcqqrCCbMO4a
drk6Jw8yJHUPbSO8dY1QpN1A52rQFukA5BIaiDzAT2ZInl6nibwQ9X5ydJhs
LTKgADLV1OOjh+ayLKewAd45NnB+MZE816VpfpqnF7SgjkXUa7TuPF5COb5G
eURnNraSFhcr5H9mttz37lO7h54r0cxo9j46rke+HIrUO2aw2VScK4YFHbmx
J1vHJ6dH/fWGg/jnvfxAFssNPiemdIjW4tbJ88O++CxwylcYVKRgIWvkcqC9
H7bNnCpje4TqyDSv4RAIak61pIKE8IVnFvDKJK9Ff3MaipWdPDr2ArqlEOcR
z17ChW5Q1o/QqF4BB+jMMcsZqp1oIRbATXCAeHQ4JNCyRlRxhvGzDpvGz4BM
o+jk1tEpWGQzIwws0I4kmgAXYNQLHT011vYftk+XBFJkxLod0GeylW9n2wPr
KSVuPZ2qrQvqQEajacmLmiwjCWvP1UCP/RUH6siu5zk1eg3bgwAM9VOQDkHB
zll2be0Ap5mMTkeedYT0ilMwE5MFh1MwxQEtkNWTdjTDqPp4rkAVUBfmIBrQ
I2pUW52fQq9egRYE5+Xs9JXzDsFQUPCQzzWZI3QLXSgYGklGJq5y7uIqJxpX
qTkyQiy1ALrMm9qoXXcFZThoLGtyIEGnl8fiYqmdSqt4i6HBW7DXAxheDhKm
AqEyQenArhDaYVSpCa1loiz4xcgCWY8NkNVCRrdGxyd9hbN6Xw9LzM/okmKO
tOCkLdTZf6xwM4a0yJ4sEozabsE2APNBPi202PUYbN0pbBchY05Hgyi8SuyN
49dlgItz1D3gbZamL7N0GtipvEZwJEHkR71jaLjXO0iK1WLMEYcP2Y0xs1VF
nc1pjmxxrw/qCcJEvESoumTzOYVKQ/hASl4IBu7AacxgbPu93khWMlycXu9b
2iH3bWRP4wrT2SYgUuw4C6P7KeEkFHbkWtw6fD9yig6ZgheEYcRIgKzxwGvn
YlAD7U9RM5wQKyKVPVBnmQsysyFHarxtvLZot3LcA3UW3nkG+Il/45Z+iI8i
Lm64y4wRIWegSQjnhNm+H/F8/qDzOdXOt/7w9tTN2WNlaJYwaJ5kkZywGGE1
rA4mdUofPhc5A3bmJWqbNEVBB5EobHwUAPrvmA2sLVJLlfEOEqkwrxFji6ZJ
0fXz98yhLfhxIPN0JJASe75cFVOUZWC9gY0I4qeY1kwC+K1+ACOiOBF1oREj
D91MtlRdreEX1nJfH75D1fGqnIOh03e9iwJVwzkjV0wyFcgakz+K+BJtArb9
QFCfGlpJvbcopn0kfX00pHwlkPWupoCpCBCMYr7oUq2qmwACH58UAW0EJhc2
6NbZvqwwAdwdZlRASDeMzkCwFUkDPR2NY4YDj+gijUKJk4hXESEUCFKsJE14
zSi8xeSckMZdG4QTBg6HZIbMwdh1Y8UtU2FOXFRUcPTEAAuHrTrV8DixW3yk
NroQ65TCIUmEAJcWWIuBlzm0BjcfRDExoDYnNZQO/Q7zMQEoi7Wnrus0UdQQ
uYq2EF/WMHUrTpVGdU8mcI8CbStGYCFD7ssSiSJY8aFGmJC+jAaX9HrJcBiB
vdFpoik4xABzfBca4KDAAUifFwImHrDryD6XmllYnI+My2Nxiizjw42zQ+d4
U/ohdCInUF92KlcNW1Vl8xvTCYOA21oc+QzauC8Dh9xOXvHOkwOSCMgP1D9G
HCJfIGoXCUAJd5F+zBerhRoOTm1GcOHAfavEWec/iALksJdeKWWLjEA1HHem
9VksV41Cs81oJP6wyBYIJ55mwG2ntaf4gKS73N2EWaybSPtxBuDAacdwTAj8
6Ji1RHt96M0M17jNLJZqIOdF2IEQcCT6xdsafjjQh7/Pp5PvL+0Bpk/miXqg
vBY9YAkKm7hI6w8BDsQCxIwpR0qbxX45ymadHo+PtA+DWjHgwGGwUfh4EKTF
7uA40MzVxd9O3pTmdDIjJP2JlAR83Oc8uQMv82WHrD1F1AcmevAoUzsHNwAf
LE4Zs8pAxZUBtXXvR3JdrubIWiiy7HiJqg2E7ndwYMKCrWg92EWvZHBL+6mg
hsNVGAigMFkDKJzQqKawqKVzTYGFAsY2g34yCwDlYC8GfudoAtGYZ5wlgP5L
dln7tDixSpVGcAWhI1w04ZOBNn8B8qrgySHtpg1hAuGcFwMNbsAizFZzgiPm
TX6BvamQ7AQ8DvUsVXn9AY/zcw9fhKHJymHAnD+Fw3kw1uDlbZoyHmEvaKJ0
wHZYlGO2re4ckIH2XuxKCWOrGR2YDfhw3JlQAds1OdOkYrzRHRLom7LuwoQc
SDtUSg3s24XdEbqKS3Z4dqCPkd8P0xE6EN7rOupCgwdBSlHECf7QcmNIDIt0
SvVJMCeEAwuPgerw1QgN7XcUTsWQketwjvaZ8G4eDfIPVBzCRwIPleyPy5ES
y3JLWdwQ8/GyWhmxIrblsTxCjfcH2mCxuvxeuwW+CwpaNp8GviudsXVefStB
0fa6GL8K9Hf69lD8CVuqODP87hDTp9FY9iEddkx0Ohjr1Zh0Vw5nosO33TFF
n6D3fLmaC0MJnJ6MurWu0IGBHqtvR4OqHBX6isEkbC119ogmzxxZFRANqs1t
f5ddkeWqQli0WFnixkdnYVVgbJsNqrPTV46mjCEchPxq4p2VV41odoRJW+vO
u2uviPN5uPiAJaumgHLAP61StlpkBC3j3LtmGAEHlDQ6Pkles6dHCMf7ssiS
xDQeJifzKKxROZmktSLYSGZ6ZxBqSDWqRk0+qRW6icz5g8iKhcsG5AiREpcH
p1HCg8UrD9OLoqwRqGTHoY9g8naYJMPUhFoAwtKyqcCdTwUTmZx6lOdIhEwH
6lmPUlsv1jBRUYruEshkSdIgl6/2aHClTv1fH8cOQZ4kHGm1BBvKiXKtlrlF
xY9GJkIUqKiyC1wnUbLSMMTIQkmxpRTEu6Jov+g6OrgJZi/R9rN6Kl13hS5R
jWo/6VzCGnHwhjQobbqoThFYM2/ixi7xRRlqOy1NqAAZNaGOXzIHxs8+3YdP
8UP+7Cd27CJIQd0thsGb6LbmCdHUTAjLKfji1NlOWiDc63I4vmlacoMyuOpL
ycX69AnLuoAkoFS1cyM+wrzcMCXAfZx9VC7aIaFgOf7zP//Tpd8HPw+SnWQ3
eZg8Sh4ne8mT1t+db/12eMf/Ot/68cWP8O9zdF/gX8n5yRH8+ywjqZn8ePzj
mr7sT/gXfdLreI0cpM5BbfLCIpKgdfm0n9zXxWfYkedq8ipJ5HqdAkA8KKJM
zS8xbl3MCJvfsDdB8K4F6LgY584Cvqi7W6inEQ1bAkugikNjGQjLrNCNVRYd
qTv8to8FE0lKkB3Z5It92GnQG5H7wWDG+RTO+ffomf0ePgUaPOOE3ank9pLP
lpvDM2sALszNaoFgsL+SMsg7FwstKmF/U4a6snhwsRPxlrNiS4m07NI1j6hy
vJVelfmUrBsEiaKvllG/2UIVEMwY5doZeLDamXukQ1OweceYFWE0MtWlBc41
F9datn2xPRCpbA5njRnzKK4JJXFxAdw3bdh89DEFzbtHzBhFy8MjTsigXFIT
FH+s7xDX8ERFnGNGrWDWUw9P1z4cXDQIcGdBcH+P336PXsPvl7BNO+IJIDKy
gBx3NOiE8qazg0RV4/CJrTfpHP/CPyigmCG+U2mX13QGKqZn1EK5i7wA/r+T
DOBzFhLXZTWt92G83yam0eSbruEnf/s//s9kB4N337pB0bKRXxT3Fh3noq6f
E209MqncQAMzM0D4wvaILluCbKBOh0hIndLuw0FIzeQEeX/4yn2C6fmNJMV3
PYtmfvT8C6IerxMiGSCQwmfCilgP5lirpzs36tcgWaLfOPOpaCMxjZ5sP9re
3d5lSpEl8Me3a4FfvxudJ2/enuupx7UGXr0PUsGRVWixaKYy05TyQXFHqT2V
o5KDn7tMHr8U53ZD1II8mQZUBUPYtt/Vl7hY48w/8SDJZ4msN9uoIXFshX/u
9HFmIn/2Qd7Z2VX88ZQ54mP8Kjg47d6JqEA2Oz4YJr5uJ+85/QC+W9MBaPLo
MhGT4oFUHeDHGFq8InmGzp/xjabubit+qVZ3j4tZqLoZSCZfKEK8zjIXsHLR
+hBcQZUt0PPhQYaBqwR94zAnwjC7RRYN8eozp4l5S14W4TvZx4YdwZTX+UuX
PaCtdvO+pR3J1f2XXu+1k+vOlY/KF6IxRKsdZZu7BADUhUq1SUUxz2ot7iHw
m0iUD9m6IOgAyXNU2KlsABYM++knYPy/hTVGFAK8gF+qquDjKsFw8PlWhRzf
kV8fSrMztWvYlQv6IqOzfX6bNO8N530f8dPmBvCek+ioAlBUW8QyPYHjsr4L
VWX8gCycyu+w2mbQgfSJY+Yvt7HRRTbNU2ZaJqLReISw82aPJKXjiDQEMkkS
jFo05aScJ1ujo1MpoYE11X76KVr5w9NklmXTMayWq3OG9XMOSVFlh859REjg
mUJkBAnu5B5KjHsD/i9KDvz97Pjf3p2cHR/h76OXB69euV968sTo5dt3r478
b/7Nw7evXx+/OeKXURIFH/XuvT740z1e/3tvT89P3sIC32v514h98hpxJgBm
zaGJ3AvUp+cw6Z1HvChYyw5sPF6gnSdYTQPhjVL5A5MJ+U8MYPTQ35CSW4+E
drrMmxSDMc6qS9F3jMcOdmNGmUfkEMMANBUBzVNd0U/3p/4J5Fvw/U90Xu2b
cDjDWi8u7Yir3LC54Z9n6gPZ/OmT/xgzXq4msPPkOfPlP+yLUteDi2S0DBVu
DlpwiF37rjPliTWb0YpNHszIcTs8Ja4yEpvprSH3egfsaUZtbR/ZKIdC/ely
Mew4zmNhJBMwmqY+qu84dZQPg+EWBuZgFDSbrCh+jlHKALo3EKg2eQ8wh5BC
jBjHCNCCMPmDNZgGzoCh+bCREQCrFIIg3/WiugwKgwoANeoXqn26UoC66fFT
ETLIqeoMkWMWHARJeM0l8oGVMfKmdj5sijOHdoxwN1JyyQGitR0EFYk0y3h2
TAHQGFSPo5sWjRmVK+S8YJG7NmRkqzHqQGuK0dSYYsQRHPGB42T4+bB7noNL
2/Y7gIf88Pyd4+F+Z9dHhuIVs6ESCQsJdm7QRVr4hsRa/IuD9UiqdvMp5e40
cRu1dbvjxNC5T+NswkY4EQ0NUmzFvFPcrHnHh2ZbI9925SWoqABjkrcOz5/j
OhXJm49vBOJbzoKEOnISe3ONwQHO+YAp9bXbOAfVY9kPjUv9JFu8IBoImbQw
jne0X/AKNmUTBRmwGDpbqGUk1UvgYanF1HvqoTESFISTwRjEkFZVelMP+FxI
b8Hri7IoqVnvVKVng2YpGjF1WWfSQ0bRAaTbOeYnLudpIecnZi4+p9FlGssg
YHWOBOtszkoMfyZDm5NbxjeectMW34vaSp4b3DQ2LDjqy3IuHufo8AcRnYEm
iFYZnRHK2cRydPQpCPZ5emN4uubkXN4skftTpoCxtxUr4AA4h7bmm7MgYA43
RboAmXZGgKiD6V9WdSM5IWcHNAtJivc5H3oKfAZBvILwbF5WnNxV8tukZkgG
LNcLUW7jFlg7EABiCOI2yiGJ7BsBrxd351++tEvkA49i6iRbL8+OaKLBUuoC
cu4Zzdkb/xaiVBbic6lyDfMyiEnZeCQ06qSs7NdGfChnK3wWvUvjTgmNgGlM
mDoTcp/9gEthZSVXrKlF2cK7PBGbv/ajx5HGuCnSMqyLh86+dS85awza+/7N
u3NomdBRfMDY19MB8HKrR4aeg8mCYtukH7JCwTGxRCe8HK34XENogetTDofj
rKmpJWHLJjg6xSg9s89NSpDepdKkhXpYjenuqlygjKc6NyjrelSB5aZhqnKw
TEKQmLRSp4MUydnz0Smr/TUVDGN8ToYEkFY3G8yAhMKoU+9xCic2UxZDJI6W
VhEza5SfLbJ6Y3yCqtV6H5V9M3Q1erRsG+G6qSq5iSaJNl+VtdSxWLFM49CD
0yXpSFiF0gzdgBBg4G8PaeBKr56BdqnyDi4LqwH7AiN3zkVWKc1bLt5JxWJR
2XETEbIBTY3UeMllW/N+rga3MGhnu3QnBvk6IgIGKevcEnpXD4W2zaVR4pTt
4Ettz+mjbN7EcyNPAwKynTr4OZMgwNB18hy5r8k3YGfJFp6xO6kt9dlfPgDC
R1m3GFpNl7VUA6IYtTsD7OmWx3KaYbZYovSoRLGylgfCJqjeOXMF8jXeQvhW
j1aWUWN1p7H0HFpVXt2lhr3XedukanQkY3z584gGTfsUsiSDtdZsh3WHshHk
OilCGuD73FM8wj/3O/a2yVt6sAIhyTWKmIPQhPK7zEUBKZh4JQBkXCUli8gh
h+GuHKuUd8AdoAcy1jzsAfX/CT1C4wANebUotHZN9GVVXicWLCE9yUu3dniZ
XrEefJlRHbLATy2fdUz/Op8itsZprlgUK6ILv3M6HBjmPhXX2ng0G3Ygy8KD
CmbAH7VM4HPdWiJ2h+bg84J1KVVbdyMLiskFpOL1MnowJfNnSihg44qZE2Qc
nkiqtCZXyoRYDWoxOBiXIEHkGCJfbmsxDdpTrSR3GpSd9Xtbo3/uq0U6CmV1
gHCoxMexgqS/NoJPlHdfaQILcZou1xaBc1yAwvv9rYrpzpH6s1j1sepD3XKV
im/OuuZGxo9HXscjeZaceOyf+6nXe42e6eHBdWrq0h8L/9h6ffDmmNhfId84
2LlLTOlxkfZx+XGgcM4rYumYguoTrMugwPuQ1xoBv9fpTc/Zw+mSVAdy6Fdk
FiscOCqNaRFD4ujqiTZsv8INASLinF4+AHmlPBa1v+Rbn1FJuCm8xeD8MiiL
kSa4DMlFSQWHbkqqWI45HnB8V1w2x01FdobSOegtySPBTCpaYo0faIWAZItx
CPDMPEsr8jkLQlwnQRq1mKduATigIAZVfyBVBUTUNqZbuisKdS/UjHAPXcbf
CEtm8nptjeDffYEtuYINVMiIdgGnQm4YXxKFK8pqWIb7mqIZjORqXbSEg6F8
lmDoWh6OYui+dNssWjhs0vWCBfs4KUYreyN+0NEIrOcHKt5NjIT1yRuhgQWj
wLGAs7Z2zYW851x1XkoooenJWglnccFiUPE7MKaw6LgYcqsa9Ri8HkJd6gcz
qhWmfgDpYyArt4A9gEFcV3mTcZTGLByVm2Dhr8UzS0fJ6nGN0UkOHMAODxeK
Q5tEda/QGxmYJqyCqgNTPLmuIIy1W6NXGNRvB0DohIcmTqr+TVZqtfBnxLtM
9IyH/G7Y5As5fGzQOgchrgN+WTdAJZJ2QZw0D1EIPiPDBTB5sShwd12YQKJd
JquVdyySE2hBENADCAN3a+qVpUDZt06goExB4JKUHQj9vPHOu1WWIx8PThWm
InCX+IHlVVy8AGwER2n7sLGZ1Ojfe7znyu6rNTIpl1mXJ6Kw5Eq1HLii7tTV
4KR4ckqBIlMlmke/SJ2qGMQDfHrBaswygxIUgggtb9u5pTU9XCQ3JlJnhoan
Wr5qu/TGVk5FPlbz0tRZ7PuJ41L6sLG0HiGEmtaYmF2KASeWjhshhx7T2B+h
tOOIFER1FGq83+sdvEv+SzGul19v8u/ExNzg1dPPetXM+pSGhC2MNmpircMS
mjj/nCZQLvsqgSOXMdLrPf+MuUiLz3NXSewq6/UOn59tNpJDzft9Dnt9BrIe
3j19nmz6ctt9Du+fbzb+pBVywXc3I4EkjpLAq+83XPyuoFivh1U/Nnq9O2rQ
6708O9qsgdv92dDQaMOJBA2xQzAZTS4zOPDYzsnnUxGV5GGf8obPE/GkRYa4
+SPlvjApYP6Xvd6r0YaL+op0khEojxTnZnqE98/P7jrXyasSq8ej/XIWV1sB
I+D1+7t2ZaOyc9DSplN5XXbNBDnhRq+v9f72ep/D4qS1U8MTTt8ebjaEDjco
vA3s8fNej5jjv30Whw6KP7uWQKCjK+yOd9c6BuH1P2y4iyMRbn94ftbrjQ42
PA8jjqMe8EU+Zzh6znDa7O0NauNAc2+P7poDMgM8h29nyRG6G58TenS0qYDr
dhlCAxucxtElaENrj+P7TcXSe3W2e7GEfoLN3m3dlNFDpFPHlcgI5oGP5VP+
kMFN+LCk5rwjENp9eZY/pM8kI0NwiMZ+16zKln7rjJlkC6EdeSGor0+f8PJk
fq2Na+orhjlCPjqMlaSAlLMee/I0pzPFBLqCM84RypH5ghDxjU7bPBfrYthy
Tp+sachCd4gHM0nUeKnIWK+tSdYBDlHq3/oafHZtYAnSZe0uPtK0gbAWCicL
cbbQg458nJ2Oz3Y7PnsoLYTpRE+TZ5/zWW+TZKNNkpF+fP/N7o+nP/63H5Pk
8BD/fv0jjfL0XHKTZNSxiu9yl77cSLqSnOTHm6nrf36dkdQ3BUJOClfYvVxV
iGIajc6wwr6H7rdG8s0v/F9rTQjSkI9X5HXTcRxG46jba3LbwibJNvzc+sCX
WtjuNDvD6g6se+vPwq2+c5lohkl5duHYjSkxVHJp7yb2l3VmRBKfzAhWwu4V
TLd5nVYfmLskW6/7Jh8MY1eu0HhKdUzoAlGNXVo0GlZOctmYri6j8QmYa+zY
y2aq7Ygn1FSzeC25Yz2G8ek1g43UDrbVYRvEN92gv1MxRFg9kAEKKoM4U+n0
HGb3xOV3nHP8FbRHLaoY3ZVIPlNXSbKg6oYBAD2nShxUL3a9X0MCO/O5FAbx
zLiHwQn1l4YDCcfgHbG+lCvHQXu2TIK5eWKalCKWpgJauk5vbITyDTO2rdEb
3HGXKaYVtLRyCRMVuRhot0In4bkyqv3k4W6wrqG3TahOa45T6WakU/eAy/0m
nzqWEH32IPnw8odkQkhAArMRqlyQ7njNXeS2u0w5PTtfCBZIb1ssZ851J27y
qMpg6W/VRPXR+VH6gw7HoY7CzCd8wKSx+zh6+8SEIS6bI6ZZkeLVxiEtXCI+
UZY9/7Hiwwi2oyDV7SybZDl6oHn0Woc8HLcedK7deqNoqkGSoa/WQSJs1SbJ
lXYYF156O+CkNH5CmbYfe/DkGg8l0uxtQslS3jvN2FSvPVEbPx2EfOQG45AH
x8UYNc6M3QR1ZQk8klau0iU/Zj3RPao9wAe4rdnKNx3abV4Bk0WQKSMjNNJo
MsCt+1kSw3z0vrPgSJRGLiLEFut0/kXRbbdeDDDLbuByspEhHPe1+Vbac5C+
HqbVg1KZV16tjOFddrS+yjQvBqaFswvfI2i27FXP6FW9qPsJY8cFI4OXHcJR
VqC1Xa7ofp9xNknxJERpVFRIvDK9K3balBW2hXsFdVNoYQS9jM01gMyMioya
zEb4zk8q1atN/di3k9dllQ31g8YM8vXBn5D9jDO6DxMOacP3N6R043DkQp6X
NdstsBCY0NrVYkSuI48MtsTqPyZaRU+gD164BKqOS8YN0jgwRPg6MOZLYajN
EkhI704mGplHkp2TAp3bOyB/pqYmGvKa4QV60W+TUYg0kXHsoyNXi2pGYJRo
EP4+lvjURLmvUsLslsJBsWHqQURt25fHLUeReOhvO9zwCPrtm8n4a74xeuLj
YRy/wM8siv8zhkPWJg3iRWCfMuL+xbt+uKIO99CG+mzep0mGJ1CD2Urq9lSs
Zs4yChcMS//G+yok6ISezfFxqYGaBWTqIEd8N61tvcd2XnqyBceglEJyKiim
VT9M96CKbq7I/M7eEJXlo7dvXslJwFiUgi0IM00ho34HNerwCCm3FXzla4kg
34not29VtjTITo8LmvBKDovLinYDDRw0jn6xU+GX+xS+hPlszU2/X8ac5P/Q
5myZXesbc/NLj+Pn/PzY3UY3oXxeG19iHMHPl1iP/e3tbU0aFRnDNfPNOL68
FwBFUVCQJl3DmJwfwJwelmT+mAtQWdLWBlHBheDqDDDwGIlSm1jJ2KQih8F8
i+PsPONsf9VoZQ0X6cfhtCyGKFyRfTnu9ukTF0NK5863XfPF9GHmP5tZhn2p
jeVmpmzLwcLhYaeLtUdns5LSzoIkMjHfpy3bgZeatiZmS1A86HcPWYplyLBV
8rQFb42St6aiYwli6FA+gsxZ+5zWxiFFd7py1xxFye+gSSFzZtfxIigR4KF2
i7J2Dpy4Fom7epYxZni1NWU7c3HwEvRMBhdgHSJMZQVr89SBGrI6xLZE+oIg
TRq/UgrV8G8RDD3UQg7ebSfHqYGmaEUa725KaRhdAPIQccF0a3CWOnB6mDo7
FYSLlCXiwfFVDC20C8/+NmE/+Axpz3fjWJHP5gSqt9883usH4h8tRJfsGc2w
jsVvuhpeTln0SvmvXyp5f7Hg/QLyjti7Wawtt1DCvu9g/z9uMIq7m/gCwi5s
4tad/buNov2z6Y7c8rOBwP3y8rZD4BadgCQVt3Ja1B9jy71Fmry0xSwj9Klz
sZkX5MJWWRZWJ2rc91rOzXAjK8bca5gA8jV7Pri0VFfbO9yzsYlbjzzeE4s4
8EboY+QKIg9G3YRPSFEq8mK2h1pH9XUCz1HXGjivehwZ/baNpD6AflvAdV57
AnA6/5V32nDlX4IYY509j4pkHJ01Y18CV73iCg7YogURtuSjyfJsIhdVp5Ev
6Znm+lZNtPKviizuQObLaA9OnbShheQ7KtwNEXQZb4tVaFlPeVjKu3Y8Z9Ih
v04udS3IB1MiNCJdUGaeJlO5lS/HemMYDWqWS6o9Jjd6j5sLa2PlQinvgtIb
QdPoyPXwXF8zz71OVr2401x13WWK0KHzd9wktgB9Yvk/fI8TAoIgON2+q0tn
1Y4X79b7DOCFOlDpigzh718nXKSJVwCXFx2D2qDW7Kf9+jbpSAk4mVGdN3F6
Yd7yilJTpXkFWZ7S9S+s+9nrd9TDh0cQi6EsuBYP1a6gukvsuJZYCF3fgCk3
S7kPBiu9iK6jAFIqFYfxkaD8+36y009OuCwV4+55dKdfJ7vdXwg8XsC5f/vr
f5cNRP/j3/76P/TwSZ44AfRJH9Ur4/k+6OwjaVJC+wenJ4PkYR+vqJdEElsV
1nXNpJ59JPwWH8INkpJ9zZnaTKPetn74+LB42g+Vvp/lioncOfLeqkD7LJNK
nzZUsq4ZuYjKpphqlVD43cPT80JiCltBiViMBKHKwar9eGWLe3QwtMgNFUau
mjqbz2xFkQ63UYdySosN9u00cA/9f0ZHtRqQ/HedLwifRxck7+AX0ojard6h
p8U/XaNwX7rtvauJfxEddYMV9zpmS7ckrY54h1Ux31neYRVNQ/lrBIZnRnRC
2XKMzgyyBr18RM4kv4LFX4q+6D+1ViaUstttw/hE3CbLfCL3zGSLJQgSpBrO
RWsrDzhtGhgwcOJbVGfeXxQfpTdEGJEWg0WJyqnMVG6X2Tl3MMYkZC7Z8A9y
gnVovVgRpNML9tkurjXuikRzGpu7pZJq4B0esjW2xWe6yG5xw902dLph6+7h
Dz9zkNi1RpBRpeKyQ11tBKp0grVtscYzZ+rsPX78cG/7i7v+vsB2ksr/SxeV
YUfjzEvtfEGJkw2mOf+amkfyL6B5wCJ2aR//BMrHrxIRUvXDKgP2RxQFJ89/
VgQkbvNfKSK0yXxV+t/lVyKhj9dVJSc11tn2ukE3MBR+NtIZIppFvWFztSEm
+P/fqQ60CtflqkHmPocFEH7NF3ExMsg79jSxWW4ECf0sPXG2z1NYJZZPfLJ2
SEzy77uuJFV+QYWK9C61UIT0+LY4Hzf6J2FDX4AL3XLoDBZ6/c+Xs4FuCRaY
UcoWjkL2+OVGEXbz8ujM9nLLOmw6iriHozBcv8aM2qb/bfbzZYy5WFD8vOUM
xv2jnrlRW7YF38uqf6lNjVr9GWuxdhPpR9o/Wgu8+Pts6ucReOfP3z8EBDr0
cczWBfx26EtvmVfOgcvHgrhus+0XxLaNXPZCpadiBt75R4qZ2Ez5nzJm3c/f
WcYoZ8at+VVGEfYTcsNgrTqk0Bcfxc/66WRHoUS7i7t9YTG1prsvsBb7/tdO
+fXr0MXur6l7dIusL+wF/hV35B+CVOgSVd0yCn/Wy6nbhJQTSQJNa8OxawdK
k2Bor9f10NaLd3VfwFIN17uyt7hpBJaL+rUh8livCqO9y3mQkTPAcqZ1PpY7
RlHiTkq6Y5oBbhXd6wti8CK4zE/uG8d8Hn8RS3gHQRCx6ypFam93EJ8U9ZD6
TAnMx5LWw7QZ14vPDWMXYNBo5a6yubWaEKwtPVSUkuZi760xV6RTz6ZYEot3
6nmcNddZVlgHIV5Tb6+Pw1Lff0S/eRo4W82NdIJk5+Lh0i9s+kAu1orSjlL7
qlmwOI7un8LVfHdHkP3FO655FkTZbX6ARNxfvDMp9UEmXpg/QmAIqUYLbYdZ
ia56mO5t14zIKwuv/hoYfzm9pDY86esCeLQRlbRC0hz8Mvw/t+sTVAK36Gw1
lG/+mfyhX0oAtvWzJxYw6Jcb//Zh2v6XYfokvaJW7xBF8Q82sV7sbtzE2i89
YfzsJr7AKPjnX1aSy0+Xi/jFOyePzUnbAG3YBTK8G+v3RB6SpjvzOtuvNXe8
ERYKGdzOLwkJ+a4r7RSWY4ThV+J0x/obFhxmfvZi5efWwaa0gstttxrzT8RW
bnm0g8TW/vw4+vEY6E9GKXUj1ra7wWXFnTQDSxddUeynvuaSYr/asomtxMaR
qfFAWoCIwR12uo+k9kIQ2mvkFpJOST8Qme01DpY6bkBKzXoBcfeDJtF5HUEl
POB2sxoRdQNd04IXfH6qUU5/dBVl1xIddyxRVkw3WiBSxLqmbRen9dDPWoxA
57tlcH5KHUvBFG5vE3YsRal/PQth/nTbHP5hgI5ufrUxoEPBEHJaDEZgZxO0
B2/aHalNXfT7a+c2uQth2hPbHPzAs0N1mUDUXfOwb0rSemNycV68+9qcmRGd
ar2Q4RivgQmaADvAUO1OAPpw/NBLIz0qVhzNYtvubm7kAMx5zOjq2KYk04l4
k6uczXq4v7KTpmRuoSVcK9uJXc8fR88PREfQWvt8bwKyJwyJCr/bYE4YSR0j
HptLOK8mbKydd8Dbb2lFmJBLpULxjYjfPGZXA8J+gIXPJR1C7EmMJdmoX3vl
VbfG42q4xaxTisD7b3w1fquNtCWtf4Hw5qZJS+Z0ZwnzGGeBzstaGLADhgtO
Xi77pbQLf9luV4U3XNR25eDOqtBc56Nj4VaF3Hge3IcWjAtGi/4Xqjl1UaWT
bLZCKqNyS5Q1V6L3qjElNYgB+PcLvq5rukSAO19mR1XasaaFg24Z3aAY7oTH
0ngrONVgy/faN/KMStbk/kwnRcuboxQqowMSP5HbECap3twOhDjOp2Cs863V
kq4TUGQkL3eo/IyoBf4qlau8nGuCC12wIGKJi35KKSYqRACsFV1uWKjEZj0O
QhlxMK6PuPaPiIKBv75SAFS9btmnADK9cuuqDdjSF3ua6fgqM8tWaJpQMWxM
VmY3Cboq4rYO2C0y1kohnuO//7n49+909iLdZPYoJP2wBusEI675neIvFO79
oPeoYVGjB3y1CMpC95QbZU/WtCXU/XhBDe/9FjNCinDiehG4WXBtOatu5GC4
L8GM6Fx5M4MHPDYkUNcLDRq+oJocZnGKzrXgo6AMiK8ypFQo6J0WxjFrs2r7
1iyDaUKXfy6+S775hn8b7nw38DYQv0ffu9/hiZ5/fUve/9a9TpxZPh36T3+X
PNx9sve0f3fryW/br3f0+LuOHvGPob797Tef0yUhTu2AdRQ/Z7Kf0/VQmu0Y
xnf9nzPvz1hp27fvk1I9XhB8mHOaff4bX3dfrKE9qs1jT2hAsvrFAgnfWGhp
wMXkGPuPFonJRW9fbvBbtrUivuBOlOl00M1OwzscwumKzoV3bPHtZr5X26FI
6I3nyMDoLJ5ka26wgd923mHD5iVdeutV2VaWInwALXRNFvPQfPKjv6mIh08L
BW8SoG9cl/NV43MlJ1kQx8BBCN+XZji3El4PNh8Fp8+GXT+zc064h/+7QBTe
E4WXI7gakw4+3zE2x+DDKfE7GyxY53JxaYNwPkVGGiXoOZzfh0BNtI+c+kKZ
f+wgE9ijBjH0bkHsoDXQxtAfBXVwPaVAJWt5IN+IFoNCEubuwGk2R7VOLucw
iuJ2eBtPqtcaJQu6fAw7kZudoqxXGJ2UQvM3dSRaBzkozejqEXLtJ3OXjyyx
RD9Iq9MwkRuR1zAxepkOW7UaCe065LgiXgmfUwnLyEqlG44mGYc9a3/Jp8TH
0mmOpTOu0nxOKkCkTW/L4dI2Ffe+dlw87LLKLxDjiqvSILjfXf5XY/Yup/ma
ZRL8v05lnM00efPWBSBbMV4CZZltFgLHaVUPbjkRl1m4zT9vAJztTcSHu71I
3ZVUDV0mVQWeBPatXKRLd+5aY0OaLyeTFcaOqW75aVBR5WyF971xFTzzOX3s
CpKrbAqLsVT0Kl3fuC+K3uZ5Qh2adDkLxEUAhjZRYKkO2JFwvk6y3eEaImZa
OzXwF4zMVhgwl9ncJnHtLUozKWkTZZLfUfNFAr9NecG8jLwn9m4g5gx+Ai6b
HMe2Klxu/GfU2onYX0eRHXftnSkHO6UrxDAbPK5PSw65gPuxq6e5WeJlJMBk
eACa8s+Fe8ZB2hfNO2S2irAQ2xTvZ9OsenN5F+0DFeCJ5yGboO5aBm5kTHAw
CtcYX0x2lWfXZPYPNt81GjQXKXCX5NoRkMxzq4CCpjVGd5fXIksLgqHUIZpz
TdMCp3Dcm4sXYqFghRCgbgWHJqoAKJOxRUfb+BeZXlDPmLjPUTYMyexUbjQn
z0AWfCdfCRu6yApK9tcLB8cZ2N1TIKqoQb69+CJrYpa8Ci5VsFdfFfYUI40t
U/YTLaK0/ju0G/G+toakt7ajUyIoQ4AJJVkxpXrQpK6h6IotAtBuJ1W+5LrA
l7rbNaqNaQtuCwcvb1gYBz0JE0zqCcxKVEuKxMjuYFNUREQv4JJbk0WyETvL
C/yo47YunR+PdExCGAbP6ZrSkn3NVVoWkIs8YjQw9kjmevEY8gJygHMFVTgM
MJ8lFmP+Qa77im+Q9kNJ5xclXVbGip2eYvTbUb1yKsuO+7/I8FrBvF5Ia6z1
ScF1UDrSC9ZOSeKR1uUv0x0k0xVf2sllyWFGU/rdktpW6pxSPhup67Y1dcgG
WJ++1ELGCxqnsLSl14s4NveRqkOgYjwzJakHySzF24dqz5I9J8upFjlDbIA7
pzehZcAVxumpaijHI7o+YeDOOHdDzM5cGiiAPe/TRA+zKCmqLuJdjkgGDyig
/1iyHPFi5IGWl8ED6bVwOY3bvnTZPP+Q2UK3m3f6eA9b3dsNeg1CPp1d80k3
fl8KAtS2+Ineju6qm6ykHXTngjqN7lM6X1bh4F34S06lj8W3iDRzlU9XQqdy
lylTSQn98RkxFXxIIWqrMR4F1q0mqXe45ovjIpe9Bynm9qSviqlENWCdVgtm
U1ryphIj7u45BjyYqHsCx0prJU9z0IW5jopIX6BNrHuCN5WtX3BicJ+76jxt
OfZ5uCRsbFziWYU2OCDXUZ28JQDkjnlTpV4YOY0Q5OwSz/atw/pa/doDdaDI
9cgwNlSmGh1zfQdR8VMMEewQn/5raAWLh7comtonbry+k66mueJ3ScWXqngh
mvRDdkt7XHdpQtWE9AibkSppwtrQ7QeY9j114EG66Rn+618QG9EFK7H0kx4G
kv/Q9RjGfpdAl5o8oZrvC+/coWgYnBMDVVtIzjzrqr9t79WMop3m/dwNj6V7
q51BEmSrB/gEDUvnFcNkZ+WKyB2z3EUd3sTWu31i3beFalGn0B/jp+IWd+3U
4zhXEGYyMUN3k+/S4GlMq0HRurA+gfoJZN/FDvA4Ls8fTXXw23d5Td3wATmn
LCG5BWDvwot3AqfmCDtHb72D0FWx7oyILnUJCEYTNHX8eU3RRex8ATypJ1bQ
BKRoqlLZWY1tLJ/OIUzbog0s3kG0Ql7/MAhs2ySo3XIpCIOuMLubrYIB6R2s
XCfRTpl94FnpfH5tBUUJmseIQr4xp4nuRiFNJYhjBWFB17PG6j3WoKPDNh2a
ivF/XH+GbYjyFnEmdTRqqtuorCGuvt7ylwgTsnywQgEPEgFrzXdqW4m7kLmt
1Rhx74wDf4N9yz67Zdpdbqq2ZeN8nIs0L9yKGxVBAjixhkj3G12XRgiB9IEl
2+8QT7iI/i+YHywYiiS6B/6k9TiJMe8vpj6XqqlJ63jD9LZcvt7qcNAt/Rht
g41npjKOe2tIAxvKwLDcTKZaLt6UDUyzmpIzQmgymnmkXtZoPNQMscBngoiC
n5FeNe4IZI2m1Ul/AW+guYnBciuZe/Vbz21wJj1QAShvIg4ffEpan8VAB0QH
tPYQ+S+6yZp8LhpvZ4yIaVTSXVwV0zBqFIEd6jvnV6+PLwUzbR8bNKLXkRSS
I4ryf6HpxJ6XwOQBJR1bnWLEg4741G1XXtsJxiU92/2QuzyUkLfPyQmKduFa
T37iGvD6wbrW1MPVZdUSfwSDjTzHoQo2k1W56/ANonAas0p+8/Zxef+Gn8Rd
Y9ZGnaeewogpipmQkGByv/tfhsNkJHz6STIcfssBkeASV1/IPzGXA/GXpsg/
snfD9UMIr14K4N3cCJpLFkA45kYl/yVv8ChjuXZkHH6nVdmUoFclW6Oj0z7f
Tff06d4eXzIg5mOJNwjKxV1LdkORU4xUVbTh4F26KdD1F8I0ibL4it97RK33
2OnP8tncMydBfDKpqbRWnRXiWZBRWHPRtR3eVCe9YdMK1cKSwxLGq9UZmlAV
L+2Bbo9VzLf20IdvUeGsNZBr1KprbJp3fuBmZVacXIouoVBu3Vmh9FnAsk8u
U1JXK3Q8THTUHc2YkDKci1XON3TJBZF41d9HDuxgeBch3Olcru7jXRVnNhr1
REEU6+AIDpL9V6DtXFPa5+mcCtnWWYbXzUyXZSoX+16scr67UKtM6/mQmyZp
yHbEMri31P4BtU92Uut8bO/ICbmfvKatII0T5HqOkRN6hvB8JTWubnq3++RD
y7mSLkZsfcRnVQRFiYNL6VBtwm4KeHb/c68nX/dvumCz1xutxs0vbDu7mqBq
w4AEs6r7yZuvDnq9t+1zv69XVg5zUKLmIBHn9FtTlnNQ9Ol3lA2wbldD/zUL
jXpZ669L/2ud5YNO6cWfTSmKMgTGORSl3HwySZd4WfSMD+2a60vYfzwjoQ58
pN/rHReiHxKcfCpiEVFK3/LJoYXFk4yXaWhqqHNEYXdXQEGogG0BB0vwes0+
3dU5WVVYGLmj3RHRuj4Bw8Ki6/Duf4Of7V4CShQMl0T0OJ93tMFbcroaz/P6
Esv+2TLs1IMcKrcc2jpjqN8fIpvEulpTf1Nj0jvo5LBExMyxGkolwfYPihvL
kPnpKiNsIfwJTQ7HKfJSvgEW3Xn5BL+74qRon5hu7yXumiYMy/q7HLxcFwH2
FTr8LwmK4jn6xirCWZWcczzhQM8MfTxZcPcub0STLVGR+WNWYEb5Vt1k19nv
6d/bZXXRl70oUAat8K7H/eTw7evXb9/gUUG5MuHFQg8Kfy1DXjWXZbVPG82/
179JDnhsmRetwbb3Di/Jc09XJ6O7oaIhnhyfv0j+/XfpVTMBfvP7PGtmOLR/
/7bF1HYdU3OH1cjFI0f1yttax6PXu+tAy6lAD0fAdwUyLRIRm5BsKWzDX6wm
YWlnNvnbSMWSsZEj+mbAQHMnAWp/gfEmHYV2GFcgr7eJgl+X/kJDpXluOZic
LUyJEJ0GsSocREMiE4h4xvHI7ktQOTinqgzHD+1S77s0Nf+ZIsT8JUpeL3Yo
Y5zdczhldB2zvNt3USugdfLeb7vmNV7g9ivUXlK/IQM7FG1QYdTeTcnPfJ9P
Jyp7R6cj6g9ZjGtNwFe4+BhDFBYAw1HfVZNNLotyXl44PcrewCx4EeZlxIVh
DtCR8KjwFgl3o4MZ3MDmR4jWdcnhwiovq9wUpuCCh+HdluSFIxcOK+bsQ7QT
ZL3G3E9pFkZsvS1zfSkO7xqtHQQ4gXIPOvYkK1IYS93HsgvoUxSvQO3utkVM
0kBzlTqzOrTCfkwSA7uzMBsMStTpDNEPmeqUh+9HEu6RdBPM7z0dMUw+XM0o
cdL1NiJE26mgwOQFKutRc1lIPyvVthfplGNDr1PfBx1i+oBbXEYt9no9ZU3+
5Ognt52bZw8wdT9Kq6EXk4fu7ix2fou9UZUfCacGKzU6Ss7fo6MTwaTkDMPY
AXIJut+6/lpUiwakUJ0svU7LVzof4ACAZr7U8XTzXXs46YmuoylXb7sWvPZq
r0kGbUqVD9g2kkxr8Nzb2GJLz2ttBBu2s3Q1b2TRVZcCpu/fCmiL8KS1Ps+G
B5xBIFlQe2pD8wYI16FzbtiqygeaP58wcksSIEwDk/IpAVvZ+85OAWpMOBLy
e7402F18EvYpPWWyfYpWcR/DPoUyVy5ONRsF1AAUtveIwaE4oi3VBKhayZ9B
sXi09+jpd32fXOQyPdIEXgwKR2tNnTFhiesPbXoyIQyMRnbWKHHVBGKxKLNB
cvz+UsL7/pO55kJ/zglA/wsf7e4j4Nq/7OrR+ewVnxKg9rAyVa/XoiNvE/in
BbPZGnl709MOTSS6zKlNuZ5bMN8PACW7AaJk+//5v8XJtdlhFElZO06k4Fx1
Kerb2x1L0Zk67Nz07RPWmroOSSDj7qAELAJ6dtbiBovPuaNr9rQNYfYycca4
pmEJdiWRShCLma1pUYt4BDGs6JCi0yUdKo5hmmz9ZvCbPl3mgy/cfoTJI4Zn
+Kef4kPsvU13zTWNdFJvLjzc3t3eMYWN3GIvP2exnXT+Umvd2eA/w1LfNdPb
V3q3a6XrLN98pS3wGQHFC8Q2X2jikIbxrKYXePpqZbJGNVJHM6pjFaNhY8Ms
bMPLt1bYMBiSgivRsseHV5WTPUy1tN3IvBxMFHr3hgUYXnjfFTn/JuXSe1eD
XuIV//TpPXxP6/vtP5RcwmyX24bZld104qGLGJYrSjcq8bggvrFEZ4b5O1iY
4EJ11OBh7w+JisjRBRKV1OvglcK74BSaCJNSMCW7ea3Hx5ksJFwtQhtrQKC2
hBTn7+ejW2jFAKojEiKbeJ+WAy8vk0zzq7wqi4UIFsl7MSYXLOuEomEi8cE4
WIjTqS5X1YTA60C4qfgFYB1rHD6Fa+rkohQLgFJIkETVGp3ns8yWknPUyhiF
+QLz5/PYk17b9aTaAPkHPFKyMrOVDEO0xoRDY37NXRGF1KVB+cnCoaNAKywG
ZjNQBj5u0mU2X7IBV6eklo4VYyyGDDINZiFcXViEMZrAakyjn37AeRPYwqq4
TrmGIOhdiHytmU53+1rhko93mwV1wvXlwl9T1cFPWaClJubls4jAPr8MVnRL
6kPMy5qmlC8c1peZEqVTBY3UkW8A22zSi77WSIG9xFCmAluC3hiB41CevOQw
+r9gScNLXmxixWMJ3GIQC23TzpioWl2uPZ/nCSzqwEWL/E0vnRn5GJgyGWLm
7hxuppXbZT1F3dk/UQC6jYAPG+xH2fxNJLlad4Wys81YZ9EbYXQRli1frBZ3
JpR2l0eQyXJstG+i7O0UZV4vYgvw23OtB8AfKwSOvupYVIrYanaue6i9vm05
1AHP0SUzhU07lX1M135i1X3nN1ij2Xd3d4u+/8CTbxxo6dJSOOanPlaJG9lL
hNajTrxuSK3frtzpAt0KfVDCkS6Qpy/TYnJDxTTD3vp3jW+dIre3bj/j1dp4
Tx/tPnv0bO/J7rPHnRvbvX1qbVF+ZAvY1Xkc7SueQDoX9oGqiXdRVWvSd1BW
p6qzyWKGzpvPojS+lUbmI94KgV1Trh1KfipgSL6+ZSVXa2HT0xBUziA3mpVP
CoaPrrM5Wqm9MA5513FxzjXn2PAO3TCLCncsXABzpe868CJ8mrVPWWJu6zXI
PT8dcXtp4agWsDTigqR0bZA8Si5g67CmzmAtpfQQMmeDmQwvaQ54whoCCRT7
AJ8Ucgm7HZtwzyi2fAt9+3Mcs7KojQ0Yw86tjKHrEMXjDMhFGaNTljY6N1GU
Ac+Rv/4oddWs6Cpfe6zwKERRyYcuKgkaUgBBuv+lYBVxjx7ecT957YFJioYi
FIYZCEaTYGj3dUA+1s3R66+yq4mCiDAUjrhrIoGw5utnYpyCmp6/NbCgghMS
GZaz+OZeQtEVtCqPTh0B0cC29UVnpgbvpt9UzRJG290CTmqr8WAkRpD0XZug
aE8+UGxjXYPa0rMH8OPecxV7TYD4F+BENoOBcFKOPQZxIUrvSJWadn5Ss0UT
rhGDtPBj/pRA/kuK3Uu+iSERJoyBtoeHU9JVs0VOV7EZJ4Ma8m5tvmFOsUzz
qr51CbtRM2RQeuTMz58yskpnpPnA7D1+UOzptIG5jlEtX68iPXT+kcePn+xh
agjVCDIJpbJ4zMVUZ2f8Mp9PosN1OCGMuzgD0jqhOYl2k6kGxfHvnKvktmzS
MsqPMoRGcILP34F2eJTWzl47/1m8IXbhNffqcwjPizVBD2N2CborRqOzQ4OV
NN3E471zGwYtZAbfQogeDFMGwHV2kWMVQW2FILa+d9yIJWUWKPxxzd5339DI
rrRUKgm5BTKLAmu0ySnyweaWR5wi+Xa3yQ1O+1ouFSpBucHn8PfwPcqDYQ3T
n1wOXx++G3R4HeFMPtnbe0KOxwNXdIBwSxR8IrqMgoXs2CCtzcorW7N78Q1j
vB4923nyAA/yVwfvT5NnT90DKjb2nz1FqfMVyQvzLa4OfuelxDc7X5sS226B
v/ndmnDHNG3Sb9uvLPGVbre9vEFFzA6S0clpgEp1IW+HfyDuQkcmc4c60/sy
6Uv06xEFiD4jQIt5WX7gfQqC59vJWwKyOPlLIeihwzkF1ElMC9FKWEIdHSq8
/IRzzarhtwx1RbzYr7snDlPwzbMHX/MoxCBOx+VV5mmHMiBLl1Fb3yxg5SuY
Fo8KXe9gNIgjmc+Jw0qhwdPU7rgGCC2tkbWI4SKC4thG61XOK5VWWWbpB+Kw
pDLyiMDEm0fIMFln+V7NJEEK5VyISbzFurucX/jxf1t+/BigQnSA4o7IG0KH
dOLCtpODxrvb0OMs+B431GsqczZB1Ay8eQ+LLNT3BmasE6qRgZToh50KNXh/
rBpcOnb2X2Fk3WOaEM/ElMgzY8NTkW9+fZX4lOaG3woZ/v2Ib++BkF4Xb9an
4LCkCrs3OYcGDvTwAVeg8GgY9SMGm8U3wBxwqBRWCTNJWMggU2R2IU4o3hM6
CwOBQdRNtjCoEfPU9CqvNaeCVzAxFcjygnwEXPoEDWV8G1X2tPGbwRdv14l5
1Nno/NDuNqLJcG/15MEDNd/Lo3AxnyDXWCQLxWQCYnbR/BvvpdBUtxrr8GH0
oCbuCaSVE59mGpRQyFhc9cwvaW1q5ps8Ojc3GLYLHGH5NynZc+VuYeQ7oyTu
I9jeKTDHiyp1V4hroKUpB4kB34kFgmXGZ7jYdMaAs7K4ndxMMMCBZQBg0a/z
KeYrMBcrBQFEdQa7DF0PwL2fvCOpyrkvwL2DlITXMPY53dT16T7nO0QZNxoY
Y+oosouyyV38lBgnbJ+LvXg9IxBhC+olypIFFeDh7t4jw2dXS6zmUnMl/3au
p1RN0aMY3I0kbGzgefScsZkKCRwQjM8nFho9jcvf5QtcJW17Oy7KRjW1JKpK
kpXKsi05fGnKYqsE5RhX6saPxdvOQ21WwOZ8j1RoiYTv447juUk98hBhL07Y
IC4GzXtBRQb1oLzAwxWRaTm2TE+6gi5cIou3DKtAVApMLAufF+1WpLmsMs3B
Iqf8/0qykO/Wms+jOcRZWM67ZTPXbLxHE86c5Parq+ZaZKS5dj220wkix2kt
DIn1KnWf2rpMIWioVU1I1qgTNpQ27edpEl/D4aVV4uS7u+aTaDlyoOMtMqaD
anNxZELWEkkEx+Tge33Kg+3ydaueRD5sCm2H+hHmW0zLjOdIJEwPuAUkP0f7
e5ovsScfMi4r61U1QDquNOfQnRbq3pFWT5NgssK7z9SHFpyZvgO1n5cI9gXO
MZPK8pp4TXXkfIJgnYWkKuUn3bV4gbEmUplOVkChAgwPin3JA0wtbSvoz8IB
vwtOpXck+IvqNhtCeEjEiWbh5uGJjOKrQVPSUvSCnY6kIOVSC4fRMmkTNsO3
TcSFe+0xRF7fll3bH530aiWOHgZjus+iKyCNz2LdyrfDqUZVSoTCWkXKtls8
vSNM5i3xVrTAAaWosxBfGhSxcXxM1TMtKKyMPPc6RievDKYnaZjR5mVapc1Z
4S057if6tTyMvniqeGbWAJS4eVp1TQo/WccVNpliZDyI42aacbonURvIyUHQ
DNXLshEnb5NILmxskvDCab1Yr9KEJMJZrdzL9A4max1FjlGGsabWZUVSoTmV
5SSdG9SF5sYkE+PRjXb2RABPoO1WU2FlCs1iJiv70BoZZuaZumcMhqsVhicO
I71zYzs5MxghXotxuSpc3njbj2eqbZvyu8ZNp9WVA25Hq+IziAcioW8iiROu
gl5JWnhiYlKXWFc1z9Ir0vwEvx0LbN4G61MLjrTwNeZmsDkXuhBYoyUkPw4k
GXDRJjGvbnbBMk0uxg1InLw9QtUE/CbvLbk9eUlhs7lMaV6FAV9OFFlbnEyK
grDBaKhj0HZCnR1jNuLxm6PjIx4DTzmMhKxjmHXgTievrj0OdDvLF44btOVx
FDj4s8QNvutzlVyXjrLWPxpqZOQj3cLEJXjn9HQUliYCvSzUxA/+RBqXlu03
fRC88m53rB4Fz2DZfHepIVVQK0aLstueohZ9bxicH2eaFWFlfFYNm3LopsEV
hogTncbeYr+DiHIQM4MufnbAW17FIG7Rftv1bZiB3R/nRECYldc9fArg16RK
O7Fnj058rLw2qx2DXl3nTWZnelJQaj/jUlvVb/giZVctnQjVClWYX0PWbHlN
KOTOrQhMOt7psg7qO7GX9q7eWnatKS9O87/D33/nttO9xqz9IUkrGzDHHGb3
lT3qlLNVeBOzHViJroOTvW/YJoJxb3I6fMkkm3OGU8ZTt8nUgppdzL1tBllr
cJGVzdAnrEA51V47+IWl83DNTDRnS5jEl2eK/egAXcptXArnFXnpyj9irRh5
MD6zYSl0UgDIsaY4fyFSbSG8bWAtgKfeDvGb8SoLZIPX6soUc/j7rqJjHVYL
0BsF2ntO5PsFjqauBRKwdh0dTTUyf6Wzqbbuzz2c5/Gi/YJj8z9PjT81QUk+
WZtgp6Wy5JfXnuL6xq2iTOKDVIm16c5Go0cVWF262M7CmEk8do7CS7T9rmB7
rL3EYX08EvLS1uc0LDnXdDJMWpUEvsxWGvBEZ1VSsv1+1gj0vhgupSLF2DnO
g+MZMFICi4zmUiG4UT88RZRdfNGdz6xCe4MxJS0PFxEB0N+nT1zAaEgGGJxp
dsn89BOBSWo5NfYrcoPM5zG9kCFv09JU8cU78soVrt1inBc+A0p1RXXDod/S
CXW3LhRGueP+bwnog65KGzi89Vpv/EEYmT56+8Xe1Co+Lo/e8bT5+dE/bYID
634O6Z9TfNp5ctf/HNE/9LRHyG3SdjtJt/VzRv8M8ekOEzv+OYVHpe01zrQ1
T0eI1K6f1kgQR7T2pzUSZEibP73c5Gm8KvMCCGK/10sO9zvCQers8yCPQNjU
veRo38Y3ghYGzul7OJBgicfkAjciwhNFoeXCxTiv3HbsPbpbWF2C2JK7Q54a
KdfWd2C3UqhPsJuHXvQ9YBqd3ssitRrAUBq66GrN0KVsilcPnu7f6nFklxPq
K73kbN9WVvEukV4y3KeQxqrGlYscEQ7HSHrmtNfj+lgBzzJwXtyq98KWDiO2
1KNALChdHIoV/fTIcaYDy5mQMX3aT+5389BeUHXQGsLiOeycKYp8wvsJ/Grg
wtY8cZeudaOwQVrO1RJvqyCnusD3GJzym9oT0TjDtLTS3eflCgwi3+ZqglQx
AwuoA+/XGDqrHcQwqWbFV+isYFcwW15BsdKAeJzPz48mnqs6pg0yb12MsgPh
p0sQB3c1XY6hMS55gQ+Dlm1U17I/oOyp1Qsj0sllDrRNoUSWgrbiGqMgBuLP
4VuZCLOhnmu2t939g+kcGijYFR2GtqDXRu7HMec9ej18hfw1Wk86hE3y3tL5
6H7ZuV0rrq8jReK5P4k81kQBWDaoFWzrwlKWXHiYbJkoP8Xf5aXrQrdmUHU5
UiQM2tVs7JaHFuFDrqho59N9fyU0ZqGUWV38xsNXcICzFd+gkdLWmStuAjWG
QzB0+mDF/iLv8DTlPhib4IwYS1c8J5z2QKGbnV9R2WBJEdULqp1ffEDpuJRx
ZVxyaKCUjbv63UJZOiLQHTVY3WQpT9XnS0fbxeWslgSCSRVpILF0lFwTPuit
0zDObkoxrxdl3SQkH/Qx7lRKXFHqThRJFkRUUXaOnMLnelNbd+j8JKY7GqXq
ni+3d/c+eoATgYWC+KVaNGxfoQ8PR/rp04FDHH769FKwLIgIgsGXk0laSwp+
Uo7pOpKp8J1oJAQgCvBaMLma84NhqbZKuoSzf9vm4RDo6hWgl78wrFROcdkE
1VHM4vMDhO9KBYBloiAtICs/Ia5gKm/AJcLYjiAs85a3QNXNJrzfYQzaY+97
NuFRYPVqjI9yYDMAhBlgV+MucYVe8qm9wRXt7Yuyk4AJoPFRYmruSx23rnwp
dWl57W9Z+ggaFl5MCsLHXUQ19UXiCJPmYFkcwEoJJy3lB8L4LdfZd6WR4tw/
tsGuyjkFxwQUtxWUh8PQj26YwY4EYKygNIPU9qz1aK+Wysfgq8kH8cpxVba+
9VGJtpB9xJqXnppEI/V1ONfHuWu7wzZyllcc5Cb+S3SM/nvRUybIXUotcu5y
PJ3l7RCSvhpzqGWKBnrTMlqby6jcMkWggSolIE/gkUuBIGXQjYXSarcm+TOK
W5viqF2rwaSiNQsJ6khV8ikzDQ8LQfkYT7HQv3/ie7VN+URW0v2VvVRC0T0f
12ULby89vxWW4C+XmEn9zbVgt3PSzm5pqrtopk/oWg+RMzdAtd3L4kLcDOdG
KayfCfXaTt6UTaa7LjcZ5ha+4GwpCkXa050Xfh8Um+ZNwAgRhU39k6OiEuOu
/rmYqJ+DfrI13Nn75zQnl1zUpZnKhcokdHyuT9vfZ4s4dPuKO918etXJSque
KFoi0F7spBjigY8qUDeCOTKEU4CAK62FU47R80gXiTr0cI65pGg9sSrUkV9a
C+sgIwsfkmdQ9fpJjDMEsbqSq5pZoGtIuT2FA7xwR3VzM2dnMzpCM2D351gN
Z0TLhGvms1rPzkenfSKfJ093976ju25lmAdFUYKKzShHkwd7IC/sPnvy6LuY
dYUFoOU+Sr7O0qy5UbUERcJQGLzGK5YIinhca423S/cx4XQ0FN0NrJnIfBVX
5DFdw0YDoJZoV3rnQCDRBu5KgBZ2pMv31KEH+lVtu3i7wgFyVEBkHDkfRjpp
VmnMbq1sMquzb2sauxKtvoCfry7XUSNnTd0RXyet13vj/EOCzbVZ+zexl6i/
Hxdl6JFvFFRTupoeh9Y7aMVIJNnNaSCmrG46b+ns4T0u4e5TteevmWH4yGmY
7M7avh4jzKYvG0nMzJeSec0nhl0bdLLInzBLMYlJcGJkTpZuDvKchu5kkK5y
W5C5ZoqOKgl68jI6pegsh+H5RGr0bHuEbJsZkp7jR7Dbyog2TnHkExFfpM1u
rEbxg04XRdXKVJfW0KcIIZgslvyi4s15LV5LUdjN9EQjLhcm6GrU3WgkCKfj
vAn7SvcEsxhWQiJW3qZc3zAWSUWYnTmvLueOB3WzKXeMQMfOeqPPwqdPjsiJ
HNWpNuYd5d6guCJ/QyjlOnFWcd2Fp3rpzLtaEl9eZNmULtt6rakqSBr6qXzY
Qg7DAZUcFLVv2ANau3XWEtOvStjgExEAMIKt01cnDAN4sQIqOSlgExK80QKz
CrZenJz1k5kOyWXP0EhdQh4OBVrhe2BNoguW+3v89DE6CBRmAO3Zam/x4493
HjzCFtGdIYkdZGRfu9wxLWBhPbWqcpGlMALq7JjlCGeJON5MK2PpgozIyYsP
2efPTkcnfR53GvEfQW7gE15vQr5uaqDDOGBB0tp+Aks04JeV5P721//+Au9s
/Ntf/8cA/3hDyiH9hQ3DJzLIkyP4UCtn6Ia+OmlRk7mi5fb9Jn4DvwEhHawP
j2ulU7ORyuuWvioybj3hfwOL0RdUuUfGQFkrWhx9nbztvioPI5gFQZA2KeVG
FBc2q0e8eVql7t528kcprSJeQ4QYuFRgX5ze8fcGDPpWoGVLb8Gmq21R5ygn
TuB3Q9wGwBfOXMk9fR4+1o/8vdPKIRO6HRjpCR02vL7CrNYtJl03wkvp3cVq
DsMq2jGwqgbKQ1rEmJ1B4CLlooerGaxQjqwMhDXsBpX8gkGS56FeVZkW7/eD
M/4JZN6cAmruBfG4XbO2Jl1LCu5HuiCtvW1FKtzH6E53YQEhOx3iAHukqqPE
XKpydXFpL21HtcAwmPB6BH5HhLu/DKABIYW3EQIFqftuTRlWuVQ2bUSTlZDH
+Aq9q7DUq8K5Z922EdpDiSr1qqc23aYFAZH5EqATTU+eZpgKO03EeVZ03cuA
qa1ObKUE6e2INbptoimRo4B9TGR45Qu1u2HdgfeLQ5FuW7GrHTIKp1iqF7iV
+vnU3LyyVvIQm4LfRN4tV9Wy9CItEibsAiVj1sXpzIGx4F0FKYHeADtwKQEA
NPDLkuEpGnTiyzZ5Fka7k0i1rMdQ1mOoQRRzm4pQOdmxZc2J1Ui4KvKePni6
S8Ul3i3LIqYAmGEs6DrOfwsDFNbHJ2kpwfPQVbvuKo8OdJM9fnqxB0w+lcuU
8DY70KfoslW9r4MPkMQcCxPiIiPM1KWU6VmDc2AbR4aI1VFrXLia3ZiBKkC9
RANmpV2KgGFVAwJte46BunnirpuKVHQkO3fRFNMeVVRmyjMJv1SxdpEHgbMg
EwtOWTafSSl9RnODorDisJSWb6Dxo35M1G2rzNDAOWBT61irvP5AYT3142dY
j5NmybpYOAQyufO6nIvO7jIhKfUidS49caMDE3DtiqeGs+6n7MFN2TQ3AUsn
eXSE7hjoDoXX2QlsPkhIpovAFJqxblfcomtS9uPHD7CWtCqXboVc0GA+16PJ
Pvxkgn0XWMJLVnyB98wbNdnEUit7s51uvE6pH62TXFtPh07tOJErblhXq3mh
0UGJYwTxN67HJX/EATOPfmClFCsP81JKbQUVcdbnqRQQXC7tk45lzhRtIq3L
FvMNgpGUqkrBSDcbdMlhlDAItpXkjaUrE2VXw6HUXt62M8AKcVpbiBztB94p
XGQSJwokvMAX/EWKDlZohT0QFkFq5HiFJ8lFacOxyy3rWhubQ0x4j7HBOHrj
MTr1sdoR1WNBHXE1/otgSwLSjXx5YH5PVrVxFhNUNmjNHIWBFCAhVdhIKhqz
FH5RaaQVRvT1HXxdPnwR6vz46cg/+2SHnuWkSPrihVpvu2S9mfrloP3zaZZ1
wpG8QD6N5Q/3kz9ecmbhEfIkdFW9xhgcBvmTEeM4+KZJxxFGAum8J5WZdh+A
8HSr5JAnlOhddNDfb+qEbzIC6c5BesS08utkYkj/dFuo4kdDj+ciy0TRpYiy
27mLEguVUtEi8vxNWeuGrwbkS7ygp9geYJ/7ClpBCBp+PpMcU3/MqShm3hrv
PL0hFxZsMUoTJkF5M3TPcFXNG1KqgRyn/mpQfN0VMHUTMAeLyGiBnhjk6xFN
Qkf33i69L8ttMI5CHNm136AdqtljL0kUe4a4rrHsTDlZ1ElLSqRsjU1qhVZZ
3bSksaOD8EzBTFKuzNqG3HWKazjmz7NJqhB+Yo0oJivxERIpeJ9E3EbtckVB
scEMB/jPgM4kqKXVDfPeIsumGh81uGSCwZi+ULFyFhzwlQL+g/4yuRtSuDDw
dIImE5YOR6u1LZVH2dHTvXH5fzj3Jql2BWixqyInnUCVMBw3vbliIQQDwHnK
DqQNStSMyynlBXGzZQpslCBAOFgYyAWCABN3Q7QBOKrtJdgEgy13ppnfAeeA
4fXCyAyOBPXOpNdDU5nL1HqtSWUtB56Z6dGAuWADs4nsY4OgACpeTCorPMqn
r8nM8CWUh+tokh5oAhr6NsXVBbqABLbAPZ+tSN1zb5KOVlF2xEDEr2Sx085x
cM4zB1/RmL72nATvDPY3YjpPpHJZllE4S5vv6qxFDqqhydx4243ZKVD/K+Ri
CO6Rz588e+owP+8Z8qO6q6Q9oDFh9IjVUrWXeXJcEEaKJPGJMfa3QNvoq7oh
wIJAAWG0mFTylWmi9KT6YJVGmyRWY3NQHJltw0hw582jbEBrRtF/BT44osAg
VlPFsDLfa8aSVFKSJ4pPbOhm6F7vzzD17xJKza7D+LRyJDsP4+jhCIFTtC2u
kvS5y7RazFagrKKRw7iK+lYtbeCvPY/0RTiVBLhhwyABG79mCKubR+CKgW25
TiuHLXROS79AtC6SYyHRgDWdc8mw62w8HFewgxTcnlxmQI9TU14NaHEq+gpx
6hZqaYn3hOSTjI0avHuxRpgZi2wMsBIH7lyWWvwBdKwpiDHBW3vR/zIgl77w
l0KYX3YhQdxg3fmUIJxXjApTokvCPtj7Nl6HrHzeSx1G/wTH2CgCA0ncsnqC
PdIEuJHqXbBWrw/eHHOsXWQFIeVIN06vKRS+dPLZKOQycZUAZOaJ8ko1/8RM
YvNn/WgY4IcjIkgpZ7pdseVJgzL9qG5MAXI7Qtg5lBwMCJKQEurkPB9m0X4W
A510FFckyiFiJvHasCWSavm3IF/OKtV08brzKUhJFArNqU/rUAxFtP0PD8Hq
P2z7u1RLG708ePXKwiTiWAU+ZBRzb4Ct18w17S5SypFOYpWckh3HMLYh0CrG
A1UbyBX1xLFA5JY+HmcLKOX+qurKXx4bKTLkRgJzKMcwqcgT8uN7R7FxF/mv
ufw1R4lEK/WQcyrZjh4r/3xeOxUTVSD/bI4+sPPD02SGVfXSSVXWBgyjRdRR
6aAFdsczCOnpY4iWywV8yra6QNlxfKBQEKtmLzIoPAP0OOEUxbfKOEvWJ9D5
DQpONnCUh5xW4DtpoaajK1DCaV44NSpMSb1OReC5Uanvuwb6rxVWFkA12/5G
q7Ijz52mS96N4FYV3I5BqzV8TMBIWOUIo/s1hRHF4ueECfocjW4H13L3OpV8
s06FG6rVfNJAUyMBGQTX5SLegEpWhdvxG4JeCnxIqoDyrFLRmdWjTqiiMd/M
JZCp+KyCJQGUQBcHg6YHthrWPKbFT9mxm6G7FbRpurXKFYN3gfQA4ooznWJm
B1U5a1auCBx8VLhyJAY070xgBV0MtUyPyF9/VjXbusFefQFFM2+XgEAnDdri
luJ0IbxFt6xk71jlxTZA6WhuuFRhlnzIjDFlrEDEs5FWg5whQ9MPOAZSuYDZ
0Q4J4nt8+x2BBr1SHETttNqca201HgqduQuW0OfiX5cULqpT4ytwnZ8c9eGB
Jp8H0X2ljynYdEz+HXxGkZzumCz4kjjF16uxjbExZBLKspwHp1Uv92t2n1Ny
c4EO0ajSJFEj9FZgpQUvu6R08TVfnlEMbQJTkOOh/hl3MzkyjUgCMlZSitrl
WEZjUi5MPgCpnITA5oQJSoZt0spbB0w3W3hzNrEhubsOxRjCLtXrzsajjyHF
eEp0iKGUZpyJkIPelLcqBHjUSgk2xUAkIJE2wYfoe0yxzCXMcZUxgDmjyJoV
NFmtTBQVObzUDeOZE2Y5yvZprJi8IqMSPzTHuCIlmKdiKJsJ9MW72iSHaA4I
fhrQu5M47u4XHzSB4YJIGRunAoaH5toOpR2F978R2Fv0axgn6UITEi51qcNr
nTA6r/NM2XnuIDZS8cqKhS23Hdj2b2qwnbJrCoT1jaJbG9ZKQMvk5ODNQSte
gqiwIrs27vOuWuolJwWiUhO5aAe+cA+73T3aEvsjXe1g4sJUDOSHXl8RqzB1
v1vO1vqSgIOo/jkPeNsvyPmPau8+e7j7FLWssxIs+OQQ1ri4ST+I0lR80KxF
7Iy4FDOcDBeQPMg4uu3kjxk/Tl2iIVCqqoW+xWCQEmvO+bb3+ZyubwTqhXkP
h8MEwTe9/xdbgc2ffnkBAA==

-->
</rfc>