From 818f0a99380e88849b51b6161a67dcc7648cf95a Mon Sep 17 00:00:00 2001
From: Lars Eggert <lars@eggert.org>
Date: Thu, 8 Jun 2023 23:14:14 +0300
Subject: [PATCH] fix: Add definition of DOWNREF from RFC3967 (#5789)
Fixes #2788, #5759
---
ietf/templates/doc/downref.html | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/ietf/templates/doc/downref.html b/ietf/templates/doc/downref.html
index b82b5027c..b8598e1ed 100644
--- a/ietf/templates/doc/downref.html
+++ b/ietf/templates/doc/downref.html
@@ -14,6 +14,15 @@
<a class="btn btn-warning my-3"
href="{% url "ietf.doc.views_downref.downref_registry_add" %}">Add downref</a>
{% endif %}
+ <div class="alert alert-info">
+ <p>
+ <a href="https://www.rfc-editor.org/rfc/rfc3967.html">RFC 3967</a>,
+ titled "Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level", specifies the rules for downward references (DOWNREFs):
+ </p>
+ <p class="mb-0">
+ "IETF procedures generally require that a standards track RFC may not have a normative reference to another standards track document at a lower maturity level or to a non standards track specification (other than specifications from other standards bodies). For example, a standards track document may not have a normative reference to an informational RFC. Exceptions to this rule are sometimes needed as the IETF uses informational RFCs to describe non-IETF standards or IETF-specific modes of use of such standards."
+ </p>
+</div>
<table class="table table-sm table-striped tablesorter">
<thead>
<tr>
@@ -41,4 +50,4 @@
{% endblock %}
{% block js %}
<script src="{% static "ietf/js/list.js" %}"></script>
-{% endblock %}
+{% endblock %}
\ No newline at end of file