<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" ipr="trust200902" docName="draft-ietf-avtcore-rtp-payload-registry-05" number="9751" category="std" consensus="true" submissionType="IETF" obsoletes="" updates="8088" symRefs="true" sortRefs="true" tocInclude="true" xml:lang="en" prepTime="2025-03-18T23:44:02" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-payload-registry-05" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9751" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="Closing the RTP Payload Format Registry">Closing the RTP Payload Format Media Types Registry</title>
    <seriesInfo name="RFC" value="9751" stream="IETF"/>
    <author initials="M." surname="Westerlund" fullname="Magnus Westerlund">
      <organization showOnFrontPage="true">Ericsson</organization>
      <address>
        <email>magnus.westerlund@ericsson.com</email>
      </address>
    </author>
    <date month="03" year="2025"/>
    <area>WIT</area>
    <workgroup>avtcore</workgroup>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">
  The working group process and the authors of RTP payload formats have sometimes
  failed to ensure that the media types are registered in the IANA 
  "RTP Payload Format Media Types" registry as
  recommended by RFC 8088. To simplify the process and rely only on
  the "Media Types" registry, this document closes the RTP payload-
  specific registry. In addition, it updates the instruction in RFC
  8088 to reflect this change.
      </t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9751" 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) 2025 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" 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>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" 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-update-to-how-to-write-an-r">Update to How to Write an RTP Payload Format</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" keepWithNext="true" 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-iana-considerations">IANA Considerations</xref></t>
          </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-security-considerations">Security Considerations</xref></t>
          </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-references">References</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-normative-references">Normative References</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-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.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.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-address">Author's Address</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">Sometimes, authors defining new Real-time Transport
   Protocol (RTP) payload formats forgot to specify registration
   of the format's media type in the "RTP Payload Format
   Media Types" registry <xref target="RTP-FORMATS" format="default" sectionFormat="of" derivedContent="RTP-FORMATS"/> as recommended by <xref target="RFC8088" format="default" sectionFormat="of" derivedContent="RFC8088"/>. In practice, this has no real impact. This registry
is not used for any purpose other than to track which media types actually have
RTP payload formats, which can be done through other means. </t>
      <t indent="0" pn="section-1-2">  It is required that media types be registered in the "Media Types" registry
  <xref target="MEDIA-TYPES" format="default" sectionFormat="of" derivedContent="MEDIA-TYPES"/> to identify the format in various signalling usages, 
  avoid collisions, and reference the defining specifications.</t>
      <t indent="0" pn="section-1-3">To resolve this situation, this document: </t>
      <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-1-4">
        <li pn="section-1-4.1"> updates the "RTP Payload Format Media Types" registry to
      include known RTP payload formats at the time of writing,</li>
        <li pn="section-1-4.2"> closes the "RTP Payload Format Media Types" registry to future
      registrations and lists this RFC as a reference, and </li>
        <li pn="section-1-4.3"> removes from <xref target="RFC8088" format="default" sectionFormat="of" derivedContent="RFC8088"/> the instruction to register RTP payload
      formats in the "RTP Payload Format Media Types" registry.</li>
      </ul>
      <t indent="0" pn="section-1-5">The origins of the "RTP Payload Format Media Types" registry, as referenced in
<xref target="RTP-FORMATS" format="default" sectionFormat="of" derivedContent="RTP-FORMATS"/>, are unclear. The registry cites <xref target="RFC4855" format="default" sectionFormat="of" derivedContent="RFC4855"/> as providing the
instructions for its maintenance. However, upon reviewing RFC 4855, no text has
been found that defines the registry's purpose and operational rules. Further
attempts to trace the registry's creation have failed to uncover any references
to its establishment. It is likely that the registry was created based on
email correspondence or at the request of an Area Director.
Consequently, there is no known specification for this registry that
requires updating upon its closure.</t>
    </section>
    <section anchor="update-to-how-to-write-an-rtp-payload-format" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-update-to-how-to-write-an-r">Update to How to Write an RTP Payload Format</name>
      <t indent="0" pn="section-2-1">The IANA Considerations section of "How to write an RTP Payload Format" (<xref target="RFC8088" section="7.4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8088#section-7.4" derivedContent="RFC8088"/>) mandates 
that RTP payload formats shall
be registered in the "RTP Payload Format Media Types" registry. The following paragraph is
   updated as shown below, thus removing the need for media types to be
   registered in the "RTP Payload Format Media Types" registry. Note that this
   update does not impact the rest of RFC 8088's status as an Informational RFC.</t>
      <t indent="0" pn="section-2-2">OLD:</t>
      <blockquote pn="section-2-3">Since all RTP payload formats contain a media type
      specification, they also need an IANA Considerations section.  The media
      type name must be registered, and this is done by requesting that IANA
      register that media name.  When that registration request is written, it
      shall also be requested that the media type is included under the "RTP
      Payload Format media types" sub-registry of the RTP registry
      (http://www.iana.org/assignments/rtp-parameters).</blockquote>
      <t indent="0" pn="section-2-4">NEW:</t>
      <blockquote pn="section-2-5">Since all RTP payload formats contain a media type
      specification, they also need an IANA Considerations section.  The media
      type name must be registered, and this is done by requesting that IANA
      register that media name in the "Media Types" registry
      (<eref target="https://www.iana.org/assignments/media-types/" brackets="none"/>).</blockquote>
    </section>
    <section anchor="IANA-Consideration" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-3-1">IANA has added the following RTP payload types to
the "RTP Payload Format Media Types" registry <xref target="RTP-FORMATS" format="default" sectionFormat="of" derivedContent="RTP-FORMATS"/>.</t>
      <table anchor="iana-entries" align="center" pn="table-1">
        <name slugifiedName="name-payload-types-added-to-the-">Payload Types Added to the RTP Payload Format Media Types Registry</name>
        <thead>
          <tr>
            <th align="left" colspan="1" rowspan="1">Media Type</th>
            <th align="left" colspan="1" rowspan="1">Subtype</th>
            <th align="left" colspan="1" rowspan="1">Clock Rate (Hz)</th>
            <th align="left" colspan="1" rowspan="1">Channels (audio)</th>
            <th align="left" colspan="1" rowspan="1">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left" colspan="1" rowspan="1">application</td>
            <td align="left" colspan="1" rowspan="1">flexfec</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 8627</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">audio</td>
            <td align="left" colspan="1" rowspan="1">EVRCNW</td>
            <td align="left" colspan="1" rowspan="1">16000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 6884</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">audio</td>
            <td align="left" colspan="1" rowspan="1">EVRCNW0</td>
            <td align="left" colspan="1" rowspan="1">16000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 6884</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">audio</td>
            <td align="left" colspan="1" rowspan="1">EVRCNW1</td>
            <td align="left" colspan="1" rowspan="1">16000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 6884</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">audio</td>
            <td align="left" colspan="1" rowspan="1">aptx</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 7310</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">audio</td>
            <td align="left" colspan="1" rowspan="1">opus</td>
            <td align="left" colspan="1" rowspan="1">48000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 7587</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">audio</td>
            <td align="left" colspan="1" rowspan="1">G711-0</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 7650</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">audio</td>
            <td align="left" colspan="1" rowspan="1">flexfec</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 8627</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">text</td>
            <td align="left" colspan="1" rowspan="1">flexfec</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 8627</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">text</td>
            <td align="left" colspan="1" rowspan="1">ttml+xml</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 8759</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">video</td>
            <td align="left" colspan="1" rowspan="1">VP8</td>
            <td align="left" colspan="1" rowspan="1">90000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 7741</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">video</td>
            <td align="left" colspan="1" rowspan="1">AV1</td>
            <td align="left" colspan="1" rowspan="1">90000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">
              <xref target="AV1-Media-Type" format="default" sectionFormat="of" derivedContent="AV1-Media-Type"/></td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">video</td>
            <td align="left" colspan="1" rowspan="1">HEVC</td>
            <td align="left" colspan="1" rowspan="1">90000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 7798</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">video</td>
            <td align="left" colspan="1" rowspan="1">smpte291</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 8331</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">video</td>
            <td align="left" colspan="1" rowspan="1">VVC</td>
            <td align="left" colspan="1" rowspan="1">90000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 9328</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">video</td>
            <td align="left" colspan="1" rowspan="1">EVC</td>
            <td align="left" colspan="1" rowspan="1">90000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 9584</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">video</td>
            <td align="left" colspan="1" rowspan="1">flexfec</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 8627</td>
          </tr>
        </tbody>
      </table>
      <t indent="0" pn="section-3-3">IANA has updated the following entries in the "RTP Payload Format Media Types" registry <xref target="RTP-FORMATS" format="default" sectionFormat="of" derivedContent="RTP-FORMATS"/>.</t>
      <table anchor="iana-update-entries" align="center" pn="table-2">
        <name slugifiedName="name-payload-types-updated-in-rt">Payload Types Updated in RTP Payload Format Media Types Registry</name>
        <thead>
          <tr>
            <th align="left" colspan="1" rowspan="1">Media Type</th>
            <th align="left" colspan="1" rowspan="1">Subtype</th>
            <th align="left" colspan="1" rowspan="1">Clock Rate (Hz)</th>
            <th align="left" colspan="1" rowspan="1">Channels (audio)</th>
            <th align="left" colspan="1" rowspan="1">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left" colspan="1" rowspan="1">audio</td>
            <td align="left" colspan="1" rowspan="1">MP4A-LATM</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 6416</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">video</td>
            <td align="left" colspan="1" rowspan="1">MP4V-ES</td>
            <td align="left" colspan="1" rowspan="1">90000</td>
            <td align="left" colspan="1" rowspan="1"> </td>
            <td align="left" colspan="1" rowspan="1">RFC 6416</td>
          </tr>
        </tbody>
      </table>
      <t indent="0" pn="section-3-5">IANA has also closed the "RTP Payload Format Media
      Types" registry <xref target="RTP-FORMATS" format="default" sectionFormat="of" derivedContent="RTP-FORMATS"/> to any further
      registrations. IANA added the following to the registry note:</t>
      <t indent="0" pn="section-3-6">NEW:</t>
      <blockquote pn="section-3-7">This registry has been closed; it was considered redundant
      because all RTP payload formats are part of the <eref target="https://www.iana.org/assignments/media-types" brackets="none">[Media Types registry]</eref>.
      See RFC 9751 for further details.</blockquote>
      <t indent="0" pn="section-3-8">In addition, IANA updated the note in the "RTP Payload
      Format Media Types" registry <xref target="RTP-FORMATS" format="default" sectionFormat="of" derivedContent="RTP-FORMATS"/> as 
      follows:</t>
      <t indent="0" pn="section-3-9">OLD:</t>
      <blockquote pn="section-3-10">Registration procedures and a registration template can be
      found in <xref target="RFC4855" format="default" sectionFormat="of" derivedContent="RFC4855"/>.</blockquote>
      <t indent="0" pn="section-3-11">NEW:</t>
      <blockquote pn="section-3-12">It was previously stated that registration procedures and a
      registration template can be found in <xref target="RFC4855" format="default" sectionFormat="of" derivedContent="RFC4855"/>.  As documented in RFC 9751, this is not the case.</blockquote>
    </section>
    <section anchor="Security-Considerations" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-4-1">This document has no security considerations as it defines an administrative rule change.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references" pn="section-5">
      <name slugifiedName="name-references">References</name>
      <references anchor="sec-normative-references" pn="section-5.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="AV1-Media-Type" target="https://www.iana.org/assignments/media-types/video/AV1" quoteTitle="true" derivedAnchor="AV1-Media-Type">
          <front>
            <title>video/AV1</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="MEDIA-TYPES" target="https://www.iana.org/assignments/media-types" quoteTitle="true" derivedAnchor="MEDIA-TYPES">
          <front>
            <title>Media Types</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="RFC8088" target="https://www.rfc-editor.org/info/rfc8088" quoteTitle="true" derivedAnchor="RFC8088">
          <front>
            <title>How to Write an RTP Payload Format</title>
            <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
            <date month="May" year="2017"/>
            <abstract>
              <t indent="0">This document contains information on how best to write an RTP payload format specification. It provides reading tips, design practices, and practical tips on how to produce an RTP payload format specification quickly and with good results. A template is also included with instructions.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8088"/>
          <seriesInfo name="DOI" value="10.17487/RFC8088"/>
        </reference>
        <reference anchor="RTP-FORMATS" target="https://www.iana.org/assignments/rtp-parameters" quoteTitle="true" derivedAnchor="RTP-FORMATS">
          <front>
            <title>RTP Payload Format Media Types</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
      </references>
      <references anchor="sec-informative-references" pn="section-5.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="RFC4855" target="https://www.rfc-editor.org/info/rfc4855" quoteTitle="true" derivedAnchor="RFC4855">
          <front>
            <title>Media Type Registration of RTP Payload Formats</title>
            <author fullname="S. Casner" initials="S." surname="Casner"/>
            <date month="February" year="2007"/>
            <abstract>
              <t indent="0">This document specifies the procedure to register RTP payload formats as audio, video, or other media subtype names. This is useful in a text-based format description or control protocol to identify the type of an RTP transmission. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4855"/>
          <seriesInfo name="DOI" value="10.17487/RFC4855"/>
        </reference>
      </references>
    </references>
    <section anchor="acknowledgments" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1">The author thanks <contact fullname="Jonathan Lennox"/>,
      <contact fullname="Zaheduzzaman Sarker"/>, <contact fullname="Bernard       Aboba"/>, <contact fullname="Elwyn Davies"/>, <contact fullname="Wes       Hardaker"/>, <contact fullname="Gunter Van de Velde"/>, <contact fullname="Éric Vyncke"/>, <contact fullname="Mahesh Jethanandani"/>, and
      <contact fullname="Hyunsik Yang"/> for their reviews and editorial fixes.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-address">Author's Address</name>
      <author initials="M." surname="Westerlund" fullname="Magnus Westerlund">
        <organization showOnFrontPage="true">Ericsson</organization>
        <address>
          <email>magnus.westerlund@ericsson.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
