Skip to content

Commit

Permalink
Cite RFC 8126 instead of RFC 5226 (closes #75)
Browse files Browse the repository at this point in the history
  • Loading branch information
@reschke
reschke committed Jun 5, 2018
1 parent 12b6ae6 commit f9fc047
Show file tree
Hide file tree
Showing 3 changed files with 54 additions and 69 deletions.
39 changes: 17 additions & 22 deletions draft-ietf-httpbis-cache-latest.xml
View file
Expand Up @@ -1752,7 +1752,7 @@
</t>
<t>
Values to be added to this namespace require IETF Review (see <xref
target="RFC5226" x:fmt="," x:sec="4.1"/>).
target="RFC8126" x:fmt="," x:sec="4.8"/>).
</t>
</section>
</section>
Expand Down Expand Up @@ -2099,7 +2099,7 @@ Warning: 112 - "network down" "Sat, 25 Aug 2012 23:34:45 GMT"
</t>
<t>
Values to be added to this namespace require IETF Review (see <xref
target="RFC5226" x:fmt="," x:sec="4.1"/>).
target="RFC8126" x:fmt="," x:sec="4.8"/>).
</t>
</section>
</section>
Expand Down Expand Up @@ -2388,23 +2388,6 @@ Warning: 112 - "network down" "Sat, 25 Aug 2012 23:34:45 GMT"
<seriesInfo name="RFC" value="7234"/>
</reference>

<reference anchor='RFC5226'>
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials='T.' surname='Narten' fullname='T. Narten'>
<organization>IBM</organization>
<address><email>narten@us.ibm.com</email></address>
</author>
<author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
<organization>Google</organization>
<address><email>Harald@Alvestrand.no</email></address>
</author>
<date year='2008' month='May' />
</front>
<seriesInfo name='BCP' value='26' />
<seriesInfo name='RFC' value='5226' />
</reference>

<reference anchor='RFC5861'>
<front>
<title abbrev="HTTP stale controls">HTTP Cache-Control Extensions for Stale Content</title>
Expand Down Expand Up @@ -2443,6 +2426,18 @@ Warning: 112 - "network down" "Sat, 25 Aug 2012 23:34:45 GMT"
<seriesInfo name="RFC" value="6265"/>
</reference>

<reference anchor="RFC8126">
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials="M." surname="Cotton" fullname="M. Cotton"/>
<author initials="B." surname="Leiba" fullname="B. Leiba"/>
<author initials="T." surname="Narten" fullname="T. Narten"/>
<date year="2017" month="June" />
</front>
<seriesInfo name="BCP" value="26"/>
<seriesInfo name="RFC" value="8126"/>
</reference>

</references>

<?BEGININC build/draft-ietf-httpbis-cache-latest.abnf-appendix ?>
Expand Down Expand Up @@ -2531,9 +2526,9 @@ Warning: 112 - "network down" "Sat, 25 Aug 2012 23:34:45 GMT"
</section>

<section title="Since draft-ietf-httpbis-cache-01" anchor="changes.since.01">
<t>
None yet.
</t>
<ul>
<li>Cite RFC 8126 instead of RFC 5226 (<eref target="https://github.com/httpwg/http-core/issues/75"/>)</li>
</ul>
</section>
</section>

Expand Down
39 changes: 17 additions & 22 deletions draft-ietf-httpbis-messaging-latest.xml
View file
Expand Up @@ -1459,7 +1459,7 @@ https://www.example.org
</t>
<t>
Values to be added to this namespace require IETF Review (see
<xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
<xref target="RFC8126" x:fmt="of" x:sec="4.8"/>), and &MUST;
conform to the purpose of transfer coding defined in this specification.
</t>
<t>
Expand Down Expand Up @@ -2096,7 +2096,7 @@ Upgrade: HTTP/2.0
</t>
<t>
Registrations happen on a "First Come First Served" basis (see
<xref target="RFC5226" x:sec="4.1" x:fmt="of"/>) and are subject to the
<xref target="RFC8126" x:sec="4.4" x:fmt="of"/>) and are subject to the
following rules:
<list style="numbers">
<t>A protocol-name token, once registered, stays registered forever.</t>
Expand Down Expand Up @@ -2786,23 +2786,6 @@ Upgrade: HTTP/2.0
<seriesInfo name="RFC" value="2557"/>
</reference>

<reference anchor='RFC5226'>
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials='T.' surname='Narten' fullname='T. Narten'>
<organization>IBM</organization>
<address><email>narten@us.ibm.com</email></address>
</author>
<author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
<organization>Google</organization>
<address><email>Harald@Alvestrand.no</email></address>
</author>
<date year='2008' month='May' />
</front>
<seriesInfo name='BCP' value='26' />
<seriesInfo name='RFC' value='5226' />
</reference>

<reference anchor="RFC5322">
<front>
<title>Internet Message Format</title>
Expand Down Expand Up @@ -2860,6 +2843,18 @@ Upgrade: HTTP/2.0
<seriesInfo name="RFC" value="7231"/>
</reference>

<reference anchor="RFC8126">
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials="M." surname="Cotton" fullname="M. Cotton"/>
<author initials="B." surname="Leiba" fullname="B. Leiba"/>
<author initials="T." surname="Narten" fullname="T. Narten"/>
<date year="2017" month="June" />
</front>
<seriesInfo name="BCP" value="26"/>
<seriesInfo name="RFC" value="8126"/>
</reference>

<!--<reference anchor='BCP97'>
<front>
<title>Handling Normative References to Standards-Track Documents</title>
Expand Down Expand Up @@ -3272,9 +3267,9 @@ Upgrade: HTTP/2.0
</section>

<section title="Since draft-ietf-httpbis-messaging-01" anchor="changes.since.01">
<t>
None yet.
</t>
<ul>
<li>Cite RFC 8126 instead of RFC 5226 (<eref target="https://github.com/httpwg/http-core/issues/75"/>)</li>
</ul>
</section>

</section>
Expand Down
45 changes: 20 additions & 25 deletions draft-ietf-httpbis-semantics-latest.xml
View file
Expand Up @@ -2385,7 +2385,7 @@ Host: www.example.org
</t>
<t>
Values to be added to this namespace require IETF Review
(see <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>) and &MUST;
(see <xref target="RFC8126" x:fmt="of" x:sec="4.8"/>) and &MUST;
conform to the purpose of content coding defined in
<xref target="content.codings"/>.
</t>
Expand Down Expand Up @@ -2615,7 +2615,7 @@ Host: www.example.org
</t>
<t>
Values to be added to this namespace require IETF Review
(see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
(see <xref target="RFC8126" x:fmt="," x:sec="4.8"/>).
</t>
</section>
</section>
Expand Down Expand Up @@ -4251,7 +4251,7 @@ Proxy-Authorization: basic aGVsbG86d29ybGQ=
</t>
<t>
Values to be added to this namespace require IETF Review
(see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
(see <xref target="RFC8126" x:fmt="," x:sec="4.8"/>).
</t>
</section>

Expand Down Expand Up @@ -5758,7 +5758,7 @@ Expect: 100-continue
</t>
<t>
Values to be added to this namespace require IETF Review
(see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
(see <xref target="RFC8126" x:fmt="," x:sec="4.8"/>).
</t>
</section>

Expand Down Expand Up @@ -7578,7 +7578,7 @@ Content-Type: text/plain
</t>
<t>
Values to be added to the HTTP status code namespace require IETF Review
(see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
(see <xref target="RFC8126" x:fmt="," x:sec="4.8"/>).
</t>
</section>

Expand Down Expand Up @@ -10232,23 +10232,6 @@ Content-Encoding: gzip
<seriesInfo name="RFC" value="6648"/>
</reference>

<reference anchor='RFC5226'>
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials='T.' surname='Narten' fullname='T. Narten'>
<organization>IBM</organization>
<address><email>narten@us.ibm.com</email></address>
</author>
<author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
<organization>Google</organization>
<address><email>Harald@Alvestrand.no</email></address>
</author>
<date year='2008' month='May' />
</front>
<seriesInfo name='BCP' value='26' />
<seriesInfo name='RFC' value='5226' />
</reference>

<reference anchor="RFC5322">
<front>
<title>Internet Message Format</title>
Expand Down Expand Up @@ -10374,6 +10357,18 @@ Content-Encoding: gzip
<seriesInfo name='RFC' value='7617'/>
</reference>

<reference anchor="RFC8126">
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials="M." surname="Cotton" fullname="M. Cotton"/>
<author initials="B." surname="Leiba" fullname="B. Leiba"/>
<author initials="T." surname="Narten" fullname="T. Narten"/>
<date year="2017" month="June" />
</front>
<seriesInfo name="BCP" value="26"/>
<seriesInfo name="RFC" value="8126"/>
</reference>

<reference anchor="OWASP" target="https://www.owasp.org/">
<front>
<title abbrev="OWASP">A Guide to Building Secure Web Applications and Web Services</title>
Expand Down Expand Up @@ -10694,9 +10689,9 @@ Content-Encoding: gzip
</section>

<section title="Since draft-ietf-httpbis-semantics-01" anchor="changes.since.01">
<t>
None yet.
</t>
<ul>
<li>Cite RFC 8126 instead of RFC 5226 (<eref target="https://github.com/httpwg/http-core/issues/75"/>)</li>
</ul>
</section>
</section>

Expand Down

0 comments on commit f9fc047

Please sign in to comment.