Skip to content

Commit 292451f

Browse files
committed
Updated independent submission text to point to RFC 5742 instead of 3932
- Legacy-Id: 1904
1 parent 1d8f81c commit 292451f

1 file changed

Lines changed: 19 additions & 16 deletions

File tree

ietf/templates/iesg/agenda_doc.html

Lines changed: 19 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -55,23 +55,26 @@ <h3>{{ title2 }}</h3>
5555
{% endif %}
5656
{% if title2|startswith:"3.3" %}
5757
<blockquote>
58-
The IESG will use RFC 3932 responses: 1) The IESG has not
59-
found any conflict between this document and IETF work; 2) The
60-
IESG thinks that this work is related to IETF work done in WG
61-
&lt;X&gt;, but this does not prevent publishing; 3) The IESG thinks
62-
that publication is harmful to work in WG &lt;X&gt; and recommends
63-
not publishing at this time; 4) The IESG thinks that this
64-
document violates the IETF procedures for &lt;X&gt; and should
65-
therefore not be published without IETF review and IESG
66-
approval; 5) The IESG thinks that this document extends an
67-
IETF protocol in a way that requires IETF review and should
68-
therefore not be published without IETF review and IESG approval.<br />
58+
The IESG will use RFC 5742 responses: 1) The IESG has concluded
59+
that there is no conflict between this document and IETF work; 2)
60+
The IESG has concluded that this work is related to IETF work done
61+
in WG &lt;X&gt;, but this relationship does not prevent
62+
publishing; 3) The IESG has concluded that publication could
63+
potentially disrupt the IETF work done in WG &lt;X&gt; and
64+
recommends not publishing the document at this time; 4) The IESG
65+
has concluded that this document violates IETF procedures for
66+
&lt;Y&gt; and should therefore not be published without IETF
67+
review and IESG approval; or 5) The IESG has concluded that this
68+
document extends an IETF protocol in a way that requires IETF
69+
review and should therefore not be published without IETF review
70+
and IESG approval.<br/>
6971
<br />
70-
The document shepherd must propose one of these responses in
71-
the Data Tracker note and supply complete text in the IESG
72-
Note portion of the write-up. The Area Director ballot positions
73-
indicate consensus with the response proposed by the
74-
document shepherd.<br />
72+
The document shepherd must propose one of these responses in the
73+
document write-up in the Data Tracker, and the document shepherd
74+
may supply text for an IESG Note in the write-up. The Area
75+
Director ballot positions indicate consensus with the response
76+
proposed by the document shepherd and agreement that the IESG
77+
should request inclusion of the IESG Note.<br/>
7578
<br />
7679
Other matters may be recorded in comments, and the comments will
7780
be passed on to the RFC Editor as community review of the document.

0 commit comments

Comments
 (0)