datatracker/ietf/templates/liaisons/guide_from_ietf.html

{% extends "base.html" %}
{# Copyright The IETF Trust 2015, All Rights Reserved #}
{% load origin %}
{% load ietf_filters static %}
{% block pagehead %}
    <link rel="stylesheet" href="{% static "ietf/css/list.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 class="text-muted">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="{% url 'ietf.doc.views_doc.document_html' name='rfc4052' %}">RFC 4052 (BCP 102), "IAB Processes for Management of IETF Liaison Relationships"</a>
        </li>
        <li>
            <a href="{% url 'ietf.doc.views_doc.document_html' name='rfc4053' %}">RFC 4053 (BCP 103), "Procedures for Handling Liaison Statements to and from the IETF"</a>
        </li>
    </ul>
    <table class="table table-sm table-striped tablesorter">
        <thead>
            <tr>
                <th scope="col" data-sort="from">
                    Submitting entity <sup><small>(1)</small></sup>
                </th>
                <th scope="col" data-sort="cc">
                    Cc: field <sup><small>(1, 2, 3)</small></sup>
                </th>
            </tr>
        </thead>
        <tbody>
        <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) &lt;iab-chair@iab.org&gt;
                <br>
                The IAB &lt;iab@iab.org&gt;

        </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) &lt;chair@ietf.org&gt;
            <br>
            The IESG &lt;iesg@ietf.org&gt;

    </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) &lt;chair@ietf.org&gt;
        <br>
        The IESG &lt;iesg@ietf.org&gt;

</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="{% url 'ietf.group.views.active_groups' group_type='wg' %}">The IETF Area Director(s)</a>
        (if not the submitter)
        <br>
        The IETF Chair &lt;chair@ietf.org&gt;
        <br>
        The IETF Area Directorate Mailing List (where applicable) <sup><small>(5)</small></sup>

</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="{% url 'ietf.group.views.active_groups' group_type='wg' %}">The IETF Working Group Chair(s)</a>
        (if not the submitter)
        <br>
        <a href="{% url 'ietf.group.views.active_groups' group_type='wg' %}">The IETF Area Director(s)</a>
        <br>
        <a href="{% url 'ietf.group.views.active_groups' group_type='wg' %}">The IETF Working Group Discussion List</a>

</td>
</tr>
</tbody>
</table>
<p>
    <sup><small>(1)</small></sup> Please see Section 4., "Approval and Transmission of Liaison Statements,"
    of
    <a href="{% url 'ietf.doc.views_doc.document_html' name='rfc4052' %}">
        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">
        &lt;statements@ietf.org&gt;
    </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 "ietf/js/list.js" %}">
    </script>
{% endblock %}