altf4arnold/datatracker
1
0
Fork 0
Code Issues Pull requests Actions 3 Packages Projects Releases Wiki Activity

fix: Move the entire RFC5742-related text into the alert box (#4978)

Browse source
This commit is contained in:
Lars Eggert 2023-01-18 18:37:12 +02:00 committed by GitHub
parent d7a7033a42
commit 28ec22aad9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 43 additions and 43 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

86
ietf/templates/iesg/agenda.html
View file

@ -45,48 +45,48 @@
</p>
{% endif %}
{% if num == "3.4" %}
<p class="alert alert-info my-3">
The IESG will use RFC 5742 responses:
</p>
<ol>
<li>
The IESG has concluded
that there is no conflict between this document and IETF work;
</li>
<li>
The IESG has concluded that this work is related to IETF work done
in WG &lt;X&gt;, but this relationship does not prevent
publishing;
</li>
<li>
The IESG has concluded that publication could
potentially disrupt the IETF work done in WG &lt;X&gt; and
recommends not publishing the document at this time;
</li>
<li>
The IESG
has concluded that this document violates IETF procedures for
&lt;Y&gt; and should therefore not be published without IETF
review and IESG approval; or
</li>
<li>
The IESG has concluded that this
document extends an IETF protocol in a way that requires IETF
review and should therefore not be published without IETF review
and IESG approval.
</li>
</ol>
<p>
The document shepherd must propose one of these responses in the
conflict-review document, and the document shepherd may supply text
for an IESG Note in that document. The Area Director ballot positions
indicate consensus with the response proposed by the document shepherd
and agreement that the IESG should request inclusion of the IESG Note.
</p>
<p>
Other matters may be recorded in comments, and the comments will
be passed on to the RFC Editor as community review of the document.
</p>
<div class="alert alert-info my-3">
<p>The IESG will use RFC 5742 responses:</p>
<ol>
<li>
The IESG has concluded
that there is no conflict between this document and IETF work;
</li>
<li>
The IESG has concluded that this work is related to IETF work done
in WG &lt;X&gt;, but this relationship does not prevent
publishing;
</li>
<li>
The IESG has concluded that publication could
potentially disrupt the IETF work done in WG &lt;X&gt; and
recommends not publishing the document at this time;
</li>
<li>
The IESG
has concluded that this document violates IETF procedures for
&lt;Y&gt; and should therefore not be published without IETF
review and IESG approval; or
</li>
<li>
The IESG has concluded that this
document extends an IETF protocol in a way that requires IETF
review and should therefore not be published without IETF review
and IESG approval.
</li>
</ol>
<p>
The document shepherd must propose one of these responses in the
conflict-review document, and the document shepherd may supply text
for an IESG Note in that document. The Area Director ballot positions
indicate consensus with the response proposed by the document shepherd
and agreement that the IESG should request inclusion of the IESG Note.
</p>
<p class="mb-0">
Other matters may be recorded in comments, and the comments will
be passed on to the RFC Editor as community review of the document.
</p>
</div>
{% endif %}
{% if "docs" in section %}
{% for doc in section.docs %}
@ -111,4 +111,4 @@
{% endif %}
{% endfor %}
{% endblock %}
{% block js %}<script>// automatically generate a right-hand navigation tab for long pages</script>{% endblock %}
{% block js %}<script>// automatically generate a right-hand navigation tab for long pages</script>{% endblock %}