Skip to content

Commit

Permalink
Script updating gh-pages from a26d87b. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Jul 24, 2024
1 parent e9226b7 commit e5e86ec
Show file tree
Hide file tree
Showing 2 changed files with 161 additions and 148 deletions.
27 changes: 20 additions & 7 deletions draft-ietf-core-href.html
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,9 @@
This simplifies parsing, comparison, and reference resolution in
environments with severe limitations on processing power, code size, and
memory size.
This RFC updates RFC 7595 to add a note on how the URI Schemes
registry RFC 7595 describes cooperates with the CRI Scheme Numbers
registry created by the present RFC.
(This "cref" paragraph will be removed by the RFC editor:)
The present revision –16 of this draft continues -15 by picking up
more comments; it was made specifically for IETF 120.
Expand Down Expand Up @@ -1039,7 +1042,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Bormann &amp; Birkholz</td>
<td class="center">Expires 23 January 2025</td>
<td class="center">Expires 25 January 2025</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1055,12 +1058,12 @@
<a href="https://www.rfc-editor.org/rfc/rfc7595" class="eref">7595</a> (if approved)</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-07-22" class="published">22 July 2024</time>
<time datetime="2024-07-24" class="published">24 July 2024</time>
</dd>
<dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Standards Track</dd>
<dt class="label-expires">Expires:</dt>
<dd class="expires"><time datetime="2025-01-23">23 January 2025</time></dd>
<dd class="expires"><time datetime="2025-01-25">25 January 2025</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand All @@ -1084,12 +1087,15 @@ <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
This simplifies parsing, comparison, and reference resolution in
environments with severe limitations on processing power, code size, and
memory size.<a href="#section-abstract-1" class="pilcrow"></a></p>
<p id="section-abstract-2"><span class="cref" id="status">(This "cref" paragraph will be removed by the RFC editor:)<br>
<p id="section-abstract-2">This RFC updates RFC 7595 to add a note on how the URI Schemes
registry RFC 7595 describes cooperates with the CRI Scheme Numbers
registry created by the present RFC.<a href="#section-abstract-2" class="pilcrow"></a></p>
<p id="section-abstract-3"><span class="cref" id="status">(This "cref" paragraph will be removed by the RFC editor:)<br>
The present revision –16 of this draft continues -15 by picking up
more comments; it was made specifically for IETF 120.
<br>
This revision still contains open issues and is intended to serve
as a snapshot.</span><a href="#section-abstract-2" class="pilcrow"></a></p>
as a snapshot.</span><a href="#section-abstract-3" class="pilcrow"></a></p>
</section>
<section class="note rfcEditorRemove" id="section-note.1">
<h2 id="name-about-this-document">
Expand Down Expand Up @@ -1125,7 +1131,7 @@ <h2 id="name-status-of-this-memo">
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow"></a></p>
<p id="section-boilerplate.1-4">
This Internet-Draft will expire on 23 January 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 25 January 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1370,14 +1376,17 @@ <h2 id="name-introduction">
<span><a href="#STD97" class="internal xref">Hypertext Transfer Protocol (HTTP)</a> [<a href="#STD97" class="cite xref">STD97</a>]</span>,
<span><a href="#RFC8141" class="internal xref">Uniform Resource Names (URNs)</a> [<a href="#RFC8141" class="cite xref">RFC8141</a>]</span>, and other similar URIs.
The exact constraints are defined in <a href="#constraints" class="auto internal xref">Section 2</a>.<a href="#section-1-5" class="pilcrow"></a></p>
<p id="section-1-6">This RFC creates a "CRI Scheme Numbers" registry and updates RFC 7595
to add a note on how this new registry cooperates with the URI Schemes
registry that RFC 7595 describes.<a href="#section-1-6" class="pilcrow"></a></p>
<div id="notational-conventions">
<section id="section-1.1">
<h3 id="name-notational-conventions">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-notational-conventions" class="section-name selfRef">Notational Conventions</a>
</h3>
<p id="section-1.1-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
described in BCP 14 <span>[<a href="#BCP14" class="cite xref">BCP14</a>]</span> when, and only when, they
described in <span>[<a href="#BCP14" class="cite xref">BCP14</a>]</span> (<a href="#RFC2119" class="auto internal xref">RFC2119</a>) (<a href="#RFC8174" class="auto internal xref">RFC8174</a>) when, and only when, they
appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow"></a></p>
<p id="section-1.1-2">In this specification, the term "byte" is used in its now customary
sense as a synonym for "octet".<a href="#section-1.1-2" class="pilcrow"></a></p>
Expand Down Expand Up @@ -5432,6 +5441,10 @@ <h2 id="name-change-log">
<li class="normal" id="appendix-D-3.1">
<p id="appendix-D-3.1.1">Add note that CRI Scheme Number registrations are oblivious of the
actual URI Scheme registrations (if any).<a href="#appendix-D-3.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="appendix-D-3.2">
<p id="appendix-D-3.2.1">Add information about how this RFC updates RFC7595 to abstract and
introduction.<a href="#appendix-D-3.2.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="appendix-D-4">Changes from -14 to -15<a href="#appendix-D-4" class="pilcrow"></a></p>
Expand Down
Loading

0 comments on commit e5e86ec

Please sign in to comment.