Re: [dhcwg] Process: draft-dec-dhcpv6-route-option and draft-droms-dhc-dhcpv6-default-router
Ted Lemon <Ted.Lemon@nominum.com> Wed, 20 May 2009 19:41 UTC
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B6AE28C196 for <dhcwg@core3.amsl.com>; Wed, 20 May 2009 12:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.468
X-Spam-Level:
X-Spam-Status: No, score=-6.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4GrKntJGij0R for <dhcwg@core3.amsl.com>; Wed, 20 May 2009 12:41:32 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with ESMTP id C868328C1AF for <dhcwg@ietf.org>; Wed, 20 May 2009 12:41:28 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKShRdSnR4C/VF2c5yfSUzpW05gImcINiQ@postini.com; Wed, 20 May 2009 12:43:06 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 455111B83A8 for <dhcwg@ietf.org>; Wed, 20 May 2009 12:43:19 -0700 (PDT)
Received: from uma.here (71.32.40.139) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Wed, 20 May 2009 12:43:05 -0700
Message-ID: <8DF42CB5-6080-4389-9362-C8C4FCED87B4@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhc WG <dhcwg@ietf.org>
In-Reply-To: <8E296595B6471A4689555D5D725EBB210CD32591@xmb-rtp-20a.amer.cisco.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 20 May 2009 12:43:04 -0700
References: <C43D8589-4584-4AED-9F26-75AF7E7B2F68@nominum.com> <8E296595B6471A4689555D5D725EBB210CD32591@xmb-rtp-20a.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [dhcwg] Process: draft-dec-dhcpv6-route-option and draft-droms-dhc-dhcpv6-default-router
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 May 2009 19:41:33 -0000
On May 20, 2009, at 6:34 AM, Bernie Volz (volz) wrote: > We should also ask what was the history for this work and did the 6man > WG send it on to the DHC WG? (If so, we'd be going around in circles > sending it back to them.) You make many excellent points, with which I entirely agree, so I won't comment on them, but just a reality check here - even if we are in a loop with 6man (and I have to admit I don't know if we are), I would *still* argue that the dhc working group is the wrong place to originate this document. If there is no working group that's chartered for this document, it should just be an internet area or routing area document or, as you say, a new working group should be chartered to shepherd it. The reason I say this is, first, that the dhc working group would have to recharter to take on this work, and therefore it doesn't save time for dhc to do it, and second, that this particular topic isn't even really related to the dhc working group charter, so it's a weird stretch for us to be considering it. But that's the point of having this discussion. If in fact the wg in general wants to take on this work, perhaps we should. Historically the wg has done work like this in the past - e.g., the classless static routes option and the original static routes option and default routers option in dhcpv4. But the topic was much less contentious there. So I'm asking the question in order to find out what people think - should we try to do this work, or not?
- [dhcwg] Process: draft-ietf-mip6-bootstrapping-in… Ted Lemon
- Re: [dhcwg] Process: draft-ietf-mip6-bootstrappin… Ted Lemon
- Re: [dhcwg] Process: draft-ietf-mip6-bootstrappin… Alper Yegin
- Re: [dhcwg] Process: draft-ietf-mip6-bootstrappin… Bernie Volz (volz)
- Re: [dhcwg] Process: draft-dec-dhcpv6-route-optio… Ted Lemon
- Re: [dhcwg] Process: draft-dec-dhcpv6-route-optio… Ted Lemon
- Re: [dhcwg] Process: draft-dec-dhcpv6-route-optio… MILES DAVID
- Re: [dhcwg] Process: draft-ietf-dec-route-option … Wojciech Dec (wdec)
- Re: [dhcwg] Process: draft-ietf-dec-route-option … Chuck Anderson