<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF"
     category="info" consensus="true" ipr="trust200902"
     docName="draft-hodges-webauthn-registries-10" number="8809" obsoletes=""
     updates="" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true"
     version="3"> 

  <!-- xml2rfc v2v3 conversion 2.45.2 -->
  <front>
    <title>Registries for Web Authentication (WebAuthn)</title>
    <seriesInfo name="RFC" value="8809"/>
    <author initials="J." surname="Hodges" fullname="Jeff Hodges">
      <organization>Google</organization>
      <address>
        <postal>
          <street>1600 Amphitheatre Parkway</street>
          <city>Mountain View</city>
          <region>CA</region>
          <code>94043</code>
          <country>United States of America</country>
        </postal>
        <email>jdhodges@google.com</email>
        <uri>https://kingsmountain.com/people/Jeff.Hodges/</uri>
      </address>
    </author>
    <author fullname="Giridhar Mandyam" initials="G." surname="Mandyam">
      <organization>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>+1 858 651 7200</phone>
        <email>mandyam@qti.qualcomm.com</email>
      </address>
    </author>
    <author fullname="Michael B. Jones" initials="M." surname="Jones">
      <organization abbrev="Microsoft">Microsoft</organization>
      <address>
        <email>mbj@microsoft.com</email>
        <uri>https://self-issued.info/</uri>
      </address>
    </author>
    <date month="August" year="2020"/>
    <area>Security</area>
    <workgroup>W3C WebAuthn Working Group</workgroup>
    <keyword>webauthn</keyword>
    <keyword>attestation</keyword>
    <keyword>extensions</keyword>
    <keyword>registry</keyword>
    <abstract>
      <t>
        This specification defines IANA registries for W3C Web Authentication (WebAuthn)
        attestation statement format identifiers and extension identifiers.
      </t>
    </abstract>
  </front>
  <middle>
    <section anchor="Introduction" numbered="true" toc="default">
      <name>Introduction</name>
      <t>
        This specification establishes IANA registries for W3C Web
        Authentication <xref target="WebAuthn" format="default"/> attestation
        statement format identifiers and extension identifiers.  The initial
        values for these registries are in the IANA Considerations section of
        the <xref target="WebAuthn" format="default"/> specification.
      </t>
      <section anchor="rnc" numbered="true" toc="default">
        <name>Requirements Notation and Conventions</name>
        <t>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"/> <xref target="RFC8174" format="default"/> when, and
        only when, they appear in all capitals, as shown here.</t>
      </section>
    </section>
    <section anchor="sctn-iana-cons" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This specification establishes two registries:</t>
      <ul spacing="normal">
        <li>the "WebAuthn Attestation Statement Format Identifiers" registry
	(see <xref target="sctn-attstn-format-registry"
	format="default"/>)</li> 
        <li>the "WebAuthn Extension Identifiers" registry (see <xref
	target="sctn-extension-ident-registry" format="default"/>)</li> 
      </ul>
      <t>Any additional processes established by the expert(s) after the
      publication of this document will be recorded on the registry web page
      at the discretion of the expert(s).</t> 
      <section anchor="sctn-attstn-format-registry" numbered="true" toc="default">
        <name>WebAuthn Attestation Statement Format Identifiers Registry</name>
        <t>
          WebAuthn attestation statement format identifiers are strings whose semantic, syntactic,
          and string-matching criteria are specified in the 
          <eref target="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-attstn-fmt-ids">
          "Attestation Statement Format Identifiers"</eref> section of <xref target="WebAuthn" format="default"/>,
          along with the concepts of attestation and attestation statement formats.
        </t>
        <t>
          Registered attestation statement format identifiers are those that have been added to the
          registry by following the procedure in
          <xref target="sctn-registering-attstn-format-idents" format="default"/>.
        </t>
        <t>Each attestation statement format identifier added to this registry
	<bcp14>MUST</bcp14> be unique amongst the set of registered
	attestation statement format identifiers.</t> 
        <t>Registered attestation statement format identifiers
	<bcp14>MUST</bcp14> be a maximum of 32 octets in length and
	<bcp14>MUST</bcp14> consist only of printable ASCII <xref
	target="RFC0020" format="default"/> characters, excluding backslash
	and double quote, i.e., VCHAR as defined in <xref target="RFC5234"
	format="default"/> but without %x22 and %x5c. Attestation statement
	format identifiers are case sensitive and may not match other
	registered identifiers in a case-insensitive manner unless the
	designated experts determine that there is a compelling reason to
	allow an exception.</t> 
        <section anchor="sctn-registering-attstn-format-idents" numbered="true" toc="default">
          <name>Registering Attestation Statement Format Identifiers</name>
          <t>WebAuthn attestation statement format identifiers are registered
	  using the Specification Required policy (see <xref target="RFC8126"
	  section="4.6" sectionFormat="of"/>).</t> 
          <t>
            The "WebAuthn Attestation Statement Format Identifiers" registry is located at
            <eref target="https://www.iana.org/assignments/webauthn" brackets="angle"/>.
            Registration requests can be made by following the instructions located there or by
            sending an email to the webauthn-reg-review@ietf.org mailing list.
          </t>
	  
      
          <t> Registration requests consist of at least the following information:</t>	  
          <dl newline="true">
	        <dt>WebAuthn Attestation Statement Format Identifier:</dt>
               <dd>An identifier meeting the requirements given in
                <xref target="sctn-attstn-format-registry"
		      format="default"/>.</dd> 
        	<dt>Description:</dt>
                <dd>A relatively short description of the attestation format.</dd>
		<dt>Specification Document(s):</dt>
                <dd>Reference to the document or documents that specify the
		attestation statement format.</dd> 
		<dt>Change Controller:</dt>
                <dd>For Standards Track RFCs, list "IETF". For others, give the name of the
                responsible party. Other details (e.g., postal address, email address, home page
                URI) may also be included.</dd>
     		<dt>Notes:</dt>
            	<dd>[optional]</dd>
	      </dl>

                     
          <t>Registrations <bcp14>MUST</bcp14> reference a freely available,
	  stable specification, e.g., as described in <xref target="RFC8126"
	  section="4.6" sectionFormat="of"/>. This specification
	  <bcp14>MUST</bcp14> include security and privacy considerations
	  relevant to the attestation statement format.</t> 
          <t>
            Note that WebAuthn attestation statement format identifiers can be registered by third
            parties (including the expert(s) themselves), if the expert(s) determines that an
            unregistered attestation statement format is widely deployed and not likely to be
            registered in a timely manner otherwise.
            Such registrations still are subject to the requirements defined, including the need to
            reference a specification.
          </t>
        </section>
        <section anchor="sctn-registering-attstn-format-idents-processing"
		 numbered="true" toc="default"> 
          <name>Registration Request Processing</name>
          <t>
            As noted in <xref target="sctn-registering-attstn-format-idents" format="default"/>,
            WebAuthn attestation statement format identifiers are registered using the
            Specification Required policy.
          </t>
          <t>
            The expert(s) will clearly identify any issues that cause a registration to be refused,
	    such as an incompletely specified attestation format.
          </t>
          <t>
            When a request is approved, the expert(s) will inform IANA, and the registration will
            be processed.
            The IESG is the arbiter of any objection.
          </t>
        </section>
        <section anchor="sctn-attstn-format-registry-values" numbered="true" toc="default">
          <name>Initial Values in the WebAuthn Attestation Statement Format Identifiers Registry</name>
          <t>
            The initial values for the "WebAuthn Attestation Statement Format
	    Identifiers" registry have been
            populated with the values listed in the
            <eref target="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-att-fmt-reg">
            "WebAuthn Attestation Statement Format Identifier
	    Registrations"</eref> section
            of <xref target="WebAuthn" format="default"/>.
	    Also, the Change Controller entry for each of those registrations is:
          </t>
         <dl newline="true">
	  <dt>Change Controller:</dt>
	  <dd> W3C Web Authentication Working Group (public&nbhy;webauthn@w3.org)</dd>
	</dl>
        </section>
      </section>

      <section anchor="sctn-extension-ident-registry" numbered="true" toc="default">
        <name>WebAuthn Extension Identifiers Registry</name>
        <t>
          WebAuthn extension identifiers are strings whose semantic, syntactic,
          and string-matching criteria are specified in the 
          <eref target="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-extension-id">
          "Extension Identifiers" </eref> section of <xref target="WebAuthn" format="default"/>.
        </t>	
        <t>
          Registered extension identifiers are those that have been added to the
          registry by following the procedure in
          <xref target="sctn-registering-extension-idents" format="default"/>.
        </t>
        <t>
          Each extension identifier added to this registry <bcp14>MUST</bcp14> be unique
          amongst the set of registered extension identifiers.
        </t>
        <t>Registered extension identifiers <bcp14>MUST</bcp14> be a maximum
	of 32 octets in length and <bcp14>MUST</bcp14> consist only of
	printable ASCII characters, excluding backslash and double quote,
	i.e., VCHAR as defined in <xref target="RFC5234" format="default"/>
	but without %x22 and %x5c. Extension identifiers are case sensitive
	and may not match other registered identifiers in a case-insensitive
	manner unless the designated experts determine that there is a
	compelling reason to allow an exception.</t> 
        <section anchor="sctn-registering-extension-idents" numbered="true" toc="default">
          <name>Registering Extension Identifiers</name>
          <t>WebAuthn extension identifiers are registered using the
	  Specification Required policy (see <xref target="RFC8126"
	  section="4.6" sectionFormat="of"/>).</t> 
          <t>The "WebAuthn Extension Identifiers" registry is located at <eref
	  target="https://www.iana.org/assignments/webauthn"
	  brackets="angle"/>. Registration requests can be made by following
	  the instructions located there or by sending an email to the
	  webauthn-reg-review@ietf.org mailing list.</t> 
	 <t>Registration requests consist of at least the following information:</t>
	  <dl newline="true">
	  <dt>WebAuthn Extension Identifier:</dt>
               <dd>An identifier meeting the requirements given in
	       <xref target="sctn-extension-ident-registry"
		     format="default"/>.</dd> 
		<dt>Description:</dt>
                <dd>A relatively short description of the extension.</dd>
		<dt>Specification Document(s):</dt>
                <dd>Reference to the document or documents that specify the extension.</dd>
		<dt>Change Controller:</dt>
                 <dd>For Standards Track RFCs, list "IETF". For others, give the name of the
                responsible party. Other details (e.g., postal address, email address, home page
                URI) may also be included.</dd>
       		<dt>Notes:</dt>
         	<dd>[optional]</dd>
           </dl>
          <t>Registrations <bcp14>MUST</bcp14> reference a freely available,
	  stable specification, e.g., as described in  <xref target="RFC8126"
	  section="4.6" sectionFormat="of"/>. This specification
	  <bcp14>MUST</bcp14> include security and privacy considerations
	  relevant to the extension.</t> 
          <t>Note that WebAuthn extensions can be registered by third parties
	  (including the expert(s) themselves), if the expert(s) determines
	  that an unregistered extension is widely deployed and not likely to
	  be registered in a timely manner otherwise. Such registrations still
	  are subject to the requirements defined, including the need to
	  reference a specification.</t> 
	  
        </section>

        <section anchor="sctn-registering-extension-idents-processing" numbered="true" toc="default">
          <name>Registration Request Processing</name>
          <t>
            As noted in <xref target="sctn-registering-extension-idents" format="default"/>,
            WebAuthn extension identifiers are registered using the
            Specification Required policy.
          </t>
          <t>
            The expert(s) will clearly identify any issues that cause a registration to be refused,
	    such as an incompletely specified extension.
          </t>
          <t>
            When a request is approved, the expert(s) will inform IANA, and the registration will
            be processed.
            The IESG is the arbiter of any objection.
          </t>
        </section>
        <section anchor="sctn-extension-ident-registry-values" numbered="true" toc="default">
          <name>Initial Values in the WebAuthn Extension Identifiers Registry</name>
          <t>
	    The initial values for the "WebAuthn Extension Identifiers"
	    registry have been 
	    populated with the values listed in the
	    <eref target="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-extensions-reg">
	    "WebAuthn Extension Identifier Registrations"</eref> section
	    of <xref target="WebAuthn" format="default"/>.
	    Also, the Change Controller entry for each of those registrations is:
          </t>
          <dl newline="true">
            <dt>Change Controller:</dt>
	    <dd> W3C Web Authentication Working Group (public&nbhy;webauthn@w3.org)</dd>
	  </dl>
 
        </section>
      </section>

    </section>

    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>See <xref target="WebAuthn" format="default"/> for relevant security
      considerations.</t> 
    </section>
  </middle>
  <back>


<displayreference target="RFC0020" to="RFC20"/>


    <references>

      <name>Normative References</name>
      <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
      <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/>
      <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
      <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
      <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.0020.xml"/>

      <reference anchor="WebAuthn" target="https://www.w3.org/TR/2019/REC-webauthn-1-20190304/">
        <front>
          <title>Web Authentication: An API for accessing Public Key Credentials</title>
          <seriesInfo name="World Wide Web Consortium (W3C)" value="Recommendation"/>
          <author initials="D." surname="Balfanz" fullname="Dirk Balfanz">
            <organization>Google</organization>
            <address>
              <email>balfanz@google.com</email>
            </address>
          </author>
          <author initials="A." surname="Czeskis" fullname="Alexei Czeskis">
            <organization>Google</organization>
            <address>
              <email>aczeskis@google.com</email>
            </address>
          </author>
          <author initials="J." surname="Hodges" fullname="Jeff Hodges">
            <organization>PayPal</organization>
            <address>
              <email>jdhodges@google.com</email>
            </address>
          </author>
          <author initials="J.C." surname="Jones" fullname="J.C. Jones">
            <organization>Mozilla</organization>
            <address>
              <email>jc@mozilla.com</email>
            </address>
          </author>
          <author initials="M." surname="Jones" fullname="Michael B. Jones">
            <organization>Microsoft</organization>
            <address>
              <email>mbj@microsoft.com</email>
              <uri>http://self-issued.info/</uri>
            </address>
          </author>
          <author initials="A." surname="Kumar" fullname="Akshay Kumar">
            <organization>Microsoft</organization>
            <address>
              <email>akshayku@microsoft.com</email>
            </address>
          </author>
          <author initials="A." surname="Liao" fullname="Angelo Liao">
            <organization>Microsoft</organization>
            <address>
              <email>huliao@microsoft.com</email>
            </address>
          </author>
          <author initials="R." surname="Lindemann" fullname="Rolf Lindemann">
            <organization>Nok Nok Labs</organization>
            <address>
              <email>rolf@noknok.com</email>
            </address>
          </author>
          <author initials="E." surname="Lundberg" fullname="Emil Lundberg">
            <organization>Yubico</organization>
            <address>
              <email>emil@yubico.com</email>
            </address>
          </author>
          <date month="March" day="4" year="2019"/>
        </front>
      </reference>
    </references>
    <section anchor="Acknowledgements" numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>Thanks to <contact fullname="Mark Nottingham"/> for valuable comments
      and suggestions. Thanks to <contact fullname="Kathleen Moriarty"/> and
      <contact fullname="Benjamin Kaduk"/> for their Area Director sponsorship
      of this specification. Thanks to <contact fullname="Amanda Baber"/>,
      <contact fullname="Sarah Banks"/>, <contact fullname="Alissa Cooper"/>,
      <contact fullname="Roman Danyliw"/>, <contact fullname="Murray
      Kucherawy"/>, <contact fullname="Paul Kyzivat"/>, <contact
      fullname="Barry Leiba"/>, <contact fullname="Hilarie Orman"/>, <contact
      fullname="Magnus Westerlund"/>, and <contact fullname="Robert Wilton"/>
      for their reviews.</t> 
    </section>
  </back>
</rfc>
