You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h2class="no-num no-toc no-ref heading settled" id="sotd"><spanclass="content">Status of this document</span></h2>
663
663
<divdata-fill-with="status">
664
-
<p><em>This section describes the status of this document at the time of its publication. A list of current <abbrtitle="World Wide Web Consortium">W3C</abbr> publications and the latest revision of this technical report can be found in the <ahref="https://www.w3.org/TR/"><abbrtitle="World Wide Web Consortium">W3C</abbr>technical reports index</a> at https://www.w3.org/TR/.</em></p>
664
+
<p><em>This section describes the status of this document at the time of its publication. A list of current <abbrtitle="World Wide Web Consortium">W3C</abbr> publications and the latest revision of this technical report can be found in the <ahref="https://www.w3.org/TR/"><abbrtitle="World Wide Web Consortium">W3C</abbr>standards and drafts index</a> at https://www.w3.org/TR/.</em></p>
665
665
<p> This document was published by the <ahref="https://www.w3.org/groups/wg/secondscreen">Second Screen Working Group</a> as an Editor’s Draft. This document is intended to become a W3C Recommendation. </p>
666
666
<p> Feedback and comments on this specification are welcome. Please use <ahref="https://github.com/w3c/openscreenprotocol/issues">Github issues</a>. </p>
667
667
<p> Publication as an Editor’s Draft does not imply endorsement by <abbrtitle="World Wide Web Consortium">W3C</abbr> and its Members. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. </p>
668
668
<p> This document was produced by a group operating under the <aclass="css" data-link-type="property" href="https://www.w3.org/policies/patent-policy/20200915/" id="sotd_patent">W3C Patent Policy</a>. <abbrtitle="World Wide Web Consortium">W3C</abbr> maintains a <ahref="https://www.w3.org/2004/01/pp-impl/74168/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <ahref="https://www.w3.org/policies/patent-policy/20200915/#def-essential">Essential
669
669
Claim(s)</a> must disclose the information in accordance with <ahref="https://www.w3.org/policies/patent-policy/20200915/#sec-Disclosure">section 6 of the <abbrtitle="World Wide Web Consortium">W3C</abbr> Patent Policy</a>. </p>
670
670
<p> This document is governed by the <ahref="https://www.w3.org/policies/process/20231103/" id="w3c_process_revision">03 November 2023 W3C Process Document</a>. </p>
display and observing or altering data intended for the controller or
831
830
receiver.</p>
832
831
<lidata-md>
833
-
<p>A listening agent should be able to discover quickly when an <adata-link-type="dfn" href="#advertising-agent" id="ref-for-advertising-agent">advertising
834
-
agent</a> becomes available or unavailable (i.e., when it connects or
832
+
<p>A listening agent should be able to discover quickly when an <adata-link-type="dfn" href="#advertising-agent" id="ref-for-advertising-agent">advertising agent</a> becomes available or unavailable (i.e., when it connects or
835
833
disconnects from the network).</p>
836
834
<lidata-md>
837
835
<p>Agents should be able to remember that a user authenticated another agent.
If the agent has never generated an agent certificate:
910
908
<ol>
911
-
<li>Let the <dfnclass="dfn-paneled" data-dfn-type="dfn" data-noexportid="certificate-serial-number-base">certificate serial number base</dfn> be a 128-bit <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc4122#section-4.4" id="ref-for-section-4.4">UUID</a>.
909
+
<li>Let the <dfnclass="dfn-paneled" data-dfn-type="dfn" data-noexportid="certificate-serial-number-base">certificate serial number base</dfn> be a 128-bit <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc4122#section-4.4" id="ref-for-section-4.4">UUID</a>.
912
910
<li>Let the <dfnclass="dfn-paneled" data-dfn-type="dfn" data-noexportid="certificate-serial-number-counter">certificate serial number counter</dfn> be a 32-bit
<li>Increment the <adata-link-type="dfn" href="#certificate-serial-number-counter" id="ref-for-certificate-serial-number-counter">certificate serial number counter</a> by one.
919
917
<li>Assign the upper 128 bits to the <adata-link-type="dfn" href="#certificate-serial-number-base" id="ref-for-certificate-serial-number-base">certificate serial number base</a>.
920
-
<li>Assign the lower 32 bits to the <adata-link-type="dfn" href="#certificate-serial-number-counter" id="ref-for-certificate-serial-number-counter①">certificate serial number counter</a>.
918
+
<li>Assign the lower 32 bits to the <adata-link-type="dfn" href="#certificate-serial-number-counter" id="ref-for-certificate-serial-number-counter①">certificate serial number counter</a>.
921
919
</ol>
922
920
</ol>
923
921
<h3class="heading settled" data-level="3.3" id="computing-agent-hostname"><spanclass="secno">3.3. </span><spanclass="content">Computing the Agent Hostname</span><aclass="self-link" href="#computing-agent-hostname"></a></h3>
<p>A type key representing the type of the message, encoded as a <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc9000#name-variable-length-integer-enc" id="ref-for-name-variable-length-integer-enc①">variable-length
1077
-
integer</a> (see <ahref="#appendix-a">Appendix A: Messages</a> for type keys)</p>
1074
+
<p>A type key representing the type of the message, encoded as a <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc9000#name-variable-length-integer-enc" id="ref-for-name-variable-length-integer-enc①">variable-length integer</a> (see <ahref="#appendix-a">Appendix A: Messages</a> for type keys)</p>
1078
1075
<lidata-md>
1079
1076
<p>The message encoded as CBOR.</p>
1080
1077
</ol>
1081
1078
<p>If an agent receives a message for which it does not recognize a type key, it
1082
1079
must close the QUIC connection with an application error code of 404 and should
1083
-
include the unknown type key in the reason phrase of the <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc9000#name-connection_close-frames" id="ref-for-name-connection_close-frames">CONNECTION_CLOSE
1084
-
frame</a>.</p>
1085
-
<p>Variable-length integers are encoded in the <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc9000#name-variable-length-integer-enc" id="ref-for-name-variable-length-integer-enc②">Variable-Length Integer Encoding</a> used by <adata-link-type="biblio" href="#biblio-rfc9000" title="QUIC: A UDP-Based Multiplexed and Secure Transport">QUIC</a>.</p>
1080
+
include the unknown type key in the reason phrase of the <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc9000#name-connection_close-frames" id="ref-for-name-connection_close-frames">CONNECTION_CLOSE frame</a>.</p>
1081
+
<p>Variable-length integers are encoded in the <adata-link-type="dfn" data-refhint-key="09174256" href="https://datatracker.ietf.org/doc/html/rfc9000#name-variable-length-integer-enc" id="ref-for-name-variable-length-integer-enc②">Variable-Length Integer Encoding</a> used by <adata-link-type="biblio" href="#biblio-rfc9000" title="QUIC: A UDP-Based Multiplexed and Secure Transport">QUIC</a>.</p>
<p>The following messages are defined using the <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc8610#section-3" id="ref-for-section-3">Concise Data Definition
1383
-
Language</a> syntax. When integer keys are used, a comment is appended to the line
1378
+
<p>The following messages are defined using the <adata-link-type="dfn" href="https://datatracker.ietf.org/doc/html/rfc8610#section-3" id="ref-for-section-3">Concise Data Definition Language</a> syntax. When integer keys are used, a comment is appended to the line
1384
1379
to indicate the name of the field. Object definitions in this specification have
1385
1380
this unusual syntax to reduce the number of bytes-on-the-wire, while maintaining
1386
1381
a human-readable name for each key. Integer keys are used instead of object
<p>The following appendix describes two encoding schemes for PSKs that take a value <code>P</code> between 20 bits and 80 bits in length and produce either a string or a <adata-link-type="dfn" href="https://www.iso.org/standard/62021.html#" id="ref-for-something①">QR
1448
-
code</a> for display to the user.</p>
1442
+
<p>The following appendix describes two encoding schemes for PSKs that take a value <code>P</code> between 20 bits and 80 bits in length and produce either a string or a <adata-link-type="dfn" href="https://www.iso.org/standard/62021.html#" id="ref-for-something①">QR code</a> for display to the user.</p>
1449
1443
<p>Agents should use these encoding schemes to maximize the interoperability of the
1450
1444
authentication step, which typically requires displaying the PSK on one
1451
1445
device and the user inputting it on another device.</p>
<dd>D. Eastlake 3rd; T. Hansen. <ahref="https://www.rfc-editor.org/rfc/rfc6234"><cite>US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)</cite></a>. May 2011. Informational. URL: <ahref="https://www.rfc-editor.org/rfc/rfc6234">https://www.rfc-editor.org/rfc/rfc6234</a>
0 commit comments