Skip to content

Commit

Permalink
Add info about how this RFC updates RFC7595 to abstract and intro.
Browse files Browse the repository at this point in the history
  • Loading branch information
cabo committed Jul 24, 2024
1 parent 805b8e7 commit a26d87b
Showing 1 changed file with 13 additions and 1 deletion.
14 changes: 13 additions & 1 deletion draft-ietf-core-href.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,10 @@ 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.

[^status]

[^status]: (This "cref" paragraph will be removed by the RFC editor:)\\
Expand Down Expand Up @@ -155,9 +159,14 @@ The supported subset includes all URIs of the
[Uniform Resource Names (URNs)](#RFC8141), and other similar URIs.
The exact constraints are defined in {{constraints}}.

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.


## Notational Conventions

{::boilerplate bcp14-tagged-bcp}
{::boilerplate bcp14-tagged-bcp14}

In this specification, the term "byte" is used in its now customary
sense as a synonym for "octet".
Expand Down Expand Up @@ -1565,6 +1574,9 @@ Changes from -15 to -16
* Add note that CRI Scheme Number registrations are oblivious of the
actual URI Scheme registrations (if any).

* Add information about how this RFC updates RFC7595 to abstract and
introduction.

Changes from -14 to -15

* Make scheme numbers unsigned and map them to negative numbers used
Expand Down

0 comments on commit a26d87b

Please sign in to comment.