<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" docName="draft-zia-route-06" indexInclude="true" ipr="trust200902" number="9223" prepTime="2022-04-27T11:34:12" scripts="Common,Latin" sortRefs="true" submissionType="independent" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en">
  <link href="https://datatracker.ietf.org/doc/draft-zia-route-06" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9223" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="ROUTE">Real-Time Transport Object Delivery over Unidirectional Transport (ROUTE)</title>
    <seriesInfo name="RFC" value="9223" stream="independent"/>
    <author initials="W" surname="Zia" fullname="Waqar Zia">
      <organization showOnFrontPage="true">Qualcomm CDMA Technologies GmbH</organization>
      <address>
        <postal>
          <street>Anzinger Str. 13</street>
          <city>Munich</city>
          <region/>
          <code>81671</code>
          <country>Germany</country>
        </postal>
        <phone/>
        <email>wzia@qti.qualcomm.com</email>
        <uri/>
      </address>
    </author>
    <author initials="T" surname="Stockhammer" fullname="Thomas Stockhammer">
      <organization showOnFrontPage="true">Qualcomm CDMA Technologies GmbH</organization>
      <address>
        <postal>
          <street>Anzinger Str. 13</street>
          <city>Munich</city>
          <region/>
          <code>81671</code>
          <country>Germany</country>
        </postal>
        <phone/>
        <email>tsto@qti.qualcomm.com</email>
        <uri/>
      </address>
    </author>
    <author initials="L" surname="Chaponniere" fullname="Lenaig Chaponniere">
      <organization showOnFrontPage="true">Qualcomm Technologies Inc.</organization>
      <address>
        <postal>
          <street>5775 Morehouse Drive</street>
          <city>San Diego</city>
          <region>CA</region>
          <code>92121</code>
          <country>United States of America</country>
        </postal>
        <phone/>
        <email>lguellec@qti.qualcomm.com</email>
        <uri/>
      </address>
    </author>
    <author initials="G" surname="Mandyam" fullname="Giridhar Mandyam">
      <organization showOnFrontPage="true">Qualcomm Technologies Inc.</organization>
      <address>
        <postal>
          <street>5775 Morehouse Drive</street>
          <city>San Diego</city>
          <region>CA</region>
          <code>92121</code>
          <country>United States of America</country>
        </postal>
        <phone/>
        <email>mandyam@qti.qualcomm.com</email>
        <uri/>
      </address>
    </author>
    <author initials="M" surname="Luby" fullname="Michael Luby">
      <organization showOnFrontPage="true">BitRipple, Inc.</organization>
      <address>
        <postal>
          <street>1133 Miller Ave</street>
          <city>Berkeley</city>
          <region>CA</region>
          <code>94708</code>
          <country>United States of America</country>
        </postal>
        <phone/>
        <email>luby@bitripple.com</email>
        <uri/>
      </address>
    </author>
    <date month="04" year="2022"/>
    <keyword>Multicast</keyword>
    <keyword>Broadcast</keyword>
    <keyword>FEC</keyword>
    <keyword>DASH</keyword>
    <keyword>HLS</keyword>
    <keyword>FLUTE</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">
   The Real-time Transport Object delivery over Unidirectional Transport
   (ROUTE) protocol is specified for robust delivery of Application Objects,
   including Application Objects with real-time delivery constraints, to
   receivers over a unidirectional transport.  Application Objects consist of
   data that has meaning to applications that use the ROUTE protocol for
   delivery of data to receivers; for example, it can be a file, a Dynamic
   Adaptive Streaming over HTTP (DASH) or HTTP Live Streaming (HLS) segment, a
   WAV audio clip, etc. The ROUTE protocol also supports low-latency streaming
   applications.</t>
      <t indent="0" pn="section-abstract-2">
   The ROUTE protocol is suitable for unicast, broadcast, and multicast
   transport. Therefore, it can be run over UDP/IP, including multicast
   IP. The ROUTE protocol can leverage the features of the underlying
   protocol layer, e.g., to provide security, it can leverage IP security
   protocols such as IPsec.</t>
      <t indent="0" pn="section-abstract-3">
   This document specifies the ROUTE protocol such that it could be used
   by a variety of services for delivery of Application Objects by
   specifying their own profiles of this protocol (e.g., by adding or
   constraining some features).</t>
      <t indent="0" pn="section-abstract-4">
   This is not an IETF specification and does not have IETF consensus.</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 document is not an Internet Standards Track specification; it is
            published for informational purposes.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This is a contribution to the RFC Series, independently of any
            other RFC stream.  The RFC Editor has chosen to publish this
            document at its discretion and makes no statement about its value
            for implementation or deployment.  Documents approved for
            publication by the RFC Editor are not candidates for any level of
            Internet Standard; see 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/rfc9223" 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) 2022 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.
        </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" keepWithNext="true" 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">Overview</xref></t>
              </li>
              <li pn="section-toc.1-1.1.2.2">
                <t indent="0" keepWithNext="true" 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-protocol-stack-for-route">Protocol Stack for ROUTE</xref></t>
              </li>
              <li pn="section-toc.1-1.1.2.3">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.3.1"><xref derivedContent="1.3" format="counter" sectionFormat="of" target="section-1.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-data-model">Data Model</xref></t>
              </li>
              <li pn="section-toc.1-1.1.2.4">
                <t indent="0" pn="section-toc.1-1.1.2.4.1"><xref derivedContent="1.4" format="counter" sectionFormat="of" target="section-1.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-architecture-and-scope-of-s">Architecture and Scope of Specification</xref></t>
              </li>
              <li pn="section-toc.1-1.1.2.5">
                <t indent="0" pn="section-toc.1-1.1.2.5.1"><xref derivedContent="1.5" format="counter" sectionFormat="of" target="section-1.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions-used-in-this-do">Conventions Used in This Document</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-route-packet-format">ROUTE Packet Format</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2">
              <li pn="section-toc.1-1.2.2.1">
                <t indent="0" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-packet-structure-and-header">Packet Structure and Header Fields</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.2">
                <t indent="0" pn="section-toc.1-1.2.2.2.1"><xref derivedContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-lct-header-extensions">LCT Header Extensions</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.3">
                <t indent="0" pn="section-toc.1-1.2.2.3.1"><xref derivedContent="2.3" format="counter" sectionFormat="of" target="section-2.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-fec-payload-id-for-source-f">FEC Payload ID for Source Flows</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.4">
                <t indent="0" pn="section-toc.1-1.2.2.4.1"><xref derivedContent="2.4" format="counter" sectionFormat="of" target="section-2.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-fec-payload-id-for-repair-f">FEC Payload ID for Repair Flows</xref></t>
              </li>
            </ul>
          </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-session-metadata">Session Metadata</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-generic-metadata">Generic Metadata</xref></t>
              </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-session-metadata-for-source">Session Metadata for Source Flows</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.3">
                <t indent="0" pn="section-toc.1-1.3.2.3.1"><xref derivedContent="3.3" format="counter" sectionFormat="of" target="section-3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-session-metadata-for-repair">Session Metadata for Repair Flows</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-delivery-object-mode">Delivery Object Mode</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-file-mode">File Mode</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2.1.2">
                  <li pn="section-toc.1-1.4.2.1.2.1">
                    <t indent="0" pn="section-toc.1-1.4.2.1.2.1.1"><xref derivedContent="4.1.1" format="counter" sectionFormat="of" target="section-4.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-extensions-to-fdt">Extensions to FDT</xref></t>
                  </li>
                  <li pn="section-toc.1-1.4.2.1.2.2">
                    <t indent="0" pn="section-toc.1-1.4.2.1.2.2.1"><xref derivedContent="4.1.2" format="counter" sectionFormat="of" target="section-4.1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-constraints-on-extended-fdt">Constraints on Extended FDT</xref></t>
                  </li>
                </ul>
              </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-entity-mode">Entity Mode</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-unsigned-package-mode">Unsigned Package Mode</xref></t>
              </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-signed-package-mode">Signed Package Mode</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-sender-operation">Sender Operation</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
              <li pn="section-toc.1-1.5.2.1">
                <t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-usage-of-alc-and-lct-for-so">Usage of ALC and LCT for Source Flow</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.2">
                <t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-route-packetization-for-sou">ROUTE Packetization for Source Flow</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2.2.2">
                  <li pn="section-toc.1-1.5.2.2.2.1">
                    <t indent="0" pn="section-toc.1-1.5.2.2.2.1.1"><xref derivedContent="5.2.1" format="counter" sectionFormat="of" target="section-5.2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-basic-route-packetization">Basic ROUTE Packetization</xref></t>
                  </li>
                  <li pn="section-toc.1-1.5.2.2.2.2">
                    <t indent="0" pn="section-toc.1-1.5.2.2.2.2.1"><xref derivedContent="5.2.2" format="counter" sectionFormat="of" target="section-5.2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-route-packetization-for-cma">ROUTE Packetization for CMAF Chunked Content</xref></t>
                  </li>
                </ul>
              </li>
              <li pn="section-toc.1-1.5.2.3">
                <t indent="0" pn="section-toc.1-1.5.2.3.1"><xref derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-timing-of-packet-emission">Timing of Packet Emission</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.4">
                <t indent="0" pn="section-toc.1-1.5.2.4.1"><xref derivedContent="5.4" format="counter" sectionFormat="of" target="section-5.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-extended-fdt-encoding-for-f">Extended FDT Encoding for File Mode Sending</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.5">
                <t indent="0" pn="section-toc.1-1.5.2.5.1"><xref derivedContent="5.5" format="counter" sectionFormat="of" target="section-5.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-fec-framework-consideration">FEC Framework Considerations</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.6">
                <t indent="0" pn="section-toc.1-1.5.2.6.1"><xref derivedContent="5.6" format="counter" sectionFormat="of" target="section-5.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-fec-transport-object-constr">FEC Transport Object Construction</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.7">
                <t indent="0" pn="section-toc.1-1.5.2.7.1"><xref derivedContent="5.7" format="counter" sectionFormat="of" target="section-5.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-super-object-construction">Super-Object Construction</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.8">
                <t indent="0" pn="section-toc.1-1.5.2.8.1"><xref derivedContent="5.8" format="counter" sectionFormat="of" target="section-5.8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-repair-packet-consideration">Repair Packet Considerations</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.9">
                <t indent="0" pn="section-toc.1-1.5.2.9.1"><xref derivedContent="5.9" format="counter" sectionFormat="of" target="section-5.9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-summary-fec-information">Summary FEC Information</xref></t>
              </li>
            </ul>
          </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-receiver-operation">Receiver Operation</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2">
              <li pn="section-toc.1-1.6.2.1">
                <t indent="0" pn="section-toc.1-1.6.2.1.1"><xref derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-basic-application-object-re">Basic Application Object Recovery for Source Flows</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.2">
                <t indent="0" pn="section-toc.1-1.6.2.2.1"><xref derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-fast-stream-acquisition">Fast Stream Acquisition</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.3">
                <t indent="0" pn="section-toc.1-1.6.2.3.1"><xref derivedContent="6.3" format="counter" sectionFormat="of" target="section-6.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-generating-extended-fdt-ins">Generating Extended FDT-Instance for File Mode</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2.3.2">
                  <li pn="section-toc.1-1.6.2.3.2.1">
                    <t indent="0" pn="section-toc.1-1.6.2.3.2.1.1"><xref derivedContent="6.3.1" format="counter" sectionFormat="of" target="section-6.3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-file-template-substitution-">File Template Substitution for Content-Location Derivation</xref></t>
                  </li>
                  <li pn="section-toc.1-1.6.2.3.2.2">
                    <t indent="0" pn="section-toc.1-1.6.2.3.2.2.1"><xref derivedContent="6.3.2" format="counter" sectionFormat="of" target="section-6.3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-filetransfer-length-derivat">File@Transfer-Length Derivation</xref></t>
                  </li>
                  <li pn="section-toc.1-1.6.2.3.2.3">
                    <t indent="0" pn="section-toc.1-1.6.2.3.2.3.1"><xref derivedContent="6.3.3" format="counter" sectionFormat="of" target="section-6.3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-fdt-instanceexpires-derivat">FDT-Instance@Expires Derivation</xref></t>
                  </li>
                </ul>
              </li>
            </ul>
          </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-fec-application">FEC Application</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-general-fec-application-gui">General FEC Application Guidelines</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-toi-mapping">TOI Mapping</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-delivery-object-reception-t">Delivery Object Reception Timeout</xref></t>
              </li>
              <li pn="section-toc.1-1.7.2.4">
                <t indent="0" pn="section-toc.1-1.7.2.4.1"><xref derivedContent="7.4" format="counter" sectionFormat="of" target="section-7.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-example-fec-operation">Example FEC Operation</xref></t>
              </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-considerations-for-defining">Considerations for Defining ROUTE Profiles</xref></t>
          </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-route-concepts">ROUTE Concepts</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.9.2">
              <li pn="section-toc.1-1.9.2.1">
                <t indent="0" pn="section-toc.1-1.9.2.1.1"><xref derivedContent="9.1" format="counter" sectionFormat="of" target="section-9.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-route-modes-of-delivery">ROUTE Modes of Delivery</xref></t>
              </li>
              <li pn="section-toc.1-1.9.2.2">
                <t indent="0" pn="section-toc.1-1.9.2.2.1"><xref derivedContent="9.2" format="counter" sectionFormat="of" target="section-9.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-file-mode-optimizations">File Mode Optimizations</xref></t>
              </li>
              <li pn="section-toc.1-1.9.2.3">
                <t indent="0" pn="section-toc.1-1.9.2.3.1"><xref derivedContent="9.3" format="counter" sectionFormat="of" target="section-9.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-in-band-signaling-of-object">In-Band Signaling of Object Transfer Length</xref></t>
              </li>
              <li pn="section-toc.1-1.9.2.4">
                <t indent="0" pn="section-toc.1-1.9.2.4.1"><xref derivedContent="9.4" format="counter" sectionFormat="of" target="section-9.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-repair-protocol-concepts">Repair Protocol Concepts</xref></t>
              </li>
            </ul>
          </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-interoperability-chart">Interoperability Chart</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-security-and-privacy-consid">Security and Privacy Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.11.2">
              <li pn="section-toc.1-1.11.2.1">
                <t indent="0" pn="section-toc.1-1.11.2.1.1"><xref derivedContent="11.1" format="counter" sectionFormat="of" target="section-11.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
              </li>
              <li pn="section-toc.1-1.11.2.2">
                <t indent="0" pn="section-toc.1-1.11.2.2.1"><xref derivedContent="11.2" format="counter" sectionFormat="of" target="section-11.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-privacy-considerations">Privacy Considerations</xref></t>
              </li>
            </ul>
          </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-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.13">
            <t indent="0" pn="section-toc.1-1.13.1"><xref derivedContent="13" format="counter" sectionFormat="of" target="section-13"/>. <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.13.2">
              <li pn="section-toc.1-1.13.2.1">
                <t indent="0" pn="section-toc.1-1.13.2.1.1"><xref derivedContent="13.1" format="counter" sectionFormat="of" target="section-13.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.13.2.2">
                <t indent="0" pn="section-toc.1-1.13.2.2.1"><xref derivedContent="13.2" format="counter" sectionFormat="of" target="section-13.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </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.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.15">
            <t indent="0" pn="section-toc.1-1.15.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="sect-1" numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <section anchor="sect-1.1" numbered="true" toc="include" removeInRFC="false" pn="section-1.1">
        <name slugifiedName="name-overview">Overview</name>
        <t indent="0" pn="section-1.1-1">
   The Real-time Transport Object delivery over Unidirectional Transport
   (ROUTE) protocol can be used for robust delivery of
   Application Objects, including Application Objects with real-time
   delivery constraints, to receivers over a unidirectional transport.
   Unidirectional transport in this document has identical meaning to that in
   RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>, i.e., transport in the direction of receiver(s)
   from a sender. The robustness is enabled by a built-in mechanism, e.g.,
   signaling for loss detection, enabling loss recovery, and optionally
   integrating application-layer Forward Error Correction (FEC).</t>
        <t indent="0" pn="section-1.1-2">
   Application Objects consist of data that has meaning to applications
   that use the ROUTE protocol for delivery of data to receivers, e.g.,
   an Application Object can be a file, an MPEG Dynamic Adaptive
   Streaming over HTTP (DASH) <xref target="DASH" format="default" sectionFormat="of" derivedContent="DASH"/> video segment, a WAV audio clip, an
   MPEG Common Media Application Format (CMAF) <xref target="CMAF" format="default" sectionFormat="of" derivedContent="CMAF"/> addressable
   resource, an MPEG-4 video clip, etc.</t>
        <t indent="0" pn="section-1.1-3">
   The ROUTE protocol is designed to enable delivery of sequences of
   related Application Objects in a timely manner to receivers, e.g., a
   sequence of DASH video segments associated to a Representation or a
   sequence of CMAF addressable resources associated to a CMAF Track.
   The applications of this protocol target services enabled on media
   consumption devices such as smartphones, tablets, television sets, and
   so on. Most of these applications are real-time in the sense that
   they are sensitive to and rely upon such timely reception of data.
   The ROUTE protocol also supports chunked delivery of real-time
   Application Objects to enable low-latency streaming applications
   (similar in its properties to chunked delivery using HTTP). The
   protocol also enables low-latency delivery of DASH and Apple HTTP
   Live Streaming (HLS) content with CMAF Chunks.</t>
        <t indent="0" pn="section-1.1-4">
   Content not intended for rendering in real time as it is received
   (e.g., a downloaded application), a file comprising continuous or
   discrete media and belonging to an app-based feature, or a file
   containing (opaque) data to be consumed by a Digital Rights
   Management (DRM) system client can also be delivered by ROUTE.</t>
        <t indent="0" pn="section-1.1-5">
   The ROUTE protocol supports a caching model where Application
   Objects are recovered into a cache at the receiver and may be made
   available to applications via standard HTTP requests from the cache.
   Many current day applications rely on using HTTP to access content;
   hence, this approach enables such applications in
   broadcast/multicast environments.</t>
        <t indent="0" pn="section-1.1-6">
   ROUTE is aligned with File Delivery over Unidirectional Transport (FLUTE)
   as defined in RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/> as well as
   the extensions defined in Multimedia Broadcast/Multicast Service (MBMS)
   <xref target="MBMS" format="default" sectionFormat="of" derivedContent="MBMS"/>, but it also makes use of some principles of
   FCAST (Object Delivery for the Asynchronous Layered Coding (ALC) and
   NACK-Oriented Reliable Multicast (NORM) Protocols) as defined in RFC 6968 <xref target="RFC6968" format="default" sectionFormat="of" derivedContent="RFC6968"/>; for example, object metadata and the
   object content may be sent together in a compound object.</t>
        <t indent="0" pn="section-1.1-7">
   The alignment to FLUTE is enabled since in addition to reusing
   several of the basic FLUTE protocol features, as referred to by this
   document, certain optimizations and restrictions are added that
   enable optimized support for real-time delivery of media data; hence,
   the name of the protocol. Among others, the source ROUTE protocol
   enables or enhances the following functionalities:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1.1-8">
          <li pn="section-1.1-8.1">Real-time delivery of object-based media data</li>
          <li pn="section-1.1-8.2">Flexible packetization, including enabling media-aware
      packetization as well as transport-aware packetization of delivery
      objects</li>
          <li pn="section-1.1-8.3">Independence of Application Objects and delivery objects, i.e., a
      delivery object may be a part of a file or may be a group of
      files.</li>
        </ul>
        <t indent="0" pn="section-1.1-9">
   Advanced Television Systems Committee (ATSC) 3.0 specifies the ROUTE
   protocol integrated with an ATSC 3.0 services layer. That
   specification will be referred to as ATSC-ROUTE <xref target="ATSCA331" format="default" sectionFormat="of" derivedContent="ATSCA331"/> for the
   remainder of this document. Digital Video Broadcasting  (DVB) has specified a profile of ATSC-ROUTE
   in DVB Adaptive Media Streaming over IP Multicast (DVB-MABR)
   <xref target="DVBMABR" format="default" sectionFormat="of" derivedContent="DVBMABR"/>. This document specifies the Application Object delivery
   aspects (delivery protocol) for such services, as the corresponding
   delivery protocol could be used as a reference by a variety of
   services by specifying profiles of ROUTE in their respective fora,
   e.g., by adding new optional features atop or by restricting various
   optional features specified in this document in a specific service
   standard. Hence, in the context of this document, the aforementioned
   ATSC-ROUTE and DVB-MABR are the services using ROUTE. The definition
   of profiles by the services also have to give due consideration to
   compatibility issues, and some related guidelines are also provided
   in this document.</t>
        <t indent="0" pn="section-1.1-10">
   This document is not an IETF specification and does not have IETF
   consensus. It is provided here to aid the production of interoperable
   implementations.</t>
      </section>
      <section anchor="sect-1.2" numbered="true" toc="include" removeInRFC="false" pn="section-1.2">
        <name slugifiedName="name-protocol-stack-for-route">Protocol Stack for ROUTE</name>
        <t indent="0" pn="section-1.2-1">
   ROUTE delivers Application Objects such as MPEG DASH or HLS segments
   and optionally the associated repair data, operating over UDP/IP
   networks, as depicted in <xref target="protocol-layering" format="default" sectionFormat="of" derivedContent="Table 1"/>. The session metadata signaling to
   realize a ROUTE session as specified in this document <bcp14>MAY</bcp14> be delivered
   out of band or in band as well. Since ROUTE delivers objects in an
   application cache at the receiver from where the application can
   access them using HTTP, an application like DASH may use its
   standardized unicast streaming mechanisms in conjunction with ROUTE
   over broadcast/multicast to augment the services. </t>
        <table anchor="protocol-layering" align="center" pn="table-1">
          <name slugifiedName="name-protocol-layering">Protocol Layering</name>
          <tbody>
            <tr>
              <td align="center" colspan="1" rowspan="1">Application (DASH and HLS segments, CMAF Chunks, etc.)            
                </td>
            </tr>
            <tr>
              <td align="center" colspan="1" rowspan="1">ROUTE                                                            
                </td>
            </tr>
            <tr>
              <td align="center" colspan="1" rowspan="1">UDP                                                              
                </td>
            </tr>
            <tr>
              <td align="center" colspan="1" rowspan="1">IP                                                               
                </td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="sect-1.3" numbered="true" toc="include" removeInRFC="false" pn="section-1.3">
        <name slugifiedName="name-data-model">Data Model</name>
        <t indent="0" pn="section-1.3-1">
   The ROUTE data model is constituted by the following key concepts.

        </t>
        <dl newline="false" spacing="normal" indent="6" pn="section-1.3-2">
          <dt pn="section-1.3-2.1">Application Object:</dt>
          <dd pn="section-1.3-2.2"> data that has meaning to the application that
   uses the ROUTE protocol for delivery of data to receivers, e.g., an
   Application Object can be a file, a DASH video segment, a WAV
   audio clip, an MPEG-4 video clip, etc.</dd>
          <dt pn="section-1.3-2.3">Delivery Object:</dt>
          <dd pn="section-1.3-2.4"> an object on course of delivery to the application
   from the ROUTE sender to ROUTE receiver.</dd>
          <dt pn="section-1.3-2.5">Transport Object:</dt>
          <dd pn="section-1.3-2.6"> an object identified by the Transport Object Identifier (TOI)
          in RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>. It
          <bcp14>MAY</bcp14> be either a source or a repair object, depending on if it is
          carried by a Source Flow or a Repair Flow, respectively.</dd>
          <dt pn="section-1.3-2.7">Transport Session:</dt>
          <dd pn="section-1.3-2.8">a Layered Coding Transport (LCT) channel, as
   defined by RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>. A Transport Session <bcp14>SHALL</bcp14> be uniquely
   identified by a unique Transport Session Identifier (TSI) value in
   the LCT header. The TSI is scoped by the IP address of the sender,
   and the IP address of the sender together with the TSI uniquely
   identify the session. Transport Sessions are a subset of a ROUTE
   session. For media delivery, a Transport Session would typically
   carry a media component, for example, a DASH Representation. Within
   each Transport Session, one or more objects are carried, typically
   objects that are related, e.g., DASH segments associated to one
	  Representation.</dd>
          <dt pn="section-1.3-2.9">ROUTE Session:</dt>
          <dd pn="section-1.3-2.10">an ensemble or multiplex of one or more
   Transport Sessions. Each ROUTE session is associated with an IP
   address/port combination. A ROUTE session typically carries one or more media
   components of streaming media e.g., Representations associated with a DASH
   Media Presentation.</dd>
          <dt pn="section-1.3-2.11">Source Flow:</dt>
          <dd pn="section-1.3-2.12">a Transport Session carrying source data. Source Flow is
   independent of the Repair Flow, i.e., the Source Flow <bcp14>MAY</bcp14> be used by
   a ROUTE receiver without the ROUTE Repair Flows.</dd>
          <dt pn="section-1.3-2.13">Repair Flow:</dt>
          <dd pn="section-1.3-2.14">a Transport Session carrying repair data for one
   or more Source Flows.</dd>
        </dl>
      </section>
      <section anchor="sect-1.4" numbered="true" toc="include" removeInRFC="false" pn="section-1.4">
        <name slugifiedName="name-architecture-and-scope-of-s">Architecture and Scope of Specification</name>
        <t indent="0" pn="section-1.4-1">
   The scope of the ROUTE protocol is to enable robust and real-time transport of
   delivery objects using LCT packets. This architecture is depicted in
   <xref target="architecture-diagram" format="default" sectionFormat="of" derivedContent="Figure 1"/>.</t>
        <t indent="0" pn="section-1.4-2">
   The normative aspects of the ROUTE protocol focus on the following
   aspects:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1.4-3">
          <li pn="section-1.4-3.1">The format of the LCT packets that carry the transport objects.</li>
          <li pn="section-1.4-3.2">The robust transport of the delivery object using a repair
      protocol based on Forward Error Correction (FEC).</li>
          <li pn="section-1.4-3.3">The definition and possible carriage of object metadata along with
      the delivery objects. Metadata may be conveyed in LCT packets
      and/or separate objects.</li>
          <li pn="section-1.4-3.4">The ROUTE session, LCT channel, and delivery object description
      provided as service metadata signaling to enable the reception of
      objects.</li>
          <li pn="section-1.4-3.5">The normative aspects (formats, semantics) of the delivery
          objects conveyed as a content manifest to be delivered along with
          the objects to optimize the performance for specific applications
          e.g., real-time delivery. The objects and manifest are made
          available to the application through an Application Object cache.
          The interface of this cache to the application is not specified in
          this document; however, it will typically be enabled by the
          application acting as an HTTP client and the cache as the HTTP
          server.</li>
        </ul>
        <figure anchor="architecture-diagram" align="left" suppress-title="false" pn="figure-1">
          <name slugifiedName="name-architecture-functional-blo">Architecture/Functional Block Diagram</name>
          <artwork name="" type="" align="left" alt="" pn="section-1.4-4.1">
                                             Application Objects
Application                                  to application
Objects from                                          ^
an application    +--------------------------------------------+
     +            |  ROUTE Receiver                   |        |
     |            |                            +------+------+ |
     |            |                            | Application | |
     |            |                            | Object Cache| |
     |            |                            +------+------+ |
     |    LCT over|    +---------------+              ^        |
     v    UDP/IP  |    | Source object |  +---------+ |        |
+----+---+        | +-&gt;+ recovery      +--+  Repair +-+        |
| ROUTE  |        | |  +---------------+  +----+----+          |
| Sender +----------+                          ^               |
+----+---+        | |                          |               |
     |            | |  +---------------+       |               |
     |            | |  | Repair object |       |               |
     |            | +-&gt;+ recovery      +-------+               |
     +-----------&gt;+    +---------------+                       |
       ROUTE      |                                            |
       Metadata   +--------------------------------------------+
</artwork>
        </figure>
      </section>
      <section anchor="sect-1.6" numbered="true" toc="include" removeInRFC="false" pn="section-1.5">
        <name slugifiedName="name-conventions-used-in-this-do">Conventions Used in This Document</name>
        <t indent="0" pn="section-1.5-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>
    <section anchor="sect-2" numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-route-packet-format">ROUTE Packet Format</name>
      <section anchor="sect-2.1" numbered="true" toc="include" removeInRFC="false" pn="section-2.1">
        <name slugifiedName="name-packet-structure-and-header">Packet Structure and Header Fields</name>
        <t indent="0" pn="section-2.1-1">
   The packet format used by ROUTE Source Flows and Repair Flows follows
   the ALC packet format specified in RFC 5775 <xref target="RFC5775" format="default" sectionFormat="of" derivedContent="RFC5775"/> with the UDP
   header followed by the default LCT header and the source FEC Payload
   ID followed by the packet payload. The overall ROUTE packet format is
   as depicted in <xref target="route-packet-format" format="default" sectionFormat="of" derivedContent="Figure 2"/>.</t>
        <figure anchor="route-packet-format" align="left" suppress-title="false" pn="figure-2">
          <name slugifiedName="name-overall-route-packet-format">Overall ROUTE Packet Format</name>
          <artwork name="" type="" align="left" alt="" pn="section-2.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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           UDP Header                          |
|                                                               |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
|                       Default LCT header                      |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         FEC Payload ID                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                          Payload Data                         |
|                               ...                             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
        </figure>
        <t indent="0" pn="section-2.1-3">
   The Default LCT header is as defined in the LCT building block in RFC
   5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>.</t>
        <t indent="0" pn="section-2.1-4">
   The LCT packet header fields <bcp14>SHALL</bcp14> be used as defined by the LCT
   building block in RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>. The semantics and usage of the
   following LCT header fields <bcp14>SHALL</bcp14> be further constrained in ROUTE as
   follows:

        </t>
        <dl newline="false" spacing="normal" indent="3" pn="section-2.1-5">
          <dt pn="section-2.1-5.1">Version number (V):</dt>
          <dd pn="section-2.1-5.2"> This 4-bit field indicates the protocol
   version number. The version number <bcp14>SHALL</bcp14> be set to '0001', as specified in
   RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>.</dd>
          <dt pn="section-2.1-5.3">Congestion Control flag (C) field:</dt>
          <dd pn="section-2.1-5.4"> This 2-bit field, as
   defined in RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>, <bcp14>SHALL</bcp14> be set to '00'.</dd>
          <dt pn="section-2.1-5.5">Protocol-Specific Indication (PSI):</dt>
          <dd pn="section-2.1-5.6"> The most significant bit of this 2-bit flag is called the
          Source Packet Indicator (SPI) and indicates whether the current
          packet is a source packet or a FEC repair packet. The SPI
          <bcp14>SHALL</bcp14> be set to '1' to indicate a source packet and
          <bcp14>SHALL</bcp14> bet set to '0' to indicate a repair
          packet.</dd>
          <dt pn="section-2.1-5.7">Transport Session Identifier flag (S):</dt>
          <dd pn="section-2.1-5.8"> This 1-bit field
   <bcp14>SHALL</bcp14> be set to '1' to indicate a 32-bit word in the TSI field.</dd>
          <dt pn="section-2.1-5.9">Transport Object Identifier flag (O):</dt>
          <dd pn="section-2.1-5.10"> This 2-bit field <bcp14>SHALL</bcp14>
   be set to '01' to indicate the number of full 32-bit words in the TOI
   field.</dd>
          <dt pn="section-2.1-5.11">Half-word flag (H):</dt>
          <dd pn="section-2.1-5.12"> This 1-bit field <bcp14>SHALL</bcp14> be set to '0' to
   indicate that no half-word field sizes are used.</dd>
          <dt pn="section-2.1-5.13">Codepoint (CP):</dt>
          <dd pn="section-2.1-5.14"> This 8-bit field is used to indicate the type of the payload
          that is carried by this packet; for ROUTE, it is defined as shown
          below to indicate the type of delivery object carried in the payload
          of the associated ROUTE packet. The remaining unmapped Codepoint
          values can be used by a service using ROUTE. In this case, the
          Codepoint values <bcp14>SHALL</bcp14> follow the semantics specified
          in the following table. "IS" stands for Initialization Segment of
          the media content such as the DASH Initialization Segment
           <xref target="DASH" format="default" sectionFormat="of" derivedContent="DASH"/>. The various modes of operation in the table
          (File/Entity/Package Mode) are specified in <xref target="sect-4" format="default" sectionFormat="of" derivedContent="Section 4"/>. The table also lists a Codepoint value range
          that is reserved for future service-specific uses.</dd>
        </dl>
        <table anchor="codepoint-values" align="center" pn="table-2">
          <name slugifiedName="name-codepoint-values">Codepoint Values</name>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Codepoint value
	      </th>
              <th align="left" colspan="1" rowspan="1">Semantics
	      </th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">0
	    </td>
              <td align="left" colspan="1" rowspan="1">Reserved (not used)
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">1
	    </td>
              <td align="left" colspan="1" rowspan="1">Non Real Time (NRT) - File Mode
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">2
	    </td>
              <td align="left" colspan="1" rowspan="1">NRT - Entity Mode
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">3
	    </td>
              <td align="left" colspan="1" rowspan="1">NRT - Unsigned Package Mode
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">4
	    </td>
              <td align="left" colspan="1" rowspan="1">NRT - Signed Package Mode
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">5
	    </td>
              <td align="left" colspan="1" rowspan="1">New IS, timeline changed
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">6
	    </td>
              <td align="left" colspan="1" rowspan="1">New IS, timeline continued
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">7
	    </td>
              <td align="left" colspan="1" rowspan="1">Redundant IS
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">8
	    </td>
              <td align="left" colspan="1" rowspan="1">Media Segment, File Mode
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">9
	    </td>
              <td align="left" colspan="1" rowspan="1">Media Segment, Entity Mode
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">10
	    </td>
              <td align="left" colspan="1" rowspan="1">Media Segment, File Mode with CMAF Random Access chunk
</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">11 - 255
	    </td>
              <td align="left" colspan="1" rowspan="1">Reserved, service-specific
</td>
            </tr>
          </tbody>
        </table>
        <dl newline="false" spacing="normal" indent="3" pn="section-2.1-7">
          <dt pn="section-2.1-7.1">Congestion Control Information (CCI):</dt>
          <dd pn="section-2.1-7.2"> For packets carrying DASH segments, CCI <bcp14>MAY</bcp14> convey
          the 32-bit earliest presentation time <xref target="DASH" format="default" sectionFormat="of" derivedContent="DASH"/> of the
          DASH segment contained in the ROUTE packet. In this case, this
          information can be used by a ROUTE receiver for fast stream
          acquisition (details in <xref target="sect-6.2" format="default" sectionFormat="of" derivedContent="Section 6.2"/>). Otherwise, this field <bcp14>SHALL</bcp14> be
          set to 0.</dd>
          <dt pn="section-2.1-7.3">Transport Session Identifier (TSI):</dt>
          <dd pn="section-2.1-7.4"> This 32-bit field
   identifies the Transport Session in ROUTE. The context of the Transport
   Session is provided by signaling metadata. The value TSI = 0 <bcp14>SHALL</bcp14> only be
   used for service-specific signaling.</dd>
          <dt pn="section-2.1-7.5">Transport Object Identifier (TOI):</dt>
          <dd pn="section-2.1-7.6"> This 32-bit field <bcp14>SHALL</bcp14>
   identify the object within this session to which the payload of the current
   packet belongs. The mapping of the TOI field to the object is provided by
   the Extended File Delivery Table (FDT).</dd>
        </dl>
      </section>
      <section anchor="sect-2.2" numbered="true" toc="include" removeInRFC="false" pn="section-2.2">
        <name slugifiedName="name-lct-header-extensions">LCT Header Extensions</name>
        <t indent="0" pn="section-2.2-1">
   The following LCT header extensions are defined or used by ROUTE:

</t>
        <dl newline="false" spacing="normal" indent="3" pn="section-2.2-2">
          <dt pn="section-2.2-2.1">EXT_FTI:</dt>
          <dd pn="section-2.2-2.2"> as specified in RFC 5775.</dd>
          <dt pn="section-2.2-2.3">EXT_TOL:</dt>
          <dd pn="section-2.2-2.4"> the length in bytes of the multicast transport object shall be
          signaled using EXT_TOL as specified by ATSC-ROUTE <xref target="ATSCA331" format="default" sectionFormat="of" derivedContent="ATSCA331"/> with 24 bits or, if required, 48 bits of
          Transfer Length. The frequency of using the EXT_TOL header extension
          is determined by channel conditions that may cause the loss of the
          packet carrying the Close Object flag (B) <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>.</dd>
          <dt pn="section-2.2-2.5"/>
          <dd pn="section-2.2-2.6">
   NOTE: The transport object length can also be determined without the use of
   EXT_TOL by examining the LCT packet with the Close Object flag
   (B). However, if this packet is lost, then the EXT_TOL information can be
   used by the receiver to determine the transport object length.</dd>
          <dt pn="section-2.2-2.7">EXT_TIME Header:</dt>
          <dd pn="section-2.2-2.8"> as specified in RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>. The Sender Current Time <bcp14>SHALL</bcp14> be signaled using
   EXT_TIME.</dd>
        </dl>
      </section>
      <section anchor="sect-2.3" numbered="true" toc="include" removeInRFC="false" pn="section-2.3">
        <name slugifiedName="name-fec-payload-id-for-source-f">FEC Payload ID for Source Flows</name>
        <t indent="0" pn="section-2.3-1">
   The syntax of the FEC Payload ID for the Compact No-Code FEC Scheme used in
   ROUTE Source Flows is a 32-bit unsigned integer value that
   <bcp14>SHALL</bcp14> express the start_offset as an octet number
   corresponding to the first octet of the fragment of the delivery object
   carried in this packet. The start_offset value for the first fragment of
   any delivery object <bcp14>SHALL</bcp14> be set to 0. <xref target="start_offset" format="default" sectionFormat="of" derivedContent="Figure 3"/> shows the 32-bit start_offset field.</t>
        <figure anchor="start_offset" align="left" suppress-title="false" pn="figure-3">
          <name slugifiedName="name-fec-payload-id-for-source-fl">FEC Payload ID for Source Flows</name>
          <artwork name="" type="" align="left" alt="" pn="section-2.3-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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                         start_offset                          |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
        </figure>
      </section>
      <section anchor="sect-2.4" numbered="true" toc="include" removeInRFC="false" pn="section-2.4">
        <name slugifiedName="name-fec-payload-id-for-repair-f">FEC Payload ID for Repair Flows</name>
        <t indent="0" pn="section-2.4-1">
   FEC Payload ID for Repair Flows is specified in RFC 6330 <xref target="RFC6330" format="default" sectionFormat="of" derivedContent="RFC6330"/>.</t>
      </section>
    </section>
    <section anchor="sect-3" numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-session-metadata">Session Metadata</name>
      <t indent="0" pn="section-3-1">
   The required session metadata for Source and Repair Flows is
   specified in the following sections. The list specified here is not
   exhaustive; a service <bcp14>MAY</bcp14> signal more metadata to meet its needs. The
   data format is also not specified beyond its cardinality; the exact
   format of specifying the data is left for the service, e.g., by using
   XML encoding format, as has been done by <xref target="DVBMABR" format="default" sectionFormat="of" derivedContent="DVBMABR"/> and <xref target="ATSCA331" format="default" sectionFormat="of" derivedContent="ATSCA331"/>.
   It is specified in the following if an attribute is mandatory (m),
   conditional mandatory (cm) or optional (o) to realize a basic ROUTE
   session. A mandatory field <bcp14>SHALL</bcp14> always be present in the session
   metadata, and a conditional mandatory field <bcp14>SHALL</bcp14> be present if the
   specified condition is true. The delivery of the session metadata to
   the ROUTE receiver is beyond the scope of this document.</t>
      <section anchor="sect-3.1" numbered="true" toc="include" removeInRFC="false" pn="section-3.1">
        <name slugifiedName="name-generic-metadata">Generic Metadata</name>
        <t indent="0" pn="section-3.1-1">
   Generic metadata is applicable to both Source and Repair Flows as
   follows. Before a receiver can join a ROUTE session, the receiver
   needs to obtain this generic metadata that contains at least the
   following information:

</t>
        <dl newline="false" spacing="normal" indent="3" pn="section-3.1-2">
          <dt pn="section-3.1-2.1">ROUTE version number (m):</dt>
          <dd pn="section-3.1-2.2"> the version number of ROUTE used
   in this session. The version number conforming to this document <bcp14>SHALL</bcp14> be
   1.</dd>
          <dt pn="section-3.1-2.3">Connection ID (m):</dt>
          <dd pn="section-3.1-2.4"> the unique identifier of a Connection,
   usually consisting of the following 4-tuple: source IP address/source port number,
   destination IP address/destination port number. The IP addresses can be
   IPv4 or IPv6 addresses depending upon which IP version is used by the
   deployment.</dd>
        </dl>
      </section>
      <section anchor="sect-3.2" numbered="true" toc="include" removeInRFC="false" pn="section-3.2">
        <name slugifiedName="name-session-metadata-for-source">Session Metadata for Source Flows</name>
        <t indent="0" pn="section-3.2-1">
   stsi (m): The LCT TSI value corresponding to the Transport Session for
   the Source Flow.

</t>
        <dl newline="false" spacing="normal" indent="3" pn="section-3.2-2">
          <dt pn="section-3.2-2.1">rt (o):</dt>
          <dd pn="section-3.2-2.2"> A Boolean flag that <bcp14>SHALL</bcp14> indicate whether the
   content component carried by this Source Flow corresponds to real-time
   streaming media or non-real-time content. When set to "true", it <bcp14>SHALL</bcp14> be
   an indication of real-time content, and when absent or set to "false", it
   <bcp14>SHALL</bcp14> be an indication of non-real-time (NRT) content.</dd>
          <dt pn="section-3.2-2.3">minBufferSize (o):</dt>
          <dd pn="section-3.2-2.4"> A 32-bit unsigned integer that <bcp14>SHALL</bcp14>
   represent, in kilobytes, the minimum required storage size of the receiver
   transport buffer for the parent LCT channel of this Source Flow. The
   buffer holds the data belonging to a source object until its complete
   reception. This attribute is only applicable when rt = "true".</dd>
          <dt pn="section-3.2-2.5"/>
          <dd pn="section-3.2-2.6">A service that chooses not to signal this attribute relies on
   the receiver implementation, which must discard the received data beyond
   its buffering capability. Such discarding of data will impact the
   service quality.</dd>
          <dt pn="section-3.2-2.7">EFDT (cm):</dt>
          <dd pn="section-3.2-2.8"> When present, <bcp14>SHALL</bcp14> contain a single instance of
   an FDT-Instance element per RFC 6726 FLUTE <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>, which
   <bcp14>MAY</bcp14> contain the optional FDT extensions as defined in <xref target="sect-4.1" format="default" sectionFormat="of" derivedContent="Section 4.1"/>. The optional EFDT element <bcp14>MAY</bcp14> only be present for File
   Mode of delivery. In File Mode, it <bcp14>SHALL</bcp14> be present if this Source Flow
   transports streaming media segments.</dd>
          <dt pn="section-3.2-2.9">contentType (o):</dt>
          <dd pn="section-3.2-2.10"> A string that <bcp14>SHALL</bcp14> represent the media
   type for the media content. It <bcp14>SHALL</bcp14> obey the semantics of the Content-Type
   header as specified by the HTTP/1.1 protocol in RFC 7231 <xref target="RFC7231" format="default" sectionFormat="of" derivedContent="RFC7231"/>. This document does not define any new contentType
   strings. In its absence, the signaling of media type for the media content
   is beyond the scope of this document.</dd>
          <dt pn="section-3.2-2.11">applicationMapping (m):</dt>
          <dd pn="section-3.2-2.12"> A set of identifiers that provide an application-specific
          mapping of the received Application Objects to the Source Flows. For
          example, for DASH, this would provide the mapping of a Source Flow
          to a specific DASH Representation from a Media Presentation
          Description (MPD), the latter identified by its Representation and
          corresponding Adaptation Set and Period IDs.</dd>
        </dl>
      </section>
      <section anchor="sect-3.3" numbered="true" toc="include" removeInRFC="false" pn="section-3.3">
        <name slugifiedName="name-session-metadata-for-repair">Session Metadata for Repair Flows</name>
        <dl indent="3" newline="false" spacing="normal" pn="section-3.3-1">
          <dt pn="section-3.3-1.1">minBuffSize (o):
          </dt>
          <dd pn="section-3.3-1.2">
            <t indent="0" pn="section-3.3-1.2.1">
	    A 32-bit unsigned integer whose value <bcp14>SHALL</bcp14>
	  represent a required size of the receiver transport buffer for
	  AL‑FEC decoding processing. When present, this attribute
	  <bcp14>SHALL</bcp14> indicate the minimum buffer size that is
	  required to handle all associated objects that are assigned to a
	  super-object, i.e., a delivery object formed by the concatenation of
	  multiple FEC transport objects in order to bundle these FEC
	  transport objects for AL-FEC protection.
</t>
            <t indent="0" pn="section-3.3-1.2.2">                                                                                      
   A service that chooses not to signal this attribute relies on the receiver
   implementation, which must discard the received repair data beyond its
   buffering capability. Such discarding of data will impact the service
	   quality.</t>
          </dd>
          <dt pn="section-3.3-1.3">fecOTI (m): 
          </dt>
          <dd pn="section-3.3-1.4">A parameter consisting of the concatenation of Common and
	  Scheme-Specific FEC Object Transmission Information (FEC OTI) as
	  defined in Sections <xref target="RFC6330" sectionFormat="bare" section="3.3.2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6330#section-3.3.2" derivedContent="RFC6330"/> and <xref target="RFC6330" sectionFormat="bare" section="3.3.3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6330#section-3.3.3" derivedContent="RFC6330"/> of <xref target="RFC6330" format="default" sectionFormat="of" derivedContent="RFC6330"/> and
	  that corresponds to the delivery objects carried in the Source Flow
	  to which this Repair Flow is associated, with the following
	  qualification: the 40-bit Transfer Length (F) field may either
	  represent the actual size of the object, or it is encoded as all
	  zeroes. In the latter case, the FEC transport object size either is
	  unknown or cannot be represented by this attribute.  In other words,
	  for the all-zeroes format, the delivery objects in the Source Flow
	  correspond to streaming content, either a live Service whereby
	  content encoding has not yet occurred at the time this session data
	  was generated or pre-recorded streaming content whose delivery
	  object sizes, albeit known at the time of session data generation,
	  are variable and cannot be represented as a single value by the
	  fecOTI attribute.
	  </dd>
          <dt pn="section-3.3-1.5">ptsi (m):
          </dt>
          <dd pn="section-3.3-1.6">TSI value(s) of each Source Flow protected by this Repair Flow.
	  </dd>
          <dt pn="section-3.3-1.7">mappingTOIx (o):
          </dt>
          <dd pn="section-3.3-1.8">Values of the constant X for use in deriving the TOI of the
	  delivery object of each protected Source Flow from the TOI of the
	  FEC (super-)object. The default value is "1". Multiple mappingTOIx
	  values <bcp14>MAY</bcp14> be provided for each protected Source
	  Flow depending upon the usage of FEC (super-)object.
	  </dd>
          <dt pn="section-3.3-1.9">mappingTOIy (o):
          </dt>
          <dd pn="section-3.3-1.10">The corresponding constant Y to each mappingTOIx, when present,
	  for use in deriving the parent SourceTOI value from the above
	  equation. The default value is "0".
	  </dd>
        </dl>
      </section>
    </section>
    <section anchor="sect-4" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-delivery-object-mode">Delivery Object Mode</name>
      <t indent="0" pn="section-4-1">
   ROUTE provides several different delivery object modes, and one of
   these modes may suit the application needs better for a given
   Transport Session. A delivery object is self contained for the
   application, typically associated with certain properties, metadata,
   and timing-related information relevant to the
   application. The signaling of the delivery object mode is done on an
   object basis using Codepoint as specified in <xref target="sect-2.1" format="default" sectionFormat="of" derivedContent="Section 2.1"/>.</t>
      <section anchor="sect-4.1" numbered="true" toc="include" removeInRFC="false" pn="section-4.1">
        <name slugifiedName="name-file-mode">File Mode</name>
        <t indent="0" pn="section-4.1-1">
   File Mode uses an out-of-band Extended FDT (EFDT) signaling for
   recovery of delivery objects with the following extensions and
   considerations.</t>
        <section anchor="sect-4.1.1" numbered="true" toc="include" removeInRFC="false" pn="section-4.1.1">
          <name slugifiedName="name-extensions-to-fdt">Extensions to FDT</name>
          <t indent="0" pn="section-4.1.1-1">
   The following extensions are specified to FDT, as specified in RFC 6726
   <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>. An Extended FDT-Instance is an
   instance of FLUTE FDT, as specified in <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>, plus optionally one or more of the following
   extensions:

</t>
          <dl newline="false" spacing="normal" indent="3" pn="section-4.1.1-2">
            <dt pn="section-4.1.1-2.1">efdtVersion:</dt>
            <dd pn="section-4.1.1-2.2"> A value that <bcp14>SHALL</bcp14> represent the version of
   this Extended FDT-Instance.</dd>
            <dt pn="section-4.1.1-2.3">maxExpiresDelta:</dt>
            <dd pn="section-4.1.1-2.4">Let "tp" represent the wall clock time at
   the receiver when the receiver acquires the first ROUTE packet carrying
   data of the object described by this Extended FDT-Instance.
   maxExpiresDelta, when present, <bcp14>SHALL</bcp14> represent a time interval that when
   added to "tp" <bcp14>SHALL</bcp14> represent the expiration time of the associated
   Extended FDT-Instance "te". The time interval is expressed in number of
   seconds. When maxExpiresDelta is not present, the expiration time of the
   Extended FDT-Instance <bcp14>SHALL</bcp14> be given by the sum of a) the value of the ERT
   field in the EXT_TIME LCT header extension in the first ROUTE packet
   carrying data of that file, and b) the current receiver time when parsing
   the packet header of that ROUTE packet. See Sections <xref target="sect-5.4" format="counter" sectionFormat="of" derivedContent="5.4"/> and <xref target="sect-6.3.3" format="counter" sectionFormat="of" derivedContent="6.3.3"/> on
   additional rules for deriving the Extended FDT-Instance expiration
   time. Hence, <tt>te = tp + maxExpiresDelta</tt>
            </dd>
            <dt pn="section-4.1.1-2.5">maxTransportSize:</dt>
            <dd pn="section-4.1.1-2.6"> An attribute that <bcp14>SHALL</bcp14> represent the
   maximum transport size in bytes of any delivery object described by this
   Extended FDT-Instance. This attribute <bcp14>SHALL</bcp14> be present if a) the
   fileTemplate is present in Extended FDT-Instance, or b) one or more File
   elements, if present in this Extended FDT-Instance, do not include the
   Transfer-Length attribute. When maxTransportSize is not present, the
   maximum transport size is not signaled, while other signaling such as the
   Transfer-Length attribute signal the exact Transfer Length of the
   object.</dd>
            <dt pn="section-4.1.1-2.7">fileTemplate:</dt>
            <dd pn="section-4.1.1-2.8">A string value, which when present and in
   conjunction with parameter substitution, is used in deriving the
   Content-Location attribute for the delivery object described by this
   Extended FDT-Instance. It <bcp14>SHALL</bcp14> include the "$TOI$" identifier. Each
   identifier <bcp14>MAY</bcp14> be suffixed as needed by specific file names within the
   enclosing '$' characters following this prototype: <tt>%0[width]d</tt>
            </dd>
          </dl>
          <t indent="0" pn="section-4.1.1-3">
   The width parameter is an unsigned integer that provides the minimum
   number of characters to be printed. If the value to be printed is
   shorter than this number, the result <bcp14>SHALL</bcp14> be padded with leading
   zeroes. The value is not truncated even if the result is larger. When
   no format tag is present, a default format tag with width=1 <bcp14>SHALL</bcp14> be
   used.</t>
          <t indent="0" pn="section-4.1.1-4">
   Strings other than identifiers <bcp14>SHALL</bcp14> only contain characters that are
   permitted within URIs according to RFC 3986 <xref target="RFC3986" format="default" sectionFormat="of" derivedContent="RFC3986"/>.</t>
          <t indent="0" pn="section-4.1.1-5">
   <tt>$$</tt> is an escape sequence in fileTemplate value, i.e., "$$" is
   non-recursively replaced with a single "$".</t>
          <t indent="0" pn="section-4.1.1-6">
   The usage of fileTemplate is described in Sender and Receiver
   operations in Sections <xref target="sect-5.4" format="counter" sectionFormat="of" derivedContent="5.4"/> and <xref target="sect-6.3" format="counter" sectionFormat="of" derivedContent="6.3"/>, respectively.</t>
        </section>
        <section anchor="sect-4.1.2" numbered="true" toc="include" removeInRFC="false" pn="section-4.1.2">
          <name slugifiedName="name-constraints-on-extended-fdt">Constraints on Extended FDT</name>
          <t indent="0" pn="section-4.1.2-1">
   The Extended FDT-Instance <bcp14>SHALL</bcp14> conform to an FDT-Instance according
   to RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/> with the following constraints: at least one
   File element and the @Expires attribute <bcp14>SHALL</bcp14> be present.</t>
          <t indent="0" pn="section-4.1.2-2">
   Content encoding <bcp14>MAY</bcp14> be used for delivery of any file described by an
   FDT-Instance.File element in the Extended FDT-Instance. The content
   encoding defined in the present document is gzip <xref target="RFC1952" format="default" sectionFormat="of" derivedContent="RFC1952"/>. When content
   encoding is used, the File@Content-Encoding and File@Content-Length
   attributes <bcp14>SHALL</bcp14> be present in the Extended FDT-Instance.</t>
        </section>
      </section>
      <section anchor="sect-4.2" numbered="true" toc="include" removeInRFC="false" pn="section-4.2">
        <name slugifiedName="name-entity-mode">Entity Mode</name>
        <t indent="0" pn="section-4.2-1">
   For Entity Mode, the following applies:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.2-2">
          <li pn="section-4.2-2.1">Delivery object metadata <bcp14>SHALL</bcp14> be expressed in
          the form of entity headers as defined in HTTP/1.1, which correspond
          to one or more of the representation header fields, payload header
          fields, and response header fields as defined in Sections <xref target="RFC7231" section="3.1" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7231#section-3.1" derivedContent="RFC7231"/>, <xref target="RFC7231" section="3.3" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7231#section-3.3" derivedContent="RFC7231"/>, and <xref target="RFC7231" section="7" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7231#section-7" derivedContent="RFC7231"/>, respectively, of
          <xref target="RFC7231" format="default" sectionFormat="of" derivedContent="RFC7231"/>.</li>
          <li pn="section-4.2-2.2">The entity headers sent along with the delivery object provide all
      information about that multicast transport object.</li>
          <li pn="section-4.2-2.3">
            <t indent="0" pn="section-4.2-2.3.1">Sending a media object (if the object is chunked) in Entity Mode
      may result in one of the following options:</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.2-2.3.2">
              <li pn="section-4.2-2.3.2.1">
                <t indent="0" pn="section-4.2-2.3.2.1.1">If the length of the chunked object is known at the sender, the
        ROUTE Entity Mode delivery object <bcp14>MAY</bcp14> be sent without using
        HTTP/1.1 chunked transfer coding, i.e., the object starts with
        an HTTP header containing the Content Length field followed
        by the concatenation of CMAF Chunks:</t>
                <artwork name="" type="" align="left" alt="" pn="section-4.2-2.3.2.1.2">
|HTTP Header+Length||---chunk ----||---chunk ----||---chunk --
--||---chunk ----|
</artwork>
              </li>
              <li pn="section-4.2-2.3.2.2">
                <t indent="0" pn="section-4.2-2.3.2.2.1">If the length of the chunked object is unknown at the sender when
        starting to send the object, HTTP/1.1 chunked transfer coding
        format <bcp14>SHALL</bcp14> be used:</t>
                <artwork name="" type="" align="left" alt="" pn="section-4.2-2.3.2.2.2">
|HTTP Header||Separator+Length||---chunk ----
||Separator+Length||---chunk ----||Separator+Length||---chunk
----||Separator+Length||---chunk ----||Separator+Length=0|
</artwork>
                <t indent="0" pn="section-4.2-2.3.2.2.3">Note, however, that it is not required to send a CMAF Chunk in
        exactly one HTTP chunk.</t>
              </li>
            </ul>
          </li>
        </ul>
      </section>
      <section anchor="sect-4.3" numbered="true" toc="include" removeInRFC="false" pn="section-4.3">
        <name slugifiedName="name-unsigned-package-mode">Unsigned Package Mode</name>
        <t indent="0" pn="section-4.3-1">
   In this delivery mode, the delivery object consists of a group of
   files that are packaged for delivery only. If applied, the client is
   expected to unpack the package and provide each file as an
   independent object to the application. Packaging is supported by
   Multipart Multipurpose Internet Mail Extensions (MIME) <xref target="RFC2557" format="default" sectionFormat="of" derivedContent="RFC2557"/>,
   where objects are packaged into one document for transport, with
   Content-Type set to multipart/related. When binary files are
   included in the package, Content-Transfer-Encoding of "binary"
   should be used for those files.</t>
      </section>
      <section anchor="sect-4.4" numbered="true" toc="include" removeInRFC="false" pn="section-4.4">
        <name slugifiedName="name-signed-package-mode">Signed Package Mode</name>
        <t indent="0" pn="section-4.4-1">
   In Signed Package Mode delivery, the delivery object consists of a
   group of files that are packaged for delivery, and the package
   includes one or more signatures for validation. Signed packaging is
   supported by RFC 8551 Secure MIME (S/MIME) <xref target="RFC8551" format="default" sectionFormat="of" derivedContent="RFC8551"/>, where objects
   are packaged into one document for transport and the package includes
   objects necessary for validation of the package.</t>
      </section>
    </section>
    <section anchor="sect-5" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-sender-operation">Sender Operation</name>
      <section anchor="sect-5.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.1">
        <name slugifiedName="name-usage-of-alc-and-lct-for-so">Usage of ALC and LCT for Source Flow</name>
        <t indent="0" pn="section-5.1-1">
   ROUTE Source Flow carries the source data as specified in RFC 5775
   <xref target="RFC5775" format="default" sectionFormat="of" derivedContent="RFC5775"/>. There are several special considerations that ROUTE
   introduces to the usage of the LCT building block as outlined in the
   following:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.1-2">
          <li pn="section-5.1-2.1">ROUTE limits the usage of the LCT building block to a single
     channel per session. Congestion control is thus sender driven in
     ROUTE. It also signifies that there is no specific congestion-control-related signaling from the sender to the receiver; the CCI
     field is either set to 0 or used for other purposes as specified
     in <xref target="sect-2.1" format="default" sectionFormat="of" derivedContent="Section 2.1"/>. The functionality of receiver-driven layered
     multicast may still be offered by the application, allowing the
     receiver application to select the appropriate delivery session
     based on the bandwidth requirement of that session.</li>
        </ul>
        <t indent="0" pn="section-5.1-3">
   Further, the following details apply to LCT:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.1-4">
          <li pn="section-5.1-4.1">
            <t indent="0" pn="section-5.1-4.1.1">The Layered Coding Transport (LCT) Building Block as defined in
     RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/> is used with the following constraints:</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.1-4.1.2">
              <li pn="section-5.1-4.1.2.1">The TSI in the LCT header <bcp14>SHALL</bcp14> be set equal to the value of
        the stsi attribute in <xref target="sect-3.2" format="default" sectionFormat="of" derivedContent="Section 3.2"/>.</li>
              <li pn="section-5.1-4.1.2.2">The Codepoint (CP) in the LCT header <bcp14>SHALL</bcp14> be used to signal
        the applied formatting as defined in the signaling metadata.</li>
              <li pn="section-5.1-4.1.2.3">
                <t indent="0" pn="section-5.1-4.1.2.3.1">In accordance with ALC, a source FEC Payload ID header is used to
        identify, for FEC purposes, the encoding symbols of the
        delivery object, or a portion thereof, carried by the
        associated ROUTE packet. This information may be sent in
        several ways:

                </t>
                <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.1-4.1.2.3.2">
                  <li pn="section-5.1-4.1.2.3.2.1">
                    <t indent="0" pn="section-5.1-4.1.2.3.2.1.1">As a simple new null FEC scheme with the following usage:
	
                    </t>
                    <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.1-4.1.2.3.2.1.2">
                      <li pn="section-5.1-4.1.2.3.2.1.2.1">The value of the source FEC Payload ID header <bcp14>SHALL</bcp14> be set to
	  0 in case the ROUTE packet contains the entire delivery object, or
	  </li>
                      <li pn="section-5.1-4.1.2.3.2.1.2.2">The value of the source FEC Payload ID header <bcp14>SHALL</bcp14> be set as a
	  direct address (start offset) corresponding to the starting byte
	  position of the portion of the object carried in this packet using a
	  32-bit field.	</li>
                    </ul>
                  </li>
                  <li pn="section-5.1-4.1.2.3.2.2">In a compatible manner to RFC 6330 <xref target="RFC6330" format="default" sectionFormat="of" derivedContent="RFC6330"/> where the SBN and ESI
	defines the start offset together with the symbol size T.</li>
                  <li pn="section-5.1-4.1.2.3.2.3">The signaling metadata provides the appropriate parameters to
	indicate any of the above modes using the srcFecPayloadId attribute.</li>
                </ul>
              </li>
            </ul>
          </li>
          <li pn="section-5.1-4.2">
            <t indent="0" pn="section-5.1-4.2.1">The LCT Header EXT_TIME extension as defined in RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>
              <bcp14>MAY</bcp14> be used by the sender in the following manner:</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.1-4.2.2">
              <li pn="section-5.1-4.2.2.1">The Sender Current Time (SCT), depending on the application,
        <bcp14>MAY</bcp14> be used to occasionally or frequently signal the sender
        current time possibly for reliever time synchronization.</li>
              <li pn="section-5.1-4.2.2.2">The Expected Residual Time (ERT) <bcp14>MAY</bcp14> be used to indicate the
        expected remaining time for transmission of the current
        object in order to optimize detection of a lost delivery object.</li>
              <li pn="section-5.1-4.2.2.3">The Sender Last Changed (SLC) flag is typically not utilized
        but <bcp14>MAY</bcp14> be used to indicate the addition/removal of Segments.</li>
            </ul>
          </li>
        </ul>
        <t indent="0" pn="section-5.1-5">
   Additional extension headers <bcp14>MAY</bcp14> be used to support real-time
   delivery. Such extension headers are defined in <xref target="sect-2.1" format="default" sectionFormat="of" derivedContent="Section 2.1"/>.</t>
      </section>
      <section anchor="sect-5.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2">
        <name slugifiedName="name-route-packetization-for-sou">ROUTE Packetization for Source Flow</name>
        <t indent="0" pn="section-5.2-1">
   The following description of the ROUTE sender operation on the
   mapping of the Application Object to the ROUTE packet payloads
   logically represents an extension of RFC 5445 <xref target="RFC5445" format="default" sectionFormat="of" derivedContent="RFC5445"/>, which in
   turn inherits the context, language, declarations, and restrictions of
   the FEC building block in RFC 5052 <xref target="RFC5052" format="default" sectionFormat="of" derivedContent="RFC5052"/>.</t>
        <t indent="0" pn="section-5.2-2">
   The data carried in the payload of a given ROUTE packet constitutes a
   contiguous portion of the Application Object. ROUTE source delivery
   can be considered as a special case of the use of the Compact No-Code
   Scheme associated with FEC Encoding ID = 0 according to Sections
   <xref target="RFC5445" sectionFormat="bare" section="3.4.1" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5445#section-3.4.1" derivedContent="RFC5445"/> and <xref target="RFC5445" sectionFormat="bare" section="3.4.2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5445#section-3.4.2" derivedContent="RFC5445"/> of <xref target="RFC5445" format="default" sectionFormat="of" derivedContent="RFC5445"/>, in which the encoding symbol
   size is exactly one byte. As specified in <xref target="sect-2.1" format="default" sectionFormat="of" derivedContent="Section 2.1"/>, for ROUTE
   Source Flows, the FEC Payload ID <bcp14>SHALL</bcp14> deliver the 32-bit
   start_offset. All receivers are expected to support, at minimum,
   operation with this special case of the Compact No-Code FEC.</t>
        <t indent="0" pn="section-5.2-3">
   Note that in the event the source object size is greater than 2<sup>32</sup> bytes
   (approximately 4.3 GB), the applications (in the broadcaster server and the
   receiver) are expected to perform segmentation/reassembly using methods
   beyond the scope of this document.</t>
        <t indent="0" pn="section-5.2-4">
   Finally, in some special cases, a ROUTE sender <bcp14>MAY</bcp14> need to produce
   ROUTE packets that do not contain any payload. This may be required,
   for example, to signal the end of a session. These dataless packets
   do not contain FEC Payload ID or payload data, but only the LCT
   header fields. The total datagram length, conveyed by outer protocol
   headers (e.g., the IP or UDP header), enables receivers to detect the
   absence of the LCT header, FEC Payload ID, and payload data.</t>
        <section anchor="sect-5.2.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.1">
          <name slugifiedName="name-basic-route-packetization">Basic ROUTE Packetization</name>
          <t indent="0" pn="section-5.2.1-1">
   In the basic operation, it is assumed that the Application Object is
   fully available at the ROUTE sender.</t>
          <ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-5.2.1-2"><li pn="section-5.2.1-2.1" derivedCounter="1.">The amount of data to be sent in a single ROUTE packet is limited
      by the maximum transfer unit of the data packets or the size of
      the remaining data of the Application Object being sent, whichever
      is smaller. The transfer unit is determined either by knowledge of
      underlying transport block sizes or by other constraints.</li>
            <li pn="section-5.2.1-2.2" derivedCounter="2.">The start_offset field in the LCT header of the ROUTE packet
      indicates the byte offset of the carried data in the Application
      Object being sent.</li>
            <li pn="section-5.2.1-2.3" derivedCounter="3.">The Close Object flag (B) is set to 1 if this is the last ROUTE
      packet carrying the data of the Application Object.</li>
          </ol>
          <t indent="0" pn="section-5.2.1-3">
   The order of packet delivery is arbitrary, but in the absence of
   other constraints, delivery with increasing start_offset value is
   recommended.</t>
        </section>
        <section anchor="sect-5.2.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.2">
          <name slugifiedName="name-route-packetization-for-cma">ROUTE Packetization for CMAF Chunked Content</name>
          <t indent="0" pn="section-5.2.2-1">
   The following additional guidelines should be followed for ROUTE
   packetization of CMAF Chunked Content in addition to the guidelines of
   <xref target="sect-5.2.1" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>:</t>
          <ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-5.2.2-2"><li pn="section-5.2.2-2.1" derivedCounter="1.">If it is the first ROUTE packet carrying a CMAF Random Access
      chunk, except for the first CMAF Chunk in the segment, the
      Codepoint value <bcp14>MAY</bcp14> be set to 10, as specified in the Codepoint
      value table in <xref target="sect-2.1" format="default" sectionFormat="of" derivedContent="Section 2.1"/>. The receiver <bcp14>MAY</bcp14> use this information
      for optimization of random access.</li>
            <li pn="section-5.2.2-2.2" derivedCounter="2.">As soon as the total length of the media object is known,
      potentially with the packaging of the last CMAF Chunk of a
      segment, the EXT_TOL extension header <bcp14>MAY</bcp14> be added to the LCT
      header to signal the Transfer Length, so that the receiver may
      know this information in a timely fashion.</li>
          </ol>
        </section>
      </section>
      <section anchor="sect-5.3" numbered="true" toc="include" removeInRFC="false" pn="section-5.3">
        <name slugifiedName="name-timing-of-packet-emission">Timing of Packet Emission</name>
        <t indent="0" pn="section-5.3-1">
   The sender <bcp14>SHALL</bcp14> use the timing information provided by the
   application to time the emission of packets for a timely reception.
   This information may be contained in the Application Objects e.g.,
   DASH segments and/or the presentation manifest. Hence, such packets of
   streaming media with real-time constraints <bcp14>SHALL</bcp14> be sent in such a
   way as to enable their timely reception with respect to the presentation
   timeline.</t>
      </section>
      <section anchor="sect-5.4" numbered="true" toc="include" removeInRFC="false" pn="section-5.4">
        <name slugifiedName="name-extended-fdt-encoding-for-f">Extended FDT Encoding for File Mode Sending</name>
        <t indent="0" pn="section-5.4-1">
   For File Mode sending:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.4-2">
          <li pn="section-5.4-2.1">The TOI field in the ROUTE packet header <bcp14>SHALL</bcp14> be set such that
      Content-Location can be derived at the receiver according to File
      Template substitution specified in <xref target="sect-6.3.1" format="default" sectionFormat="of" derivedContent="Section 6.3.1"/>.</li>
          <li pn="section-5.4-2.2">After sending the first packet with a given TOI value, none of the
      packets pertaining to this TOI <bcp14>SHALL</bcp14> be sent later than the wall
      clock time as derived from maxExpiresDelta. The EXT_TIME header
      with Expected Residual Time (ERT) <bcp14>MAY</bcp14> be used in order to convey
      more accurate expiry time.</li>
        </ul>
      </section>
      <section anchor="sect-5.5" numbered="true" toc="include" removeInRFC="false" pn="section-5.5">
        <name slugifiedName="name-fec-framework-consideration">FEC Framework Considerations</name>
        <t indent="0" pn="section-5.5-1">
   The FEC framework uses concepts of the FECFRAME work as defined in
   RFC 6363 <xref target="RFC6363" format="default" sectionFormat="of" derivedContent="RFC6363"/>, as well as the FEC building block, RFC 5052
   <xref target="RFC5052" format="default" sectionFormat="of" derivedContent="RFC5052"/>, which is adopted in the existing FLUTE/ALC/LCT
   specifications.</t>
        <t indent="0" pn="section-5.5-2">
   The FEC design adheres to the following principles:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.5-3">
          <li pn="section-5.5-3.1">FEC-related information is provided only where needed.</li>
          <li pn="section-5.5-3.2">Receivers not capable of this framework can ignore repair packets.</li>
          <li pn="section-5.5-3.3">The FEC is symbol based with fixed symbol size per protected
     Source Flow. The ALC protocol and existing FEC schemes are reused.</li>
          <li pn="section-5.5-3.4">A FEC Repair Flow provides protection of delivery objects from one
     or more Source Flows.</li>
        </ul>
        <t indent="0" pn="section-5.5-4">
   The FEC-specific components of the FEC framework are:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.5-5">
          <li pn="section-5.5-5.1">FEC Repair Flow declaration including all FEC-specific
     information.</li>
          <li pn="section-5.5-5.2">A FEC transport object that is the concatenation of a delivery object,
     padding octets, and size information in order to form a chunk of data that has a size in symbols of N, where N &gt;= 1.</li>
          <li pn="section-5.5-5.3">A FEC super-object that is the concatenation of one or more FEC
     transport objects in order to bundle FEC transport objects for FEC
     protection.</li>
          <li pn="section-5.5-5.4">A FEC protocol and packet structure.</li>
        </ul>
        <t indent="0" pn="section-5.5-6">
   A receiver needs to be able to recover delivery objects from repair
   packets based on available FEC information.</t>
      </section>
      <section anchor="sect-5.6" numbered="true" toc="include" removeInRFC="false" pn="section-5.6">
        <name slugifiedName="name-fec-transport-object-constr">FEC Transport Object Construction</name>
        <t indent="0" pn="section-5.6-1">
   In order to identify a delivery object in the context of the repair
   protocol, the following information is needed:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.6-2">
          <li pn="section-5.6-2.1">TSI and TOI of the delivery object. In this case, the FEC object
     corresponds to the (entire) delivery object.</li>
          <li pn="section-5.6-2.2">Octet range of the delivery object, i.e., start offset within the delivery
     object and number of subsequent and contiguous octets of delivery object
     that constitutes the FEC object (i.e., the FEC-protected portion of the
     source object). In this case, the FEC object corresponds to a contiguous
     byte range portion of the delivery object.</li>
        </ul>
        <t indent="0" pn="section-5.6-3">
   Typically, for real-time object delivery with smaller delivery object
   sizes, the first mapping is applied, i.e., the delivery object is a
   FEC object.</t>
        <t indent="0" pn="section-5.6-4">
   Assuming that the FEC object is the delivery object, for each
   delivery object, the associated FEC transport object is comprised of
   the concatenation of the delivery object, padding octets (P), and the
   FEC object size (F) in octets, where F is carried in a 4-octet field.</t>
        <t indent="0" pn="section-5.6-5">
   The FEC transport object size S, in FEC encoding symbols, <bcp14>SHALL</bcp14> be an
   integer multiple of the symbol size Y.  S is determined from the session
   information and/or the repair packet headers.</t>
        <t indent="0" pn="section-5.6-6">
   F is carried in the last 4 octets of the FEC transport object.
   Specifically, let:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.6-7">
          <li pn="section-5.6-7.1">F be the size of the delivery object in octets,</li>
          <li pn="section-5.6-7.2">F' be the F octets of data of the delivery object,</li>
          <li pn="section-5.6-7.3">f' denote the four octets of data carrying the value of F in
     network octet order (high-order octet first),</li>
          <li pn="section-5.6-7.4">S be the size of the FEC transport object with S=ceil((F+4)/Y),
     where the ceil() function rounds the result upward to its nearest
     integer,</li>
          <li pn="section-5.6-7.5">P' be S*Y-4-F octets of data, i.e., padding placed between the
     delivery object and the 4-byte field conveying the value of F and
     located at the end of the FEC transport object, and</li>
          <li pn="section-5.6-7.6">O' be the concatenation of F', P', and f'.</li>
        </ul>
        <t indent="0" pn="section-5.6-8">
   O' then constitutes the FEC transport object of size S*Y octets. Note
   that padding octets and the object size F are not sent in source
   packets of the delivery object but are only part of a FEC transport
   object that FEC decoding recovers in order to extract the FEC object
   and thus the delivery object or portion of the delivery object that
   constitutes the FEC object. In the above context, the FEC transport
   object size in symbols is S.</t>
        <t indent="0" pn="section-5.6-9">
   The general information about a FEC transport object that is
   conveyed to a FEC-enabled receiver is the source TSI, source TOI, and
   the associated octet range within the delivery object comprising the
   associated FEC object. However, as the size in octets of the FEC
   object is provided in the appended field within the FEC transport
   object, the remaining information can be conveyed as:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.6-10">
          <li pn="section-5.6-10.1">The TSI and TOI of the delivery object from which the FEC object
     associated with the FEC transport object is generated</li>
          <li pn="section-5.6-10.2">The start octet within the delivery object for the associated FEC object</li>
          <li pn="section-5.6-10.3">The size in symbols of the FEC transport object, S</li>
        </ul>
      </section>
      <section anchor="sect-5.7" numbered="true" toc="include" removeInRFC="false" pn="section-5.7">
        <name slugifiedName="name-super-object-construction">Super-Object Construction</name>
        <t indent="0" pn="section-5.7-1">
   From the FEC Repair Flow declaration, the construction of a FEC
   super-object as the concatenation of one or more FEC transport
   objects can be determined. The FEC super-object includes the general
   information about the FEC transport objects as described in the
   previous sections, as well as the placement order of FEC transport
   objects within the FEC super-object.</t>
        <t indent="0" pn="section-5.7-2">
   Let:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.7-3">
          <li pn="section-5.7-3.1">N be the total number of FEC transport objects for the FEC super-object
     construction.</li>
          <li pn="section-5.7-3.2">For i = 0, ..., N-1, let S[i] be the size in symbols of FEC
     transport object i.</li>
          <li pn="section-5.7-3.3">B' be the FEC super-object that is the concatenation of the FEC
     transport objects in numerical order, comprised of K = Sum of N
     source symbols, each symbol denoted as S[i].</li>
        </ul>
        <t indent="0" pn="section-5.7-4">
   For each FEC super-object, the remaining general information that
   needs to be conveyed to a FEC-enabled receiver, beyond what is
   already carried in the FEC transport objects that constitute the FEC
   super-object, comprises:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.7-5">
          <li pn="section-5.7-5.1">The total number of FEC transport objects N.</li>
          <li pn="section-5.7-5.2">
            <t indent="0" pn="section-5.7-5.2.1">For each FEC transport object:</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.7-5.2.2">
              <li pn="section-5.7-5.2.2.1">The TSI and TOI of the delivery object from which the FEC object
        associated with the FEC transport object is generated,</li>
              <li pn="section-5.7-5.2.2.2">The start octet within the delivery object for the associated FEC
        object, and</li>
              <li pn="section-5.7-5.2.2.3">The size in symbols of the FEC transport object.</li>
            </ul>
          </li>
        </ul>
        <t indent="0" pn="section-5.7-6">
   The carriage of the FEC repair information is discussed below.</t>
      </section>
      <section anchor="sect-5.8" numbered="true" toc="include" removeInRFC="false" pn="section-5.8">
        <name slugifiedName="name-repair-packet-consideration">Repair Packet Considerations</name>
        <t indent="0" pn="section-5.8-1">
   The repair protocol is based on Asynchronous Layered Coding (ALC) as
   defined in RFC 5775 <xref target="RFC5775" format="default" sectionFormat="of" derivedContent="RFC5775"/> and the Layered Coding Transport (LCT)
   Building Block as defined in RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/> with the following
   details:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.8-2">
          <li pn="section-5.8-2.1">
            <t indent="0" pn="section-5.8-2.1.1">The Layered Coding Transport (LCT) Building Block as defined in
     RFC 5651 <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/> is used as defined in Asynchronous Layered
     Coding (ALC), <xref target="sect-2.1" format="default" sectionFormat="of" derivedContent="Section 2.1"/>. In addition, the following constraint
     applies:</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.8-2.1.2">
              <li pn="section-5.8-2.1.2.1">The TSI in the LCT header <bcp14>SHALL</bcp14> identify the Repair Flow to
       which this packet applies by the matching the value of the ptsi
       attribute in the signaling metadata among the LCT channels
       carrying Repair Flows.</li>
            </ul>
          </li>
          <li pn="section-5.8-2.2">
            <t indent="0" pn="section-5.8-2.2.1">The FEC building block is used according to RFC 6330 <xref target="RFC6330" format="default" sectionFormat="of" derivedContent="RFC6330"/>,
     but only repair packets are delivered.</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.8-2.2.2">
              <li pn="section-5.8-2.2.2.1">Each repair packet within the scope of the Repair Flow (as indicated
        by the TSI field in the LCT header) <bcp14>SHALL</bcp14> carry the repair symbols for
        a corresponding FEC transport object/super-object as identified by its
        TOI. The repair object/super- object TOI <bcp14>SHALL</bcp14> be unique for each FEC
        super-object that is created within the scope of the TSI.</li>
            </ul>
          </li>
        </ul>
      </section>
      <section anchor="sect-5.9" numbered="true" toc="include" removeInRFC="false" pn="section-5.9">
        <name slugifiedName="name-summary-fec-information">Summary FEC Information</name>
        <t indent="0" pn="section-5.9-1">
   For each super-object (identified by a unique TOI within a Repair
   Flow that is in turn identified by the TSI in the LCT header) that is
   generated, the following information needs to be communicated to the
   receiver:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.9-2">
          <li pn="section-5.9-2.1">
            <t indent="0" pn="section-5.9-2.1.1">The FEC configuration consisting of:</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.9-2.1.2">
              <li pn="section-5.9-2.1.2.1">FEC Object Transmission Information (OTI) per RFC 5052
        <xref target="RFC5052" format="default" sectionFormat="of" derivedContent="RFC5052"/>.</li>
              <li pn="section-5.9-2.1.2.2">Additional FEC information (see <xref target="sect-3.3" format="default" sectionFormat="of" derivedContent="Section 3.3"/>).</li>
              <li pn="section-5.9-2.1.2.3">The total number of FEC objects included in the FEC super-object, N.</li>
            </ul>
          </li>
          <li pn="section-5.9-2.2">
            <t indent="0" pn="section-5.9-2.2.1">For each FEC transport object:</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.9-2.2.2">
              <li pn="section-5.9-2.2.2.1">TSI and TOI of the delivery object used to generate the FEC
        object associated with the FEC transport object,</li>
              <li pn="section-5.9-2.2.2.2">The start octet within the delivery object of the associated FEC
        object, if applicable, and</li>
              <li pn="section-5.9-2.2.2.3">The size in symbols of the FEC transport object, S.</li>
            </ul>
          </li>
        </ul>
        <t indent="0" pn="section-5.9-3">
   The above information is delivered:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.9-4">
          <li pn="section-5.9-4.1">Statically in the session metadata as defined in <xref target="sect-3.3" format="default" sectionFormat="of" derivedContent="Section 3.3"/>, and</li>
          <li pn="section-5.9-4.2">Dynamically in an LCT extension header.</li>
        </ul>
      </section>
    </section>
    <section anchor="sect-6" numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-receiver-operation">Receiver Operation</name>
      <t indent="0" pn="section-6-1">
   The receiver receives packets and filters those packets according to
   the following. From the ROUTE session and each contained LCT channel,
   the receiver regenerates delivery objects from the ROUTE session and
   each contained LCT channel.</t>
      <t indent="0" pn="section-6-2">
   In the event that the receiver receives data that does not conform to
   the ROUTE protocol specified in this document, the receiver <bcp14>SHOULD</bcp14>
   attempt to recover gracefully by e.g., informing the application about
   the issues using means beyond the scope of this document. The ROUTE
   packetization specified in <xref target="sect-5.2.1" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/> implies that the receiver
   <bcp14>SHALL NOT</bcp14> receive overlapping data; if such a condition is
   encountered at the receiver, the packet <bcp14>SHALL</bcp14> be assumed to be
   corrupted.</t>
      <t indent="0" pn="section-6-3">
   The basic receiver operation is provided below (it assumes an error-free
   scenario), while repair considerations are provided in <xref target="sect-7" format="default" sectionFormat="of" derivedContent="Section 7"/>.</t>
      <section anchor="sect-6.1" numbered="true" toc="include" removeInRFC="false" pn="section-6.1">
        <name slugifiedName="name-basic-application-object-re">Basic Application Object Recovery for Source Flows</name>
        <t indent="0" pn="section-6.1-1">
   Upon receipt of each ROUTE packet of a Source Flow, the receiver
   proceeds with the following steps in the order listed.</t>
        <ol spacing="normal" type="%d)" indent="adaptive" start="1" pn="section-6.1-2"><li pn="section-6.1-2.1" derivedCounter="1)">The ROUTE receiver is expected to parse the LCT and FEC Payload ID to
     verify that it is a valid header. If it is not valid, then the payload is
     discarded without further processing.</li>
          <li pn="section-6.1-2.2" derivedCounter="2)">All ROUTE packets used to recover a specific delivery object carry the
     same TOI value in the LCT header.</li>
          <li pn="section-6.1-2.3" derivedCounter="3)">The ROUTE receiver is expected to assert that the TSI and the
     Codepoint represent valid operation points in the signaling metadata,
     i.e., the signaling contains a matching entry to the TSI value provided in
     the packet header, as well as for this TSI, and the Codepoint field in the
     LCT header has a valid Codepoint mapping.</li>
          <li pn="section-6.1-2.4" derivedCounter="4)">
            <t indent="0" pn="section-6.1-2.4.1">The ROUTE receiver should process the remainder of the payload,
     including the appropriate interpretation of the other payload header
     fields, using the source FEC Payload ID (to determine the
     start_offset) and the payload data to reconstruct the corresponding
     object as follows:

            </t>
            <ol spacing="normal" type="a" indent="adaptive" start="1" pn="section-6.1-2.4.2"><li pn="section-6.1-2.4.2.1" derivedCounter="a.">For File Mode, upon receipt of the first ROUTE packet
         payload for an object, the ROUTE receiver uses the
         File@Transfer-Length attribute of the associated Extended FDT-Instance, when present, to determine the length T of the
         object. When the File@Transfer-Length attribute is not
         present in the Extended FDT-Instance, the receiver uses the
         maxTransportSize attribute of the associated Extended FDT-Instance to determine the maximum length T' of the object.
         Alternatively, and specifically for delivery modes other than
         File Mode, the EXT_TOL header can be used to determine the length
         T of the object.</li>
              <li pn="section-6.1-2.4.2.2" derivedCounter="b.">The ROUTE receiver allocates buffer space for the T or T'
         bytes that the object will or may occupy.</li>
              <li pn="section-6.1-2.4.2.3" derivedCounter="c.">The ROUTE receiver computes the length of the payload, Y, by
         subtracting the payload header length from the total length
         of the received payload.</li>
              <li pn="section-6.1-2.4.2.4" derivedCounter="d.">
                <t indent="0" pn="section-6.1-2.4.2.4.1">The ROUTE receiver allocates a Boolean array RECEIVED[0..T-1] or
         RECEIVED[0..T'-1], as appropriate, with all entries initialized to
         false to track received object symbols. The ROUTE receiver
         continuously acquires packet payloads for the object as long as all
         of the following conditions are satisfied:</t>
                <ol type="i" indent="adaptive" spacing="normal" start="1" pn="section-6.1-2.4.2.4.2">
	   <li pn="section-6.1-2.4.2.4.2.1" derivedCounter="i.">there is at least one entry in RECEIVED still set to false,
	   </li>
                  <li pn="section-6.1-2.4.2.4.2.2" derivedCounter="ii.">the object has not yet expired, and</li>
                  <li pn="section-6.1-2.4.2.4.2.3" derivedCounter="iii.">
                    <t indent="0" pn="section-6.1-2.4.2.4.2.3.1">the application has not given up on reception of this object.</t>
                    <t indent="0" pn="section-6.1-2.4.2.4.2.3.2">More details are provided below. </t>
                  </li>
                </ol>
              </li>
              <li pn="section-6.1-2.4.2.5" derivedCounter="e.">
                <t indent="0" pn="section-6.1-2.4.2.5.1">For each received ROUTE packet payload for the object
                (including the first payload), the steps to be taken to help
                recover the object are as follows:

                </t>
                <ol spacing="normal" type="i" indent="adaptive" start="1" pn="section-6.1-2.4.2.5.2"><li pn="section-6.1-2.4.2.5.2.1" derivedCounter="i.">If the packet includes an
                EXT_TOL or EXT_FTI header, modify the Boolean array
                RECEIVED[0..T'-1] to become RECEIVED[0..T-1].</li>
                  <li pn="section-6.1-2.4.2.5.2.2" derivedCounter="ii.">Let X be the value of the start_offset field in the ROUTE
	    packet header and let Y be the length of the payload, Y, computed
	    by subtracting the LCT header size and the FEC Payload ID size
	    from the total length of the received packet.</li>
                  <li pn="section-6.1-2.4.2.5.2.3" derivedCounter="iii.">The ROUTE receiver copies the data into the appropriate place
	    within the space reserved for the object and sets RECEIVED[X
	    ... X+Y-1] = true.</li>
                  <li pn="section-6.1-2.4.2.5.2.4" derivedCounter="iv.">If all T entries of RECEIVED are true, then the receiver has
	    recovered the entire object.</li>
                </ol>
              </li>
            </ol>
          </li>
        </ol>
        <t indent="0" pn="section-6.1-3">
   Upon recovery of both the complete set of packet payloads for the
   delivery object associated with a given TOI value, and the metadata
   for that delivery object, the reception of the delivery object, now a
   fully received Application Object, is complete.</t>
        <t indent="0" pn="section-6.1-4">
   Given the timely reception of ROUTE packets belonging to an
   Application Object, the receiver <bcp14>SHALL</bcp14> make the Application Objects
   available to the application in a timely fashion using the
   application-provided timing data (e.g., the timing data signaled via
   the presentation manifest file). For example, HTTP/1.1 chunked
   transfer may need to be enabled to transfer the Application Objects
   if MPD@availabilityTimeOffset is signaled in the DASH presentation
   manifest in order to allow for the timely sending of segment data to the
   application.</t>
      </section>
      <section anchor="sect-6.2" numbered="true" toc="include" removeInRFC="false" pn="section-6.2">
        <name slugifiedName="name-fast-stream-acquisition">Fast Stream Acquisition</name>
        <t indent="0" pn="section-6.2-1">
   When the receiver initially starts reception of ROUTE packets, it is likely
   that the reception does not start from the very first packet carrying the
   data of a multicast transport object; in this case, such a partially
   received object is normally discarded. However, the channel acquisition or
   "tune-in" times can be improved if the partially received object is usable
   by the application.  One example realization for this is as follows:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-6.2-2">
          <li pn="section-6.2-2.1">The receiver checks for the first received packet with the
     Codepoint value set to 10, indicating the start of a CMAF Random
     Access chunk.</li>
          <li pn="section-6.2-2.2">The receiver <bcp14>MAY</bcp14> make the partially received object (a partial
     DASH segment starting from the packet above) available to the
     application for fast stream acquisition.</li>
          <li pn="section-6.2-2.3">It <bcp14>MAY</bcp14> recover the earliest presentation time of this CMAF Random
     Access chunk from the ROUTE packet LCT Congestion Control
     Information (CCI) field as specified in <xref target="sect-2.1" format="default" sectionFormat="of" derivedContent="Section 2.1"/> to be able to
     add a new Period element in the MPD exposed to the application
      containing just the partially received DASH segment with period
      continuity signaling.</li>
        </ul>
      </section>
      <section anchor="sect-6.3" numbered="true" toc="include" removeInRFC="false" pn="section-6.3">
        <name slugifiedName="name-generating-extended-fdt-ins">Generating Extended FDT-Instance for File Mode</name>
        <t indent="0" pn="section-6.3-1">
   An Extended FDT-Instance conforming to RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>, is produced at the receiver using the service metadata
   and in-band signaling in the following steps:</t>
        <section anchor="sect-6.3.1" numbered="true" toc="include" removeInRFC="false" pn="section-6.3.1">
          <name slugifiedName="name-file-template-substitution-">File Template Substitution for Content-Location Derivation</name>
          <t indent="0" pn="section-6.3.1-1">
   The Content-Location element of the Extended FDT for a specific
   Application Object is derived as follows:</t>
          <t indent="0" pn="section-6.3.1-2">
   "$TOI$" is substituted with the unique TOI value in the LCT header of
   the ROUTE packets used to recover the given delivery object (as
   specified in <xref target="sect-6.1" format="default" sectionFormat="of" derivedContent="Section 6.1"/>).</t>
          <t indent="0" pn="section-6.3.1-3">
   After the substitution, the fileTemplate <bcp14>SHALL</bcp14> be a valid URL
   corresponding to the Content-Location attribute of the associated
   Application Object.</t>
          <t indent="0" pn="section-6.3.1-4">
   An example @fileTemplate using a width of 5 is:
   fileTemplate="myVideo$TOI%05d$.mps", resulting in file names with
   exactly five digits in the number portion. The Media Segment file
   name for TOI=33 using this template is myVideo00033.mps.</t>
        </section>
        <section anchor="sect-6.3.2" numbered="true" toc="include" removeInRFC="false" pn="section-6.3.2">
          <name slugifiedName="name-filetransfer-length-derivat">File@Transfer-Length Derivation</name>
          <t indent="0" pn="section-6.3.2-1">
   Either the EXT_FTI header (per RFC 5775 <xref target="RFC5775" format="default" sectionFormat="of" derivedContent="RFC5775"/>) or the EXT_TOL
   header, when present, is used to derive the Transport Object Length
   (TOL) of the File. If the File@Transfer-Length parameter in the
   Extended FDT-Instance is not present, then the EXT_TOL header or the
   or EXT_FTI header <bcp14>SHALL</bcp14> be present. Note that a header containing the
   transport object length (EXT_TOL or EXT_FTI) need not be present in
   each packet header. If the broadcaster does not know the length of
   the transport object at the beginning of the transfer, an EXT_TOL or
   EXT_FTI header <bcp14>SHALL</bcp14> be included in at least the last packet of the
   file and should be included in the last few packets of the transfer.</t>
        </section>
        <section anchor="sect-6.3.3" numbered="true" toc="include" removeInRFC="false" pn="section-6.3.3">
          <name slugifiedName="name-fdt-instanceexpires-derivat">FDT-Instance@Expires Derivation</name>
          <t indent="0" pn="section-6.3.3-1">
   When present, the maxExpiresDelta attribute <bcp14>SHALL</bcp14> be used to generate
   the value of the FDT-Instance@Expires attribute. The receiver is
   expected to add this value to its wall clock time when acquiring the
   first ROUTE packet carrying the data of a given delivery object to
   obtain the value for @Expires.</t>
          <t indent="0" pn="section-6.3.3-2">
   When maxExpiresDelta is not present, the EXT_TIME header with
   Expected Residual Time (ERT) <bcp14>SHALL</bcp14> be used to derive the expiry time
   of the Extended FDT-Instance. When both maxExpiresDelta and the ERT
   of EXT_TIME are present, the smaller of the two values should be used
   as the incremental time interval to be added to the receiver's
   current time to generate the effective value for @Expires. When
   neither maxExpiresDelta nor the ERT field of the EXT_TIME header is
   present, then the expiration time of the Extended FDT-Instance is
   given by its @Expires attribute.</t>
        </section>
      </section>
    </section>
    <section anchor="sect-7" numbered="true" toc="include" removeInRFC="false" pn="section-7">
      <name slugifiedName="name-fec-application">FEC Application</name>
      <section anchor="sect-7.1" numbered="true" toc="include" removeInRFC="false" pn="section-7.1">
        <name slugifiedName="name-general-fec-application-gui">General FEC Application Guidelines</name>
        <t indent="0" pn="section-7.1-1">
   It is up to the receiver to decide to use zero, one, or more of the
   FEC streams. Hence, the application assigns a recovery property to
   each flow, which defines aspects such as the delay and the required
   memory if one or the other is chosen. The receiver <bcp14>MAY</bcp14> decide whether
   or not to utilize Repair Flows based on the following considerations:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.1-2">
          <li pn="section-7.1-2.1">The desired start-up and end-to-end latency. If a Repair Flow
     requires a significant amount of buffering time to be effective,
     such Repair Flow might only be used in time-shift operations or in
     poor reception conditions, since use of such Repair Flow trades
     off end-to-end latency against DASH Media Presentation quality.</li>
          <li pn="section-7.1-2.2">FEC capabilities, i.e., the receiver <bcp14>MAY</bcp14> pick only the FEC
     algorithm that it supports.</li>
          <li pn="section-7.1-2.3">Which Source Flows are being protected; for example, if the Repair
     Flow protects Source Flows that are not selected by the receiver,
     then the receiver may not select the Repair Flow.</li>
          <li pn="section-7.1-2.4">Other considerations such as available buffer size, reception
     conditions, etc.</li>
        </ul>
        <t indent="0" pn="section-7.1-3">
   If a receiver decides to acquire a certain Repair Flow, then the
   receiver must receive data on all Source Flows that are protected by
   that Repair Flow to collect the relevant packets.</t>
      </section>
      <section anchor="sect-7.2" numbered="true" toc="include" removeInRFC="false" pn="section-7.2">
        <name slugifiedName="name-toi-mapping">TOI Mapping</name>
        <t indent="0" pn="section-7.2-1">
   When mappingTOIx/mappingTOIy are used to signal X and Y values, the TOI
   value(s) of the one or more source objects (sourceTOI) protected by a given
   FEC transport object or FEC super-object with a TOI value rTOI is derived
   through an equation sourceTOI = X*rTOI + Y.</t>
        <t indent="0" pn="section-7.2-2">
   When neither mappingTOIx nor mappingTOIy is present, there is a 1:1
   relationship between each delivery object carried in the Source Flow
   as identified by ptsi to a FEC object carried in this Repair Flow.
   In this case, the TOI of each of those delivery objects <bcp14>SHALL</bcp14> be
   identical to the TOI of the corresponding FEC object.</t>
      </section>
      <section anchor="sect-7.3" numbered="true" toc="include" removeInRFC="false" pn="section-7.3">
        <name slugifiedName="name-delivery-object-reception-t">Delivery Object Reception Timeout</name>
        <t indent="0" pn="section-7.3-1">
   The permitted start and end times for the receiver to perform the
   file repair procedure, in case of unsuccessful broadcast file
   reception, and associated rules and parameters are as follows:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3-2">
          <li pn="section-7.3-2.1">The latest time that the file repair procedure may start is bound
     by the @Expires attribute of the FDT-Instance.</li>
          <li pn="section-7.3-2.2">
            <t indent="0" pn="section-7.3-2.2.1">The receiver may choose to start the file repair procedure
            earlier if it detects the occurrence of any of the following
            events:</t>
            <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7.3-2.2.2">
              <li pn="section-7.3-2.2.2.1">Presence of the Close Object flag (B) in the LCT header
        <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/> for the file of interest;</li>
              <li pn="section-7.3-2.2.2.2">Presence of the Close Session flag (A) in the LCT header
        <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/> before the nominal expiration of the Extended FDT-Instance as defined by the @Expires attribute.</li>
            </ul>
          </li>
        </ul>
      </section>
      <section anchor="sect-7.4" numbered="true" toc="include" removeInRFC="false" pn="section-7.4">
        <name slugifiedName="name-example-fec-operation">Example FEC Operation</name>
        <t indent="0" pn="section-7.4-1">
   To be able to recover the delivery objects that are protected by a Repair
   Flow, a receiver needs to obtain the necessary Service signaling metadata
   fragments that describe the corresponding collection of delivery objects
   that are covered by this Repair Flow.  A Repair Flow is characterized by
   the combination of an LCT channel, a unique TSI number, as well as the
   corresponding protected Source Flows.</t>
        <t indent="0" pn="section-7.4-2">
   If a receiver acquires data of a Repair Flow, the receiver is expected to
   collect all packets of all protected Transport Sessions.  Upon receipt of
   each packet, whether it is a source or repair packet, the receiver proceeds
   with the following steps in the order listed.</t>
        <ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-7.4-3"><li pn="section-7.4-3.1" derivedCounter="1.">The receiver is expected to parse
        the packet header and verify that it is a valid header. If it is not
        valid, then the packet <bcp14>SHALL</bcp14> be discarded without
        further processing.</li>
          <li pn="section-7.4-3.2" derivedCounter="2.">The receiver is expected to parse the TSI field of the packet
          header and verify that a matching value exists in the Service
          signaling for the Repair Flow or the associated Protected Source
          Flow. If no match is found, the packet <bcp14>SHALL</bcp14> be
          discarded without further processing.</li>
          <li pn="section-7.4-3.3" derivedCounter="3.">
            <t indent="0" pn="section-7.4-3.3.1">The receiver processes the remainder of the packet, including
            interpretation of the other header fields, and using the source
            FEC Payload ID (to determine the start_offset byte position within
            the source object), the Repair FEC Payload ID, as well as the
            payload data, reconstructs the decoding blocks corresponding to a
            FEC super-object as follows:</t>
            <ol spacing="normal" type="a" indent="adaptive" start="1" pn="section-7.4-3.3.2"><li pn="section-7.4-3.3.2.1" derivedCounter="a.">For a source packet, the
            receiver identifies the delivery object to which the received
            packet is associated using the session information and the TOI
            carried in the payload header. Similarly, for a repair object, the
            receiver identifies the FEC super-object to which the received
            packet is associated using the session information and the TOI
            carried in the payload header.</li>
              <li pn="section-7.4-3.3.2.2" derivedCounter="b.">For source packets, the receiver collects the data for each
              FEC super-object and recovers FEC super-objects in the same way
              as a Source Flow in <xref target="sect-6.1" format="default" sectionFormat="of" derivedContent="Section 6.1"/>. The received FEC super-object is then mapped
              to a source block and the corresponding encoding symbols are
              generated.</li>
              <li pn="section-7.4-3.3.2.3" derivedCounter="c.">With the reception of the repair packets, the FEC
              super-object can be recovered.</li>
              <li pn="section-7.4-3.3.2.4" derivedCounter="d.">Once the FEC super-object is recovered, the individual
         delivery objects can be extracted.</li>
            </ol>
          </li>
        </ol>
      </section>
    </section>
    <section anchor="sect-8" numbered="true" toc="include" removeInRFC="false" pn="section-8">
      <name slugifiedName="name-considerations-for-defining">Considerations for Defining ROUTE Profiles</name>
      <t indent="0" pn="section-8-1">
   Services (e.g., ATSC-ROUTE <xref target="ATSCA331" format="default" sectionFormat="of" derivedContent="ATSCA331"/>, DVB-MABR <xref target="DVBMABR" format="default" sectionFormat="of" derivedContent="DVBMABR"/>, etc.) may define specific ROUTE "profiles" based
   on this document in their respective standards organizations. An example is
   noted in the overview section: DVB has specified a profile of ATSC-ROUTE in
   DVB Adaptive Media Streaming over IP Multicast (DVB-MABR) <xref target="DVBMABR" format="default" sectionFormat="of" derivedContent="DVBMABR"/>. The definition has the following
   considerations. Services <bcp14>MAY</bcp14></t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-8-2">
        <li pn="section-8-2.1">Restrict the signaling of certain values signaled in the LCT header
     and/or provision unused fields in the LCT header.</li>
        <li pn="section-8-2.2">Restrict using certain LCT header extensions and/or add new LCT
        header extensions.</li>
        <li pn="section-8-2.3">Restrict or limit usage of some Codepoints and/or assign semantics
        to service-specific Codepoints marked as reserved in this
        document.</li>
        <li pn="section-8-2.4">Restrict usage of certain Service signaling attributes and/or add
        their own service metadata.</li>
      </ul>
      <t indent="0" pn="section-8-3">
   Services <bcp14>SHALL NOT</bcp14> redefine the semantics of any of the ROUTE
   attributes in LCT headers and extensions, as well as Service signaling
   attributes already specified in this document.</t>
      <t indent="0" pn="section-8-4">
   By following these guidelines, services can define profiles that are
   interoperable.</t>
    </section>
    <section anchor="sect-9" numbered="true" toc="include" removeInRFC="false" pn="section-9">
      <name slugifiedName="name-route-concepts">ROUTE Concepts</name>
      <section anchor="sect-9.1" numbered="true" toc="include" removeInRFC="false" pn="section-9.1">
        <name slugifiedName="name-route-modes-of-delivery">ROUTE Modes of Delivery</name>
        <t indent="0" pn="section-9.1-1">
   Different ROUTE delivery modes specified in <xref target="sect-4" format="default" sectionFormat="of" derivedContent="Section 4"/> are optimized for delivery of different types of media
   data. For example, File Mode is specifically optimized for delivering DASH
   content using Segment Template with number substitution. Using File
   Template in EFDT avoids the need for the repeated sending of metadata as
   outlined in the following section. Same optimizations, however, cannot be
   used for time substitution and segment timeline where the addressing of
   each segment is time dependent and in general does not follow a fixed or
   repeated pattern. In this case, Entity Mode is more optimized since it carries the
   file location in band. Also, Entity Mode can be used to deliver
   a file or part of the file using HTTP Partial Content response headers.</t>
      </section>
      <section anchor="sect-9.2" numbered="true" toc="include" removeInRFC="false" pn="section-9.2">
        <name slugifiedName="name-file-mode-optimizations">File Mode Optimizations</name>
        <t indent="0" pn="section-9.2-1">
   In File Mode, the delivery object represents an Application Object. This
   mode replicates FLUTE as defined in RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/> but with the ability to send static and pre-known file
   metadata out of band.</t>
        <t indent="0" pn="section-9.2-2">
   In FLUTE, FDT-Instances are delivered in band and need to be generated and
   delivered in real time if objects are generated in real time at the
   sender. These FDT-Instances have some differences as compared to the FDT
   specified in <xref target="RFC6726" sectionFormat="of" section="3.4.2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6726#section-3.4.2" derivedContent="RFC6726"/> and Section 7.2.10 of MBMS
   <xref target="MBMS" format="default" sectionFormat="of" derivedContent="MBMS"/>. The key difference is that besides separated delivery of file
   metadata from the delivery object it describes, the FDT functionality in
   ROUTE may be extended by additional file metadata and rules that enable the
   receiver to generate the Content-Location attribute of the File element of
   the FDT, on the fly. This is done by using information in both the
   extensions to the FDT and the LCT header. The combination of pre-delivery
   of static file metadata and receiver self generation of dynamic file
   metadata avoids the necessity of continuously sending the FDT-Instances for
   real-time objects. Such modified FDT functionality in ROUTE is referred to
   as the Extended FDT.</t>
      </section>
      <section anchor="sect-9.3" numbered="true" toc="include" removeInRFC="false" pn="section-9.3">
        <name slugifiedName="name-in-band-signaling-of-object">In-Band Signaling of Object Transfer Length</name>
        <t indent="0" pn="section-9.3-1">
   As an extension to FLUTE, ROUTE allows for using EXT_TOL LCT header
   extension with 24 bits or, if required, 48 bits to signal the Transfer
   Length directly within the ROUTE packet.</t>
        <t indent="0" pn="section-9.3-2">
   The transport object length can also be determined without the use of
   EXT_TOL by examining the LCT packet with the Close Object flag (B).
   However, if this packet is lost, then the EXT_TOL information can be
   used by the receiver to determine the transport object length.</t>
        <t indent="0" pn="section-9.3-3">
   Applications using ROUTE for delivery of low-latency streaming content may
   make use of this feature for sender-end latency optimizations: the sender
   does not have to wait for the completion of the packaging of a whole
   Application Object to find its Transfer Length to be included in the FDT
   before the sending can start.  Rather, partially encoded data can already
   be started to be sent via the ROUTE sender. As the time approaches when the
   encoding of the Application Object is nearing completion, and the length of
   the object becomes known (e.g., the time of writing the last CMAF Chunk of
   a DASH segment), only then the sender can signal the object length using
   the EXT TOL LCT header. For example, for a 2-second DASH segment with
   100-millisecond chunks, it may result in saving up to 1.9 second latency at
   the sending end.</t>
      </section>
      <section anchor="sect-9.4" numbered="true" toc="include" removeInRFC="false" pn="section-9.4">
        <name slugifiedName="name-repair-protocol-concepts">Repair Protocol Concepts</name>
        <t indent="0" pn="section-9.4-1">
   The ROUTE repair protocol is FEC-based and is enabled as an additional
   layer between the transport layer (e.g., UDP) and the object delivery layer
   protocol. The FEC reuses concepts of the FEC Framework defined in RFC 6363
   <xref target="RFC6363" format="default" sectionFormat="of" derivedContent="RFC6363"/>, but in contrast to the FEC
   Framework in RFC 6363 <xref target="RFC6363" format="default" sectionFormat="of" derivedContent="RFC6363"/>, the ROUTE
   repair protocol does not protect packets but instead protects delivery
   objects as delivered in the source protocol. In addition, as an extension
   to FLUTE, it supports the protection of multiple objects in one source
   block which is in alignment with the FEC Framework as defined in RFC 6363
   <xref target="RFC6363" format="default" sectionFormat="of" derivedContent="RFC6363"/>. Each FEC source block may
   consist of parts of a delivery object, as a single delivery object (similar
   to FLUTE) or multiple delivery objects that are bundled prior to FEC
   protection.  ROUTE FEC makes use of FEC schemes in a similar way as those
   defined in RFC 5052 <xref target="RFC5052" format="default" sectionFormat="of" derivedContent="RFC5052"/> and uses the
   terminology of that document. The FEC scheme defines the FEC encoding and
   decoding as well as the protocol fields and procedures used to identify
   packet payload data in the context of the FEC scheme.</t>
        <t indent="0" pn="section-9.4-2">
   In ROUTE, all packets are LCT packets as defined in RFC 5651
   <xref target="RFC5651" format="default" sectionFormat="of" derivedContent="RFC5651"/>. Source and repair packets may be distinguished by:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-9.4-3">
          <li pn="section-9.4-3.1">Different ROUTE sessions, i.e., they are carried on different
     UDP/IP port combinations.</li>
          <li pn="section-9.4-3.2">Different LCT channels, i.e., they use different TSI values in the
     LCT header.</li>
          <li pn="section-9.4-3.3">The most significant PSI bit in the LCT, if carried in the same LCT
     channel. This mode of operation is mostly suitable for FLUTE-compatible
     deployments.</li>
        </ul>
      </section>
    </section>
    <section anchor="sect-10" numbered="true" toc="include" removeInRFC="false" pn="section-10">
      <name slugifiedName="name-interoperability-chart">Interoperability Chart</name>
      <t indent="0" pn="section-10-1">
   As noted in prevision sections, ATSC-ROUTE <xref target="ATSCA331" format="default" sectionFormat="of" derivedContent="ATSCA331"/> and DVB-MABR
   <xref target="DVBMABR" format="default" sectionFormat="of" derivedContent="DVBMABR"/> are considered services using this document that constrain
   specific features as well as add new ones. In this context, the
   following table is an informative comparison of the interoperability
   of ROUTE as specified in this document with ATSC-ROUTE
   <xref target="ATSCA331" format="default" sectionFormat="of" derivedContent="ATSCA331"/> and DVB-MABR <xref target="DVBMABR" format="default" sectionFormat="of" derivedContent="DVBMABR"/>:</t>
      <table anchor="interoperability" align="center" pn="table-3">
        <name slugifiedName="name-interoperability-chart-2">Interoperability Chart</name>
        <thead>
          <tr>
            <th align="left" rowspan="1" colspan="1">Element</th>
            <th align="left" rowspan="1" colspan="1">ATSC-ROUTE</th>
            <th align="left" rowspan="1" colspan="1">This Document</th>
            <th align="left" rowspan="1" colspan="1">DVB-MABR</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left" rowspan="2" colspan="1">LCT header field</td>
            <td align="left" rowspan="1" colspan="1">PSI LSB set to 0 for Source Flow</td>
            <td align="left" rowspan="1" colspan="1">Not defined</td>
            <td align="left" rowspan="1" colspan="1">Set to 1 for Source Flow for CMAF Random Access chunk</td>
          </tr>
          <tr>
            <td align="left" rowspan="1" colspan="1">CCI may be set to 0</td>
            <td align="left" rowspan="1" colspan="2">CCI may be set to EPT for Source Flow</td>
          </tr>
          <tr>
            <td align="left" rowspan="2" colspan="1">LCT header extensions</td>
            <td align="left" rowspan="1" colspan="1">EXT_ROUTE_​PRESENTATION_TIME Header used for Media Delivery Event (MDE) mode</td>
            <td align="left" rowspan="1" colspan="1">Not defined; may be added by a profile.</td>
            <td align="left" rowspan="1" colspan="1">Shall not be used.</td>
          </tr>
          <tr>
            <td align="left" rowspan="1" colspan="1">EXT_TIME Header linked to MDE mode in Annex A.3.7.2 <xref target="ATSCA331" format="default" sectionFormat="of" derivedContent="ATSCA331"/></td>
            <td align="left" rowspan="1" colspan="2">EXT_TIME Header may be used regardless (for FDT-Instance@Expires calculation)</td>
          </tr>
          <tr>
            <td align="left" rowspan="1" colspan="1">Codepoints</td>
            <td align="left" colspan="1" rowspan="1">Full set</td>
            <td align="left" colspan="1" rowspan="1">Does not specify range 11 - 255 (leaves to profiles)</td>
            <td align="left" colspan="1" rowspan="1">Restricted to 5 - 9</td>
          </tr>
          <tr>
            <td align="left" rowspan="1" colspan="1">Session metadata</td>
            <td align="left" colspan="1" rowspan="1">Full set</td>
            <td align="left" colspan="1" rowspan="1">Only defines a small subset of data necessary for setting up Source and                                                
      Repair Flows. Does not define format or encoding of data except if data is                                                              
      integral/alphanumerical. Leaves rest to profiles.</td>
            <td align="left" colspan="1" rowspan="1">Reuses A/331 metadata, duplicated from its own Service signaling.</td>
          </tr>
          <tr>
            <td align="left" rowspan="2" colspan="1">Extended FDT</td>
            <td align="left" colspan="1" rowspan="1">Instance shall not be sent with Source Flow</td>
            <td align="left" colspan="1" rowspan="1">Not restricted, may be restricted by a profile.</td>
            <td align="left" colspan="1" rowspan="1">Instance shall not be sent with Source Flow</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">No restriction</td>
            <td align="center" rowspan="1" colspan="2">Only allowed in File Mode</td>
          </tr>
          <tr>
            <td align="left" rowspan="1" colspan="1">Delivery Object Mode</td>
            <td align="center" rowspan="1" colspan="2">File, Entity, Signed/unsigned package</td>
            <td align="left" colspan="1" rowspan="1">Signed/unsigned package not allowed</td>
          </tr>
          <tr>
            <td align="left" rowspan="1" colspan="1">Sender operation: Packetization</td>
            <td align="left" colspan="1" rowspan="1">Defined for DASH segment</td>
            <td align="center" colspan="2" rowspan="1">Defined for DASH segment and CMAF Chunks                                                                     
    </td>
          </tr>
          <tr>
            <td align="left" rowspan="2" colspan="1">Receiver object recovery</td>
            <td align="left" colspan="1" rowspan="1">Object handed to application upon complete reception</td>
            <td align="center" rowspan="1" colspan="2">Object may be handed before completion if MPD@availabilityTimeOffset signaled</td>
          </tr>
          <tr>
            <td align="center" colspan="1" rowspan="1">-</td>
            <td align="center" colspan="2" rowspan="1">Fast Stream acquisition guidelines provided</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section anchor="sect-11" numbered="true" toc="include" removeInRFC="false" pn="section-11">
      <name slugifiedName="name-security-and-privacy-consid">Security and Privacy Considerations</name>
      <section anchor="sect-11.1" numbered="true" toc="include" removeInRFC="false" pn="section-11.1">
        <name slugifiedName="name-security-considerations">Security Considerations</name>
        <t indent="0" pn="section-11.1-1">
   As noted in <xref target="sect-9" format="default" sectionFormat="of" derivedContent="Section 9"/>, ROUTE is aligned with
   FLUTE as specified in RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>
   and only diverges in certain signaling optimizations, especially for the
   real-time object delivery case. Hence, most of the security considerations
   documented in RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/> for the
   data flow itself, the session metadata (session control parameters in RFC
   6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>), and the associated
   building blocks apply directly to ROUTE as elaborated in the following
   along with some additional considerations.</t>
        <t indent="0" pn="section-11.1-2">
   Both encryption and integrity protection applied either on file or
   packet level, as recommended in the file corruption considerations of RFC
   6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>, <bcp14>SHOULD</bcp14> be used for ROUTE. Additionally, RFC 3740
   <xref target="RFC3740" format="default" sectionFormat="of" derivedContent="RFC3740"/> documents multicast security architecture in great detail
   with clear security recommendations that <bcp14>SHOULD</bcp14> be followed.</t>
        <t indent="0" pn="section-11.1-3">
   When ROUTE is carried over UDP and a reverse channel from receiver to
   sender is available, the security mechanisms provided in RFC 9147
   <xref target="RFC9147" format="default" sectionFormat="of" derivedContent="RFC9147"/> <bcp14>SHOULD</bcp14> be applied.</t>
        <t indent="0" pn="section-11.1-4">
   In regard to considerations for attacks against session description, this
   document does not specify the semantics or mechanism of delivery of session
   metadata, though the same threats apply for service using ROUTE as
   well. Hence, a service using ROUTE <bcp14>SHOULD</bcp14> take these threats
   into consideration and address them appropriately following the guidelines
   provided by RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>. Additionally, to the recommendations of RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/>, for Internet connected devices,
   services <bcp14>SHOULD</bcp14> enable clients to access the session
   description information using HTTPS with customary
   authentication/authorization, instead of sending this data via
   multicast/broadcast, since considerable security work has been done already
   in this unicast domain, which can enable highly secure access of session
   description data. Accessing via unicast, however, will have different privacy
   considerations, noted in <xref target="sect-11.2" format="default" sectionFormat="of" derivedContent="Section 11.2"/>. Note
   that in general the multicast/broadcast stream is delayed with respect to
   the unicast stream.  Therefore, the session description protocol
   <bcp14>SHOULD</bcp14> be time synchronized with the broadcast stream,
   particularly if the session description contains security-related
   information.</t>
        <t indent="0" pn="section-11.1-5">
   In regard to FDT, there is one key difference for File Mode when using File
   Template in EFDT, which avoids repeated sending of FDT-Instances and hence,
   the corresponding threats noted in RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/> do not apply directly to ROUTE in this case. The threat,
   however, is shifted to the ALC/LCT headers, since they carry the additional
   signaling that enables determining Content-Location and
   File@Transfer-Length in this case. Hence, integrity protection
   recommendations of ALC/LCT header <bcp14>SHOULD</bcp14> be considered with
   higher emphasis in this case for ROUTE.</t>
        <t indent="0" pn="section-11.1-6">
   Finally, attacks against the congestion control building block for
   the case of ROUTE can impact the optional fast stream acquisition
   specified in <xref target="sect-6.2" format="default" sectionFormat="of" derivedContent="Section 6.2"/>. Receivers <bcp14>SHOULD</bcp14> have robustness against
   timestamp values that are suspicious, e.g., by comparing the signaled
   time in the LCT headers with the approximate time signaled by the
   MPD, and <bcp14>SHOULD</bcp14> discard outlying values. Additionally, receivers <bcp14>MUST</bcp14>
   adhere to the expiry timelines as specified in <xref target="sect-6" format="default" sectionFormat="of" derivedContent="Section 6"/>. Integrity
   protection mechanisms documented in RFC 6726 <xref target="RFC6726" format="default" sectionFormat="of" derivedContent="RFC6726"/> <bcp14>SHOULD</bcp14> be used
   to address this threat.</t>
      </section>
      <section anchor="sect-11.2" numbered="true" toc="include" removeInRFC="false" pn="section-11.2">
        <name slugifiedName="name-privacy-considerations">Privacy Considerations</name>
        <t indent="0" pn="section-11.2-1">
   Encryption mechanisms recommended for security considerations in
   <xref target="sect-11.1" format="default" sectionFormat="of" derivedContent="Section 11.1"/> <bcp14>SHOULD</bcp14> also be applied to enable privacy and protection
   from snooping attacks.</t>
        <t indent="0" pn="section-11.2-2">
   Since this protocol is primarily targeted for IP multicast/broadcast
   environments where the end user is mostly listening, identity
   protection and user data retention considerations are more protected
   than in the unicast case. Best practices for enabling privacy on IP
   multicast/broadcast <bcp14>SHOULD</bcp14> be applied by the operators, e.g.,
   "<xref target="RFC8932" format="title" sectionFormat="of" derivedContent="Recommendations for DNS Privacy Service Operators"/>" in RFC 8932
   <xref target="RFC8932" format="default" sectionFormat="of" derivedContent="RFC8932"/>.</t>
        <t indent="0" pn="section-11.2-3">
   However, if clients access session description information via HTTPS,
   the same privacy considerations and solutions <bcp14>SHALL</bcp14> apply to this
   access as for regular HTTPS communication, an area that is very well
   studied and the concepts of which are being integrated directly into
   newer transport protocols such as IETF QUIC <xref target="RFC9000" format="default" sectionFormat="of" derivedContent="RFC9000"/> enabling HTTP/3
   <xref target="I-D.ietf-quic-http" format="default" sectionFormat="of" derivedContent="HTTP3"/>. Hence, such newer protocols <bcp14>SHOULD</bcp14> be used to foster privacy.</t>
        <t indent="0" pn="section-11.2-4">
   Note that streaming services <bcp14>MAY</bcp14> contain content that may only be
   accessed via DRM (digital rights management) systems.  DRM systems
   can prevent unauthorized access to content delivered via ROUTE.</t>
      </section>
    </section>
    <section anchor="sect-12" numbered="true" toc="include" removeInRFC="false" pn="section-12">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-12-1">This document has no IANA actions.
      </t>
    </section>
  </middle>
  <back>
    <displayreference target="I-D.ietf-quic-http" to="HTTP3"/>
    <references pn="section-13">
      <name slugifiedName="name-references">References</name>
      <references pn="section-13.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="ATSCA331" quoteTitle="true" derivedAnchor="ATSCA331">
          <front>
            <title>Signaling, Delivery, Synchronization, and Error Protection</title>
            <author>
              <organization showOnFrontPage="true">Advanced Television Systems Committee</organization>
            </author>
            <date month="March" year="2022"/>
          </front>
          <seriesInfo name="ATSC Standard" value="A/331:2022-03"/>
        </reference>
        <reference anchor="RFC1952" target="https://www.rfc-editor.org/info/rfc1952" quoteTitle="true" derivedAnchor="RFC1952">
          <front>
            <title>GZIP file format specification version 4.3</title>
            <author initials="P." surname="Deutsch" fullname="P. Deutsch">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1996" month="May"/>
            <abstract>
              <t indent="0">This specification defines a lossless compressed data format that is compatible with the widely used GZIP utility.  This memo provides information for the Internet community.  This memo does not specify an Internet standard of any kind.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1952"/>
          <seriesInfo name="DOI" value="10.17487/RFC1952"/>
        </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 initials="S." surname="Bradner" fullname="S. Bradner">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1997" month="March"/>
            <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="RFC2557" target="https://www.rfc-editor.org/info/rfc2557" quoteTitle="true" derivedAnchor="RFC2557">
          <front>
            <title>MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
            <author initials="J." surname="Palme" fullname="J. Palme">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Hopmann" fullname="A. Hopmann">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="N." surname="Shelness" fullname="N. Shelness">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1999" month="March"/>
            <abstract>
              <t indent="0">This document a) defines the use of a MIME multipart/related structure to aggregate a text/html root resource and the subsidiary resources it references, and b) specifies a MIME content-header (Content-Location) that allow URIs in a multipart/related text/html root body part to reference subsidiary resources in other body parts of the same multipart/related structure.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2557"/>
          <seriesInfo name="DOI" value="10.17487/RFC2557"/>
        </reference>
        <reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986" quoteTitle="true" derivedAnchor="RFC3986">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Fielding" fullname="R. Fielding">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L." surname="Masinter" fullname="L. Masinter">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2005" month="January"/>
            <abstract>
              <t indent="0">A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource.  This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet.  The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier.  This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>
        <reference anchor="RFC5052" target="https://www.rfc-editor.org/info/rfc5052" quoteTitle="true" derivedAnchor="RFC5052">
          <front>
            <title>Forward Error Correction (FEC) Building Block</title>
            <author initials="M." surname="Watson" fullname="M. Watson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Luby" fullname="M. Luby">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L." surname="Vicisano" fullname="L. Vicisano">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2007" month="August"/>
            <abstract>
              <t indent="0">This document describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for bulk data transfer over IP multicast.  This document defines a framework for the definition of the information that needs to be communicated in order to use an FEC code for bulk data transfer, in addition to the encoded data itself, and for definition of formats and codes for communication of that information.  Both information communicated with the encoded data itself and information that needs to be communicated 'out-of-band' are considered.  The procedures for specifying new FEC codes, defining the information communication requirements associated with those codes and registering them with the Internet Assigned Numbers Authority (IANA) are also described.  The requirements on Content Delivery Protocols that wish to use FEC codes defined within this framework are also defined.  The companion document titled "The Use of Forward Error Correction (FEC) in Reliable Multicast" describes some applications of FEC codes for delivering content. This document obsoletes RFC 3452.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5052"/>
          <seriesInfo name="DOI" value="10.17487/RFC5052"/>
        </reference>
        <reference anchor="RFC5445" target="https://www.rfc-editor.org/info/rfc5445" quoteTitle="true" derivedAnchor="RFC5445">
          <front>
            <title>Basic Forward Error Correction (FEC) Schemes</title>
            <author initials="M." surname="Watson" fullname="M. Watson">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2009" month="March"/>
            <abstract>
              <t indent="0">This document provides Forward Error Correction (FEC) Scheme specifications according to the Reliable Multicast Transport (RMT) FEC building block for the Compact No-Code FEC Scheme, the Small Block, Large Block, and Expandable FEC Scheme, the Small Block Systematic FEC Scheme, and the Compact FEC Scheme.  This document obsoletes RFC 3695 and assumes responsibility for the FEC Schemes defined in RFC 3452.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5445"/>
          <seriesInfo name="DOI" value="10.17487/RFC5445"/>
        </reference>
        <reference anchor="RFC5651" target="https://www.rfc-editor.org/info/rfc5651" quoteTitle="true" derivedAnchor="RFC5651">
          <front>
            <title>Layered Coding Transport (LCT) Building Block</title>
            <author initials="M." surname="Luby" fullname="M. Luby">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Watson" fullname="M. Watson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L." surname="Vicisano" fullname="L. Vicisano">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2009" month="October"/>
            <abstract>
              <t indent="0">The Layered Coding Transport (LCT) Building Block provides transport level support for reliable content delivery and stream delivery protocols.  LCT is specifically designed to support protocols using IP multicast, but it also provides support to protocols that use unicast.  LCT is compatible with congestion control that provides multiple rate delivery to receivers and is also compatible with coding techniques that provide reliable delivery of content.  This document obsoletes RFC 3451.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5651"/>
          <seriesInfo name="DOI" value="10.17487/RFC5651"/>
        </reference>
        <reference anchor="RFC5775" target="https://www.rfc-editor.org/info/rfc5775" quoteTitle="true" derivedAnchor="RFC5775">
          <front>
            <title>Asynchronous Layered Coding (ALC) Protocol Instantiation</title>
            <author initials="M." surname="Luby" fullname="M. Luby">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Watson" fullname="M. Watson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L." surname="Vicisano" fullname="L. Vicisano">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2010" month="April"/>
            <abstract>
              <t indent="0">This document describes the Asynchronous Layered Coding (ALC) protocol, a massively scalable reliable content delivery protocol. Asynchronous Layered Coding combines the Layered Coding Transport (LCT) building block, a multiple rate congestion control building block and the Forward Error Correction (FEC) building block to provide congestion controlled reliable asynchronous delivery of content to an unlimited number of concurrent receivers from a single sender.  This document obsoletes RFC 3450.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5775"/>
          <seriesInfo name="DOI" value="10.17487/RFC5775"/>
        </reference>
        <reference anchor="RFC6330" target="https://www.rfc-editor.org/info/rfc6330" quoteTitle="true" derivedAnchor="RFC6330">
          <front>
            <title>RaptorQ Forward Error Correction Scheme for Object Delivery</title>
            <author initials="M." surname="Luby" fullname="M. Luby">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Shokrollahi" fullname="A. Shokrollahi">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Watson" fullname="M. Watson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="T." surname="Stockhammer" fullname="T. Stockhammer">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L." surname="Minder" fullname="L. Minder">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2011" month="August"/>
            <abstract>
              <t indent="0">This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 6, for the RaptorQ FEC code and its application to reliable delivery of data objects.</t>
              <t indent="0">RaptorQ codes are a new family of codes that provide superior flexibility, support for larger source block sizes, and better coding efficiency than Raptor codes in RFC 5053.  RaptorQ is also a fountain code, i.e., as many encoding symbols as needed can be generated on the fly by the encoder from the source symbols of a source block of data.  The decoder is able to recover the source block from almost any set of encoding symbols of sufficient cardinality -- in most cases, a set of cardinality equal to the number of source symbols is sufficient; in rare cases, a set of cardinality slightly more than the number of source symbols is required.</t>
              <t indent="0">The RaptorQ code described here is a systematic code, meaning that all the source symbols are among the encoding symbols that can be generated.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6330"/>
          <seriesInfo name="DOI" value="10.17487/RFC6330"/>
        </reference>
        <reference anchor="RFC6363" target="https://www.rfc-editor.org/info/rfc6363" quoteTitle="true" derivedAnchor="RFC6363">
          <front>
            <title>Forward Error Correction (FEC) Framework</title>
            <author initials="M." surname="Watson" fullname="M. Watson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Begen" fullname="A. Begen">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="V." surname="Roca" fullname="V. Roca">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2011" month="October"/>
            <abstract>
              <t indent="0">This document describes a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss.  The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media.  This framework can be used to define Content Delivery Protocols that provide FEC for streaming media delivery or other packet flows.  Content Delivery Protocols defined using this framework can support any FEC scheme (and associated FEC codes) that is compliant with various requirements defined in this document. Thus, Content Delivery Protocols can be defined that are not specific to a particular FEC scheme, and FEC schemes can be defined that are not specific to a particular Content Delivery Protocol.   [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6363"/>
          <seriesInfo name="DOI" value="10.17487/RFC6363"/>
        </reference>
        <reference anchor="RFC6726" target="https://www.rfc-editor.org/info/rfc6726" quoteTitle="true" derivedAnchor="RFC6726">
          <front>
            <title>FLUTE - File Delivery over Unidirectional Transport</title>
            <author initials="T." surname="Paila" fullname="T. Paila">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Walsh" fullname="R. Walsh">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Luby" fullname="M. Luby">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="V." surname="Roca" fullname="V. Roca">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Lehtonen" fullname="R. Lehtonen">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2012" month="November"/>
            <abstract>
              <t indent="0">This document defines File Delivery over Unidirectional Transport (FLUTE), a protocol for the unidirectional delivery of files over the Internet, which is particularly suited to multicast networks.  The specification builds on Asynchronous Layered Coding, the base protocol designed for massively scalable multicast distribution. This document obsoletes RFC 3926.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6726"/>
          <seriesInfo name="DOI" value="10.17487/RFC6726"/>
        </reference>
        <reference anchor="RFC7231" target="https://www.rfc-editor.org/info/rfc7231" quoteTitle="true" derivedAnchor="RFC7231">
          <front>
            <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
            <author initials="R." surname="Fielding" fullname="R. Fielding" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Reschke" fullname="J. Reschke" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2014" month="June"/>
            <abstract>
              <t indent="0">The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems.  This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7231"/>
          <seriesInfo name="DOI" value="10.17487/RFC7231"/>
        </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 initials="B." surname="Leiba" fullname="B. Leiba">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2017" month="May"/>
            <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="RFC8551" target="https://www.rfc-editor.org/info/rfc8551" quoteTitle="true" derivedAnchor="RFC8551">
          <front>
            <title>Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification</title>
            <author initials="J." surname="Schaad" fullname="J. Schaad">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Ramsdell" fullname="B. Ramsdell">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="S." surname="Turner" fullname="S. Turner">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2019" month="April"/>
            <abstract>
              <t indent="0">This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 4.0.  S/MIME provides a consistent way to send and receive secure MIME data.  Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality.  Compression can be used to reduce data size.  This document obsoletes RFC 5751.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8551"/>
          <seriesInfo name="DOI" value="10.17487/RFC8551"/>
        </reference>
      </references>
      <references pn="section-13.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="CMAF" target="https://www.iso.org/standard/71975.html" quoteTitle="true" derivedAnchor="CMAF">
          <front>
            <title>Information technology -- Multimedia application format (MPEG-A) -- Part 19: Common media application format (CMAF) for segmented media</title>
            <author>
              <organization showOnFrontPage="true">International Organization for Standardization</organization>
            </author>
            <date month="January" year="2018"/>
          </front>
          <seriesInfo name="ISO/IEC FDIS" value="23000-19"/>
          <refcontent>First edition</refcontent>
        </reference>
        <reference anchor="DASH" target="https://www.iso.org/standard/79329.html" quoteTitle="true" derivedAnchor="DASH">
          <front>
            <title>Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media presentation description and segment formats</title>
            <author>
              <organization showOnFrontPage="true">International Organization for Standardization</organization>
            </author>
            <date month="December" year="2019"/>
          </front>
          <seriesInfo name="ISO/IEC" value="23009-1:2019"/>
          <refcontent>Fourth edition</refcontent>
        </reference>
        <reference anchor="DVBMABR" quoteTitle="true" derivedAnchor="DVBMABR">
          <front>
            <title>Digital Video Broadcasting (DVB); Adaptive media streaming over IP multicast</title>
            <author>
              <organization showOnFrontPage="true">ETSI</organization>
            </author>
            <date month="November" year="2020"/>
          </front>
          <seriesInfo name="ETSI TS" value="103 769"/>
          <refcontent>version 1.1.1</refcontent>
        </reference>
        <reference anchor="I-D.ietf-quic-http" quoteTitle="true" target="https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-34" derivedAnchor="HTTP3">
          <front>
            <title>Hypertext Transfer Protocol Version 3 (HTTP/3)</title>
            <author fullname="Mike Bishop" role="editor"> </author>
            <date month="February" day="2" year="2021"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-quic-http-34"/>
          <format type="TXT" target="https://www.ietf.org/archive/id/draft-ietf-quic-http-34.txt"/>
          <refcontent>Work in Progress</refcontent>
        </reference>
        <reference anchor="MBMS" quoteTitle="true" derivedAnchor="MBMS">
          <front>
            <title>Universal Mobile Telecommunications Systems (UMTS); LTE; 5G; Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs</title>
            <author>
              <organization showOnFrontPage="true">ETSI</organization>
            </author>
            <date month="May" year="2021"/>
          </front>
          <seriesInfo name="ETSI TS" value="126 346"/>
          <refcontent>version 16.9.1</refcontent>
        </reference>
        <reference anchor="RFC3740" target="https://www.rfc-editor.org/info/rfc3740" quoteTitle="true" derivedAnchor="RFC3740">
          <front>
            <title>The Multicast Group Security Architecture</title>
            <author initials="T." surname="Hardjono" fullname="T. Hardjono">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Weis" fullname="B. Weis">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2004" month="March"/>
            <abstract>
              <t indent="0">This document provides an overview and rationale of the multicast security architecture used to secure data packets of large multicast groups.  The document begins by introducing a Multicast Security Reference Framework, and proceeds to identify the security services that may be part of a secure multicast solution.  This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3740"/>
          <seriesInfo name="DOI" value="10.17487/RFC3740"/>
        </reference>
        <reference anchor="RFC6968" target="https://www.rfc-editor.org/info/rfc6968" quoteTitle="true" derivedAnchor="RFC6968">
          <front>
            <title>FCAST: Object Delivery for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols</title>
            <author initials="V." surname="Roca" fullname="V. Roca">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Adamson" fullname="B. Adamson">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2013" month="July"/>
            <abstract>
              <t indent="0">This document introduces the FCAST reliable object (e.g., file) delivery application.  It is designed to operate either on top of the underlying Asynchronous Layered Coding (ALC) / Layered Coding Transport (LCT) reliable multicast transport protocol or the NACK-Oriented Reliable Multicast (NORM) transport protocol.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6968"/>
          <seriesInfo name="DOI" value="10.17487/RFC6968"/>
        </reference>
        <reference anchor="RFC8932" target="https://www.rfc-editor.org/info/rfc8932" quoteTitle="true" derivedAnchor="RFC8932">
          <front>
            <title>Recommendations for DNS Privacy Service Operators</title>
            <author initials="S." surname="Dickinson" fullname="S. Dickinson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Overeinder" fullname="B. Overeinder">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="van Rijswijk-Deij" fullname="R. van Rijswijk-Deij">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Mankin" fullname="A. Mankin">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2020" month="October"/>
            <abstract>
              <t indent="0">This document presents operational, policy, and security considerations for DNS recursive resolver operators who choose to offer DNS privacy services.  With these recommendations, the operator can make deliberate decisions regarding which services to provide, as well as understanding how those decisions and the alternatives impact the privacy of users. </t>
              <t indent="0">This document also presents a non-normative framework to assist writers of a Recursive operator Privacy Statement, analogous to DNS Security Extensions (DNSSEC) Policies and DNSSEC Practice Statements described in RFC 6841.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="232"/>
          <seriesInfo name="RFC" value="8932"/>
          <seriesInfo name="DOI" value="10.17487/RFC8932"/>
        </reference>
        <reference anchor="RFC9000" target="https://www.rfc-editor.org/info/rfc9000" quoteTitle="true" derivedAnchor="RFC9000">
          <front>
            <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
            <author initials="J." surname="Iyengar" fullname="J. Iyengar" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Thomson" fullname="M. Thomson" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2021" month="May"/>
            <abstract>
              <t indent="0">This document defines the core of the QUIC transport protocol.  QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances.  Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9000"/>
          <seriesInfo name="DOI" value="10.17487/RFC9000"/>
        </reference>
        <reference anchor="RFC9147" target="https://www.rfc-editor.org/info/rfc9147" quoteTitle="true" derivedAnchor="RFC9147">
          <front>
            <title>The Datagram Transport Layer Security (DTLS) Protocol Version 1.3</title>
            <author initials="E." surname="Rescorla" fullname="E. Rescorla">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="H." surname="Tschofenig" fullname="H. Tschofenig">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="N." surname="Modadugu" fullname="N. Modadugu">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2022" month="April"/>
            <abstract>
              <t indent="0">This document specifies version 1.3 of the Datagram Transport Layer Security (DTLS) protocol. DTLS 1.3 allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
              <t indent="0">The DTLS 1.3 protocol is based on the Transport Layer Security (TLS) 1.3 protocol and provides equivalent security guarantees with the exception of order protection / non-replayability.  Datagram semantics of the underlying transport are preserved by the DTLS protocol.</t>
              <t indent="0">This document obsoletes RFC 6347.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9147"/>
          <seriesInfo name="DOI" value="10.17487/RFC9147"/>
        </reference>
      </references>
    </references>
    <section anchor="sect-14" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1">
   As outlined in the introduction and in ROUTE concepts in <xref target="sect-9" format="default" sectionFormat="of" derivedContent="Section 9"/>,
   the concepts specified in this document are the culmination of the
   collaborative work of several experts and organizations over the
   years. The authors would especially like to acknowledge the work and
   efforts of the following people and organizations to help realize the
   technologies described in this document (in no specific order): <contact fullname="Mike    Luby"/>, <contact fullname="Kent Walker"/>, <contact fullname="Charles Lo"/>, and other colleagues from Qualcomm
   Incorporated, LG Electronics, Nomor Research, Sony, and BBC R&amp;D.</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="W" surname="Zia" fullname="Waqar Zia">
        <organization showOnFrontPage="true">Qualcomm CDMA Technologies GmbH</organization>
        <address>
          <postal>
            <street>Anzinger Str. 13</street>
            <city>Munich</city>
            <region/>
            <code>81671</code>
            <country>Germany</country>
          </postal>
          <phone/>
          <email>wzia@qti.qualcomm.com</email>
          <uri/>
        </address>
      </author>
      <author initials="T" surname="Stockhammer" fullname="Thomas Stockhammer">
        <organization showOnFrontPage="true">Qualcomm CDMA Technologies GmbH</organization>
        <address>
          <postal>
            <street>Anzinger Str. 13</street>
            <city>Munich</city>
            <region/>
            <code>81671</code>
            <country>Germany</country>
          </postal>
          <phone/>
          <email>tsto@qti.qualcomm.com</email>
          <uri/>
        </address>
      </author>
      <author initials="L" surname="Chaponniere" fullname="Lenaig Chaponniere">
        <organization showOnFrontPage="true">Qualcomm Technologies Inc.</organization>
        <address>
          <postal>
            <street>5775 Morehouse Drive</street>
            <city>San Diego</city>
            <region>CA</region>
            <code>92121</code>
            <country>United States of America</country>
          </postal>
          <phone/>
          <email>lguellec@qti.qualcomm.com</email>
          <uri/>
        </address>
      </author>
      <author initials="G" surname="Mandyam" fullname="Giridhar Mandyam">
        <organization showOnFrontPage="true">Qualcomm Technologies Inc.</organization>
        <address>
          <postal>
            <street>5775 Morehouse Drive</street>
            <city>San Diego</city>
            <region>CA</region>
            <code>92121</code>
            <country>United States of America</country>
          </postal>
          <phone/>
          <email>mandyam@qti.qualcomm.com</email>
          <uri/>
        </address>
      </author>
      <author initials="M" surname="Luby" fullname="Michael Luby">
        <organization showOnFrontPage="true">BitRipple, Inc.</organization>
        <address>
          <postal>
            <street>1133 Miller Ave</street>
            <city>Berkeley</city>
            <region>CA</region>
            <code>94708</code>
            <country>United States of America</country>
          </postal>
          <phone/>
          <email>luby@bitripple.com</email>
          <uri/>
        </address>
      </author>
    </section>
  </back>
</rfc>
