RE: [dhcwg] Draft agenda

Ralph Droms <rdroms@cisco.com> Tue, 26 July 2005 13:44 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxPjS-0001We-Gi; Tue, 26 Jul 2005 09:44:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxPjQ-0001WZ-Is for dhcwg@megatron.ietf.org; Tue, 26 Jul 2005 09:44:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18414 for <dhcwg@ietf.org>; Tue, 26 Jul 2005 09:44:26 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DxQET-0004ae-LQ for dhcwg@ietf.org; Tue, 26 Jul 2005 10:16:34 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 26 Jul 2005 09:44:18 -0400
X-IronPort-AV: i="3.95,143,1120449600"; d="scan'208"; a="63961856:sNHT33418872"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j6QDiHVu004444; Tue, 26 Jul 2005 09:44:17 -0400 (EDT)
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 26 Jul 2005 09:44:17 -0400
Received: from 10.86.240.169 ([10.86.240.169]) by xmb-rtp-211.amer.cisco.com ([64.102.31.118]) via Exchange Front-End Server email.cisco.com ([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; Tue, 26 Jul 2005 13:44:17 +0000
Received: from localhost.localdomain by email.cisco.com; 26 Jul 2005 13:44:59 +0000
Subject: RE: [dhcwg] Draft agenda
From: Ralph Droms <rdroms@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2164F0C4@xmb-rtp-20a.amer.cisco.com>
References: <8E296595B6471A4689555D5D725EBB2164F0C4@xmb-rtp-20a.amer.cisco.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Tue, 26 Jul 2005 09:44:58 -0400
Message-Id: <1122385498.19886.121.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2)
X-OriginalArrivalTime: 26 Jul 2005 13:44:17.0341 (UTC) FILETIME=[1E1A56D0:01C591E8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org, Stig Venaas <Stig.Venaas@uninett.no>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

Bernie - I commented during this last call, as well.  And there were
comments from other reviewers during the previous last call, so I'm
comfortable with the level of review (I won't speak for Stig on this
point).  I would like to hear from Stuart as to whether the revs to the
spec address his concerns.

- Ralph

On Sat, 2005-07-23 at 21:22 -0400, Bernie Volz (volz) wrote:
> There were only two people to comment - Ted Lemon and David Hankins (and
> THANKS FOR YOUR COMMENTS!). And, as far as I determine from the current
> discussion the only issue outstanding is the second paragraph of section
> 6.3.
> 
> But, I fear that this is will not make the cut for the required level of
> feedback for a WG Last Call as past experience has shown that to be the
> case.
> 
> Much of the problem is that I think not many people care about this
> issue any longer as everyone that did at one time is using TXT records
> to store the "client identity" (so there's no need for the DHCID RR and
> actually deploying that will just make more work), conflicts are
> basically already being resolved, and the (DHCPv4) FQDN option has been
> in deployment for years. Thus, very few comment on these drafts (or has
> long since lost interest in doing so).
> 
> This is also one reason I personally would like to see 6.3 stay as it
> is. Existing deployments that are using TXT records and doing conflict
> resolution just fine should not be required to switch to the algorithm
> specified in the draft (yes, I know we don't say MUST). They should just
> be able to switch to the DHCID RR.
> 
> - Bernie
> 
> > -----Original Message-----
> > From: Ralph Droms (rdroms) 
> > Sent: Saturday, July 23, 2005 3:27 PM
> > To: Bernie Volz (volz)
> > Cc: Stig Venaas; dhcwg@ietf.org; Margaret Wasserman
> > Subject: RE: [dhcwg] Draft agenda
> > 
> > Well, I believe there was significant discussion of the draft 
> > during the
> > WG last call, indicating good review on the part of the WG.
> >  
> > But, I was away during a good part of the last call, and I haven't
> > slogged through all of the e-mail.  Are there any outstanding issues
> > from the last call that still need to be resolved?
> > 
> > I don't think I was clear in my earlier response to your request for a
> > slot in the WG agenda.  Seems to me the mailing list is the 
> > right place
> > for the discussion to continue, at this point, as I think it is more
> > likely we can come to consensus on the last call issues (if 
> > any) on the
> > mailing list rather than in a short time slot at the WG meeting.
> > 
> > - Ralph
> > 
> > On Sat, 2005-07-23 at 15:19 -0400, Bernie Volz (volz) wrote:
> > > But, perhaps a better first question is where do the WG 
> > Chairs believe
> > > we stand with respect to the just concluded last call on 
> > this document?
> > > 
> > >    This message announces a WG last call on "Resolution of DNS
> > >    Name Conflicts among DHCP Clients"
> > >    <draft-ietf-dhc-ddns-resolution-09.txt>.  The last call will
> > >    conclude at 1700 EST (USA) on 2005-07-22. 
> > > 
> > > I realize that this just ended, so that may not yet be a 
> > fair question
> > > to ask.
> > > 
> > > And, if the answer is that there wasn't sufficient 
> > feedback, I think we
> > > have a bigger issue at hand that should be added to the 
> > agenda ... What
> > > will it take for the DHC WG to get sufficient input into 
> > the Last Call
> > > process to make it work. Otherwise, we might as well 
> > dissolve the WG?
> > > 
> > > You can probably tell that I am extremely frustrated by all this and
> > > these work items (FQDN, Conflict Resolution, DHCID RR) will 
> > soon need a
> > > new person willing to sheppard them through the process.
> > > 
> > > - Bernie
> > > 
> > > > -----Original Message-----
> > > > From: Bernie Volz (volz) 
> > > > Sent: Saturday, July 23, 2005 3:10 PM
> > > > To: Ralph Droms (rdroms)
> > > > Cc: Stig Venaas; dhcwg@ietf.org
> > > > Subject: RE: [dhcwg] Draft agenda
> > > > 
> > > > Well, that's too bad as this work has been dragging on for a 
> > > > long time and it would really be nice to put it to bed.
> > > > 
> > > > I'd much rather spend time on this than the 10 minutes for 
> > > > RFC 3942 as there really isn't much more to report than what 
> > > > I've requested IANA to post on the 
> > > > http://www.iana.org/assignments/bootp-dhcp-parameters page.
> > > > 
> > > > - Bernie 
> > > > 
> > > > > -----Original Message-----
> > > > > From: Ralph Droms (rdroms) 
> > > > > Sent: Saturday, July 23, 2005 3:06 PM
> > > > > To: Bernie Volz (volz)
> > > > > Cc: Stig Venaas; dhcwg@ietf.org
> > > > > Subject: RE: [dhcwg] Draft agenda
> > > > > 
> > > > > At this point, I don't think we have time in the WG meeting 
> > > > agenda to
> > > > > get in a good discussion of the draft.
> > > > > 
> > > > > Might be a good topic for a bar BOF for interested WG members...
> > > > > 
> > > > > - Ralph
> > > > > 
> > > > > On Sun, 2005-07-17 at 09:50 -0400, Bernie Volz (volz) wrote:
> > > > > > Do we want to discuss the Conflict Resolution draft?
> > > > > > 
> > > > > > - Bernie 
> > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: dhcwg-bounces@ietf.org 
> > [mailto:dhcwg-bounces@ietf.org] 
> > > > > > > On Behalf Of Stig Venaas
> > > > > > > Sent: Monday, July 11, 2005 3:57 AM
> > > > > > > To: dhcwg@ietf.org
> > > > > > > Cc: Ralph Droms (rdroms)
> > > > > > > Subject: [dhcwg] Draft agenda
> > > > > > > 
> > > > > > > Here is the first draft agenda for the dhc WG meeting 
> > > > at IETF-63.
> > > > > > > Please contact the chairs to request an agenda slot...
> > > > > > > 
> > > > > > > Stig
> > > > > > > 
> > > > > > >                           DHC WG agenda - IETF 63
> > > > > > >                             <date and time TBD>
> > > > > > >                    (Last revised 07/10/2005 14:16:50 ET)
> > > > > > >                    -------------------------------------
> > > > > > > 
> > > > > > > Administrivia                                      Ralph 
> > > > > > > Droms      10 minutes
> > > > > > >   Agenda bashing; blue sheets; scribe; Jabber scribe
> > > > > > >   Request for milestones for dhc WG drafts
> > > > > > > 
> > > > > > > DHCP Option for Proxy Server Configuration         M. 
> > > > > > > Alexander     10 minutes
> > > > > > >   <draft-ietf-dhc-proxyserver-opt-02.txt>
> > > > > > > 
> > > > > > > Merging of data from DHCP4 and DHCPv6              
> > > > > > > Chown/Venaas     10 minutes
> > > > > > >   <draft-venaas-dhc-dual-stack-merge>
> > > > > > > 
> > > > > > > DHCPv6 Default Address Selection Policy option     T. 
> > > > > > > Fujisaki      10 minutes
> > > > > > >   <draft-fujisaki-dhc-addr-select-opt-00.txt>
> > > > > > > 
> > > > > > > Zone Suffix Option for DHCPv6                      
> > R. Yan     
> > > > > > >       10 minutes
> > > > > > >   <draft-yan-dhc-dhcpv6-opt-dnszone-02.txt>
> > > > > > > 
> > > > > > > Status report on option code registration          
> > B. Volz    
> > > > > > >       10 minutes
> > > > > > > 
> > > > > > > Route Injection for DHCPv6 Prefix Delegation       
> > TBD        
> > > > > > >       10 minutes
> > > > > > > 
> > > > > > > DHCPv6<->DNA interaction                           
> > TBD        
> > > > > > >       10 minutes
> > > > > > >                                                     
> >           
> > > > > > >      -----------
> > > > > > >                                                     
> >           
> > > > > > >       80 minutes
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > 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