RE: [dhcwg] WG last calls on several WG documents
"Bernie Volz \(volz\)" <volz@cisco.com> Tue, 26 December 2006 19:45 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GzIFH-0004p3-M2; Tue, 26 Dec 2006 14:45:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GzIFF-0004oh-Rk for dhcwg@ietf.org; Tue, 26 Dec 2006 14:45:53 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GzIFE-0004Yn-Ed for dhcwg@ietf.org; Tue, 26 Dec 2006 14:45:53 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 26 Dec 2006 14:45:53 -0500
X-IronPort-AV: i="4.12,211,1165208400"; d="scan'208"; a="110310298:sNHT71002352"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kBQJjqju028956; Tue, 26 Dec 2006 14:45:52 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kBQJjqGB011848; Tue, 26 Dec 2006 14:45:52 -0500 (EST)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Dec 2006 14:45:52 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] WG last calls on several WG documents
Date: Tue, 26 Dec 2006 14:45:50 -0500
Message-ID: <8E296595B6471A4689555D5D725EBB2102DD72FE@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] WG last calls on several WG documents
Thread-Index: Accizd8ZHcHZpo7BEduE6QARJOT6egGVZuiw
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, Stig Venaas <Stig.Venaas@uninett.no>
X-OriginalArrivalTime: 26 Dec 2006 19:45:52.0064 (UTC) FILETIME=[7324DC00:01C72926]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4773; t=1167162352; x=1168026352; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20WG=20last=20calls=20on=20several=20WG=20doc uments |Sender:=20 |To:=20=22Ralph=20Droms=20\(rdroms\)=22=20<rdroms@cisco.com>, =0A=20=20=20 =20=20=20=20=20=22Stig=20Venaas=22=20<Stig.Venaas@uninett.no>; bh=N5eC6F4NzOuc+1jh47m1iBtn5MOLu/5zB4QjRqnvqrs=; b=yabKKqX5oLj8Ry4YNRGx+A6bCR99YRY+nwkcgJdfTedSctMxBuCpNK9PtAsS5Flx1wSAOB3X iT26dzeY93sGgMJ35OkhmQVmHRIF1ZY3cSlT1qaOha2QbZDn7kAeeslG;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s ig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: dhcwg <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org
I'm a bit confused as to why we need this much support just for a WG Last Call. I thought that the WG Last Call would be where we'd need to assure the required support before advancing documents on to an IESG Last Call? RFC 2418 is a bit unclear as to exactly what can trigger a WG Last Call, but the "in most cases" clause is what I recall being used in the past? 7.4. Working Group Last-Call When a WG decides that a document is ready for publication it may be submitted to the IESG for consideration. In most cases the determination that a WG feels that a document is ready for publication is done by the WG Chair issuing a working group Last- Call. The decision to issue a working group Last-Call is at the discretion of the WG Chair working with the Area Director. A working group Last-Call serves the same purpose within a working group that an IESG Last-Call does in the broader IETF community (see [1]). As we now have two WG chairs and thus two sets of opinions, is there a need for a tie breaking decision between the two chairs that is triggering this (and based on the text this is done with the AD)? Or is there some other uncertainty that exists with regards to these drafts? And, given that if we get the support now, we'll have to get it again during the WG Last Call anyway? Also, from the San Diego meeting minutes: WG last call: draft-ietf-dhc-dhcpv6-agentopt-delegate-01 draft-volz-dhc-dhcpv6-srsn-option-00 The consensus in the room was that the documents are ready to go to WG last call; the consensus will be confirmed on the WG mailing list after draft-volz-dhc-dhcpv6-srsn-option-00 is republished as dhc WG work item draft-ietf-dhc-dhcpv6-srsn-option-00 and draft-ietf-dhc-dhcpv6-agentopt-delegate-01 is revised with some editorial changes based on draft-volz-dhc-dhcpv6-srsn-option-00. draft-ietf-dhc-dhcpv6-ero-00 The consensus in the room was that the document is ready to go to WG last call; consensus will be confirmed on the WG mailing list draft-ietf-dhc-dhcvp6-leasequery-00 The consensus in the room was that the document is ready go to WG last call; consensus will be confirmed on the WG mailing list. No one raised any objections to going to last call (either at the San Deigo meeting or on the mailing list). Or is there a new procedure in place? I didn't find any RFC 2418 bis document (except for 3934 on mailing lists)? (On the other hand, delaying has allowed for new versions of draft-ietf-dhc-dhcpv6-agentopt-delegate-02 and now draft-ietf-dhc-dhcvp6-leasequery-01. So, perhaps it is not all bad.) - Bernie -----Original Message----- From: Ralph Droms (rdroms) Sent: Monday, December 18, 2006 12:57 PM To: dhcwg Cc: Stig Venaas Subject: [dhcwg] WG last calls on several WG documents 3rd try - So far, we've only received responses as summarized below. We need additional positive support (from others than draft authors!) to move forward with these draft. - Ralph ===== We need to confirm WG consensus in support of holding WG last calls on several dhc WG documents that were discussed at the WG meeting in San Diego. The first four of these documents are: draft-ietf-dhc-dhcpv6-agentopt-delegate-01 DHCPv6 Relay Agent Assignment Notification (RAAN) Option Yes - Fred Templin Yes - David Hankins Yes - John Brzozowski Yes - Bernie Volz (author) draft-ietf-dhc-dhcpv6-srsn-option-00 DHCPv6 Server Reply Sequence Number Option Yes - Fred Templin No opinion - David Hankins Yes - John Brzozowski Yes - Bernie Volz (author) draft-ietf-dhc-dhcpv6-ero-00 DHCPv6 Relay Agent Echo Request Option No opinion - Fred Templin Yes - David Hankins Yes - John Brzozowski (author) Yes - Bernie Volz (author) draft-ietf-dhc-dhcvp6-leasequery-00 DHCPv6 Leasequery No opinion - Fred Templin Yes - David Hankins Yes - John Brzozowski (author) Yes - Bernie Volz (author) If you have any objections to a WG last call for any of these documents, please respond to the mailing list. If you are in agreement that these documents are ready for WG last call, send a positive ACK to the mailing list so we can assess support for those last calls. We will review the responses received by Mon, Nov 27 and initiate the supported WG last calls at that time. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] WG last calls on several WG documents Ralph Droms
- [dhcwg] WG last calls on several WG documents Ralph Droms
- Re: [dhcwg] WG last calls on several WG documents Said Ouissal
- Re: [dhcwg] WG last calls on several WG documents Said Ouissal
- RE: [dhcwg] WG last calls on several WG documents Templin, Fred L
- [dhcwg] WG last calls on several WG documents Ralph Droms
- Re: [dhcwg] WG last calls on several WG documents Ralph Droms
- Re: [dhcwg] WG last calls on several WG documents Ralph Droms
- RE: [dhcwg] WG last calls on several WG documents Brzozowski, John
- Re: [dhcwg] WG last calls on several WG documents Ralph Droms
- RE: [dhcwg] WG last calls on several WG documents Bernie Volz (volz)
- Re: [dhcwg] WG last calls on several WG documents David W. Hankins
- Re: [dhcwg] WG last calls on several WG documents Ted Lemon
- RE: [dhcwg] WG last calls on several WG documents Bernie Volz (volz)
- Re: [dhcwg] WG last calls on several WG documents Kim Kinnear
- Re: [dhcwg] WG last calls on several WG documents Richard Johnson
- Re: [dhcwg] WG last calls on several WG documents Said Ouissal
- RE: [dhcwg] WG last calls on several WG documents Bernie Volz (volz)
- RE: [dhcwg] WG last calls on several WG documents Woundy, Richard
- Re: [dhcwg] WG last calls on several WG documents Stig Venaas
- Re: [dhcwg] WG last calls on several WG documents Ted Lemon
- RE: [dhcwg] WG last calls on several WG documents Bernie Volz (volz)
- RE: [dhcwg] WG last calls on several WG documents Templin, Fred L
- Re: [dhcwg] WG last calls on several WG documents Ted Lemon
- RE: [dhcwg] WG last calls on several WG documents Bernie Volz (volz)
- RE: [dhcwg] WG last calls on several WG documents Bernie Volz (volz)