[dhcwg] Draft for Re-chartering

"Bernie Volz (volz)" <volz@cisco.com> Mon, 27 November 2017 02:36 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CF64A1200F1 for <dhcwg@ietfa.amsl.com>; Sun, 26 Nov 2017 18:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id sSD35jRgxW6W for <dhcwg@ietfa.amsl.com>; Sun, 26 Nov 2017 18:36:39 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E516C1201F2 for <dhcwg@ietf.org>; Sun, 26 Nov 2017 18:36:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20633; q=dns/txt; s=iport; t=1511750198; x=1512959798; h=from:to:subject:date:message-id:mime-version; bh=cojQ5ua1YogG8Q5FEG3O82r0NWs6AAkuokdAct4iLeY=; b=lGhSFE7fq7B/F/UNTIoY+npOF9auE9wH10Y9WC5eTKvQVRxVmfSenkcR l7y5WegX1sNQaD4P+N7V6HzHFqvy/X5OxiLYTdwk9RhDLlNRWvFn1B4yJ 7Gn4OxQ2GpX1n+fVKtpN4JfzwUpd88xPG2fdcIihwX1NO7AzBPjxsus3m 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D1AAD2eRta/51dJa1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJKRC5mbi6OGI8VmGqCEQoliXY/GAEBAQEBAQEBAWsdC4VNBj4?= =?us-ascii?q?gAUBAJgEEGwyJKmQQqBk6insBAQEBAQEEAQEBAQEBARwFgzqCB5F9BZkmiSACg?= =?us-ascii?q?XSFfI0Rgh+GDIssjHaJFwIRGQGBOQEfOYFQbxWCUgEBD4RUiXuBFAEBAQ?=
X-IronPort-AV: E=Sophos; i="5.44,462,1505779200"; d="scan'208,217"; a="36640519"
Received: from rcdn-core-6.cisco.com ([]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Nov 2017 02:36:29 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com []) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id vAR2aShr008621 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dhcwg@ietf.org>; Mon, 27 Nov 2017 02:36:28 GMT
Received: from xch-aln-003.cisco.com ( by XCH-RCD-003.cisco.com ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sun, 26 Nov 2017 20:36:28 -0600
Received: from xch-aln-003.cisco.com ([]) by XCH-ALN-003.cisco.com ([]) with mapi id 15.00.1320.000; Sun, 26 Nov 2017 20:36:28 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Draft for Re-chartering
Thread-Index: AdNnKHnFDJ0pfbDmQeqJKheqkwE8GA==
Date: Mon, 27 Nov 2017 02:36:27 +0000
Message-ID: <c75fcb03185b49bab003dfa5e6a8f795@XCH-ALN-003.cisco.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_c75fcb03185b49bab003dfa5e6a8f795XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/9EElOm0t3t18U1GisU6se9QaXuI>
Subject: [dhcwg] Draft for Re-chartering
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Nov 2017 02:36:41 -0000


At IETF-100 in Singapore we discussed re-chartering the WG (see https://datatracker.ietf.org/meeting/100/materials/slides-100-dhc-dhc-recharter/). There were a few minor comments regarding that proposed text and a revised text based on those comments is below.

Please comment on suggested changes/improvements.

Begin Re-charter Text -->
The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP
for automated allocation, configuration and management of IP addresses
and TCP/IP protocol stack parameters. DHCPv4 is currently a Draft
Standard and is documented in RFC 2131 and RFC 2132. DHCPv6 is currently
a Proposed Standard and is being updated and the WG plans to advance the
protocol to full standard.

The DHC WG is responsible for defining DHCP protocol extensions.
Definitions of new DHCP options that are delivered using standard
mechanisms with documented semantics are not considered a protocol
extension and thus are generally outside of scope for the DHC WG. Such
options should be defined within their respective WGs and reviewed by
DHCP experts in the Internet Area Directorate. However, if such options
require protocol extensions or new semantics, the protocol extension
work must be done in the DHC WG. Or, when no respective WG exists, the
DHC WG may take on the option definitions work with approval from the
responsible Area Director.

The DHC WG has the following main objectives:

1. Develop documents that help explain operational considerations for
the wider community if and as needed.

2. Assist other WGs and independent submissions in defining options
(that follow RFC 7227 guidelines) and to assure DHCP operational
considerations are properly documented.

3. Additional topics and any option definition work may only be added
with approval from the responsible Area Director or by re-chartering.

4. Issue an updated version of the DHCPv6 base specification, and after
an appropriate interval following publication, advance to full standard.
<-- End Re-charter Text

-          Tomek & Bernie