[dhcwg] DHC WG Recharter - Thu 9:00-11:30
"Bernie Volz (volz)" <volz@cisco.com> Wed, 31 July 2013 09:24 UTC
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2718A21F99DC for <dhcwg@ietfa.amsl.com>; Wed, 31 Jul 2013 02:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fGLt1pUdCodZ for <dhcwg@ietfa.amsl.com>; Wed, 31 Jul 2013 02:24:36 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 70DF021F9B53 for <dhcwg@ietf.org>; Wed, 31 Jul 2013 02:22:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13202; q=dns/txt; s=iport; t=1375262549; x=1376472149; h=from:to:subject:date:message-id:mime-version; bh=dU/Mk6sgST/+NZXhGPB7HfC21GuITs0CwkaC2i0jVcQ=; b=Y2WEYWMl05SNtaUZ++F8TMYGtRC+kW/gpUZIEvG9uiR0GNWAJFeHmv4N Y0hZXYse/odkL36TxdzBGJHfiDhUx2XcctMzl/sv6YOBr+B7ryd4axHQ/ eIASKBNaRCqZzylTC8MppqUx7KpqHmf8o7JCwwcC71FMiDOHhxuELbWuF c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAAfX+FGtJV2a/2dsb2JhbABbgkJENVC+HIEXFnSCJgEELV4BKlYmAQQbDId8mAegUI9Ng1BxA6krgxSCKg
X-IronPort-AV: E=Sophos; i="4.89,786,1367971200"; d="scan'208,217"; a="241486641"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 31 Jul 2013 09:22:19 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6V9MJbs006027 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Wed, 31 Jul 2013 09:22:19 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.99]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Wed, 31 Jul 2013 04:22:19 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHC WG Recharter - Thu 9:00-11:30
Thread-Index: Ac6NzueCYI4LOaIpSyKAgSQd1bcd6w==
Date: Wed, 31 Jul 2013 09:22:18 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E18620B61@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.252.154]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E18620B61xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] DHC WG Recharter - Thu 9:00-11:30
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 31 Jul 2013 09:24:48 -0000
At Thursday's DHC WG session, please be prepared to discuss the re-charter. The text is below.
Proposed DHC WG Charter:
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 documented in RFC 3315.
Subsequent RFCs document additional options and other enhancements to
the specifications.
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 outside of scope for DHC WG. Such options should
be defined within their respective WGs and reviewed by the DHCP
Directorate. However, if such options require protocol extensions or new
semantics, the protocol extension work must be done in the DHC WG.
The DHC WG has the following main objectives:
* Develop extensions to the DHCPv6 infrastructure as required to meet
new applications and deployments of DHCP. The topics currently
in development are:
- DHCPv6 Failover, High Availability and Load Balancing
- DNS Update strategies for delegated prefixes (draft-ietf-dhc-dns-pd)
- Extend DHCPv6 to work with multiple provisioning domains
- DHCP provisioning of IPv4 clients over IPv6 networks
- SOLMAXRT counter update
- Container option
- Access Network Identifier (draft-ietf-dhc-access-network-identifier)
- New NTP option to replace OPTION_NTP_SERVER (RFC 5908)
- Prefix coloring (draft-bhandari-dhc-class-based-prefix)
Additional topics may only be added with approval from the responsible
Area Director or by re-chartering.
* Specify guidelines for creating new DHCPv6 options.
* Develop documents that help explain operational considerations for
the wider community.
* Advance DHCPv6 (RFC 3315) along the IETF Standards Track. This will
include writing analyses, corrections, and clarifications of the DHCPv6
specifications, including RFC 3315, RFC3633, RFC3736 and other RFCs
defining additional options, which identifies and resolves ambiguities,
contradictory specifications and other obstacles to development of
interoperable implementations.
END
- [dhcwg] DHC WG Recharter - Thu 9:00-11:30 Bernie Volz (volz)