[dhcwg] DHC WG DHCP Directorate - Thu 9:00-11:30
"Bernie Volz (volz)" <volz@cisco.com> Wed, 31 July 2013 09:25 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 0672C21F9EAC for <dhcwg@ietfa.amsl.com>; Wed, 31 Jul 2013 02:25:54 -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 nJDRFma9x0rk for <dhcwg@ietfa.amsl.com>; Wed, 31 Jul 2013 02:25:46 -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 335CA21F99D0 for <dhcwg@ietf.org>; Wed, 31 Jul 2013 02:25:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26825; q=dns/txt; s=iport; t=1375262724; x=1376472324; h=from:to:subject:date:message-id:mime-version; bh=9+sLp2tIrCmRAuenkU/5hU8Ju7eXoqQeghvFdLvhXEE=; b=SqiTL6ib5GWZ0mo4A99PSSYoxOHxO7GPkL2epzcpBGJQNl116YnH9Y2M sPEAIUHrkcVLjjlimO70mvz4O2tpsp5gH9gCiyiMcoNG/duC+CmqHICPX armfJ5FZDkeegssTNnkWisk8VLgJj6hqhXO6dFS9kARZ6+wz3+jqmXyGH A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAAfX+FGtJXG+/2dsb2JhbABbgkJENVC+HIEXFnSCJgEELT4CHgEqFkAmAQQbDId8mAegUI42CgGBDINQcQOUCJUjgxSBaAEIFyI
X-IronPort-AV: E=Sophos; i="4.89,786,1367971200"; d="scan'208,217"; a="241487598"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 31 Jul 2013 09:25:11 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6V9PAKg024805 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Wed, 31 Jul 2013 09:25:10 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.99]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Wed, 31 Jul 2013 04:25:10 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHC WG DHCP Directorate - Thu 9:00-11:30
Thread-Index: Ac6Nz7ovIHCudntcRGqylEDKksdoDw==
Date: Wed, 31 Jul 2013 09:25:09 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E18620C2C@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_489D13FBFA9B3E41812EA89F188F018E18620C2Cxmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] DHC WG DHCP Directorate - 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:26:07 -0000
At Thursday's DHC WG meeting please be prepared to discuss the DHCP Directorate. The proposed text is below: DHCP Directorate The DHCP Directorate is an advisory group of DHCP experts selected by the Internet Area Directors. The notion of a directorate is defined in RFC 2418 as follows: In many areas, the Area Directors have formed an advisory group or directorate. These comprise experienced members of the IETF and the technical community represented by the area. The specific name and the details of the role for each group differ from area to area, but the primary intent is that these groups assist the Area Director(s), e.g., with the review of specifications produced in the area. What Does the Directorate Do? The main purpose of the DHCP Directorate is to review all documents submitted to the IESG for publication that define new DHCP (DHCPv6 or DHCPv4) options, DHCP messages, or DHCP client, relay agent or server processing. Generally speaking, documents advanced by the DHC WG will have already received review from members of the DHCP Directorate and thus may not require such review. While the DHC WG is active, the DHCP Directorate is responsible for reviewing DHCP options or other extensions (for both IPv4 and IPv6). The Directorate is expected to review all proposed extensions to DHCP to ensure that they are consistent with the DHCP specification and other option formats, that they do not duplicate existing mechanisms, etc. Generally speaking, the Directorate will not be responsible for evaluating the semantic content of proposed options. The tasks performed by the Directorate are: 1. Review all documents submitted to the IESG for publication that have DHCP options, messages, or processing requirements. A review is triggered: - By request for early review (by any AD or by any WG chair) - By a document moving to 'publication requested' state - By entry on the IESG agenda (for other documents) 2. Assist ADs with judgment issues when requested - The ADs may send email to the directorate list when they have issues that they want help with. Examples for judgment issues are: - New option formats. - New client, relay, server agent processing. 3. Try to follow IETF documents related to DHCP as early as possible and provide guidance to authors as early as possible. How is Document Review Organized? 1. The DHCP Directorate Coordinator assigns each document that is triggered for review to at least two (2) reviewers and issues a Review Request. Authors and contributors to a document must not be assigned. The Review Request will include the document and review deadline. 2. The assigned reviewers must acknowledge and agree to review the document within 72 hours and respond with a "can review by deadline" or "can't review". No reply is interpreted as "can't review". 3. If the Coordinator does not receive "can review by deadline" within 72 hours, the Coordinator selects at least one or two additional reviewers. This process is repeated until at least two reviewers are found. 4. The reviewers provide comments as appropriate (IETF Last Call, Area Director, document authors). 5. The Coordinator may decide to call upon additional reviewers if expected review is overdue or the topic under review is a complex one. How is the Directorate Formed? 1. Directorate members are assigned to the Directorate by the Internet Area Directors. 2. There is an expectation that Directorate membership will not be limited to 'old-time DHCP gods from years past'. It is assumed that the Directorate will include younger and newer participants who are interested in 'learning while doing work'. 3. Each assignment is for a three year term, unless the member or Internet Area Director requests a shorter term. 4. The terms are staggered so that approximately 1/3 of the directorate members have their term end each year. 5. When the Directorate is first established members of the Directorate will be assigned either one year, two years, or three years in their first term. 6. When a member's term expires, the Internet ADs may replace the person whose term expires, may reappoint the same person, or may reduce the size of the Directorate. There is no expectation that the same person will either want to be returned, or will be returned. 7. The three year term serves as the limit of the commitment of a Directorate member, but also serves as a way to return Directorate members to the community. 8. In deciding whether to reappoint a member whose term has expired, the Internet ADs may consider the quantity of work that they have done, the ADs' impression of the quality of the work, and the comments from the authors and other Directorate members regarding the reviews. 9. If a member resigns before the member's term expires, the Internet Area Directors may appoint a replacement. 10. The Internet Area Directors may remove a member before the member's term expires, and may appoint a replacement. 11. Internet ADs can assign additional members to the Directorate whenever they want to, subject to willingness of people to serve. 12. Both ADs need to agree in order to assign a member to the Directorate. 13. Both ADs select one of the Directorate members as the DHCP Directorate Coordinator on a yearly basis. END
- [dhcwg] DHC WG DHCP Directorate - Thu 9:00-11:30 Bernie Volz (volz)