<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" consensus="true" docName="draft-moskowitz-ipsecme-ipseckey-eddsa-09" indexInclude="true" ipr="trust200902" number="9373" prepTime="2023-03-15T14:08:02" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en">
  <link href="https://datatracker.ietf.org/doc/draft-moskowitz-ipsecme-ipseckey-eddsa-09" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9373" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="IPSECKEY EdDSA">EdDSA Value for IPSECKEY</title>
    <seriesInfo name="RFC" value="9373" stream="IETF"/>
    <author fullname="Robert Moskowitz" initials="R" surname="Moskowitz">
      <organization showOnFrontPage="true">HTT Consulting</organization>
      <address>
        <postal>
          <street/>
          <city>Oak Park</city>
          <region>MI</region>
          <code>48237</code>
          <country>United States of America</country>
        </postal>
        <email>rgm@labs.htt-consult.com</email>
      </address>
    </author>
    <author fullname="Tero Kivinen" initials="T" surname="Kivinen">
      <address>
        <email>kivinen@iki.fi</email>
      </address>
    </author>
    <author fullname="Michael C. Richardson" initials="M." surname="Richardson">
      <organization abbrev="Sandelman" showOnFrontPage="true">Sandelman Software Works</organization>
      <address>
        <email>mcr+ietf@sandelman.ca</email>
        <uri>https://www.sandelman.ca/</uri>
      </address>
    </author>
    <date month="03" year="2023"/>
    <area>sec</area>
    <keyword>IPSECKEY EdDSA</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">
	This document assigns a value for Edwards-Curve Digital Signature Algorithm (EdDSA) Public Keys to the "IPSECKEY Resource Record Parameters" registry.
</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/rfc9373" 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) 2023 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-ipseckey-support-for-eddsa">IPSECKEY Support for EdDSA</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</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-update-to-the-iana-ipseckey">Update to the IANA IPSECKEY Registry</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2.1.2">
                  <li pn="section-toc.1-1.3.2.1.2.1">
                    <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.2.1.2.1.1"><xref derivedContent="3.1.1" format="counter" sectionFormat="of" target="section-3.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-reformat-the-algorithm-type">Reformat the Algorithm Type Field Registry</xref></t>
                  </li>
                  <li pn="section-toc.1-1.3.2.1.2.2">
                    <t indent="0" pn="section-toc.1-1.3.2.1.2.2.1"><xref derivedContent="3.1.2" format="counter" sectionFormat="of" target="section-3.1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-add-to-the-algorithm-type-f">Add to the Algorithm Type Field Registry</xref></t>
                  </li>
                </ul>
              </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-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="Appendix A" format="default" sectionFormat="of" target="section-appendix.a"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-ipseckey-eddsa-example">IPSECKEY EdDSA Example</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-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1"> 
	IPSECKEY <xref target="RFC4025" format="default" sectionFormat="of" derivedContent="RFC4025"/> is a resource record (RR) for the Domain Name 
	System (DNS) that is used to store public keys for use in IP 
	security (IPsec) systems. The IPSECKEY RR relies on the IPSECKEY 
	"Algorithm Type Field" registry <xref target="IANA-IPSECKEY" format="default" sectionFormat="of" derivedContent="IANA-IPSECKEY"/> to enumerate the permissible formats for the 
	public keys.
</t>
      <t indent="0" pn="section-1-2">
	This document adds support for Edwards-Curve Digital Security 
	Algorithm (EdDSA) public keys in the format defined in <xref target="RFC8080" format="default" sectionFormat="of" derivedContent="RFC8080"/> to the IPSECKEY RR.
</t>
    </section>
    <section anchor="IPSECKEY" numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-ipseckey-support-for-eddsa">IPSECKEY Support for EdDSA</name>
      <t indent="0" pn="section-2-1">
	When using the EdDSA public key in the IPSECKEY RR, the value 
	4 is used as an algorithm and the public key is formatted as 
	specified in "Edwards-Curve Digital Security 
	Algorithm (EdDSA) for DNSSEC" (<xref target="RFC8080" sectionFormat="of" section="3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8080#section-3" derivedContent="RFC8080"/>).
</t>
      <table anchor="table1" align="center" pn="table-1">
        <name/>
        <thead>
          <tr>
            <th align="left" colspan="1" rowspan="1">Value</th>
            <th align="left" colspan="1" rowspan="1">Description</th>
            <th align="left" colspan="1" rowspan="1">Format Description</th>
            <th align="left" colspan="1" rowspan="1">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left" colspan="1" rowspan="1">4</td>
            <td align="left" colspan="1" rowspan="1">An EdDSA Public Key</td>
            <td align="left" colspan="1" rowspan="1">
              <xref target="RFC8080" sectionFormat="comma" section="3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8080#section-3" derivedContent="RFC8080"/></td>
            <td align="left" colspan="1" rowspan="1">This RFC</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section anchor="IANA" numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <section anchor="IANA_IPSECKEY_reg" numbered="true" toc="include" removeInRFC="false" pn="section-3.1">
        <name slugifiedName="name-update-to-the-iana-ipseckey">Update to the IANA IPSECKEY Registry</name>
        <section anchor="IANA_IPSECKEY_Alg_format" numbered="true" toc="include" removeInRFC="false" pn="section-3.1.1">
          <name slugifiedName="name-reformat-the-algorithm-type">Reformat the Algorithm Type Field Registry</name>
          <t indent="0" pn="section-3.1.1-1">
	Per this document, IANA has added the "Format 
	Description" field to the "Algorithm Type Field" registry of the 
	"IPSECKEY Resource Record Parameters" <xref target="IANA-IPSECKEY" format="default" sectionFormat="of" derivedContent="IANA-IPSECKEY"/>. In addition, IANA has updated the 
	"Description" field in existing entries of that registry to 
	explicitly state that they are for "Public" keys:
</t>
          <table anchor="table2" align="center" pn="table-2">
            <name/>
            <thead>
              <tr>
                <th align="left" colspan="1" rowspan="1">Value</th>
                <th align="left" colspan="1" rowspan="1">Description</th>
                <th align="left" colspan="1" rowspan="1">Format Description</th>
                <th align="left" colspan="1" rowspan="1">Reference</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left" colspan="1" rowspan="1">0</td>
                <td align="left" colspan="1" rowspan="1">No Public key is present</td>
                <td align="left" colspan="1" rowspan="1"/>
                <td align="left" colspan="1" rowspan="1">
                  <xref target="RFC4025" format="default" sectionFormat="of" derivedContent="RFC4025"/></td>
              </tr>
              <tr>
                <td align="left" colspan="1" rowspan="1">1</td>
                <td align="left" colspan="1" rowspan="1">A DSA Public Key</td>
                <td align="left" colspan="1" rowspan="1">
                  <xref target="RFC2536" sectionFormat="comma" section="2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc2536#section-2" derivedContent="RFC2536"/></td>
                <td align="left" colspan="1" rowspan="1">
                  <xref target="RFC4025" format="default" sectionFormat="of" derivedContent="RFC4025"/></td>
              </tr>
              <tr>
                <td align="left" colspan="1" rowspan="1">2</td>
                <td align="left" colspan="1" rowspan="1">An RSA Public Key</td>
                <td align="left" colspan="1" rowspan="1">
                  <xref target="RFC3110" sectionFormat="comma" section="2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3110#section-2" derivedContent="RFC3110"/></td>
                <td align="left" colspan="1" rowspan="1">
                  <xref target="RFC4025" format="default" sectionFormat="of" derivedContent="RFC4025"/></td>
              </tr>
              <tr>
                <td align="left" colspan="1" rowspan="1">3</td>
                <td align="left" colspan="1" rowspan="1">An ECDSA Public Key</td>
                <td align="left" colspan="1" rowspan="1">
                  <xref target="RFC6605" sectionFormat="comma" section="4" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6605#section-4" derivedContent="RFC6605"/></td>
                <td align="left" colspan="1" rowspan="1">
                  <xref target="RFC8005" format="default" sectionFormat="of" derivedContent="RFC8005"/></td>
              </tr>
            </tbody>
          </table>
          <t indent="0" pn="section-3.1.1-3">
	IANA added a reference to this document to the "Algorithm Type Field" registry. 
</t>
        </section>
        <section anchor="IANA_IPSECKEY_Alg_add" numbered="true" toc="include" removeInRFC="false" pn="section-3.1.2">
          <name slugifiedName="name-add-to-the-algorithm-type-f">Add to the Algorithm Type Field Registry</name>
          <t indent="0" pn="section-3.1.2-1">
	Further, IANA has made the following addition 
	to the "Algorithm Type Field" registry within the "IPSECKEY Resource Record Parameters" <xref target="IANA-IPSECKEY" format="default" sectionFormat="of" derivedContent="IANA-IPSECKEY"/>:
</t>
          <table anchor="table3" align="center" pn="table-3">
            <name/>
            <thead>
              <tr>
                <th align="left" colspan="1" rowspan="1">Value</th>
                <th align="left" colspan="1" rowspan="1">Description</th>
                <th align="left" colspan="1" rowspan="1">Format Description</th>
                <th align="left" colspan="1" rowspan="1">Reference</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left" colspan="1" rowspan="1">4</td>
                <td align="left" colspan="1" rowspan="1">An EdDSA Public Key</td>
                <td align="left" colspan="1" rowspan="1">
                  <xref target="RFC8080" sectionFormat="comma" section="3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8080#section-3" derivedContent="RFC8080"/></td>
                <td align="left" colspan="1" rowspan="1">This RFC</td>
              </tr>
            </tbody>
          </table>
        </section>
      </section>
    </section>
    <section anchor="security-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-4-1">
   The security considerations discussed in <xref target="RFC4025" format="default" sectionFormat="of" derivedContent="RFC4025"/> apply.  This document 
   does not introduce any new security considerations. 
</t>
    </section>
  </middle>
  <back>
    <references pn="section-5">
      <name slugifiedName="name-references">References</name>
      <references pn="section-5.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="IANA-IPSECKEY" target="https://www.iana.org/assignments/ipseckey-rr-parameters" quoteTitle="true" derivedAnchor="IANA-IPSECKEY">
          <front>
            <title>IPSECKEY Resource Record Parameters</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="RFC8080" target="https://www.rfc-editor.org/info/rfc8080" quoteTitle="true" derivedAnchor="RFC8080">
          <front>
            <title>Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSEC</title>
            <author fullname="O. Sury" initials="O." surname="Sury"/>
            <author fullname="R. Edmonds" initials="R." surname="Edmonds"/>
            <date month="February" year="2017"/>
            <abstract>
              <t indent="0">This document describes how to specify Edwards-curve Digital Security Algorithm (EdDSA) keys and signatures in DNS Security (DNSSEC).  It uses EdDSA with the choice of two curves: Ed25519 and Ed448.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8080"/>
          <seriesInfo name="DOI" value="10.17487/RFC8080"/>
        </reference>
      </references>
      <references pn="section-5.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="RFC2536" target="https://www.rfc-editor.org/info/rfc2536" quoteTitle="true" derivedAnchor="RFC2536">
          <front>
            <title>DSA KEYs and SIGs in the Domain Name System (DNS)</title>
            <author fullname="D. Eastlake 3rd" initials="D." surname="Eastlake 3rd"/>
            <date month="March" year="1999"/>
            <abstract>
              <t indent="0">A standard method for storing US Government Digital Signature Algorithm keys and signatures in the Domain Name System is described which utilizes DNS KEY and SIG resource records. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2536"/>
          <seriesInfo name="DOI" value="10.17487/RFC2536"/>
        </reference>
        <reference anchor="RFC3110" target="https://www.rfc-editor.org/info/rfc3110" quoteTitle="true" derivedAnchor="RFC3110">
          <front>
            <title>RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</title>
            <author fullname="D. Eastlake 3rd" initials="D." surname="Eastlake 3rd"/>
            <date month="May" year="2001"/>
            <abstract>
              <t indent="0">This document describes how to produce RSA/SHA1 SIG resource records (RRs) in Section 3 and, so as to completely replace RFC 2537, describes how to produce RSA KEY RRs in Section 2. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3110"/>
          <seriesInfo name="DOI" value="10.17487/RFC3110"/>
        </reference>
        <reference anchor="RFC4025" target="https://www.rfc-editor.org/info/rfc4025" quoteTitle="true" derivedAnchor="RFC4025">
          <front>
            <title>A Method for Storing IPsec Keying Material in DNS</title>
            <author fullname="M. Richardson" initials="M." surname="Richardson"/>
            <date month="March" year="2005"/>
            <abstract>
              <t indent="0">This document describes a new resource record for the Domain Name System (DNS). This record may be used to store public keys for use in IP security (IPsec) systems. The record also includes provisions for indicating what system should be contacted when an IPsec tunnel is established with the entity in question.</t>
              <t indent="0">This record replaces the functionality of the sub-type #4 of the KEY Resource Record, which has been obsoleted by RFC 3445. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4025"/>
          <seriesInfo name="DOI" value="10.17487/RFC4025"/>
        </reference>
        <reference anchor="RFC6605" target="https://www.rfc-editor.org/info/rfc6605" quoteTitle="true" derivedAnchor="RFC6605">
          <front>
            <title>Elliptic Curve Digital Signature Algorithm (DSA) for DNSSEC</title>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <author fullname="W.C.A. Wijngaards" initials="W.C.A." surname="Wijngaards"/>
            <date month="April" year="2012"/>
            <abstract>
              <t indent="0">This document describes how to specify Elliptic Curve Digital Signature Algorithm (DSA) keys and signatures in DNS Security (DNSSEC).  It lists curves of different sizes and uses the SHA-2 family of hashes for signatures. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6605"/>
          <seriesInfo name="DOI" value="10.17487/RFC6605"/>
        </reference>
        <reference anchor="RFC8005" target="https://www.rfc-editor.org/info/rfc8005" quoteTitle="true" derivedAnchor="RFC8005">
          <front>
            <title>Host Identity Protocol (HIP) Domain Name System (DNS) Extension</title>
            <author fullname="J. Laganier" initials="J." surname="Laganier"/>
            <date month="October" year="2016"/>
            <abstract>
              <t indent="0">This document specifies a resource record (RR) for the Domain Name System (DNS) and how to use it with the Host Identity Protocol (HIP).  This RR allows a HIP node to store in the DNS its Host Identity (HI), the public component of the node public-private key pair; its Host Identity Tag (HIT), a truncated hash of its public key (PK); and the domain names of its rendezvous servers (RVSs).  This document obsoletes RFC 5205.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8005"/>
          <seriesInfo name="DOI" value="10.17487/RFC8005"/>
        </reference>
      </references>
    </references>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-ipseckey-eddsa-example">IPSECKEY EdDSA Example</name>
      <t indent="0" pn="section-appendix.a-1"> 
The following is an example of an IPSECKEY RR with no gateway, and an
  EdDSA public key.  It uses the IPSECKEY presentation format which is base64.
</t>
      <artwork name="" type="" align="left" alt="" pn="section-appendix.a-2">

   foo.example.com. IN IPSECKEY (
         10 0 4 . 3WTXgUvpn1RlCXnm80gGY2LZ/ErUUEZtZ33IDi8yfhM= )

	</artwork>
      <t indent="0" pn="section-appendix.a-3"> 
	The associated EdDSA private key (in hex) is as follows:
</t>
      <artwork name="" type="" align="left" alt="" pn="section-appendix.a-4">

   c7be71a45cbf87785f639dc4fd1c82637c21b5e02488939976ece32b9268d0b7

	</artwork>
    </section>
    <section numbered="false" toc="include" removeInRFC="false" pn="section-appendix.b">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.b-1">
	Thanks to the Security Area Director, <contact fullname="Paul Wouters"/>, for his initial review. Also, thanks to Security Area Director, <contact fullname="Roman Danyliw"/>, for his final reviews and document shepherding.
</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.c">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="Robert Moskowitz" initials="R" surname="Moskowitz">
        <organization showOnFrontPage="true">HTT Consulting</organization>
        <address>
          <postal>
            <street/>
            <city>Oak Park</city>
            <region>MI</region>
            <code>48237</code>
            <country>United States of America</country>
          </postal>
          <email>rgm@labs.htt-consult.com</email>
        </address>
      </author>
      <author fullname="Tero Kivinen" initials="T" surname="Kivinen">
        <address>
          <email>kivinen@iki.fi</email>
        </address>
      </author>
      <author fullname="Michael C. Richardson" initials="M." surname="Richardson">
        <organization abbrev="Sandelman" showOnFrontPage="true">Sandelman Software Works</organization>
        <address>
          <email>mcr+ietf@sandelman.ca</email>
          <uri>https://www.sandelman.ca/</uri>
        </address>
      </author>
    </section>
  </back>
</rfc>
