5598762608
* Update vnu.jar * Fix py2 -> py3 issue * Run pyupgrade * test: Add default-jdk to images * test: Add option to also validate HTML with vnu.jar Since it's already installed in bin. Don't do this by default, since it increases the time needed for tests by ~50%. * fix: Stop the urlizer from urlizing in linkified mailto: text * More HTML fixes * More HTML validation fixes * And more HTML fixes * Fix floating badge * Ignore unicode errors * Only URLize docs that are existing * Final fixes * Don't URLize everything during test-crawl * Feed HTML into vnu using python rather than Java to speed things up * Allow test-crawl to start vnu on a different port * Increase retry count to vnu. Restore batch size to 30. * More HTML validation fixes * Use urllib3 to make requests to vnu, since overriding requests_mock is tricky * Undo commit of unmodified file * Also urlize ftp links * Fix matching of file name * More HTML fixes * Add `is_valid_url` filter * weekday -> data-weekday * urlencode URLs * Add and use vnu_fmt_message. Bump vnu max buffer. * Simplify doc_exists * Don't add tab link to mail archive if the URL is invalid * Run urlize_ietf_docs before linkify Reduces the possibility of generating incorrect HTML * Undo superfluous change * Runner fixes * Consolidate vnu message filtering into vnu_filter_message * Correctly handle multiple persons with same name * Minimze diff * Fix HTML nits * Print source snippet in vnu_fmt_message * Only escape if there is something to escape * Fix snippet * Skip crufty old IPR declarations * Only include modal when needed. Add handles. * Fix wordwrap+linkification * Update ietf/doc/templatetags/ietf_filters.py * Update ietf/doc/templatetags/tests_ietf_filters.py * Don't right-align second column
57 lines
3 KiB
HTML
57 lines
3 KiB
HTML
{% extends "base.html" %}
|
||
{# Copyright The IETF Trust 2015, All Rights Reserved #}
|
||
{% load origin textfilters ietf_filters%}
|
||
{% block title %}Active areas{% endblock %}
|
||
{% block content %}
|
||
{% origin %}
|
||
<h1>Areas</h1>
|
||
<p>
|
||
The IETF divides its work into a number of areas, each comprised of working groups that relate to that area's focus. The area structure is defined by the IESG, and the IESG can add areas, redefine areas, merge areas, change the number of ADs assigned to an area, or close down areas.
|
||
</p>
|
||
<p>
|
||
Changes to the area structure affect the IETF in many ways; decisions to change the area structure are taken in consultation with the community.
|
||
</p>
|
||
<p>
|
||
When changing the area structure, the IESG can decide which members are responsible for new and changed areas, including making one sitting AD responsible for multiple areas, but the IESG can only add new members through the
|
||
<a href="https://www.ietf.org/nomcom/index.html">NomCom process</a>.
|
||
</p>
|
||
<p>
|
||
The primary task of area management is handled by one or two Area Directors per area. An AD may be advised by one or more directorates, which are created, selected, chaired and if necessary disbanded by the AD. Directorates may be specific to an area, specific to a technology, or chartered in some other fashion.
|
||
</p>
|
||
<p>
|
||
The ADs for an area are jointly responsible for making sure the WGs in the area are well coordinated, that there is coverage for the technologies needed in the area, and that the challenges most important to the Internet in that area are indeed being worked on.
|
||
</p>
|
||
<p>
|
||
For more information about the role of the IESG in areas and working groups, please see
|
||
<a href="https://www.ietf.org/rfc/rfc3710.txt">RFC 3710 ("An IESG charter")</a>,
|
||
Section 6 and
|
||
<a href="https://www.ietf.org/rfc/rfc2418.txt">RFC 2418 ("IETF Working Group Guidelines and Procedures")</a>.
|
||
</p>
|
||
<p>
|
||
A full list of active working groups, sorted by area, may be found at
|
||
<a href="{% url 'ietf.group.views.active_groups' group_type='wg' %}">
|
||
{% url 'ietf.group.views.active_groups' group_type='wg' %}
|
||
</a>.
|
||
</p>
|
||
<p>
|
||
The IESG decides which areas working groups belong to. The charter of each area is listed below:
|
||
</p>
|
||
<ul>
|
||
{% for area in areas %}
|
||
<li>
|
||
<a href="#id-{{ area.acronym|slugify }}">{{ area.acronym|upper }} – {{ area.name }}</a>
|
||
</li>
|
||
{% endfor %}
|
||
</ul>
|
||
{% for area in areas %}
|
||
<h2 class="mt-3" id="id-{{ area.acronym|slugify }}">
|
||
{{ area.name }}
|
||
<a href="{% url 'ietf.group.views.active_groups' group_type='wg' %}#{{ area.acronym }}">({{ area.acronym|upper }})</a>
|
||
</h2>
|
||
{% if area.description %}
|
||
<p>
|
||
{{ area.description|urlize_ietf_docs|linkify|safe }}
|
||
</p>
|
||
{% endif %}
|
||
{% endfor %}
|
||
{% endblock %} |