datatracker/ietf/templates/liaisons/field_help.html

{% extends "base.html" %}
{# Copyright The IETF Trust 2015, All Rights Reserved #}
{% load origin %}

{% load ietf_filters %}

{% block title %}Liaison statement field help{% endblock %}

{% block content %}
  {% origin %}
  <h1>Liaison statement field help</h1>

  <p>
    The table below provides descriptions of the fields included in the
    liaison statement submission form, and suggestions for completing them,
    where appropriate.  Additional materials that may be useful in
    completing this form can be found in the following documents:
  </p>

  <ul>
    <li>
      <a href="/liaison/help/to_ietf/">
	Liaison statements to the IETF: guidelines for completing the "To:" and "Cc:" fields
      </a>
    </li>
    <li>
      <a href="/liaison/help/from_ietf/">
	Liaison statements from the IETF: guidelines for completing the "Cc:" field
      </a>
    </li>
    <li>
      <a href="/wg/">Active IETF working groups</a>
    </li>
    <li>
      <a href="/liaison/managers/">IETF liaison managers</a>
    </li>
  </ul>

  <p>
    For definitive information on generating liaison statements, please
    see
    <a href="{{ "4053"|rfcurl }}">
      RFC 4053 (BCP 103) "Procedures for Handling Liaison Statements to and from the IETF."
    </a>
  </p>

  <table class="table table-condensed table-striped">
    <thead>
      <tr>
	<th>Field</th>
	<th>Sub-field</th>
	<th>Description</th>
	<th>Comments</th>
      </tr>
    </thead>
    <tr>
      <th>From</th>
      <th>Organization</th>
      <td>The organization submitting the liaison statement.</td>
      <td>The field is filled in automatically.</td>
    </tr>
    <tr>
      <td></td>
      <th>Submitter</th>
      <td>
	The name and e-mail address of the person submitting the liaison statement.
      </td>
      <td>The field is filled in automatically.</td>
    </tr>
    <tr>
      <td></td>
      <th>Reply to</th>
      <td>
	The e-mail address(es) that will be inserted in the "To" field when a recipient hits the "reply" button on the message.
      </td>
      <td>Mandatory format: Name &lt;e-mail address&gt</td>
    </tr
    <tr>
      <th>To</th>
      <th>Organization</th>
      <td>
	The name of the organization (and sub-group, if applicable) to which the liaison statement is being sent.
      </td>
      <td>
	Drop-down menu with available choices.  If an SDO is not listed, please contact statements@ietf.org
      </td>
    </tr>
    <tr>
      <td></td>
      <th>POC(s)</th>
      <td>
	The e-mail address(es) of the recipient(s) of the liaison statement, separated by commas.
      </td>
      <td>The field is filled in automatically.</td>
    </tr>
    <tr>
      <th>Other email addresses</th>
      <th>Response contact</th>
      <td>
	The e-mail address(es) to which any response should be sent, separated by commas.
      </td>
      <td>Optional. Suggested format: Name &lt;e-mail address&gt</td>
    </tr>
    <tr>
      <td></td>
      <th>Technical contact</th>
      <td>
	The e-mail address(es) of individuals or lists that may be contacted for clarification of the liaison statement, separated by commas.
      </td>
      <td>Optional. Suggested format: Name &lt;e-mail address&gt</td>
    </tr>
    <tr>
      <td></td>
      <th>Cc</th>
      <td>
	The e-mail address(es) of the copy recipient(s) of the liaison statement, one on each line.
      </td>
      <td>Optional. Suggested format: Name &lt;e-mail address&gt</td>
    </tr>
    <tr>
      <th>Purpose</th>
      <th>Purpose</th>
      <td>
	The intent of the liaison statement.  Normally, one of four choices: (a) For action, (b) For comment, (c) For information, (d) In Response.
      </td>
      <td>
	The submitter selects one of the four choices, or selects "other" and indicates the intent.
      </td>
    </tr>
    <tr>
      <td></td>
      <th>Deadline</th>
      <td>The date by which a comment or action is required.</td>
      <td>
	Mandatory if the purpose is "For comment" or "For action." Otherwise, optional.
      </td>
    </tr>

    <tr>
      <th>Liaison statements</th>
      <th>Title</th>
      <td>The title of the liaison statement.</td>
      <td>Mandatory.</td>
    </tr>
    <tr>
      <td></td>
      <th>Submission date</th>
      <td>The date the liaison was originally submitted.</td>
      <td>Mandatory.</td>
    </tr>
    <tr>
      <td></td>
      <th>Body</th>
      <td>The text of the liaison statement.</td>
      <td>
	Mandatory if there are no attachments. Optional if the text of the liaison statement is provided in an attachment.
      </td>
    </tr>

    <tr>
      <th>Add attachment</th>
      <th>Title</th>
      <td>The title of the attachment.</td>
      <td>
	Optional if there is text in the body, mandatory if there is not.
      </td>
    </tr>
    <tr>
      <td></td>
      <th>File</th>
      <td>Browse to find the attachment.</td>
      <td>
	Optional if there is text in the body, mandatory if there is not.
      </td>
    </tr>
  </table>
{% endblock %}