Re: [dhcwg] Draft for Re-chartering

Timothy Winters <twinters@iol.unh.edu> Thu, 11 January 2018 12:46 UTC

Return-Path: <twinters@iol.unh.edu>
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 31A1712DA6A for <dhcwg@ietfa.amsl.com>; Thu, 11 Jan 2018 04:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level:
X-Spam-Status: No, score=-2.689 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_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 5NB5bDO-4G8H for <dhcwg@ietfa.amsl.com>; Thu, 11 Jan 2018 04:46:28 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4438A126CC4 for <dhcwg@ietf.org>; Thu, 11 Jan 2018 04:46:28 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id r78so5286324wme.0 for <dhcwg@ietf.org>; Thu, 11 Jan 2018 04:46:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0QXNVh9xr8knT/5J1knGxF8WWLVTWAPjvhOOGjR6FZ8=; b=R2n4fMHkI7PKesDMJIqPHVlJ64NgCdJgLmYZJrQpTghoIQqSfvYhiFs6xd3mCHg7GC 6OKUWJ3p2Fm8cLwYjDU3SX4lCiHg6N/7JcuwZHxaTSyp14OkywjD3CJwiZh5zvdWYOZp psJnID8X+7+uwhdcdyH1S7fHis6gdso0PqLLA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0QXNVh9xr8knT/5J1knGxF8WWLVTWAPjvhOOGjR6FZ8=; b=eG1Tg3HD3YpU0gHOuOZe9pi/f8sbe7XtTdxs7CiB0OYAsANPocWXZ8BEsOKTTHDyA5 Cebq2Ji5Bc2ftxcLziZZhlBjAdv6bj7PtOXXCpsclXfU3W8cG++dyDERvXIpAMr9UP2Z 0KvqZ5nlPEVArhdxANf/HZyeEnQG9RAAoeJEWVBILDxAu9z78dDrgekpzjO//8k88UB4 Gd+e+zohrKvsD598CcHrgtN4D6t75H05C3yfxzj299AIZsoqluL4K2YhFXCcGa5RiTzD qhorJ/P5zkkulQYRv5mmAR0eMcKfKUbzwjywSbqstuGVpdCOnVMt0lyOKA9Q9CmYZiey dGYw==
X-Gm-Message-State: AKwxytcAsO6waqJ11p+Xt7IyBB9S6ZLuJMnEwsQwKOki2L2Hc0xg5zid BV6yW9TL/3bSMrpNjJKMRGESDNSeOlIwNG/ARE/Zcg==
X-Google-Smtp-Source: ACJfBou9QeHyHZv71RZsj+kWFRxe6LWVdE9fJHiw4Y3EtVuCOeVO0o4qfMRnb5xKiG+9JvPGXjBSTGo2xdC4fWCSOaY=
X-Received: by 10.28.68.4 with SMTP id r4mr1157691wma.94.1515674786725; Thu, 11 Jan 2018 04:46:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.111.77 with HTTP; Thu, 11 Jan 2018 04:46:05 -0800 (PST)
In-Reply-To: <F1CF4761-37D2-4E38-A0B1-C59A13C45136@fugue.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> <d178085afc214003aaaa673571749781@XCH-ALN-003.cisco.com> <F1CF4761-37D2-4E38-A0B1-C59A13C45136@fugue.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Thu, 11 Jan 2018 07:46:05 -0500
Message-ID: <CAOSSMjXhUQCFyxreS90FrQU4zDe_3zJxRqPrCixs7XOHFg7ADA@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="001a1148d7b44226c505627f89cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/lZCdhAmOpxUng6vyboLlVWJlZvw>
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: Thu, 11 Jan 2018 12:46:31 -0000

I also think this charter looks ready to go.

~Tim

On Wed, Jan 10, 2018 at 5:45 PM, Ted Lemon <mellon@fugue.com> wrote:

> LGTM!
>
>
> On Jan 10, 2018, at 5:43 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
>
> 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 <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> 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.
>
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>


-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR