@@ -178,6 +178,35 @@ Table of Contents
178178
179179 No new registrations for IANA.
180180
181+ [RFC8175] is mentioned here in order to give the reference
182+ classification code a chance to mess up.
183+
184+
185+ 6. References
186+
187+ 6.1. Normative References
188+
189+ [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
190+ Requirement Levels", BCP 14, RFC 2119,
191+ DOI 10.17487/RFC2119, March 1997,
192+ <https://www.rfc-editor.org/info/rfc2119>.
193+
194+ [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
195+ 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
196+ May 2017, <https://www.rfc-editor.org/info/rfc8174>.
197+
198+ 6.2. Informative References
199+
200+ [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
201+ Writing an IANA Considerations Section in RFCs", BCP 26,
202+ RFC 8126, DOI 10.17487/RFC8126, June 2017,
203+ <https://www.rfc-editor.org/info/rfc8126>.
204+
205+ [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.
206+ Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175,
207+ DOI 10.17487/RFC8175, June 2017,
208+ <https://www.rfc-editor.org/info/rfc8175>.
209+
181210Author's Address
182211
183212 %(author)s
@@ -190,6 +219,10 @@ Author's Address
190219
191220
192221
222+ Appendix A. Comments
223+
224+ [RFC8174] is mentioned here just to give the reference classification
225+ code a chance to mess up.
193226
194227
195228
0 commit comments