forked from adamlaska/datatracker
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathguide_from_ietf.html
More file actions
87 lines (75 loc) · 4.23 KB
/
guide_from_ietf.html
File metadata and controls
87 lines (75 loc) · 4.23 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
{% extends "base.html" %}
{# Copyright The IETF Trust 2015, All Rights Reserved #}
{% load origin %}
{% load ietf_filters static %}
{% block pagehead %}
<link rel="stylesheet" href="{% static "jquery.tablesorter/css/theme.bootstrap.min.css" %}">
{% endblock %}
{% block title %}Liaison statements from the IETF - guidelines for completing the "Cc:" field{% endblock %}
{% block content %}
{% origin %}
<h1>Liaison statements from the IETF<br><small>Guidelines for completing the "Cc:" field</small></h1>
<p>The individuals copied on a liaison statement that is sent by the IETF to another Standards Development Organization (SDO) depend on the IETF entity that is sending the liaison statement.</p>
<p>
The following table provides guidelines for completing the "Cc:" field of liaison statements that are sent by the IETF.</p>
<p>For definitive information on generating liaison statements, please
see:</p>
<ul>
<li><a href="{{ "4052"|rfcurl }}">RFC 4052 (BCP 102), "IAB Processes for Management of IETF Liaison Relationships"</a></li>
<li><a href="{{ "4053"|rfcurl }}">RFC 4053 (BCP 103), "Procedures for Handling Liaison Statements to and from the IETF"</a></li>
</ul>
<table class="table table-condensed table-striped tablesorter">
<thead>
<tr>
<th>Submitting entity <sup><small>(1)</small></sup></th>
<th>Cc: field <sup><small>(1, 2, 3)</small></sup></th>
</tr>
</thead>
<tr>
<td>The IAB</td>
<td><a href="https://www.ietf.org/liaison/managers.html">The IETF Liaison Manager for the SDO</a> <sup><small>(4)</small></sup><br>
The IAB Chair (if not the submitter) <iab-chair@iab.org><br>
The IAB <iab@iab.org></li></td></tr>
<tr>
<td>The IESG</td>
<td><a href="https://www.ietf.org/liaison/managers.html">The IETF Liaison Manager for the SDO</a> <sup><small>(4)</small></sup><br>
The IETF Chair (if not the submitter) <chair@ietf.org><br>
The IESG <iesg@ietf.org></li></td></tr>
<tr>
<td>The IETF</td>
<td><a href="https://www.ietf.org/liaison/managers.html">The IETF Liaison Manager for the SDO</a> <sup><small>(4)</small></sup><br>
The IETF Chair (if not the submitter) <chair@ietf.org><br>
The IESG <iesg@ietf.org></li></td></tr>
<tr>
<td>An IETF Area</td>
<td><a href="https://www.ietf.org/liaison/managers.html">The IETF Liaison Manager for the SDO</a> <sup><small>(4)</small></sup><br>
<a href="/wg/">The IETF Area Director(s)</a> (if not the submitter)<br>
The IETF Chair <chair@ietf.org><br>
The IETF Area Directorate Mailing List (where applicable) <sup><small>(5)</small></sup></li></td></tr>
<tr>
<td>An IETF Working Group</td>
<td><a href="https://www.ietf.org/liaison/managers.html">The IETF Liaison Manager for the SDO</a> <sup><small>(4)</small></sup><br>
<a href="/wg/">The IETF Working Group Chair(s)</a> (if not the submitter)<br>
<a href="/wg/">The IETF Area Director(s)</a><br>
<a href="/wg/">The IETF Working Group Discussion List</a></li></td></tr>
</table>
<p>
<sup><small>(1)</small></sup> Please see Section 4., "Approval and Transmission of Liaison Statements,"
of <a href="{{ "4052"|rfcurl }}">RFC 4052</a> for information on who may submit a liaison statement on behalf of an IETF entity, and who should be copied.
</p>
<p>
<sup><small>(2)</small></sup> The IETF Secretariat, <a href="mailto:statements@ietf.org"><statements@ietf.org></a>, is automatically blind-copied on every liaison statement sent by the IETF.
</p>
<p>
<sup><small>(3)</small></sup> Any addresses included in the "Response Contact" and "Technical Contact" fields of a liaison statement will also receive copies of the liaison statement.
</p>
<p>
<sup><small>(4)</small></sup> This guideline does not apply when sending a liaison statement to an SDO where no formal liaison relationship exists between the IETF and that SDO.
</p>
<p>
<sup><small>(5)</small></sup> A list of Area Directorate mailing lists is not currently available.
</p>
{% endblock %}
{% block js %}
<script src="{% static "jquery.tablesorter/js/jquery.tablesorter.combined.min.js" %}"></script>
{% endblock %}