<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" 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" xml:lang="en" prepTime="2024-06-11T19:33:23" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-evc-07" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9584" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="RTP Payload Format for EVC">RTP Payload Format for Essential Video Coding (EVC)</title>
    <seriesInfo name="RFC" value="9584" stream="IETF"/>
    <author initials="S." surname="Zhao" fullname="Shuai Zhao">
      <organization showOnFrontPage="true">Intel</organization>
      <address>
        <postal>
          <street>2200 Mission College Blvd</street>
          <city>Santa Clara</city>
          <region>California</region>
          <code>95054</code>
          <country>United States of America</country>
        </postal>
        <email>shuai.zhao@ieee.org</email>
      </address>
    </author>
    <author initials="S." surname="Wenger" fullname="Stephan Wenger">
      <organization showOnFrontPage="true">Tencent</organization>
      <address>
        <postal>
          <street>2747 Park Blvd</street>
          <city>Palo Alto</city>
          <region>California</region>
          <code>94588</code>
          <country>United States of America</country>
        </postal>
        <email>stewe@stewe.org</email>
      </address>
    </author>
    <author initials="Y." surname="Lim" fullname="Youngkwon Lim">
      <organization showOnFrontPage="true">Samsung Electronics</organization>
      <address>
        <postal>
          <street>6625 Excellence Way</street>
          <city>Plano</city>
          <region>Texas</region>
          <code>75013</code>
          <country>United States of America</country>
        </postal>
        <email>yklwhite@gmail.com</email>
      </address>
    </author>
    <date month="06" year="2024"/>
    <area>WIT</area>
    <workgroup>avtcore</workgroup>
    <keyword>EVC</keyword>
    <keyword>ISO/IEC 23094-1</keyword>
    <keyword>Essential Video Coding</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">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 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>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9584" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2024 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2">
              <li pn="section-toc.1-1.1.2.1">
                <t indent="0" pn="section-toc.1-1.1.2.1.1"><xref derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-overview-of-the-evc-codec">Overview of the EVC Codec</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2.1.2">
                  <li pn="section-toc.1-1.1.2.1.2.1">
                    <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.2.1.1"><xref derivedContent="1.1.1" format="counter" sectionFormat="of" target="section-1.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-coding-tool-features-inform">Coding-Tool Features (Informative)</xref></t>
                  </li>
                  <li pn="section-toc.1-1.1.2.1.2.2">
                    <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.2.2.1"><xref derivedContent="1.1.2" format="counter" sectionFormat="of" target="section-1.1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-systems-and-transport-inter">Systems and Transport Interfaces</xref></t>
                  </li>
                  <li pn="section-toc.1-1.1.2.1.2.3">
                    <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.2.3.1"><xref derivedContent="1.1.3" format="counter" sectionFormat="of" target="section-1.1.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-parallel-processing-support">Parallel Processing Support (Informative)</xref></t>
                  </li>
                  <li pn="section-toc.1-1.1.2.1.2.4">
                    <t indent="0" pn="section-toc.1-1.1.2.1.2.4.1"><xref derivedContent="1.1.4" format="counter" sectionFormat="of" target="section-1.1.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-nal-unit-header">NAL Unit Header</xref></t>
                  </li>
                </ul>
              </li>
              <li pn="section-toc.1-1.1.2.2">
                <t indent="0" pn="section-toc.1-1.1.2.2.1"><xref derivedContent="1.2" format="counter" sectionFormat="of" target="section-1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-overview-of-the-payload-for">Overview of the Payload Format</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions">Conventions</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-definitions-and-abbreviatio">Definitions and Abbreviations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2">
              <li pn="section-toc.1-1.3.2.1">
                <t indent="0" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-definitions">Definitions</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2.1.2">
                  <li pn="section-toc.1-1.3.2.1.2.1">
                    <t indent="0" pn="section-toc.1-1.3.2.1.2.1.1"><xref derivedContent="3.1.1" format="counter" sectionFormat="of" target="section-3.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-definitions-from-the-evc-st">Definitions from the EVC Standard</xref></t>
                  </li>
                  <li pn="section-toc.1-1.3.2.1.2.2">
                    <t indent="0" pn="section-toc.1-1.3.2.1.2.2.1"><xref derivedContent="3.1.2" format="counter" sectionFormat="of" target="section-3.1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-definitions-specific-to-thi">Definitions Specific to This Document</xref></t>
                  </li>
                </ul>
              </li>
              <li pn="section-toc.1-1.3.2.2">
                <t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-abbreviations">Abbreviations</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-rtp-payload-format">RTP Payload Format</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-rtp-header-usage">RTP Header Usage</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.2">
                <t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-payload-header-usage">Payload Header Usage</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.3">
                <t indent="0" pn="section-toc.1-1.4.2.3.1"><xref derivedContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-payload-structures">Payload Structures</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2.3.2">
                  <li pn="section-toc.1-1.4.2.3.2.1">
                    <t indent="0" pn="section-toc.1-1.4.2.3.2.1.1"><xref derivedContent="4.3.1" format="counter" sectionFormat="of" target="section-4.3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-single-nal-unit-packets">Single NAL Unit Packets</xref></t>
                  </li>
                  <li pn="section-toc.1-1.4.2.3.2.2">
                    <t indent="0" pn="section-toc.1-1.4.2.3.2.2.1"><xref derivedContent="4.3.2" format="counter" sectionFormat="of" target="section-4.3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-aggregation-packets-aps">Aggregation Packets (APs)</xref></t>
                  </li>
                  <li pn="section-toc.1-1.4.2.3.2.3">
                    <t indent="0" pn="section-toc.1-1.4.2.3.2.3.1"><xref derivedContent="4.3.3" format="counter" sectionFormat="of" target="section-4.3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-fragmentation-units-fus">Fragmentation Units (FUs)</xref></t>
                  </li>
                </ul>
              </li>
              <li pn="section-toc.1-1.4.2.4">
                <t indent="0" pn="section-toc.1-1.4.2.4.1"><xref derivedContent="4.4" format="counter" sectionFormat="of" target="section-4.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-decoding-order-number">Decoding Order Number</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-packetization-rules">Packetization Rules</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-de-packetization-process">De-packetization Process</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-payload-format-parameters">Payload Format Parameters</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.7.2">
              <li pn="section-toc.1-1.7.2.1">
                <t indent="0" pn="section-toc.1-1.7.2.1.1"><xref derivedContent="7.1" format="counter" sectionFormat="of" target="section-7.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-media-type-registration">Media Type Registration</xref></t>
              </li>
              <li pn="section-toc.1-1.7.2.2">
                <t indent="0" pn="section-toc.1-1.7.2.2.1"><xref derivedContent="7.2" format="counter" sectionFormat="of" target="section-7.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-optional-parameters-definit">Optional Parameters Definition</xref></t>
              </li>
              <li pn="section-toc.1-1.7.2.3">
                <t indent="0" pn="section-toc.1-1.7.2.3.1"><xref derivedContent="7.3" format="counter" sectionFormat="of" target="section-7.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-sdp-parameters">SDP Parameters</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.7.2.3.2">
                  <li pn="section-toc.1-1.7.2.3.2.1">
                    <t indent="0" pn="section-toc.1-1.7.2.3.2.1.1"><xref derivedContent="7.3.1" format="counter" sectionFormat="of" target="section-7.3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-mapping-of-payload-type-par">Mapping of Payload Type Parameters to SDP</xref></t>
                  </li>
                  <li pn="section-toc.1-1.7.2.3.2.2">
                    <t indent="0" pn="section-toc.1-1.7.2.3.2.2.1"><xref derivedContent="7.3.2" format="counter" sectionFormat="of" target="section-7.3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-usage-with-sdp-offer-answer">Usage with SDP Offer/Answer Model</xref></t>
                  </li>
                  <li pn="section-toc.1-1.7.2.3.2.3">
                    <t indent="0" pn="section-toc.1-1.7.2.3.2.3.1"><xref derivedContent="7.3.3" format="counter" sectionFormat="of" target="section-7.3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-multicast">Multicast</xref></t>
                  </li>
                  <li pn="section-toc.1-1.7.2.3.2.4">
                    <t indent="0" pn="section-toc.1-1.7.2.3.2.4.1"><xref derivedContent="7.3.4" format="counter" sectionFormat="of" target="section-7.3.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-usage-in-declarative-sessio">Usage in Declarative Session Descriptions</xref></t>
                  </li>
                  <li pn="section-toc.1-1.7.2.3.2.5">
                    <t indent="0" pn="section-toc.1-1.7.2.3.2.5.1"><xref derivedContent="7.3.5" format="counter" sectionFormat="of" target="section-7.3.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-considerations-for-paramete">Considerations for Parameter Sets</xref></t>
                  </li>
                </ul>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-use-with-feedback-messages">Use with Feedback Messages</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.8.2">
              <li pn="section-toc.1-1.8.2.1">
                <t indent="0" pn="section-toc.1-1.8.2.1.1"><xref derivedContent="8.1" format="counter" sectionFormat="of" target="section-8.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-picture-loss-indication-pli">Picture Loss Indication (PLI)</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.2">
                <t indent="0" pn="section-toc.1-1.8.2.2.1"><xref derivedContent="8.2" format="counter" sectionFormat="of" target="section-8.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-full-intra-request-fir">Full Intra Request (FIR)</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="10" format="counter" sectionFormat="of" target="section-10"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-congestion-control">Congestion Control</xref></t>
          </li>
          <li pn="section-toc.1-1.11">
            <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="11" format="counter" sectionFormat="of" target="section-11"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.12">
            <t indent="0" pn="section-toc.1-1.12.1"><xref derivedContent="12" format="counter" sectionFormat="of" target="section-12"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.12.2">
              <li pn="section-toc.1-1.12.2.1">
                <t indent="0" pn="section-toc.1-1.12.2.1.1"><xref derivedContent="12.1" format="counter" sectionFormat="of" target="section-12.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.12.2.2">
                <t indent="0" pn="section-toc.1-1.12.2.2.1"><xref derivedContent="12.2" format="counter" sectionFormat="of" target="section-12.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.13">
            <t indent="0" pn="section-toc.1-1.13.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.14">
            <t indent="0" pn="section-toc.1-1.14.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">The Essential Video Coding <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> standard,  which is formally designated as ISO/IEC International Standard 23094-1 <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>, was published in 2020.  One of MPEG's goals is to keep 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" format="default" sectionFormat="of" derivedContent="EVC"/> are reported to provide coding efficiency gains over High Efficiency Video Coding <xref target="HEVC" format="default" sectionFormat="of" derivedContent="HEVC"/> and Advanced Video Coding <xref target="AVC" format="default" sectionFormat="of" derivedContent="AVC"/> under certain configurations.</t>
      <t indent="0" pn="section-1-2">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" format="default" sectionFormat="of" derivedContent="RFC6184"/>, Scalable Video Coding (SVC) <xref target="RFC6190" format="default" sectionFormat="of" derivedContent="RFC6190"/>, High Efficiency Video Coding (HEVC) <xref target="RFC7798" format="default" sectionFormat="of" derivedContent="RFC7798"/>, and Versatile Video Coding (VVC) <xref target="RFC9328" format="default" sectionFormat="of" derivedContent="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" format="default" sectionFormat="of" derivedContent="RFC6184"/> is widely deployed and generally known in the relevant implementer communities.  Certain mechanisms described in <xref target="RFC6190" format="default" sectionFormat="of" derivedContent="RFC6190"/> were incorporated, as EVC supports temporal scalability. EVC currently does not offer higher forms of scalability.</t>
      <section anchor="overview-of-the-evc-codec" numbered="true" removeInRFC="false" toc="include" pn="section-1.1">
        <name slugifiedName="name-overview-of-the-evc-codec">Overview of the EVC Codec</name>
        <t indent="0" pn="section-1.1-1">The codings described in <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>, <xref target="AVC" format="default" sectionFormat="of" derivedContent="AVC"/>, <xref target="HEVC" format="default" sectionFormat="of" derivedContent="HEVC"/>, and <xref target="VVC" format="default" sectionFormat="of" derivedContent="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" format="default" sectionFormat="of" derivedContent="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 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_info of <xref target="VVC" format="default" sectionFormat="of" derivedContent="VVC"/>.</t>
        <t indent="0" pn="section-1.1-2">Conceptually, all EVC, AVC, HEVC, and VVC include a Video Coding Layer (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" numbered="true" removeInRFC="false" toc="include" pn="section-1.1.1">
          <name slugifiedName="name-coding-tool-features-inform">Coding-Tool Features (Informative)</name>
          <dl newline="true" indent="3" spacing="normal" pn="section-1.1.1-1">
            <dt pn="section-1.1.1-1.1">Coding blocks and transform structure</dt>
            <dd pn="section-1.1.1-1.2">
              <t indent="0" pn="section-1.1.1-1.2.1">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 profiles utilize HEVC-like quad-tree-blocks partitioning
          that allows a block to be divided horizontally and vertically 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 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 indent="0" pn="section-1.1.1-1.2.2">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 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 RLE-based approach to encode the quantized coefficients.</t>
            </dd>
            <dt pn="section-1.1.1-1.3">Entropy coding</dt>
            <dd pn="section-1.1.1-1.4">
              <t indent="0" pn="section-1.1.1-1.4.1">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>
            </dd>
            <dt pn="section-1.1.1-1.5">In-loop filtering</dt>
            <dd pn="section-1.1.1-1.6">
              <t indent="0" pn="section-1.1.1-1.6.1">The Baseline profile of EVC uses the deblocking filter defined in H.263 Annex J <xref target="VIDEO-CODING" format="default" sectionFormat="of" derivedContent="VIDEO-CODING"/>. 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. 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 signals of up to 25 different filters to be sent for the luma 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>
            </dd>
            <dt pn="section-1.1.1-1.7">Inter prediction</dt>
            <dd pn="section-1.1.1-1.8">
              <t indent="0" pn="section-1.1.1-1.8.1">The basis of 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" mode. The Main profile includes six additional tools to provide improved 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>
            </dd>
            <dt pn="section-1.1.1-1.9">Intra prediction and intra coding</dt>
            <dd pn="section-1.1.1-1.10">
              <t indent="0" pn="section-1.1.1-1.10.1">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 Enhanced Intra Prediction Directions (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>
            </dd>
            <dt pn="section-1.1.1-1.11">Reference frames management</dt>
            <dd pn="section-1.1.1-1.12">
              <t indent="0" pn="section-1.1.1-1.12.1">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 sequence parameter set (SPS). For the Main profile, DPB management can be handled much more flexibly using explicitly signaled Reference Picture Lists (RPLs) in the SPS or slice level.</t>
            </dd>
          </dl>
        </section>
        <section anchor="systems-and-transport-interfaces" numbered="true" removeInRFC="false" toc="include" pn="section-1.1.2">
          <name slugifiedName="name-systems-and-transport-inter">Systems and Transport Interfaces</name>
          <t indent="0" pn="section-1.1.2-1">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 (i.e., SPS), two picture-level parameter sets (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 indent="0" pn="section-1.1.2-2">A number of key components that influenced the NAL design of EVC as well as this document are described below:</t>
          <dl newline="true" indent="3" spacing="normal" pn="section-1.1.2-3">
            <dt pn="section-1.1.2-3.1">Sequence parameter set</dt>
            <dd pn="section-1.1.2-3.2">
              <t indent="0" pn="section-1.1.2-3.2.1">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 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 Multipoint Control Units (MCUs) involved), a CVS can be as long in duration as the whole session.</t>
            </dd>
            <dt pn="section-1.1.2-3.3">Picture and adaptation parameter set</dt>
            <dd pn="section-1.1.2-3.4">
              <t indent="0" pn="section-1.1.2-3.4.1">The Picture Parameter Set (PPS) and the Adaptation Parameter Set (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; whereas the APS contains information, such as adaptive loop filter coefficients, that are likely to change from picture to picture.</t>
            </dd>
            <dt pn="section-1.1.2-3.5">Profile, level, and toolsets</dt>
            <dd pn="section-1.1.2-3.6">
              <t indent="0" pn="section-1.1.2-3.6.1">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 be confused with the "toolset" discussed below) that a decoder compliant with this profile has to support. In EVC, profiles are defined in Annex A of <xref target="EVC" format="default" sectionFormat="of" derivedContent="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 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>
              <t indent="0" pn="section-1.1.2-3.6.2">Profiles and levels are signaled in the highest parameter set available, the SPS.</t>
              <t indent="0" pn="section-1.1.2-3.6.3">EVC contains another mechanism related to the use of coding tools, known as the toolset syntax elements. These syntax elements, toolset_idc_h and toolset_idc_l (located in the SPS), are bitmasks that 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>
            </dd>
            <dt pn="section-1.1.2-3.7">Bitstream and elementary stream</dt>
            <dd pn="section-1.1.2-3.8">
              <t indent="0" pn="section-1.1.2-3.8.1">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>
            </dd>
            <dt pn="section-1.1.2-3.9">Random access support</dt>
            <dd pn="section-1.1.2-3.10">
              <t indent="0" pn="section-1.1.2-3.10.1">EVC supports random access mechanisms based on IDR and clean random access (CRA) access units.</t>
            </dd>
            <dt pn="section-1.1.2-3.11">Temporal scalability support</dt>
            <dd pn="section-1.1.2-3.12">
              <t indent="0" pn="section-1.1.2-3.12.1">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>
            </dd>
            <dt pn="section-1.1.2-3.13">Reference picture management</dt>
            <dd pn="section-1.1.2-3.14">
              <t indent="0" pn="section-1.1.2-3.14.1">EVC's reference picture management is POC-based, similar to HEVC. In the Main profile, substantially all reference picture list manipulations available in HEVC are specified, including explicit transmissions or updates of reference picture 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>
            </dd>
            <dt pn="section-1.1.2-3.15">SEI Message</dt>
            <dd pn="section-1.1.2-3.16">
              <t indent="0" pn="section-1.1.2-3.16.1">EVC inherits many of HEVC's SEI messages, occasionally with syntax and/or semantics changes, making them applicable to EVC. 
In addition, some of the codec-agnostic SEI messages of the VSEI specification <xref target="VSEI" format="default" sectionFormat="of" derivedContent="VSEI"/> are also mapped.</t>
            </dd>
          </dl>
        </section>
        <section anchor="parallel-processing-support-informative" numbered="true" removeInRFC="false" toc="include" pn="section-1.1.3">
          <name slugifiedName="name-parallel-processing-support">Parallel Processing Support (Informative)</name>
          <t indent="0" pn="section-1.1.3-1">EVC's Baseline profile includes no tools specifically addressing
          parallel-processing support. The Main profile includes independently
          decodable slices for parallel processing.  The slices are defined as
          any rectangular region within a picture. They can be encoded to have
          coding dependencies with other slices from the previous picture but
          not with other slices in the same picture. No specific support for
          parallel processing is specified in this RTP payload format.</t>
        </section>
        <section anchor="NALUnitHeader" numbered="true" removeInRFC="false" toc="include" pn="section-1.1.4">
          <name slugifiedName="name-nal-unit-header">NAL Unit Header</name>
          <t indent="0" pn="section-1.1.4-1">EVC maintains the NAL unit concept of <xref target="VVC" format="default" sectionFormat="of" derivedContent="VVC"/> with different parameter options. EVC also uses a two-byte NAL unit header, as shown in <xref target="evc-nuh" format="default" sectionFormat="of" derivedContent="Figure 1"/>.  The payload of a NAL unit refers to the NAL unit excluding the NAL unit header.</t>
          <figure anchor="evc-nuh" align="left" suppress-title="false" pn="figure-1">
            <name slugifiedName="name-the-structure-of-the-evc-na">The Structure of the EVC NAL Unit Header</name>
            <artwork align="left" pn="section-1.1.4-2.1">
                     0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 
                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                    |F|   Type    | TID | Reserve |E|
                    +-------------+-----------------+</artwork>
          </figure>
          <t indent="0" pn="section-1.1.4-3">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>
          <dl indent="3" newline="false" spacing="normal" pn="section-1.1.4-4">
            <dt pn="section-1.1.4-4.1">F:</dt>
            <dd pn="section-1.1.4-4.2">
              <t indent="0" pn="section-1.1.4-4.2.1">1 bit</t>
              <dl indent="3" newline="false" spacing="normal" pn="section-1.1.4-4.2.2">
                <dt pn="section-1.1.4-4.2.2.1">forbidden_zero_bit:</dt>
                <dd pn="section-1.1.4-4.2.2.2">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" format="default" sectionFormat="of" derivedContent="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" format="default" sectionFormat="of" derivedContent="Section 4.3.3"/>.</dd>
              </dl>
            </dd>
            <dt pn="section-1.1.4-4.3">Type:</dt>
            <dd pn="section-1.1.4-4.4">
              <t indent="0" pn="section-1.1.4-4.4.1">6 bits</t>
              <dl indent="3" newline="false" spacing="normal" pn="section-1.1.4-4.4.2">
                <dt pn="section-1.1.4-4.4.2.1">nal_unit_type_plus1:</dt>
                <dd pn="section-1.1.4-4.4.2.2">
                  <t indent="0" pn="section-1.1.4-4.4.2.2.1">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>
                  <t indent="0" pn="section-1.1.4-4.4.2.2.2">NalUnitType = nal_unit_type_plus1 - 1.</t>
                  <t indent="0" pn="section-1.1.4-4.4.2.2.3">The NAL unit type is detailed in Table 4 of <xref target="EVC" format="default" sectionFormat="of" derivedContent="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 of <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>. Note that
	      nal_unit_type_plus1 <bcp14>MUST NOT</bcp14> be zero.</t>
                </dd>
              </dl>
            </dd>
            <dt pn="section-1.1.4-4.5">TID:</dt>
            <dd pn="section-1.1.4-4.6">
              <t indent="0" pn="section-1.1.4-4.6.1">3 bits</t>
              <dl indent="3" newline="false" spacing="normal" pn="section-1.1.4-4.6.2">
                <dt pn="section-1.1.4-4.6.2.1">nuh_temporal_id:</dt>
                <dd pn="section-1.1.4-4.6.2.2">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).</dd>
              </dl>
            </dd>
            <dt pn="section-1.1.4-4.7">Reserve:</dt>
            <dd pn="section-1.1.4-4.8">
              <t indent="0" pn="section-1.1.4-4.8.1">5 bits</t>
              <dl indent="3" newline="false" spacing="normal" pn="section-1.1.4-4.8.2">
                <dt pn="section-1.1.4-4.8.2.1">nuh_reserved_zero_5bits:</dt>
                <dd pn="section-1.1.4-4.8.2.2">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 Annex A of <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> shall ignore
	    (i.e., remove from the bitstream and discard) all NAL units with
	    values of nuh_reserved_zero_5bits greater than 0.</dd>
              </dl>
            </dd>
            <dt pn="section-1.1.4-4.9">E:</dt>
            <dd pn="section-1.1.4-4.10">
              <t indent="0" pn="section-1.1.4-4.10.1">1 bit</t>
              <dl indent="3" newline="false" spacing="normal" pn="section-1.1.4-4.10.2">
                <dt pn="section-1.1.4-4.10.2.1">nuh_extension_flag:</dt>
                <dd pn="section-1.1.4-4.10.2.2">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 Annex A of <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> shall ignore
	    (i.e., remove from the bitstream and discard) all NAL units with
	    values of nuh_extension_flag equal to 1.</dd>
              </dl>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="overview-of-the-payload-format" numbered="true" removeInRFC="false" toc="include" pn="section-1.2">
        <name slugifiedName="name-overview-of-the-payload-for">Overview of the Payload Format</name>
        <t indent="0" pn="section-1.2-1">This payload format defines the following processes required for transport of EVC-coded data over RTP <xref target="RFC3550" format="default" sectionFormat="of" derivedContent="RFC3550"/>:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1.2-2">
          <li pn="section-1.2-2.1">usage of RTP header with this payload format</li>
          <li pn="section-1.2-2.2">packetization of EVC-coded NAL units into RTP packets using
          three types of payload structures: a single NAL unit, aggregation,
          and fragment unit</li>
          <li pn="section-1.2-2.3">transmission of EVC NAL units of the same bitstream within a
          single RTP stream</li>
          <li pn="section-1.2-2.4">usage of media type parameters to be used with the Session
          Description Protocol (SDP) <xref target="RFC8866" format="default" sectionFormat="of" derivedContent="RFC8866"/></li>
          <li pn="section-1.2-2.5">usage of RTCP feedback messages</li>
        </ul>
      </section>
    </section>
    <section anchor="conventions" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-conventions">Conventions</name>
      <t indent="0" pn="section-2-1">
    The key words "<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 "<bcp14>OPTIONAL</bcp14>" in this document are to be
    interpreted as described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they appear in all capitals, as
    shown here.
      </t>
    </section>
    <section anchor="definitionsandabbr" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-definitions-and-abbreviatio">Definitions and Abbreviations</name>
      <section anchor="definitions" numbered="true" removeInRFC="false" toc="include" pn="section-3.1">
        <name slugifiedName="name-definitions">Definitions</name>
        <t indent="0" pn="section-3.1-1">This document uses the terms and definitions of EVC.  <xref target="definitionforevc" format="default" sectionFormat="of" derivedContent="Section 3.1.1"/>
lists relevant definitions from <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> for convenience.  <xref target="def" format="default" sectionFormat="of" derivedContent="Section 3.1.2"/>
provides definitions specific to this document.</t>
        <section anchor="definitionforevc" numbered="true" removeInRFC="false" toc="include" pn="section-3.1.1">
          <name slugifiedName="name-definitions-from-the-evc-st">Definitions from the EVC Standard</name>
          <dl spacing="normal" newline="true" indent="3" pn="section-3.1.1-1">
            <dt pn="section-3.1.1-1.1">Access Unit (AU):</dt>
            <dd pn="section-3.1.1-1.2">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.</dd>
            <dt pn="section-3.1.1-1.3">Adaptation Parameter Set (APS):</dt>
            <dd pn="section-3.1.1-1.4">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.</dd>
            <dt pn="section-3.1.1-1.5">Bitstream:</dt>
            <dd pn="section-3.1.1-1.6">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 CVSs.</dd>
            <dt pn="section-3.1.1-1.7">Coded Picture:</dt>
            <dd pn="section-3.1.1-1.8">A coded representation of a picture containing all CTUs of the
	    picture.</dd>
            <dt pn="section-3.1.1-1.9">Coded Video Sequence (CVS):</dt>
            <dd pn="section-3.1.1-1.10">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.</dd>
            <dt pn="section-3.1.1-1.11">Coding Tree Block (CTB):</dt>
            <dd pn="section-3.1.1-1.12">An NxN block of samples for some value of N such that the
	    division of a component into CTBs is a partitioning.</dd>
            <dt pn="section-3.1.1-1.13">Coding Tree Unit (CTU):</dt>
            <dd pn="section-3.1.1-1.14">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 color planes and syntax structures used to code
	    the samples.</dd>
            <dt pn="section-3.1.1-1.15">Decoded Picture:</dt>
            <dd pn="section-3.1.1-1.16">A decoded picture is derived by decoding a coded picture.</dd>
            <dt pn="section-3.1.1-1.17">Decoded Picture Buffer (DPB):</dt>
            <dd pn="section-3.1.1-1.18">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" format="default" sectionFormat="of" derivedContent="EVC"/>
	    standard.</dd>
            <dt pn="section-3.1.1-1.19">Dynamic Range Adjustment (DRA):</dt>
            <dd pn="section-3.1.1-1.20">A mapping process that is applied to the decoded picture prior to
	    cropping and output as part of the decoding process; it is
	    controlled by parameters conveyed in an Adaptation Parameter Set
	    (APS).</dd>
            <dt pn="section-3.1.1-1.21">Hypothetical Reference Decoder (HRD):</dt>
            <dd pn="section-3.1.1-1.22">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.</dd>
            <dt pn="section-3.1.1-1.23">IDR Access Unit:</dt>
            <dd pn="section-3.1.1-1.24">An access unit in which the coded picture is an IDR picture.</dd>
            <dt pn="section-3.1.1-1.25">IDR Picture:</dt>
            <dd pn="section-3.1.1-1.26">The coded picture for which each VCL NAL unit has NalUnitType equal to IDR_NUT.</dd>
            <dt pn="section-3.1.1-1.27">Level:</dt>
            <dd pn="section-3.1.1-1.28">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.</dd>
            <dt pn="section-3.1.1-1.29">Network Abstraction Layer (NAL) Unit:</dt>
            <dd pn="section-3.1.1-1.30">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.</dd>
            <dt pn="section-3.1.1-1.31">Network Abstraction Layer (NAL) Unit Stream:</dt>
            <dd pn="section-3.1.1-1.32">A sequence of NAL units.</dd>
            <dt pn="section-3.1.1-1.33">Non-IDR Picture:</dt>
            <dd pn="section-3.1.1-1.34">A coded picture that is not an IDR picture.</dd>
            <dt pn="section-3.1.1-1.35">Non-VCL NAL Unit:</dt>
            <dd pn="section-3.1.1-1.36">A NAL unit that is not a VCL NAL unit.</dd>
            <dt pn="section-3.1.1-1.37">Picture Parameter Set (PPS):</dt>
            <dd pn="section-3.1.1-1.38">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.</dd>
            <dt pn="section-3.1.1-1.39">Picture Order Count (POC):</dt>
            <dd pn="section-3.1.1-1.40">A variable that is associated with each picture, uniquely
	    identifies the associated picture among all pictures in the CVS,
	    and (when the associated picture is to be output from the 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
	    DPB.</dd>
            <dt pn="section-3.1.1-1.41">Raw Byte Sequence Payload (RBSP):</dt>
            <dd pn="section-3.1.1-1.42">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.</dd>
            <dt pn="section-3.1.1-1.43">Sequence Parameter Set (SPS):</dt>
            <dd pn="section-3.1.1-1.44">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.</dd>
            <dt pn="section-3.1.1-1.45">Slice:</dt>
            <dd pn="section-3.1.1-1.46">An integer number of tiles of a picture in the tile scan of
	    the picture, exclusively contained in a single NAL unit.</dd>
            <dt pn="section-3.1.1-1.47">Tile:</dt>
            <dd pn="section-3.1.1-1.48">A rectangular region of CTUs within a particular tile column and
	    a particular tile row in a picture.</dd>
            <dt pn="section-3.1.1-1.49">Tile Column:</dt>
            <dd pn="section-3.1.1-1.50">A rectangular region of CTUs having a height equal to the height
	    of the picture and width specified by syntax elements in the
	    PPS.</dd>
            <dt pn="section-3.1.1-1.51">Tile Row:</dt>
            <dd pn="section-3.1.1-1.52">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.</dd>
            <dt pn="section-3.1.1-1.53">Tile Scan:</dt>
            <dd pn="section-3.1.1-1.54">A specific sequential ordering of CTUs partitioning a picture
	    in which the CTUs are ordered consecutively in CTU raster scan in
	    a tile, whereas tiles in a picture are ordered consecutively in a
	    raster scan of the tiles of the picture.</dd>
            <dt pn="section-3.1.1-1.55">Video Coding Layer (VCL) NAL Unit:</dt>
            <dd pn="section-3.1.1-1.56">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.</dd>
          </dl>
        </section>
        <section anchor="def" numbered="true" removeInRFC="false" toc="include" pn="section-3.1.2">
          <name slugifiedName="name-definitions-specific-to-thi">Definitions Specific to This Document</name>
          <dl newline="true" spacing="normal" indent="3" pn="section-3.1.2-1">
            <dt pn="section-3.1.2-1.1">Media-Aware Network Element (MANE):</dt>
            <dd pn="section-3.1.2-1.2">
              <t indent="0" pn="section-3.1.2-1.2.1">A network
            element, such as a middlebox, selective forwarding unit, or
            application-layer gateway, that is capable of parsing certain
            aspects of the RTP payload headers or the RTP payload and reacting
            to their contents.</t>
              <aside pn="section-3.1.2-1.2.2">
                <t indent="0" pn="section-3.1.2-1.2.2.1">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
	    <xref target="RFC3550" section="7" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3550#section-7" derivedContent="RFC3550"/>.</t>
              </aside>
            </dd>
            <dt pn="section-3.1.2-1.3">NAL unit decoding order:</dt>
            <dd pn="section-3.1.2-1.4">A NAL unit order that conforms
	  to the constraints on NAL unit order given in Section 7.4.2.3 of
	  <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> and follows the order of NAL units in the
	  bitstream.</dd>
            <dt pn="section-3.1.2-1.5">NALU-time:</dt>
            <dd pn="section-3.1.2-1.6">The value that the RTP timestamp would have
          if the NAL unit would be transported in its own RTP packet.</dd>
            <dt pn="section-3.1.2-1.7">NAL unit output order:</dt>
            <dd pn="section-3.1.2-1.8">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" format="default" sectionFormat="of" derivedContent="EVC"/>, and in which NAL units within an access unit
          are in their decoding order.</dd>
            <dt pn="section-3.1.2-1.9">RTP stream:</dt>
            <dd pn="section-3.1.2-1.10">See <xref target="RFC7656" format="default" sectionFormat="of" derivedContent="RFC7656"/>.  Within the
          scope of this document, one RTP stream is utilized to transport an
          EVC bitstream, which may contain one or more temporal
          sub-layers.</dd>
            <dt pn="section-3.1.2-1.11">Transmission order:</dt>
            <dd pn="section-3.1.2-1.12">The order of packets in ascending
          RTP sequence number order (in modulo arithmetic).  Within an
          Aggregation Packet (AP), the NAL unit transmission order is the same as
          the order of appearance of NAL units in the packet.</dd>
          </dl>
        </section>
      </section>
      <section anchor="abbreviations" numbered="true" removeInRFC="false" toc="include" pn="section-3.2">
        <name slugifiedName="name-abbreviations">Abbreviations</name>
        <dl newline="false" spacing="normal" indent="9" pn="section-3.2-1">
          <dt pn="section-3.2-1.1">AU</dt>
          <dd pn="section-3.2-1.2">Access Unit</dd>
          <dt pn="section-3.2-1.3">AP</dt>
          <dd pn="section-3.2-1.4">Aggregation Packet</dd>
          <dt pn="section-3.2-1.5">APS</dt>
          <dd pn="section-3.2-1.6">Adaptation Parameter Set</dd>
          <dt pn="section-3.2-1.7">ATS</dt>
          <dd pn="section-3.2-1.8">Adaptive Transform Selection</dd>
          <dt pn="section-3.2-1.9">B</dt>
          <dd pn="section-3.2-1.10">Bi-predictive</dd>
          <dt pn="section-3.2-1.11">CBR</dt>
          <dd pn="section-3.2-1.12">Constant Bit Rate</dd>
          <dt pn="section-3.2-1.13">CPB</dt>
          <dd pn="section-3.2-1.14">Coded Picture Buffer</dd>
          <dt pn="section-3.2-1.15">CTB</dt>
          <dd pn="section-3.2-1.16">Coding Tree Block</dd>
          <dt pn="section-3.2-1.17">CTU</dt>
          <dd pn="section-3.2-1.18">Coding Tree Unit</dd>
          <dt pn="section-3.2-1.19">CVS</dt>
          <dd pn="section-3.2-1.20">Coded Video Sequence</dd>
          <dt pn="section-3.2-1.21">DPB</dt>
          <dd pn="section-3.2-1.22">Decoded Picture Buffer</dd>
          <dt pn="section-3.2-1.23">HRD</dt>
          <dd pn="section-3.2-1.24">Hypothetical Reference Decoder</dd>
          <dt pn="section-3.2-1.25">HSS</dt>
          <dd pn="section-3.2-1.26">Hypothetical Stream Scheduler</dd>
          <dt pn="section-3.2-1.27">I</dt>
          <dd pn="section-3.2-1.28">Intra</dd>
          <dt pn="section-3.2-1.29">IDR</dt>
          <dd pn="section-3.2-1.30">Instantaneous Decoding Refresh</dd>
          <dt pn="section-3.2-1.31">LSB</dt>
          <dd pn="section-3.2-1.32">Least Significant Bit</dd>
          <dt pn="section-3.2-1.33">LTRP</dt>
          <dd pn="section-3.2-1.34">Long-Term Reference Picture</dd>
          <dt pn="section-3.2-1.35">MMVD</dt>
          <dd pn="section-3.2-1.36">Merge with Motion Vector Difference</dd>
          <dt pn="section-3.2-1.37">MSB</dt>
          <dd pn="section-3.2-1.38">Most Significant Bit</dd>
          <dt pn="section-3.2-1.39">NAL</dt>
          <dd pn="section-3.2-1.40">Network Abstraction Layer</dd>
          <dt pn="section-3.2-1.41">P</dt>
          <dd pn="section-3.2-1.42">Predictive</dd>
          <dt pn="section-3.2-1.43">POC</dt>
          <dd pn="section-3.2-1.44">Picture Order Count</dd>
          <dt pn="section-3.2-1.45">PPS</dt>
          <dd pn="section-3.2-1.46">Picture Parameter Set</dd>
          <dt pn="section-3.2-1.47">QP</dt>
          <dd pn="section-3.2-1.48">Quantization Parameter</dd>
          <dt pn="section-3.2-1.49">RBSP</dt>
          <dd pn="section-3.2-1.50">Raw Byte Sequence Payload</dd>
          <dt pn="section-3.2-1.51">RGB</dt>
          <dd pn="section-3.2-1.52">Red, Green, and Blue</dd>
          <dt pn="section-3.2-1.53">SAR</dt>
          <dd pn="section-3.2-1.54">Sample Aspect Ratio</dd>
          <dt pn="section-3.2-1.55">SEI</dt>
          <dd pn="section-3.2-1.56">Supplemental Enhancement Information</dd>
          <dt pn="section-3.2-1.57">SODB</dt>
          <dd pn="section-3.2-1.58">String Of Data Bits</dd>
          <dt pn="section-3.2-1.59">SPS</dt>
          <dd pn="section-3.2-1.60">Sequence Parameter Set</dd>
          <dt pn="section-3.2-1.61">STRP</dt>
          <dd pn="section-3.2-1.62">Short-Term Reference Picture</dd>
          <dt pn="section-3.2-1.63">VBR</dt>
          <dd pn="section-3.2-1.64">Variable Bit Rate</dd>
          <dt pn="section-3.2-1.65">VCL</dt>
          <dd pn="section-3.2-1.66">Video Coding Layer</dd>
        </dl>
      </section>
    </section>
    <section anchor="RTPPayloadFormat" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-rtp-payload-format">RTP Payload Format</name>
      <section anchor="RTPHeaderUsage" numbered="true" removeInRFC="false" toc="include" pn="section-4.1">
        <name slugifiedName="name-rtp-header-usage">RTP Header Usage</name>
        <t indent="0" pn="section-4.1-1">The format of the RTP header is specified in <xref target="RFC3550" format="default" sectionFormat="of" derivedContent="RFC3550"/> (included as
<xref target="rtp-header" format="default" sectionFormat="of" derivedContent="Figure 2"/> for convenience).  This payload format uses the fields of
the header in a manner consistent with that specification.</t>
        <t indent="0" pn="section-4.1-2">The RTP payload (and the settings for some RTP header bits) for
APs and Fragmentation Units (FUs) are specified in Sections 
<xref target="aps" format="counter" sectionFormat="of" derivedContent="4.3.2"/> and <xref target="funits" format="counter" sectionFormat="of" derivedContent="4.3.3"/>, respectively.</t>
        <figure anchor="rtp-header" align="left" suppress-title="false" pn="figure-2">
          <name slugifiedName="name-rtp-header-according-to-rfc">RTP Header According to RFC 3550</name>
          <artwork align="left" pn="section-4.1-3.1">
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X|  CC   |M|     PT      |       sequence number         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           timestamp                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                             ....                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
        </figure>
        <t indent="0" pn="section-4.1-4">The RTP header information to be set according to this RTP payload format is set as follows:</t>
        <dl newline="false" spacing="normal" indent="3" pn="section-4.1-5">
          <dt pn="section-4.1-5.1">Marker bit (M):</dt>
          <dd pn="section-4.1-5.2">
            <t indent="0" pn="section-4.1-5.2.1">1 bit</t>
            <t indent="0" pn="section-4.1-5.2.2">Set for the last packet of the access 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>
          </dd>
          <dt pn="section-4.1-5.3">Payload Type (PT):</dt>
          <dd pn="section-4.1-5.4">
            <t indent="0" pn="section-4.1-5.4.1">7 bits</t>
            <t indent="0" pn="section-4.1-5.4.2">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>
          </dd>
          <dt pn="section-4.1-5.5">Sequence Number (SN):</dt>
          <dd pn="section-4.1-5.6">
            <t indent="0" pn="section-4.1-5.6.1">16 bits</t>
            <t indent="0" pn="section-4.1-5.6.2">Set and used in accordance with <xref target="RFC3550" format="default" sectionFormat="of" derivedContent="RFC3550"/>.</t>
          </dd>
          <dt pn="section-4.1-5.7">Timestamp:</dt>
          <dd pn="section-4.1-5.8">
            <t indent="0" pn="section-4.1-5.8.1">32 bits</t>
            <t indent="0" pn="section-4.1-5.8.2">The RTP timestamp is set to the sampling timestamp of the
	  content. A 90 kHz clock rate <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 <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" format="default" sectionFormat="of" derivedContent="EVC"/>. Receivers
	  <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" format="default" sectionFormat="of" derivedContent="EVC"/>.</t>
          </dd>
          <dt pn="section-4.1-5.9">Synchronization source (SSRC):</dt>
          <dd pn="section-4.1-5.10">
            <t indent="0" pn="section-4.1-5.10.1">32 bits</t>
            <t indent="0" pn="section-4.1-5.10.2">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>
          </dd>
        </dl>
      </section>
      <section anchor="PayloadHeaderUsage" numbered="true" removeInRFC="false" toc="include" pn="section-4.2">
        <name slugifiedName="name-payload-header-usage">Payload Header Usage</name>
        <t indent="0" pn="section-4.2-1">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, and E) as the NAL unit header, as shown in <xref target="NALUnitHeader" format="default" sectionFormat="of" derivedContent="Section 1.1.4"/>, irrespective of the type of the payload
        structure.</t>
        <t indent="0" pn="section-4.2-2">The TID value indicates (among other things) the relative
        importance of an RTP packet, for example, because NAL units with
        larger TID values are not used to decode the ones with
        smaller TID values. A lower value of TID indicates a higher
        importance. More important NAL units <bcp14>MAY</bcp14> be better
        protected against transmission losses than less important NAL
        units.</t>
      </section>
      <section anchor="PayloadStructures" numbered="true" removeInRFC="false" toc="include" pn="section-4.3">
        <name slugifiedName="name-payload-structures">Payload Structures</name>
        <t indent="0" pn="section-4.3-1">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 indent="0" pn="section-4.3-2">The three different payload structures are as follows:</t>
        <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-4.3-3">
          <li pn="section-4.3-3.1">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" format="default" sectionFormat="of" derivedContent="Section 4.3.1"/>.</li>
          <li pn="section-4.3-3.2">Aggregation Packet (AP): Contains more than one NAL unit
          within one access unit.  This payload structure is specified in
          <xref target="aps" format="default" sectionFormat="of" derivedContent="Section 4.3.2"/>.</li>
          <li pn="section-4.3-3.3">Fragmentation Unit (FU): Contains a subset of a single
          NAL unit. This payload structure is specified in <xref target="funits" format="default" sectionFormat="of" derivedContent="Section 4.3.3"/>.</li>
        </ul>
        <section anchor="SingleNALUnit" numbered="true" removeInRFC="false" toc="include" pn="section-4.3.1">
          <name slugifiedName="name-single-nal-unit-packets">Single NAL Unit Packets</name>
          <t indent="0" pn="section-4.3.1-1">A single NAL unit packet contains exactly one NAL unit and
          consists of a payload header as defined in Table 4 of <xref target="EVC" format="default" sectionFormat="of" derivedContent="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" format="default" sectionFormat="of" derivedContent="Figure 3"/>.</t>
          <figure anchor="single-nhr" align="left" suppress-title="false" pn="figure-3">
            <name slugifiedName="name-the-structure-of-a-single-n">The Structure of a Single NAL Unit Packet</name>
            <artwork align="left" pn="section-4.3.1-2.1">
   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        |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
          </figure>
          <t indent="0" pn="section-4.3.1-3">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" format="default" sectionFormat="of" derivedContent="Section 7.2"/>) is greater than 0, the DONL field <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 (where sprop-max-don-diff is equal to 0), the DONL field <bcp14>MUST NOT</bcp14> be present.</t>
        </section>
        <section anchor="aps" numbered="true" removeInRFC="false" toc="include" pn="section-4.3.2">
          <name slugifiedName="name-aggregation-packets-aps">Aggregation Packets (APs)</name>
          <t indent="0" pn="section-4.3.2-1">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 indent="0" pn="section-4.3.2-2">An AP aggregates NAL units of one access unit, and it <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 indent="0" pn="section-4.3.2-3">An AP consists of a payload header, as defined in Table 4 of <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> (denoted here as PayloadHdr with Type=56), followed by two or more aggregation units, as shown in <xref target="au-hdr" format="default" sectionFormat="of" derivedContent="Figure 4"/>.</t>
          <figure anchor="au-hdr" align="left" suppress-title="false" pn="figure-4">
            <name slugifiedName="name-the-structure-of-an-aggrega">The Structure of an Aggregation Packet</name>
            <artwork align="left" pn="section-4.3.2-4.1">
  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        |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
          </figure>
          <t indent="0" pn="section-4.3.2-5">The fields in the payload header of an AP are set as follows. The F bit <bcp14>MUST</bcp14> be equal to 0 if the F bit of each aggregated NAL unit is equal to zero; otherwise, it <bcp14>MUST</bcp14> be equal to 1. The Type field <bcp14>MUST</bcp14> be equal to 56.</t>
          <t indent="0" pn="section-4.3.2-6">The value of TID <bcp14>MUST</bcp14> be the smallest value of TID of all the aggregated NAL units. The value of Reserve and E <bcp14>MUST</bcp14> be equal to 0 for this specification.</t>
          <aside pn="section-4.3.2-7">
            <t indent="0" pn="section-4.3.2-7.1">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>
          </aside>
          <t indent="0" pn="section-4.3.2-8">An AP <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 <bcp14>MUST</bcp14> fit into
          an IP packet, and the size <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 <bcp14>MUST NOT</bcp14> contain
          FUs specified in <xref target="funits" format="default" sectionFormat="of" derivedContent="Section 4.3.3"/>. APs <bcp14>MUST NOT</bcp14> be nested; i.e., an AP cannot contain another AP.</t>
          <aside pn="section-4.3.2-9">
            <t indent="0" pn="section-4.3.2-9.1">Informative note: If a receiver encounters nested
	  APs, which is against the aforementioned
	  requirement, it has several options, listed in order of ease of
	  implementation: 1) ignore the nested AP; 2) ignore the nested AP and
	  report a "packet loss" to the decoder, if such functionality exists
	  in the API; and 3) implement support for nested APs and extract the
	  NAL units from these nested APs.</t>
          </aside>
          <t indent="0" pn="section-4.3.2-10">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" format="default" sectionFormat="of" derivedContent="Figure 5"/>.</t>
          <figure anchor="au-first-nhdr" align="left" suppress-title="false" pn="figure-5">
            <name slugifiedName="name-the-structure-of-the-first-">The Structure of the First Aggregation Unit in an AP</name>
            <artwork align="left" pn="section-4.3.2-11.1">
  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                              |
 |                                                               |
 |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                               :
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
          </figure>
          <aside pn="section-4.3.2-12">
            <t indent="0" pn="section-4.3.2-12.1">Informative note: The first octet of <xref target="au-first-nhdr" format="default" sectionFormat="of" derivedContent="Figure 5"/> (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>
          </aside>
          <t indent="0" pn="section-4.3.2-13">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 indent="0" pn="section-4.3.2-14">If sprop-max-don-diff is greater than 0, the DONL field <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 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 (where sprop-max-don-diff is equal to 0), the DONL field <bcp14>MUST NOT</bcp14> be present in an aggregation unit that is the first aggregation unit in an AP.</t>
          <t indent="0" pn="section-4.3.2-15">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" format="default" sectionFormat="of" derivedContent="Figure 6"/>.</t>
          <figure anchor="au-not-first-nhdr" align="left" suppress-title="false" pn="figure-6">
            <name slugifiedName="name-the-structure-of-an-aggregat"> The Structure of an Aggregation Unit That Is Not the First Aggregation Unit in an AP</name>
            <artwork align="left" pn="section-4.3.2-16.1">
  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    |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               |
  |                                                               |
  |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                               :
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
          </figure>
          <aside pn="section-4.3.2-17">
            <t indent="0" pn="section-4.3.2-17.1">Informative note: The first octet of <xref target="au-not-first-nhdr" format="default" sectionFormat="of" derivedContent="Figure 6"/> (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>
          </aside>
          <t indent="0" pn="section-4.3.2-18"><xref target="au-wout-donl" format="default" sectionFormat="of" derivedContent="Figure 7"/> presents an example of an AP that
          contains two aggregation units, labeled "NALU 1" and "NALU 2",
          without the DONL field being present.</t>
          <figure anchor="au-wout-donl" align="left" suppress-title="false" pn="figure-7">
            <name slugifiedName="name-an-example-of-an-ap-packet-">An Example of an AP Packet Containing Two Aggregation Units without the DONL Field</name>
            <artwork align="left" pn="section-4.3.2-19.1">
  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        |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
          </figure>
          <t indent="0" pn="section-4.3.2-20"><xref target="au-with-donl" format="default" sectionFormat="of" derivedContent="Figure 8"/> presents an example of an AP that contains two aggregation
units, labeled "NALU 1" and "NALU 2", with the DONL field being present.</t>
          <figure anchor="au-with-donl" align="left" suppress-title="false" pn="figure-8">
            <name slugifiedName="name-an-example-of-an-ap-contain">An Example of an AP Containing Two Aggregation Units with the DONL Field</name>
            <artwork align="left" pn="section-4.3.2-21.1">
  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        |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
          </figure>
        </section>
        <section anchor="funits" numbered="true" removeInRFC="false" toc="include" pn="section-4.3.3">
          <name slugifiedName="name-fragmentation-units-fus">Fragmentation Units (FUs)</name>
          <t indent="0" pn="section-4.3.3-1">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 <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 indent="0" pn="section-4.3.3-2">When a NAL unit is fragmented and conveyed within FUs, it is referred to as a fragmented NAL unit.  APs <bcp14>MUST NOT</bcp14> be fragmented.  FUs <bcp14>MUST NOT</bcp14> be nested; i.e., an FU must not contain a subset of another FU.</t>
          <t indent="0" pn="section-4.3.3-3">The RTP timestamp of an RTP packet carrying an FU is set to the NALU-time of the fragmented NAL unit.</t>
          <t indent="0" pn="section-4.3.3-4">An FU consists of a payload header as defined in Table 4 of <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> (denoted as PayloadHdr with 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" format="default" sectionFormat="of" derivedContent="Figure 9"/>.</t>
          <figure anchor="fu-payload" align="left" suppress-title="false" pn="figure-9">
            <name slugifiedName="name-the-structure-of-an-fu">The Structure of an FU</name>
            <artwork align="left" pn="section-4.3.3-5.1">
  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        |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
          </figure>
          <t indent="0" pn="section-4.3.3-6">The fields in the payload header are set as follows.  The Type field <bcp14>MUST</bcp14> be equal to 57.  The fields F, TID, Reserve, and E <bcp14>MUST</bcp14> be equal to the fields F, TID, Reserve, and E, respectively, of the fragmented NAL unit.</t>
          <t indent="0" pn="section-4.3.3-7">The FU header consists of an S bit, an E bit, and a 6-bit FuType field, as shown in <xref target="fu-header" format="default" sectionFormat="of" derivedContent="Figure 10"/>.</t>
          <figure anchor="fu-header" align="left" suppress-title="false" pn="figure-10">
            <name slugifiedName="name-the-structure-of-fu-header">The Structure of FU Header</name>
            <artwork align="left" pn="section-4.3.3-8.1">
                           0 1 2 3 4 5 6 7
                          +-+-+-+-+-+-+-+-+
                          |S|E|  FuType   |
                          +---------------+</artwork>
          </figure>
          <t indent="0" pn="section-4.3.3-9">The semantics of the FU header fields are as follows:</t>
          <dl indent="3" newline="false" spacing="normal" pn="section-4.3.3-10">
            <dt pn="section-4.3.3-10.1">S:</dt>
            <dd pn="section-4.3.3-10.2">
              <t indent="0" pn="section-4.3.3-10.2.1">1 bit</t>
              <t indent="0" pn="section-4.3.3-10.2.2">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 <bcp14>MUST</bcp14> be set to 0.</t>
            </dd>
            <dt pn="section-4.3.3-10.3">E:</dt>
            <dd pn="section-4.3.3-10.4">
              <t indent="0" pn="section-4.3.3-10.4.1">1 bit</t>
              <t indent="0" pn="section-4.3.3-10.4.2">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 <bcp14>MUST</bcp14> be set to 0.</t>
            </dd>
            <dt pn="section-4.3.3-10.5">FuType:</dt>
            <dd pn="section-4.3.3-10.6">
              <t indent="0" pn="section-4.3.3-10.6.1">6 bits</t>
              <t indent="0" pn="section-4.3.3-10.6.2">The field FuType <bcp14>MUST</bcp14> be equal to the field Type of the fragmented NAL unit.</t>
            </dd>
          </dl>
          <t indent="0" pn="section-4.3.3-11">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 indent="0" pn="section-4.3.3-12">If sprop-max-don-diff is greater than 0 and the S bit is equal to 1, the DONL field <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 (where sprop-max-don-diff is equal to 0, or where the S bit is equal to 0), the DONL field <bcp14>MUST NOT</bcp14> be present in the FU.</t>
          <t indent="0" pn="section-4.3.3-13">A non-fragmented NAL unit <bcp14>MUST NOT</bcp14> be transmitted in one FU; i.e., the S-bit and E-bit <bcp14>MUST NOT</bcp14> both be set to 1 in the same FU header.</t>
          <t indent="0" pn="section-4.3.3-14">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. Instead, the information of the NAL unit header of the fragmented NAL unit is conveyed in F, TID, 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 <bcp14>MUST NOT</bcp14> be empty.</t>
          <t indent="0" pn="section-4.3.3-15">If an FU is lost, the receiver <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 indent="0" pn="section-4.3.3-16">A receiver in an endpoint or a MANE <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 <bcp14>MUST</bcp14> be set to 1 to indicate a syntax violation.</t>
        </section>
      </section>
      <section anchor="DON" numbered="true" removeInRFC="false" toc="include" pn="section-4.4">
        <name slugifiedName="name-decoding-order-number">Decoding Order Number</name>
        <t indent="0" pn="section-4.4-1">For each NAL unit, the variable AbsDon is derived; it represents the
decoding order number that is indicative of the NAL unit decoding
order.</t>
        <t indent="0" pn="section-4.4-2">Let NAL unit n be the n-th NAL unit in transmission order within an
RTP stream.</t>
        <t indent="0" pn="section-4.4-3">If sprop-max-don-diff is equal to 0, then AbsDon[n] (the value of AbsDon for NAL unit n) is derived as equal to n.</t>
        <t indent="0" pn="section-4.4-4">Otherwise (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>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.4-5">
          <li pn="section-4.4-5.1">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].</li>
          <li pn="section-4.4-5.2">
            <t indent="0" pn="section-4.4-5.2.1">Otherwise (where n is greater than 0), the following applies
          for derivation of AbsDon[n]:</t>
            <artwork align="left" pn="section-4.4-5.2.2">
If DON[n] == DON[n-1],
   AbsDon[n] = AbsDon[n-1]

If (DON[n] &gt; DON[n-1] and DON[n] - DON[n-1] &lt; 32768),
   AbsDon[n] = AbsDon[n-1] + DON[n] - DON[n-1]

If (DON[n] &lt; DON[n-1] and DON[n-1] - DON[n] &gt;= 32768),
   AbsDon[n] = AbsDon[n-1] + 65536 - DON[n-1] + DON[n]

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

If (DON[n] &lt; DON[n-1] and DON[n-1] - DON[n] &lt; 32768),
   AbsDon[n] = AbsDon[n-1] - (DON[n-1] - DON[n])
</artwork>
          </li>
        </ul>
        <t indent="0" pn="section-4.4-6">For any two NAL units (m and n), the following applies:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.4-7">
          <li pn="section-4.4-7.1">When AbsDon[n] is greater than AbsDon[m], the NAL unit n
          follows NAL unit m in NAL unit decoding order.</li>
          <li pn="section-4.4-7.2">When AbsDon[n] is equal to AbsDon[m], the NAL unit decoding
          order of the two NAL units can be in either order.</li>
          <li pn="section-4.4-7.3">When AbsDon[n] is less than AbsDon[m], the NAL unit n precedes
          NAL unit m in decoding order.</li>
        </ul>
        <aside pn="section-4.4-8">
          <t indent="0" pn="section-4.4-8.1">Informative note: When two consecutive NAL units in
	the NAL unit decoding order has different values of AbsDon, the
	absolute difference between the two AbsDon values may be greater than
	or equal to 1.</t>
        </aside>
        <aside pn="section-4.4-9">
          <t indent="0" pn="section-4.4-9.1">Informative note: There are multiple reasons to allow
        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 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 and gaps in the values of AbsDon may
        occur.</t>
        </aside>
      </section>
    </section>
    <section anchor="PacketizationRules" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-packetization-rules">Packetization Rules</name>
      <t indent="0" pn="section-5-1">The following packetization rules apply:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5-2">
        <li pn="section-5-2.1">If sprop-max-don-diff is greater than 0, the transmission order of
        NAL units carried in the RTP stream <bcp14>MAY</bcp14> be different
        from the NAL unit decoding order. Otherwise (where sprop-max-don-diff
        equals 0), the transmission order of NAL units carried in the RTP
        stream <bcp14>MUST</bcp14> be the same as the NAL unit decoding
        order.</li>
        <li pn="section-5-2.2">A NAL unit of small size <bcp14>SHOULD</bcp14> be encapsulated in
        an 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.</li>
        <li pn="section-5-2.3">Each non-VCL NAL unit <bcp14>SHOULD</bcp14>, when possible from an
        MTU size match viewpoint, be encapsulated in an AP with its associated
        VCL NAL unit as, typically, a non-VCL NAL unit would be meaningless
        without the associated VCL NAL unit being available.</li>
        <li pn="section-5-2.4">A single NAL unit packet <bcp14>MUST</bcp14> be used for carrying
        precisely one NAL unit in an RTP packet.</li>
      </ul>
    </section>
    <section anchor="DepacketizationProcess" numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-de-packetization-process">De-packetization Process</name>
      <t indent="0" pn="section-6-1">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 indent="0" pn="section-6-2">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 indent="0" pn="section-6-3">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 be considered.</t>
      <t indent="0" pn="section-6-4">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, <bcp14>MUST NOT</bcp14> be passed to the decoder.</t>
      <t indent="0" pn="section-6-5">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" buffer. Receivers should also prepare for transmission delay jitter; that is, either reserve separate buffers for transmission delay jitter buffering and de-packetization 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 decoding and playback.</t>
      <t indent="0" pn="section-6-6">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 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" format="default" sectionFormat="of" derivedContent="Section 4.3.2"/>. 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" format="default" sectionFormat="of" derivedContent="Section 4.3.3"/>.</t>
      <t indent="0" pn="section-6-7">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 indent="0" pn="section-6-8">When sprop-max-don-diff is greater than 0, the process described in the remainder of this section applies.</t>
      <t indent="0" pn="section-6-9">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 indent="0" pn="section-6-10">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 indent="0" pn="section-6-11">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 indent="0" pn="section-6-12">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 indent="3" pn="section-6-13">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>
      <t indent="0" pn="section-6-14">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>
    <section anchor="PayloadFormatParameters" numbered="true" removeInRFC="false" toc="include" pn="section-7">
      <name slugifiedName="name-payload-format-parameters">Payload Format Parameters</name>
      <t indent="0" pn="section-7-1">This section specifies the optional parameters. A mapping of the parameters with the Session Description Protocol (SDP) <xref target="RFC8866" format="default" sectionFormat="of" derivedContent="RFC8866"/> is also provided for applications that use SDP.</t>
      <t indent="0" pn="section-7-2">Parameters starting with the string "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, "sprop" parameters are being sent. This uncommon characteristic of the "sprop" parameters may not be intuitive in the context of some signaling protocol concepts, especially with Offer/Answer.  Please see <xref target="sdpoa" format="default" sectionFormat="of" derivedContent="Section 7.3.2"/> for guidance specific to the use of sprop parameters in the Offer/Answer case.</t>
      <section anchor="oparams" numbered="true" removeInRFC="false" toc="include" pn="section-7.1">
        <name slugifiedName="name-media-type-registration">Media Type Registration</name>
        <t indent="0" pn="section-7.1-1">The receiver <bcp14>MUST</bcp14> ignore any parameter unspecified
        in this document.</t>
        <dl spacing="normal" newline="false" indent="3" pn="section-7.1-2">
          <dt pn="section-7.1-2.1">Type name:</dt>
          <dd pn="section-7.1-2.2">video</dd>
          <dt pn="section-7.1-2.3">Subtype name:</dt>
          <dd pn="section-7.1-2.4">evc</dd>
          <dt pn="section-7.1-2.5">Required parameters:</dt>
          <dd pn="section-7.1-2.6">N/A</dd>
          <dt pn="section-7.1-2.7">Optional parameters:</dt>
          <dd pn="section-7.1-2.8">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" format="default" sectionFormat="of" derivedContent="Section 7.2"/> for definitions)</dd>
          <dt pn="section-7.1-2.9">Encoding considerations:</dt>
          <dd pn="section-7.1-2.10">This type is only defined for
          transfer via RTP <xref target="RFC3550" format="default" sectionFormat="of" derivedContent="RFC3550"/>.</dd>
          <dt pn="section-7.1-2.11">Security considerations:</dt>
          <dd pn="section-7.1-2.12">See <xref target="Security" format="default" sectionFormat="of" derivedContent="Section 9"/>
          of RFC 9584.</dd>
          <dt pn="section-7.1-2.13">Interoperability considerations:</dt>
          <dd pn="section-7.1-2.14">N/A</dd>
          <dt pn="section-7.1-2.15">Published specification:</dt>
          <dd pn="section-7.1-2.16">Please refer to RFC 9584 and
          EVC standard <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>.</dd>
          <dt pn="section-7.1-2.17">Applications that use this media type:</dt>
          <dd pn="section-7.1-2.18">Any application
          that relies on EVC-based video services over RTP</dd>
          <dt pn="section-7.1-2.19">Fragment identifier considerations:</dt>
          <dd pn="section-7.1-2.20">N/A</dd>
          <dt pn="section-7.1-2.21">Additional information:</dt>
          <dd pn="section-7.1-2.22">N/A</dd>
          <dt pn="section-7.1-2.23">Person &amp; email address to contact for further
	  information:</dt>
          <dd pn="section-7.1-2.24">
            <br/>Stephan Wenger (stewe@stewe.org)</dd>
          <dt pn="section-7.1-2.25">Intended usage:</dt>
          <dd pn="section-7.1-2.26">COMMON</dd>
          <dt pn="section-7.1-2.27">Restrictions on usage:</dt>
          <dd pn="section-7.1-2.28">N/A</dd>
          <dt pn="section-7.1-2.29">Author:</dt>
          <dd pn="section-7.1-2.30">See Authors' Addresses section of RFC 9584.</dd>
          <dt pn="section-7.1-2.31">Change controller:</dt>
          <dd pn="section-7.1-2.32">IETF &lt;avtcore@ietf.org&gt;</dd>
        </dl>
      </section>
      <section anchor="optionalParameters" numbered="true" removeInRFC="false" toc="include" pn="section-7.2">
        <name slugifiedName="name-optional-parameters-definit">Optional Parameters Definition</name>
        <dl newline="true" indent="3" spacing="normal" pn="section-7.2-1">
          <dt pn="section-7.2-1.1">profile-id, level-id, toolset-id:</dt>
          <dd pn="section-7.2-1.2">
            <t indent="0" pn="section-7.2-1.2.1">These parameters indicate the profile, the level, and
          constraints of the bitstream carried by the RTP stream or a
          specific set of the profile, the level, and constraints the receiver
          supports.</t>
            <t indent="0" pn="section-7.2-1.2.2">More specifications of these parameters, including how they
          relate to syntax elements specified in <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> are
          provided below.</t>
          </dd>
          <dt pn="section-7.2-1.3">profile-id:</dt>
          <dd pn="section-7.2-1.4">
            <t indent="0" pn="section-7.2-1.4.1">When profile-id is not present, a value of 0 (i.e., the
           Baseline profile) <bcp14>MUST</bcp14> be inferred.</t>
            <t indent="0" pn="section-7.2-1.4.2">When used to indicate properties of a bitstream, profile-id
           <bcp14>MUST</bcp14> be derived from the profile_idc in the SPS.</t>
            <t indent="0" pn="section-7.2-1.4.3">EVC bitstreams transported over RTP using the technologies of
           this document <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, 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 profile.  A similar exception can be made for Main
           profile and Main Still picture profile.</t>
          </dd>
          <dt pn="section-7.2-1.5">level-id:</dt>
          <dd pn="section-7.2-1.6">
            <t indent="0" pn="section-7.2-1.6.1">When level-id is not present, a value of 90 (corresponding
           to level 3, which allows for approximately standard-definition
           television (SD TV) resolution and frame rates; see Annex A of <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>) <bcp14>MUST</bcp14> be inferred.</t>
            <t indent="0" pn="section-7.2-1.6.2">When used to indicate properties of a bitstream, level-id
           <bcp14>MUST</bcp14> be derived from the level_idc in the SPS.</t>
            <t indent="0" pn="section-7.2-1.6.3">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 <bcp14>MUST</bcp14> also be supported.</t>
          </dd>
          <dt pn="section-7.2-1.7">toolset-id:</dt>
          <dd pn="section-7.2-1.8">This parameter is a base64-encoding representation (<xref target="RFC4648" section="4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4648#section-4" derivedContent="RFC4648"/>) of a 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
	<bcp14>MUST</bcp14> be derived from toolset_idh_h and toolset_idc_l in
	the sequence parameter set.</dd>
          <dt pn="section-7.2-1.9">max-recv-level-id:</dt>
          <dd pn="section-7.2-1.10">
            <t indent="0" pn="section-7.2-1.10.1">This parameter <bcp14>MAY</bcp14> be used to indicate the
        highest level a receiver supports.</t>
            <t indent="0" pn="section-7.2-1.10.2">The value of max-recv-level-id <bcp14>MUST</bcp14> be in the range
        of 0 to 255, inclusive.</t>
            <t indent="0" pn="section-7.2-1.10.3">When max-recv-level-id is not present, the value is inferred to be
        equal to level-id.</t>
            <t indent="0" pn="section-7.2-1.10.4">max-recv-level-id <bcp14>MUST NOT</bcp14> be present when the
        highest level the receiver supports is not higher than the default
        level.</t>
          </dd>
          <dt pn="section-7.2-1.11">sprop-sps:</dt>
          <dd pn="section-7.2-1.12">
            <t indent="0" pn="section-7.2-1.12.1">This parameter <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 (',') list of base64-encoding representations (<xref target="RFC4648" section="4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4648#section-4" derivedContent="RFC4648"/>) of the sequence
	parameter set NAL units as specified in Section 7.3.2.1 of <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>.</t>
          </dd>
          <dt pn="section-7.2-1.13">sprop-pps:</dt>
          <dd pn="section-7.2-1.14">
            <t indent="0" pn="section-7.2-1.14.1">This parameter <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 (',') list of base64-encoding representations (<xref target="RFC4648" section="4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4648#section-4" derivedContent="RFC4648"/>) of the picture
	parameter set NAL units as specified in Section 7.3.2.2 of <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>.</t>
          </dd>
          <dt pn="section-7.2-1.15">sprop-sei:</dt>
          <dd pn="section-7.2-1.16">
            <t indent="0" pn="section-7.2-1.16.1">This parameter <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" format="default" sectionFormat="of" derivedContent="VSEI"/>.</t>
            <t indent="0" pn="section-7.2-1.16.2">The value of the parameter is a comma-separated (',') list of
	base64-encoding representations (<xref target="RFC4648" section="4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4648#section-4" derivedContent="RFC4648"/>) of SEI NAL units as specified in
	<xref target="VSEI" format="default" sectionFormat="of" derivedContent="VSEI"/>.</t>
            <aside pn="section-7.2-1.16.3">
              <t indent="0" pn="section-7.2-1.16.3.1">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 couple of examples are described below.</t>
              <ol type="1" indent="adaptive" spacing="normal" start="1" pn="section-7.2-1.16.3.2">
                <li pn="section-7.2-1.16.3.2.1" derivedCounter="1.">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; and sending
                it in sprop-sei rather than in the bitstream at each entry
                point may help with saving bits and allow one to configure
                the renderer only once, avoiding unwanted artifacts.</li>
                <li pn="section-7.2-1.16.3.2.2" derivedCounter="2.">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).</li>
              </ol>
            </aside>
          </dd>
          <dt pn="section-7.2-1.17">sprop-max-don-diff:</dt>
          <dd pn="section-7.2-1.18">
            <t indent="0" pn="section-7.2-1.18.1">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 <bcp14>MUST</bcp14> be equal to 0.</t>
            <t indent="0" pn="section-7.2-1.18.2">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>
            <t indent="0" pn="section-7.2-1.18.3">The value of sprop-max-don-diff <bcp14>MUST</bcp14> be an integer in the range of 0 to 32767, inclusive.</t>
            <t indent="0" pn="section-7.2-1.18.4">When not present, the value of sprop-max-don-diff is inferred to be equal to 0.</t>
          </dd>
          <dt pn="section-7.2-1.19">sprop-depack-buf-bytes:</dt>
          <dd pn="section-7.2-1.20">
            <t indent="0" pn="section-7.2-1.20.1">This parameter signals the required size of the de-packetization buffer in units of bytes.  The value of the parameter <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 <xref target="DepacketizationProcess" format="default" sectionFormat="of" derivedContent="Section 6"/>.</t>
            <t indent="0" pn="section-7.2-1.20.2">The value of sprop-depack-buf-bytes <bcp14>MUST</bcp14> be an integer in the range of 0 to 4294967295, inclusive.</t>
            <t indent="0" pn="section-7.2-1.20.3">When sprop-max-don-diff is present and greater than 0, this parameter <bcp14>MUST</bcp14> be present and the value <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>
            <aside pn="section-7.2-1.20.4">
              <t indent="0" pn="section-7.2-1.20.4.1">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>
            </aside>
          </dd>
          <dt pn="section-7.2-1.21">depack-buf-cap:</dt>
          <dd pn="section-7.2-1.22">
            <t indent="0" pn="section-7.2-1.22.1">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>
            <t indent="0" pn="section-7.2-1.22.2">When not present, the value of depack-buf-cap is inferred to be
          equal to 4294967295.  The value of depack-buf-cap
          <bcp14>MUST</bcp14> be an integer in the range of 1 to 4294967295,
          inclusive.</t>
            <aside pn="section-7.2-1.22.3">
              <t indent="0" pn="section-7.2-1.22.3.1">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. When network
          jitter occurs, an appropriately sized jitter buffer has to be
          available as well. </t>
            </aside>
          </dd>
        </dl>
      </section>
      <section anchor="sdp-parameters" numbered="true" removeInRFC="false" toc="include" pn="section-7.3">
        <name slugifiedName="name-sdp-parameters">SDP Parameters</name>
        <t indent="0" pn="section-7.3-1">The receiver <bcp14>MUST</bcp14> ignore any parameter unspecified in this document.</t>
        <section anchor="mapping-of-payload-type-parameters-to-sdp" numbered="true" removeInRFC="false" toc="include" pn="section-7.3.1">
          <name slugifiedName="name-mapping-of-payload-type-par">Mapping of Payload Type Parameters to SDP</name>
          <t indent="0" pn="section-7.3.1-1">The media type video/evc string is mapped to fields in the Session Description Protocol (SDP) <xref target="RFC8866" format="default" sectionFormat="of" derivedContent="RFC8866"/> as follows:</t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3.1-2">
            <li pn="section-7.3.1-2.1">The media name in the "m=" line of SDP <bcp14>MUST</bcp14>
            be video.</li>
            <li pn="section-7.3.1-2.2">The encoding name in the "a=rtpmap" line of SDP
            <bcp14>MUST</bcp14> be evc (the media subtype).</li>
            <li pn="section-7.3.1-2.3">The clock rate in the "a=rtpmap" line <bcp14>MUST</bcp14> be
            90000.</li>
            <li pn="section-7.3.1-2.4">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,
            <bcp14>MUST</bcp14> be included in the "a=fmtp" line of SDP. The
            "a=fmtp" line is expressed as a media type string, in the form of a
            semicolon-separated list of parameter=value pairs.</li>
            <li pn="section-7.3.1-2.5">The <bcp14>OPTIONAL</bcp14> parameters sprop-sps, sprop-pps,
            and sprop-sei, when present, <bcp14>MUST</bcp14> be included in
            the "a=fmtp" line of SDP or conveyed using the "fmtp" source
            attribute as specified in <xref target="RFC5576" sectionFormat="of" section="6.3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5576#section-6.3" derivedContent="RFC5576"/>. For a particular media format
            (i.e., RTP payload type), sprop-sps, sprop-pps, or sprop-sei
            <bcp14>MUST NOT</bcp14> be both included in the "a=fmtp" line of
            SDP and conveyed using the "fmtp" source attribute. When included
            in the "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 "a=fmtp" line of
            SDP for a particular payload type, the parameters sprop-sps,
            sprop-pps, and sprop-sei <bcp14>MUST</bcp14> be applied to each
            SSRC with the payload type. When conveyed using the "fmtp" source
            attribute, these parameters are only associated with the given
            source and payload type as parts of the "fmtp" source
            attribute.</li>
          </ul>
          <aside pn="section-7.3.1-3">
            <t indent="0" pn="section-7.3.1-3.1">Informative note: Conveyance of sprop-sps and sprop-pps
          using the "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" format="default" sectionFormat="of" derivedContent="RFC7667"/>.</t>
          </aside>
          <t indent="0" pn="section-7.3.1-4">A general usage of media representation in SDP is as follows:</t>
          <artwork align="left" pn="section-7.3.1-5">
m=video 49170 RTP/AVP 98
a=rtpmap:98 evc/90000
a=fmtp:98 profile-id=1;
  sprop-sps=&lt;sequence parameter set data&gt;;
  sprop-pps=&lt;picture parameter set data&gt;;
</artwork>
          <t indent="0" pn="section-7.3.1-6">A SIP 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>
          <artwork align="left" pn="section-7.3.1-7">
Offerer-&gt;Answerer:
      m=video 49170 RTP/AVP 98
      a=rtpmap:98 evc/90000
      a=fmtp:98 profile-id=1; level_id=90;
</artwork>
          <t indent="0" pn="section-7.3.1-8">The above represents an offer for symmetric video communication
          using <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/> and its payload specification at the main
          profile and level 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" format="default" sectionFormat="of" derivedContent="EVC"/>. At the same time, if this offer were accepted "as
          is", the offer can expect that the Answerer would be able to receive
          and properly decode EVC media up to and including level 3.</t>
          <artwork align="left" pn="section-7.3.1-9">
Answerer-&gt;Offerer:
      m=video 49170 RTP/AVP 98
      a=rtpmap:98 evc/90000
      a=fmtp:98 profile-id=1; level_id=60
</artwork>
          <aside pn="section-7.3.1-10">
            <t indent="0" pn="section-7.3.1-10.1">Informative note: level_id shall be set equal to a
          value of 30 times the level number specified in Table A.1 of
          <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>.</t>
          </aside>
          <t indent="0" pn="section-7.3.1-11">With this answer to the offer above, the system receiving the
          offer advises the Offerer that it is incapable of handling evc at
          level 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>
        <section anchor="sdpoa" numbered="true" removeInRFC="false" toc="include" pn="section-7.3.2">
          <name slugifiedName="name-usage-with-sdp-offer-answer">Usage with SDP Offer/Answer Model</name>
          <t indent="0" pn="section-7.3.2-1">This section describes the negotiation of unicast messages using the Offer/Answer model described in <xref target="RFC3264" format="default" sectionFormat="of" derivedContent="RFC3264"/> and its updates.</t>
          <t indent="0" pn="section-7.3.2-2">This section applies to all profiles defined in <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>, specifically to Baseline, Main, and the associated still image profiles.</t>
          <t indent="0" pn="section-7.3.2-3">The following limitations and rules pertaining to the media configuration apply:</t>
          <t indent="0" pn="section-7.3.2-4">The parameters identifying a media format configuration for EVC are profile-id and level-id. Profile_id <bcp14>MUST</bcp14> be used symmetrically.</t>
          <t indent="0" pn="section-7.3.2-5">The Answerer <bcp14>MUST</bcp14> structure its answer according to one of the following two options:</t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3.2-6">
            <li pn="section-7.3.2-6.1">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</li>
            <li pn="section-7.3.2-6.2">remove the media format (payload type) completely (when one or
            more of the parameter values are not supported).</li>
          </ul>
          <aside pn="section-7.3.2-7">
            <t indent="0" pn="section-7.3.2-7.1">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" format="default" sectionFormat="of" derivedContent="Section 7.3.2.1"/> ("Payload Format Configuration").</t>
          </aside>
          <t indent="0" pn="section-7.3.2-8">To simplify handling and matching of these configurations, the same RTP payload type number used in the offer <bcp14>SHOULD</bcp14> also be used in the answer, as specified in <xref target="RFC3264" format="default" sectionFormat="of" derivedContent="RFC3264"/>.</t>
          <t indent="0" pn="section-7.3.2-9">The answer <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 anchor="formatconfig" numbered="true" removeInRFC="false" toc="exclude" pn="section-7.3.2.1">
            <name slugifiedName="name-payload-format-configuratio">Payload Format Configuration</name>
            <t indent="0" pn="section-7.3.2.1-1">The following limitations and rules pertain to the configuration of the payload format buffer management.</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3.2.1-2">
              <li pn="section-7.3.2.1-2.1">
                <t indent="0" pn="section-7.3.2.1-2.1.1">The parameters sprop-max-don-diff and sprop-depack-buf-bytes describe the properties of an RTP stream that the Offerer or the Answerer is sending for the media format configuration. This differs from the normal usage of the Offer/Answer parameters; normally, such parameters declare the properties of the bitstream or RTP stream that the Offerer or the Answerer is able to receive. When dealing with EVC, the Offerer assumes that the Answerer will be able to receive media encoded using the configuration being offered.</t>
              </li>
            </ul>
            <aside pn="section-7.3.2.1-3">
              <t indent="0" pn="section-7.3.2.1-3.1">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>
            </aside>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3.2.1-4">
              <li pn="section-7.3.2.1-4.1">
                <t indent="0" pn="section-7.3.2.1-4.1.1">When an Offerer offers an interleaved stream, indicated
              by the presence of sprop-max-don-diff with a value larger than
              zero, the Offerer <bcp14>MUST</bcp14> include the size of the
              de-packetization buffer sprop-depack-buf-bytes.</t>
              </li>
              <li pn="section-7.3.2.1-4.2">
                <t indent="0" pn="section-7.3.2.1-4.2.1">To enable the Offerer and Answerer to inform each other
              about their capabilities for de-packetization buffering in
              receiving RTP streams, both parties are
              <bcp14>RECOMMENDED</bcp14> to include depack-buf-cap.</t>
              </li>
              <li pn="section-7.3.2.1-4.3">
                <t indent="0" pn="section-7.3.2.1-4.3.1">The parameters sprop-sps or sprop-pps, when present
              (included in the "a=fmtp" line of SDP or conveyed using the
              "fmtp" source attribute, as specified in <xref target="RFC5576" sectionFormat="of" section="6.3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5576#section-6.3" derivedContent="RFC5576"/>), are used for out-of-band
              transport of the parameter sets (SPS or PPS, respectively).  The
              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 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: one from the Answerer to the Offerer, and
              the other in the opposite direction. In case some RTP packets
              are sent before the SDP Offer/Answer settles down, in-band
              parameter sets <bcp14>MUST</bcp14> be used for those RTP stream
              parts sent before the SDP Offer/Answer.</t>
              </li>
              <li pn="section-7.3.2.1-4.4">
                <t indent="0" pn="section-7.3.2.1-4.4.1">The following rules apply to transport of parameter sets
              in the Offerer-to-Answerer direction.</t>
                <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3.2.1-4.4.2">
                  <li pn="section-7.3.2.1-4.4.2.1">
                    <t indent="0" pn="section-7.3.2.1-4.4.2.1.1">An offer <bcp14>MAY</bcp14> include 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>
                  </li>
                  <li pn="section-7.3.2.1-4.4.2.2">
                    <t indent="0" pn="section-7.3.2.1-4.4.2.2.1">If the level to use in the Offerer-to-Answerer
		direction is equal to the default level in the offer, the
		Answerer <bcp14>MUST</bcp14> be prepared to use the parameter
		sets included in sprop-sps and sprop-pps (either included in
		the "a=fmtp" line of SDP or conveyed using the "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 <bcp14>MUST</bcp14> ignore
		sprop-vps, sprop-sps, and sprop-pps (either included in the
		"a=fmtp" line of SDP or conveyed using the "fmtp" source
		attribute), and the Offerer <bcp14>MUST</bcp14> transmit
		parameter sets in-band.</t>
                  </li>
                </ul>
              </li>
              <li pn="section-7.3.2.1-4.5">
                <t indent="0" pn="section-7.3.2.1-4.5.1">The following rules apply to transport of parameter sets in
            the Answerer-to-Offerer direction.</t>
                <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3.2.1-4.5.2">
                  <li pn="section-7.3.2.1-4.5.2.1">
                    <t indent="0" pn="section-7.3.2.1-4.5.2.1.1">An answer <bcp14>MAY</bcp14> include 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>
                  </li>
                  <li pn="section-7.3.2.1-4.5.2.2">
                    <t indent="0" pn="section-7.3.2.1-4.5.2.2.1">The Offerer <bcp14>MUST</bcp14> be prepared to use the
              parameter sets included in sprop-sps and sprop-pps (either
              included in the "a=fmtp" line of SDP or conveyed using the
              "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>
                  </li>
                </ul>
              </li>
              <li pn="section-7.3.2.1-4.6">
                <t indent="0" pn="section-7.3.2.1-4.6.1">When sprop-sps and/or sprop-pps are conveyed using the
            "fmtp" source attribute, as specified in <xref target="RFC5576" sectionFormat="of" section="6.3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5576#section-6.3" derivedContent="RFC5576"/>, the receiver of the parameters
            <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 "fmtp" source attribute. Parameter sets associated with one
            source (given as part of the "fmtp" source attribute)
            <bcp14>MUST</bcp14> only be used to decode NAL units conveyed in
            RTP packets from the same source (given as part of the "fmtp"
            source attribute). When this mechanism is in use, SSRC collision
            detection and resolution <bcp14>MUST</bcp14> be performed as
            specified in <xref target="RFC5576" format="default" sectionFormat="of" derivedContent="RFC5576"/>.</t>
              </li>
            </ul>
            <t indent="0" pn="section-7.3.2.1-5"><xref target="params-interpretation" format="default" sectionFormat="of" derivedContent="Figure 11"/> lists the interpretation of all the parameters that <bcp14>MAY</bcp14> be used for the various combinations of offer, answer, and direction attributes.</t>
            <figure anchor="params-interpretation" align="left" suppress-title="false" pn="figure-11">
              <name slugifiedName="name-interpretation-of-parameter">Interpretation of Parameters for Various Combinations of
	      Offers, Answers, and Direction Attributes</name>
              <artwork align="left" pn="section-7.3.2.1-6.1">
                                 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; 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, level down-grading is allowed)

 P: properties of the bitstream to be sent
 R: receiver capabilities
 -: not usable; when present MUST be ignored</artwork>
            </figure>
            <t indent="0" pn="section-7.3.2.1-7">Parameters used for declaring receiver capabilities are, in general, downgradable, i.e., they express the upper limit for a sender's possible behavior. Thus, a sender <bcp14>MAY</bcp14> select to set its encoder using only lower/lesser or equal values of these parameters.</t>
            <t indent="0" pn="section-7.3.2.1-8">When a 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 indent="0" pn="section-7.3.2.1-9">An implementation <bcp14>SHOULD</bcp14> be able to understand all media type parameters (including all optional media type parameters), even if it 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. This leads to higher chances of interoperability beyond the most basic interop points (for which, as described above, no optional parameters are necessary).</t>
            <aside pn="section-7.3.2.1-10">
              <t indent="0" pn="section-7.3.2.1-10.1">Informative note: In implementations of various H.26x video coding payload formats including those for <xref target="AVC" format="default" sectionFormat="of" derivedContent="AVC"/> and <xref target="HEVC" format="default" sectionFormat="of" derivedContent="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 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 process, of the capabilities of the involved systems (walled gardens, baseline requirements defined in application standards higher up in the stack, and similar).</t>
            </aside>
            <t indent="0" pn="section-7.3.2.1-11">An 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 to provide the bitstream property parameters that the media sender will use. This also has the effect that the Offerer has to be able to receive this media format configuration, and not only to send it.</t>
          </section>
        </section>
        <section anchor="multicast" numbered="true" removeInRFC="false" toc="include" pn="section-7.3.3">
          <name slugifiedName="name-multicast">Multicast</name>
          <t indent="0" pn="section-7.3.3-1">For bitstreams being delivered over multicast, the following rules apply:</t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3.3-2">
            <li pn="section-7.3.3-2.1">
              <t indent="0" pn="section-7.3.3-2.1.1">The media format configuration is identified by profile-id
            and level-id. These media format configuration parameters,
            including level-id, <bcp14>MUST</bcp14> be used symmetrically;
            that is, the 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 in multicast is not changeable.</t>
            </li>
            <li pn="section-7.3.3-2.2">
              <t indent="0" pn="section-7.3.3-2.2.1">To simplify the handling and matching of these
            configurations, the same RTP payload type number used in the offer
            <bcp14>SHOULD</bcp14> also be used in the answer, as specified in
            <xref target="RFC3264" format="default" sectionFormat="of" derivedContent="RFC3264"/>. An answer <bcp14>MUST NOT</bcp14>
            contain a payload type number used in the offer unless the
            configuration is the same as in the offer.</t>
            </li>
            <li pn="section-7.3.3-2.3">
              <t indent="0" pn="section-7.3.3-2.3.1">Parameter sets received <bcp14>MUST</bcp14> be associated
            with the originating source and <bcp14>MUST</bcp14> only be used
            in decoding the incoming bitstream from the same source.</t>
            </li>
            <li pn="section-7.3.3-2.4">
              <t indent="0" pn="section-7.3.3-2.4.1">The rules for other parameters are the same as above for
            unicast as long as the three above rules are obeyed.</t>
            </li>
          </ul>
        </section>
        <section anchor="declativeSessiondesc" numbered="true" removeInRFC="false" toc="include" pn="section-7.3.4">
          <name slugifiedName="name-usage-in-declarative-sessio">Usage in Declarative Session Descriptions</name>
          <t indent="0" pn="section-7.3.4-1">When EVC over RTP is offered with SDP in a declarative style, as in the Real-Time Streaming Protocol (RTSP) <xref target="RFC7826" format="default" sectionFormat="of" derivedContent="RFC7826"/> or Session Announcement Protocol (SAP) <xref target="RFC2974" format="default" sectionFormat="of" derivedContent="RFC2974"/>, the following considerations apply.</t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3.4-2">
            <li pn="section-7.3.4-2.1">
              <t indent="0" pn="section-7.3.4-2.1.1">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 <bcp14>MUST</bcp14> be used:</t>
              <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-7.3.4-2.1.2">
                <li pn="section-7.3.4-2.1.2.1">
                  <t indent="0" pn="section-7.3.4-2.1.2.1.1">Declaring actual configuration or bitstream properties:</t>
                  <ul spacing="compact" bare="false" empty="false" indent="3" pn="section-7.3.4-2.1.2.1.2">
                    <li pn="section-7.3.4-2.1.2.1.2.1">
                      <t indent="0" pn="section-7.3.4-2.1.2.1.2.1.1">profile-id</t>
                    </li>
                    <li pn="section-7.3.4-2.1.2.1.2.2">
                      <t indent="0" pn="section-7.3.4-2.1.2.1.2.2.1">level-id</t>
                    </li>
                    <li pn="section-7.3.4-2.1.2.1.2.3">
                      <t indent="0" pn="section-7.3.4-2.1.2.1.2.3.1">sprop-sps</t>
                    </li>
                    <li pn="section-7.3.4-2.1.2.1.2.4">
                      <t indent="0" pn="section-7.3.4-2.1.2.1.2.4.1">sprop-pps</t>
                    </li>
                    <li pn="section-7.3.4-2.1.2.1.2.5">
                      <t indent="0" pn="section-7.3.4-2.1.2.1.2.5.1">sprop-max-don-diff</t>
                    </li>
                    <li pn="section-7.3.4-2.1.2.1.2.6">
                      <t indent="0" pn="section-7.3.4-2.1.2.1.2.6.1">sprop-depack-buf-bytes</t>
                    </li>
                    <li pn="section-7.3.4-2.1.2.1.2.7">
                      <t indent="0" pn="section-7.3.4-2.1.2.1.2.7.1">sprop-sei</t>
                    </li>
                  </ul>
                </li>
                <li pn="section-7.3.4-2.1.2.2">
                  <t indent="0" pn="section-7.3.4-2.1.2.2.1">Not usable (when present, they <bcp14>MUST</bcp14> be ignored):</t>
                  <ul spacing="compact" bare="false" empty="false" indent="3" pn="section-7.3.4-2.1.2.2.2">
                    <li pn="section-7.3.4-2.1.2.2.2.1">
                      <t indent="0" pn="section-7.3.4-2.1.2.2.2.1.1">depack-buf-cap</t>
                    </li>
                    <li pn="section-7.3.4-2.1.2.2.2.2">
                      <t indent="0" pn="section-7.3.4-2.1.2.2.2.2.1">recv-sublayer-id</t>
                    </li>
                  </ul>
                </li>
                <li pn="section-7.3.4-2.1.2.3">
                  <t indent="0" pn="section-7.3.4-2.1.2.3.1">A receiver of the SDP is required to support all parameters and values of the parameters provided; otherwise, the receiver <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>
                </li>
              </ul>
            </li>
          </ul>
        </section>
        <section anchor="consider4pps" numbered="true" removeInRFC="false" toc="include" pn="section-7.3.5">
          <name slugifiedName="name-considerations-for-paramete">Considerations for Parameter Sets</name>
          <t indent="0" pn="section-7.3.5-1">When out-of-band transport of parameter sets is used, parameter sets <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>
      </section>
    </section>
    <section anchor="FeedbackMessage" numbered="true" removeInRFC="false" toc="include" pn="section-8">
      <name slugifiedName="name-use-with-feedback-messages">Use with Feedback Messages</name>
      <t indent="0" pn="section-8-1">The following subsections define the use of the Picture Loss Indication (PLI) <xref target="RFC4585" format="default" sectionFormat="of" derivedContent="RFC4585"/> and Full Intra Request (FIR) <xref target="RFC5104" format="default" sectionFormat="of" derivedContent="RFC5104"/> feedback messages with <xref target="EVC" format="default" sectionFormat="of" derivedContent="EVC"/>.</t>
      <t indent="0" pn="section-8-2">In accordance with this document, a sender <bcp14>MUST NOT</bcp14> send Slice Loss Indication (SLI) or Reference Picture Selection Indication (RPSI); and a receiver <bcp14>MUST</bcp14> ignore RPSI and <bcp14>MUST</bcp14> treat a received SLI as a received PLI, ignoring the "First", "Number", and "PictureID" fields of the PLI.</t>
      <section anchor="PLI" numbered="true" removeInRFC="false" toc="include" pn="section-8.1">
        <name slugifiedName="name-picture-loss-indication-pli">Picture Loss Indication (PLI)</name>
        <t indent="0" pn="section-8.1-1">As specified in <xref target="RFC4585" sectionFormat="of" section="6.3.1" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4585#section-6.3.1" derivedContent="RFC4585"/>, the reception of a PLI by a media sender indicates "the loss of an undefined amount of coded video data belonging to one or more 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 an EVC sender <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 mechanisms of <xref target="RFC4585" format="default" sectionFormat="of" derivedContent="RFC4585"/> <bcp14>MUST</bcp14> be observed.</t>
      </section>
      <section anchor="FIR" numbered="true" removeInRFC="false" toc="include" pn="section-8.2">
        <name slugifiedName="name-full-intra-request-fir">Full Intra Request (FIR)</name>
        <t indent="0" pn="section-8.2-1">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" format="default" sectionFormat="of" derivedContent="RFC8082"/>.</t>
        <t indent="0" pn="section-8.2-2">Upon reception of a FIR, a sender <bcp14>MUST</bcp14> send an IDR picture. Parameter sets <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" numbered="true" removeInRFC="false" toc="include" pn="section-9">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-9-1">The scope of this section is limited to the payload format itself and to one feature of <xref target="EVC" format="default" sectionFormat="of" derivedContent="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 in <xref target="RFC3550" sectionFormat="of" section="14" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3550#section-14" derivedContent="RFC3550"/>) 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 indent="0" pn="section-9-2">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 indent="0" pn="section-9-3">RTP packets using the payload format defined in this specification are subject to the security considerations discussed in the RTP specification <xref target="RFC3550" format="default" sectionFormat="of" derivedContent="RFC3550"/> and in any applicable RTP profile such as RTP/AVP <xref target="RFC3551" format="default" sectionFormat="of" derivedContent="RFC3551"/>, RTP/AVPF <xref target="RFC4585" format="default" sectionFormat="of" derivedContent="RFC4585"/>, RTP/SAVP <xref target="RFC3711" format="default" sectionFormat="of" derivedContent="RFC3711"/>, or RTP/SAVPF <xref target="RFC5124" format="default" sectionFormat="of" derivedContent="RFC5124"/>.  However, as "Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution" <xref target="RFC7202" format="default" sectionFormat="of" derivedContent="RFC7202"/> discusses, it is not an RTP payload format's responsibility to discuss or mandate what solutions are used to meet the basic security goals like confidentiality, integrity, and source authenticity for RTP in general.  This responsibility lies on anyone using RTP in an application.  They can find guidance on available security mechanisms and important considerations in "Options for Securing RTP Sessions" <xref target="RFC7201" format="default" sectionFormat="of" derivedContent="RFC7201"/>. Applications <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 indent="0" pn="section-9-4">Because the data compression used with this payload format is applied 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 indent="0" pn="section-9-5">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 <bcp14>RECOMMENDED</bcp14> based on <xref target="RFC7202" format="default" sectionFormat="of" derivedContent="RFC7202"/>.</t>
      <t indent="0" pn="section-9-6">Like HEVC <xref target="RFC7798" format="default" sectionFormat="of" derivedContent="RFC7798"/> and VVC <xref target="VVC" format="default" sectionFormat="of" derivedContent="VVC"/>, EVC <xref target="EVC" format="default" sectionFormat="of" derivedContent="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 indent="0" pn="section-9-7">EVC <xref target="EVC" format="default" sectionFormat="of" derivedContent="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 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 indent="0" pn="section-9-8">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" numbered="true" removeInRFC="false" toc="include" pn="section-10">
      <name slugifiedName="name-congestion-control">Congestion Control</name>
      <t indent="0" pn="section-10-1">Congestion control for RTP <bcp14>SHALL</bcp14> be used in accordance with RTP <xref target="RFC3550" format="default" sectionFormat="of" derivedContent="RFC3550"/> and with any applicable RTP profile, e.g., AVP <xref target="RFC3551" format="default" sectionFormat="of" derivedContent="RFC3551"/> or AVPF <xref target="RFC4585" format="default" sectionFormat="of" derivedContent="RFC4585"/>. If best-effort service is being used, an additional requirement is that users of this payload format <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. This condition can be satisfied by implementing congestion-control mechanisms to adapt the transmission rate by implementing the number of layers subscribed for a layered multicast session or by arranging for a receiver to leave the session if the loss rate is unacceptably high.</t>
      <t indent="0" pn="section-10-2">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 indent="0" pn="section-10-3">The key mechanism available in <xref target="EVC" format="default" sectionFormat="of" derivedContent="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 indent="0" pn="section-10-4">The mechanisms mentioned above generally work within a defined profile and level; 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 streams. This may be accomplished by using different RTP payload types.</t>
      <t indent="0" pn="section-10-5">MANEs <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's viewpoint) experiences congestion.</t>
    </section>
    <section anchor="iana-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-11">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-11-1">The media type specified in <xref target="oparams" format="default" sectionFormat="of" derivedContent="Section 7.1"/> has been registered with IANA.</t>
    </section>
  </middle>
  <back>
    <references pn="section-12">
      <name slugifiedName="name-references">References</name>
      <references pn="section-12.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="EVC" target="https://www.iso.org/standard/57797.html" quoteTitle="true" derivedAnchor="EVC">
          <front>
            <title>Information technology -- General video coding -- Part 1: Essential video coding</title>
            <author>
              <organization showOnFrontPage="true"/>
            </author>
            <date month="October" year="2020"/>
          </front>
          <seriesInfo name="ISO/IEC" value="23094-1:2020"/>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC3264" target="https://www.rfc-editor.org/info/rfc3264" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC3550" target="https://www.rfc-editor.org/info/rfc3550" quoteTitle="true" derivedAnchor="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 indent="0">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" target="https://www.rfc-editor.org/info/rfc3551" quoteTitle="true" derivedAnchor="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 indent="0">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" target="https://www.rfc-editor.org/info/rfc3711" quoteTitle="true" derivedAnchor="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 indent="0">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" target="https://www.rfc-editor.org/info/rfc4585" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC4648" target="https://www.rfc-editor.org/info/rfc4648" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC5104" target="https://www.rfc-editor.org/info/rfc5104" quoteTitle="true" derivedAnchor="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 indent="0">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 indent="0">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="RFC5124" target="https://www.rfc-editor.org/info/rfc5124" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC5576" target="https://www.rfc-editor.org/info/rfc5576" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC7826" target="https://www.rfc-editor.org/info/rfc7826" quoteTitle="true" derivedAnchor="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 indent="0">This memorandum defines the Real-Time Streaming Protocol (RTSP) version 2.0, which obsoletes RTSP version 1.0 defined in RFC 2326.</t>
              <t indent="0">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>
          </front>
          <seriesInfo name="RFC" value="7826"/>
          <seriesInfo name="DOI" value="10.17487/RFC7826"/>
        </reference>
        <reference anchor="RFC8082" target="https://www.rfc-editor.org/info/rfc8082" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC8866" target="https://www.rfc-editor.org/info/rfc8866" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC9328" target="https://www.rfc-editor.org/info/rfc9328" quoteTitle="true" derivedAnchor="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 indent="0">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="VSEI" target="https://www.itu.int/rec/T-REC-H.274" quoteTitle="true" derivedAnchor="VSEI">
          <front>
            <title>Versatile supplemental enhancement information messages for coded video bitstreams</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date month="March" year="2024"/>
          </front>
          <seriesInfo name="ITU-T Recommendation" value="H.274"/>
        </reference>
      </references>
      <references pn="section-12.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="AVC" target="https://www.iso.org/standard/66069.html" quoteTitle="true" derivedAnchor="AVC">
          <front>
            <title>Part 10: Advanced video coding</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date month="October" year="2014"/>
          </front>
          <seriesInfo name="ITU-T Recommendation" value="H.264"/>
        </reference>
        <reference anchor="HEVC" target="https://www.itu.int/rec/T-REC-H.265" quoteTitle="true" derivedAnchor="HEVC">
          <front>
            <title>High efficiency video coding</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date month="November" year="2019"/>
          </front>
          <seriesInfo name="ITU-T Recommendation" value="H.265"/>
        </reference>
        <reference anchor="MPEG2S" quoteTitle="true" derivedAnchor="MPEG2S">
          <front>
            <title>Information technology - Generic coding of moving pictures and associated audio information - Part 1: Systems</title>
            <author>
              <organization showOnFrontPage="true">IS0/IEC</organization>
            </author>
            <date month="June" year="2013"/>
          </front>
          <seriesInfo name="ISO/IEC" value="13818-1:2013"/>
        </reference>
        <reference anchor="RFC2974" target="https://www.rfc-editor.org/info/rfc2974" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC6184" target="https://www.rfc-editor.org/info/rfc6184" quoteTitle="true" derivedAnchor="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 indent="0">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 indent="0">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"/>
        </reference>
        <reference anchor="RFC6190" target="https://www.rfc-editor.org/info/rfc6190" quoteTitle="true" derivedAnchor="RFC6190">
          <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 indent="0">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 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="RFC7201" target="https://www.rfc-editor.org/info/rfc7201" quoteTitle="true" derivedAnchor="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 indent="0">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" target="https://www.rfc-editor.org/info/rfc7202" quoteTitle="true" derivedAnchor="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 indent="0">This memo discusses the problem of securing real-time multimedia sessions. It also explains why the Real-time Transport Protocol (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a single media security mechanism. This is relevant for designers and reviewers of future RTP extensions to ensure that appropriate security mechanisms are mandated and that any such mechanisms are specified in a manner that conforms with the RTP architecture.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7202"/>
          <seriesInfo name="DOI" value="10.17487/RFC7202"/>
        </reference>
        <reference anchor="RFC7656" target="https://www.rfc-editor.org/info/rfc7656" quoteTitle="true" derivedAnchor="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 indent="0">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" target="https://www.rfc-editor.org/info/rfc7667" quoteTitle="true" derivedAnchor="RFC7667">
          <front>
            <title>RTP Topologies</title>
            <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
            <author fullname="S. Wenger" initials="S." surname="Wenger"/>
            <date month="November" year="2015"/>
            <abstract>
              <t indent="0">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="RFC7798" target="https://www.rfc-editor.org/info/rfc7798" quoteTitle="true" derivedAnchor="RFC7798">
          <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 indent="0">This memo describes an RTP payload format for the 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="VIDEO-CODING" target="https://www.itu.int/rec/T-REC-H.263" quoteTitle="true" derivedAnchor="VIDEO-CODING">
          <front>
            <title>Video coding for low bit rate communication</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date month="January" year="2005"/>
          </front>
          <seriesInfo name="ITU-T Recommendation" value="H.263"/>
        </reference>
        <reference anchor="VVC" target="http://www.itu.int/rec/T-REC-H.266" quoteTitle="true" derivedAnchor="VVC">
          <front>
            <title>Versatile video coding</title>
            <author>
              <organization showOnFrontPage="true">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="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1">Large parts of this specification share text with the RTP payload
      format for VVC <xref target="RFC9328" format="default" sectionFormat="of" derivedContent="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>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author initials="S." surname="Zhao" fullname="Shuai Zhao">
        <organization showOnFrontPage="true">Intel</organization>
        <address>
          <postal>
            <street>2200 Mission College Blvd</street>
            <city>Santa Clara</city>
            <region>California</region>
            <code>95054</code>
            <country>United States of America</country>
          </postal>
          <email>shuai.zhao@ieee.org</email>
        </address>
      </author>
      <author initials="S." surname="Wenger" fullname="Stephan Wenger">
        <organization showOnFrontPage="true">Tencent</organization>
        <address>
          <postal>
            <street>2747 Park Blvd</street>
            <city>Palo Alto</city>
            <region>California</region>
            <code>94588</code>
            <country>United States of America</country>
          </postal>
          <email>stewe@stewe.org</email>
        </address>
      </author>
      <author initials="Y." surname="Lim" fullname="Youngkwon Lim">
        <organization showOnFrontPage="true">Samsung Electronics</organization>
        <address>
          <postal>
            <street>6625 Excellence Way</street>
            <city>Plano</city>
            <region>Texas</region>
            <code>75013</code>
            <country>United States of America</country>
          </postal>
          <email>yklwhite@gmail.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
