Re: [dhcwg] Draft for Re-chartering

Tomek Mrugalski <tomasz.mrugalski@gmail.com> Wed, 10 January 2018 16:59 UTC

Return-Path: <tomasz.mrugalski@gmail.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 4FEFA12D9FF for <dhcwg@ietfa.amsl.com>; Wed, 10 Jan 2018 08:59:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 upzITNwa-5fy for <dhcwg@ietfa.amsl.com>; Wed, 10 Jan 2018 08:59:38 -0800 (PST)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 D7AC112D969 for <dhcwg@ietf.org>; Wed, 10 Jan 2018 08:59:37 -0800 (PST)
Received: by mail-lf0-x22e.google.com with SMTP id u2so6141149lff.7 for <dhcwg@ietf.org>; Wed, 10 Jan 2018 08:59:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=JjDgkFWNh4L4np5p6/6jcSkHtg0h4PfUdvIB8GF3Eg8=; b=pNiR1vd046ZqrNHNbdculxMurBoSYMUS4LfGyAYXEHWa0SvStrgbybLV3e5hVMArJ7 bKbB9nKvEgJ5kqBNF/KYPPwBeOc+2P/78BBW4xXAUvdcTqWVEibj8sWM6OHR2n8p8gvV KtqDlnvJuJjtDELfxNItZmEO728oYbVZRlDjT7+Mgw/czgXi4WXrZmUo1Gzcet1+SbEa Y3CsgK/EjUyPwAcbBFhqMjGp9hFYRgNWzRRHJ7Oq6xeqalzbPXvNcAfs3g85hgeF2O89 g0NIpC8U/eti9tsq0BWYX/p6MQFTeXFZaJvQRbR7b1AVd6Z8qBZvBGy/Pg8r3D3SULfi lA3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=JjDgkFWNh4L4np5p6/6jcSkHtg0h4PfUdvIB8GF3Eg8=; b=Y9k84x/4XTSkBdpNwSFhxIC5N1XqRNDwGyfL7wDZgnKzqgUTCw2IS3H7GQf4FH1LzQ tan/ZXtDZ0Vjn/pOZsOKLAfxJZLr+eA3aB6tT7Yc2jAJmRGmFI7wGIWm9AoIKTI73exS LRQeH4icj9Dy1qI2dCUcrUEceAL+lwgXo/xJLNRyjZlYa26HGHwUxRsmJDMumdJjJbXc k4kD68X5osEfTNqVrg79Dg8hY7pBTfOhdPHNTK3xDF4Pia2EFLu9N3Mm0jT7CRDE+EiV BjMjn2x8xT/tuAM1VNGcG10wWGoKQdV7u0lXHNtnx7BbxxVn+NonqRyRS73imtJ+smjK V7cA==
X-Gm-Message-State: AKGB3mJyM2rrBzQyCfB7FRVgVXRX4WNu/9mumJQ3QR5phdUhrrFz1kGk eksPg/9KoXtfFRjRV6a//V5FPsF0
X-Google-Smtp-Source: ACJfBot+ZDorl/c7tjNzLm+j5b/EgUGhFkNysgYX9CfzADEPXTkFfrMmatAVrb2O5vNrsGGu/S80GA==
X-Received: by 10.46.60.23 with SMTP id j23mr11318724lja.107.1515603575721; Wed, 10 Jan 2018 08:59:35 -0800 (PST)
Received: from [192.168.1.100] (109241079151.gdansk.vectranet.pl. [109.241.79.151]) by smtp.googlemail.com with ESMTPSA id h97sm3454299lji.77.2018.01.10.08.59.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jan 2018 08:59:34 -0800 (PST)
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <c75fcb03185b49bab003dfa5e6a8f795@XCH-ALN-003.cisco.com> <0fd9d640-55d0-d7a2-eb06-a6de681b5491@gmail.com> <76942a0f18d24473a8fe54be29f4b4b8@XCH-ALN-003.cisco.com>
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Message-ID: <4ddc320c-4b7c-dee3-88e9-aa958147b2bb@gmail.com>
Date: Wed, 10 Jan 2018 17:59:30 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <76942a0f18d24473a8fe54be29f4b4b8@XCH-ALN-003.cisco.com>
Content-Type: multipart/alternative; boundary="------------180929DD244876092973EBC0"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/VS9x_klJj3hub2tY6JvoI2g0fRc>
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 16:59:40 -0000

W dniu 08.01.2018 o 03:04, Bernie Volz (volz) pisze:
>
> So, how about we go with:
>
>  
>
> 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 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 are related to operational considerations of
>
> DHCP 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.
>
The text looks great to me.

>  This includes all of Tomek’s proposed changes EXCEPT for adding
> anything to (2) for “external organizations”.
>
That's fine. I was not really keen of adding it, just asked whether
people thought this would be needed.

Tomek