Re: [dhcwg] Draft for Re-chartering

"Bernie Volz (volz)" <volz@cisco.com> Wed, 10 January 2018 22:43 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 266251205F0 for <dhcwg@ietfa.amsl.com>; Wed, 10 Jan 2018 14:43:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
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, T_KAM_HTML_FONT_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzGf8YRTK4cm for <dhcwg@ietfa.amsl.com>; Wed, 10 Jan 2018 14:43:44 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A0D71241FC for <dhcwg@ietf.org>; Wed, 10 Jan 2018 14:43:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22242; q=dns/txt; s=iport; t=1515624224; x=1516833824; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=w9oDPjSGEi8rH2mUNd26UqlwQYY/c4SbgRkE582om5I=; b=N4gJJm1FayvD0Vm2tNTfpe/Ft20xAgV/HOJ9jVzXWr37UJ//dyx4b0lU V7R8A6XjmgEzdkJNF7tjwAJnJugMGF6KYAVyBfhee4/wCv+0z5GNlZ0Zo PVf175yagMCC3Ecnpu2uFrD2r+BLyjiZPxH5ZaJAajyT7+eZWaJCxXfxN g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AqAQC6lVZa/4oNJK1eGQEBAQEBAQEBAQEBAQcBAQEBAYJKRzBmdCcHhACKJI5eggKJDI4kghYKhTsCGoQsPxgBAQEBAQEBAQFrKIUjAQEBAQMjCj4OEAIBCA4DBAEBKAMCAgIfERQJCAIEDgUIiUdMAxWvQIInh0INgnABAQEBAQEBAQEBAQEBAQEBAQEBAQEdhCCCFYZugmtEBIIlgmGCZQWZcok1PQKQQoR4lBeNe4h5AhEZAYE7AR85gVBvFYJnhFd4ikkBgRYBAQE
X-IronPort-AV: E=Sophos; i="5.46,342,1511827200"; d="scan'208,217"; a="55110334"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jan 2018 22:43:43 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w0AMhhFf005538 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Jan 2018 22:43:43 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 10 Jan 2018 16:43:42 -0600
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1320.000; Wed, 10 Jan 2018 16:43:42 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <mellon@fugue.com>
CC: Tomek Mrugalski <tomasz.mrugalski@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Draft for Re-chartering
Thread-Index: AdNnKHnFDJ0pfbDmQeqJKheqkwE8GAd5QraAAMW1QJAAkn7VAAAKvFjw///AfYCAAGA78P//1tmAgABi2EA=
Date: Wed, 10 Jan 2018 22:43:42 +0000
Message-ID: <d178085afc214003aaaa673571749781@XCH-ALN-003.cisco.com>
References: <c75fcb03185b49bab003dfa5e6a8f795@XCH-ALN-003.cisco.com> <0fd9d640-55d0-d7a2-eb06-a6de681b5491@gmail.com> <76942a0f18d24473a8fe54be29f4b4b8@XCH-ALN-003.cisco.com> <C804CF0C-1826-41BC-8BAA-4B57F63834B9@fugue.com> <ffa2ac46b00b4f12a89c8e14656502c8@XCH-ALN-003.cisco.com> <D463E9C1-F0B8-4F0F-B6D6-3D08CC3A3934@fugue.com> <e7925ca38e954eca9ad7ea6924b6da01@XCH-ALN-003.cisco.com> <8D440DD0-06BA-45F3-A919-E1CCC0C18206@fugue.com>
In-Reply-To: <8D440DD0-06BA-45F3-A919-E1CCC0C18206@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.67.125]
Content-Type: multipart/alternative; boundary="_000_d178085afc214003aaaa673571749781XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/wKABmQpCLyvPXUKO7aUQRYWx_DY>
Subject: Re: [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: Wed, 10 Jan 2018 22:43:47 -0000

Hi:

OK, dropped #3 (while it is standard practice, it might not always be obvious to all so I thought it was useful) and added the “or sponsored by an appropriate AD”.

So, I think we are now with the following proposed re-charter text:

The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP
for automated allocation, configuration and management of IP addresses,
IPv6 prefixes, IP protocol stack and other 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 or sponsored by an
appropriate AD 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.

The DHC WG has the following main objectives:

1. Informational documents providing operational or implementation advice
about DHCPv6, as well as documents specifying standard mechanisms for
operating, administering and managing DHCPv6 servers, clients, and relay
agents.

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. Issue an updated version of the DHCPv6 base specification, and after
an appropriate interval following publication, advance to full standard.


-          Bernie

From: Ted Lemon [mailto:mellon@fugue.com]
Sent: Wednesday, January 10, 2018 5:32 PM
To: Bernie Volz (volz) <volz@cisco.com>
Cc: Tomek Mrugalski <tomasz.mrugalski@gmail.com>; dhcwg@ietf.org
Subject: Re: [dhcwg] Draft for Re-chartering

On Jan 10, 2018, at 2:43 PM, Bernie Volz (volz) <volz@cisco.com<mailto:volz@cisco.com>> wrote:
OK, that leaves us saying nothing about this particular issue and it will still be up to Suresh (or the then current AD) to deal with new options work that wasn’t done elsewhere. But I guess that isn’t “in our charter” to resolve. Though we could work in the following minor change if we wanted to attempt to at least capture the spirit - “within their respective WGs or sponsored by an appropriate AD”.

Yup.

I think you could really just delete point 3—it's just repeating things that are standard practice.