Re: [dhcwg] DHC WG DHCP Directorate - Updated

"Bernie Volz (volz)" <volz@cisco.com> Thu, 15 August 2013 03:49 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 0AA7C21E8113 for <dhcwg@ietfa.amsl.com>; Wed, 14 Aug 2013 20:49:20 -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 syFJRkfjOTnX for <dhcwg@ietfa.amsl.com>; Wed, 14 Aug 2013 20:49:13 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id CB60511E81CC for <dhcwg@ietf.org>; Wed, 14 Aug 2013 20:49:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=54912; q=dns/txt; s=iport; t=1376538553; x=1377748153; h=from:to:subject:date:message-id:mime-version; bh=8rT/cw2Hj3YhPplGDR7B58TX7gNJW0CBjaOYH5lklJE=; b=Zo+M0xXW5rM83/F6TN2p2pNRmxxFB6Q/XtHdT2Q1V9zBgTA1/aj4gwRD Ie+2KclDnLidYa062fr5OkH2woHfGQgugTd2eDfcbSSahE8Wh/voKacMA tkGLoxAgaAP3Pj0NIOOLcXEVChR1hk6lMXGVPDHXHfg/E/f8g9kMbACLs 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApcGAIBPDFKtJV2c/2dsb2JhbABbgkJENVC/IYEhFm0HgiQBAQEBAxoTPgIBHQEIEQQBAQsWAQY5FAkJAQQTCAELh3wMmRSgRI8DCgGBEQ0qgxx3A5QNlSmDG4FoAQgXIg
X-IronPort-AV: E=Sophos; i="4.89,882,1367971200"; d="scan'208,217"; a="247539051"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 15 Aug 2013 03:49:02 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r7F3n2X1014230 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 15 Aug 2013 03:49:02 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.180]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Wed, 14 Aug 2013 22:49:02 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHC WG DHCP Directorate - Updated
Thread-Index: Ac6ZaXpJvdqiKiX3QbO6YikAxKBMAA==
Date: Thu, 15 Aug 2013 03:49:01 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1866D494@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.246.34]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1866D494xmbrcdx04ciscoc_"
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 14 Aug 2013 20:50:12 -0700
Subject: Re: [dhcwg] DHC WG DHCP Directorate - Updated
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: Thu, 15 Aug 2013 03:49:20 -0000

Based on the discussion at the DHC WG in Berlin (IETF-87), the DHCP Directorate was updated as below. Please comment as to whether you are happy with this version or if you have issues as I will ask Ted to do what is needed to initiate this directorate on August 26!

The changes were in the "What Does the Directorate Do?" and "How is Document Review Organized?" (4-7).

DHCP Directorate

The DHCP Directorate is an advisory group of DHCP experts selected by the Internet Area Directors.

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 to ensure that they are consistent with the DHCP specifications and other option formats, that they do not duplicate existing mechanisms, etc.  The Directorate will not be responsible for evaluating the semantic content of proposed options.

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.

The DHCP Directorate does not have a formal role in the standards approval process. It is simply providing input for the Internet ADs who are deciding how to ballot the document.

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). Comments must be provided in a transparent and timely manner.
5. The Coordinator may decide to call upon additional reviewers, such as if the expected review is overdue, or the topic under review is a complex one, at the request of the Area Director, or there is conflict or contention in the reviews.
6. The reviews are sent to the DHCP Directorate mailing list and Internet ADs. Ordinarily, copies are sent to the authors/editors, the shepherding AD(s), the relevant document shepherd(s) and working group chairs.  The archives are publicly viewable, at <TBD - insert URL here>.
7. Reviews must include the following boilerplate text:
I am an assigned DHCP directorate reviewer for <draft-foo.txt>. These comments were written primarily for the benefit of the Internet Area Directors. Document editors and shepherd(s) should treat these comments just like they would treat comments from any other IETF contributors and resolve them along with any other Last Call comments that have been received. For more details on the DHCP Directorate, see http://www.ietf.org/iesg/directorate.html.

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.


-      Tomek & Bernie

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, July 31, 2013 5:25 AM
To: dhcwg@ietf.org
Subject: [dhcwg] DHC WG DHCP Directorate - Thu 9:00-11:30

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